Categories
- All Categories
- 132 Oracle Analytics News
- 24 Oracle Analytics Videos
- 14.6K Oracle Analytics Forums
- 5.6K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 51 Oracle Analytics Trainings
- 9 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 3 Oracle Analytics Industry
- Find Partners
- For Partners
OBIEE schema lock

Hello all,
We are using obiee 11g.
Now a day BI platform schema is getting locked and once we get it unlocked system works fine.
We were unable to find out why the schema is getting locked frequencly.
Can you please suggest, how can we debug/find out this.
Thanks,
Answers
-
First of all, what do you mean by schema getting locked? Do you mean that the BI Platform schema is locked? When you connect directly as the BI Platform user on the Database do you encounter any of these locking issues?
0 -
+1 to Joel - which schema? And have you already checked what your DBAs say?
0 -
Thanks Christian for your response,
It is RCU (BI_Platform)schema.
They are not telling anything, and asked me to identify the issue at our end. Since OBIEE only using it.
0 -
Thanks Joel for your response,
It is RCU (BI_Platform)schema.
When you connect directly as the BI Platform user on the Database do you encounter any of these locking issues?
Not connecting through directly database.
ans : No
It is being used in usage reports.
And there is no password change also in the schema.
0 -
you'll need to perform a number of tests to verify the root cause of your issue - that's why I suggested that you connect via SQL*Plus/ SQL Developer/ TOAD to verify that the RCU user can connect to the DB. Your DBAs will need to assist you with this as they have visibility of what might be causing the locks. They need to work with you...
0 -
Thanks for response Joel.
Let me investigate with my DBA team.
0 -
Hi 684461 -
If you want to get your hands dirty, and dig a little bit, you could enable some more granular tracing/logging on the BI Server (bi_server1) ... potentially even the Admin server (AdminServer). This is done from the application-side, via the application server and/or the FMW EM console. As has already been pointed out, there are a number of things that may be driving this. Start with the above suggestions and try to eliminate some of the possibilities.
Take a look at some of the material:
https://docs.oracle.com/cd/E29542_01/core.1111/e10105/logs.htm#ASADM215
OBIEE 11g: Tracking Down Faults in BI Systems Management (Doc ID 1494055.1)
OBIEE 11g: How To Enable Enterprise Manager FMw Control (sysman) Tracing (Doc ID 2065423.1) --> bi_server1 section
Regards,
Charles
0