uploadRpd Failed: Failure in trying to acquire lock

Getting the following error while uploading RPD in our new 12c Environment:

uploadRpd Failed: Failure in trying to acquire lock. Check bi-lcm-logs or diagnostics. Error Desc Code: DESC_CODE_SERVER_EXCEPTION




Open the em Navigate to Business Intelligence -> Configuration->Performance Tab and uncheck Disallow RPD Updates, click apply save changes.


my obiee login page is taking forever to load.

Try this to reduce the time to login to obiee home page.

Stop all BI services.

Take back up (if necessary) of most recent log and keep them on local drive

DELETE LOG FILES from each of the sub folder inside :

DELETE all the Log files in :

No Log Found OBIEE Error


when checking Manage Sessions -> View Log for a report that was run, the following message is seen:

No Log Found


This usually occurs when the Logging Level has not been set for query executions.

The easiest way to solve this is to set  System Logging Level  via the Admini Tool.

Step 1:

In online mode navigate to the Options dialog

Step 2:

Select Repository tab and enter a logging level from 1 to 5 then click OK.

Slowly Changing Dimension type III

In SCD type 3, a new column is added to the orginal data, which displays the partial historical data
Let us consider the example:

EmpNo Name Location
1001     Mark  Delhi

Consider Mark moves from Delhi to Manchester, then a new column is added to the previous data as shown below

EmpNo Name CurrentLocation     PreviousLocation
1001     Mark  Manchester            Delhi
Consider Mark moves again from Manchester to Dublin then you have

EmpNo Name CurrentLocation     PreviousLocation
1001     Mark  Dublin                    Manchester

So, SCD type 3 maintains partial history

It maintains partial history and with this size of the table doesn't increase as much as it does in SCD type 2

The organisation doesn't have complete information the employee as it cannot track the complete history of the employee i.e., from the above example when Mark moves to Dublin the organisation doesn't have any trace of his working in Delhi.

Note: SCD type 3 maintains Current data + partial history

Slowly Changing Dimension type II

In SCD type 2 a new record will be inserted in addition to the old record. In SCD type 2 historical
data is maintained so you will have both the old record and the new record
Let us consider the example below:

EmpKey Name Location
1001 Mark London

Now, Mark moves from London to Manchester. In SCD type 2 a new record is created to the old record.
So, now you have
EmpKey Name Location
1001       Mark  London
2001       Mark  Manchester

If he moves from Manchester to Dublin then you have

EmpKey Name Location
1001       Mark  London
2001       Mark  Manchester
3001       Mark  Dubin

So, historical data is maintained

As SCD type 2 contains historical data the organisation can track where Mark worked before moving to Manchester.

As it maintains historical data the size of the table increases gradually

In other words SCD type II stores Current data + Historical data

Slowly Changing Dimension type 1

Slowly Changing Dimension Type 1

In SCD Type1 the old data is overwritten by the new data. The old data is permanently deleted
Let us consider an example

EmpNo Name Location
1001     Mark London

Consider Mark moves to Manchester. In SCD type 1 the old data is completely vanishes. So the data
will be stored as

EmpNo Name Location
1001     Mark  Manchester

There are no traces of old location

SCD type 1 can be easily implemented as there is overwriting of the data and we don't store the
historical data
The disadvantage of SCD type 1 is that the organisation doesn't where Mark worked before i.e., there
is no trace that Mark worked in London.

In other words SCD type 1 stores only current data.

RICE Components

RICE stands for Reports, Interfaces, Conversions and Enhancements.

During an Oracle Apps implementation, additional configuration, design, or programming requirements are necessary to satisfy functional requirements and achieve the desired functionality. RICE objects represent requirements not currently supported within the core functionality of an Oracle Application Module being implemented and thus require additional technical development to satisfy the functional requirement of an organization.

Reports: For Business purpose, user may require a report with some data. Based on user requirement the Technical consultant will develop the report using SQL / PL SQL / Report Builder / Apex / Discoverer.
Conversion: One time data to be uploaded in the oracle apps like supplier data, customer data in excel / from legacy system to the oracle apps base tables / master. Interfaces: Interfaces are similar to conversion. Conversion is a one­time process where as Interface is a regular process. Interfaces can be scheduled daily or periodically.
Inbound Interface: Transferring the data from the legacy / third party system into the Oracle apps base tables.
Outbound Interface: Transferring the data from the Oracle apps base tables to the legacy / third party system.
Enhancements: Enhancements / Extensions are personalizing the forms based on user requirements.

In simple, during an Implementation / development project RICE components involves: 1. Creation of Reports that are not available as standard reports in the oracle apps modules. 2. Creation of the Interfaces to external systems. 3. Creation of Conversion programs to transfer data from a legacy system to the new system. 4. Enhancements (or extensions) to the existing system to ad