RCU Schema Configuration failed with the error “The specified prefix already exists”

Process:

We all know that we need to create RCU schemas before starting OBIEE 11G (In fact, for any Fusion Middleware application) Installation. Because it is the base store for FMW.

Problem:

Recently I came across a scenario where my customer created RCU schemas with Oracle Repository Creation Utility (RCU) version 11.1.1.3.0 and Installed OBIEE 11.1.1.3.0. Now after new OBIEE 11.1.1.5.0 release he wants to upgrade his application from 11.1.1.3.0. But he is not interested at the In-place upgrade. Therefore, we uninstalled weblogic and OBIEE 11.1.1.3.0 and started RCU 11.1.1.3.0 to drop the _BIPLATFORM and _MDS schemas.

The RCU shown up with successful message and so we thought everything is cleaned up and it’s good to create schemas again. I started RCU 11.1.1.5.0 and selected Oracle Business Intelligence component and given prefix as DEV. But am not able to assign this prefix and got a message like “The specified prefix already exists”.  Though I got successful dropped schemas message, just for cross check I looked at database for the DEV_BIPLATFORM and DEV_MDS schemas. There I am not seeing any of them.

Cause:

Then I checked at dropped schemas log generated by RCU and realized that there is an entry in System.SCHEMA_VERSION_REGISTRY$ table which is stopping me to assign the same DEV prefix which we used for earlier version schemas.

Actually, the RCU should drop schemas using mdsschemamanager.pl script. This script has capability to do cascade delete and will delete entries in System.SCHEMA_VERSION_REGISTRY$ table.

To make sure this log into RCU DATABASE as sys and run the following SQL Query:

Select * from System.SCHEMA_VERSION_REGISTRY$;

If this query returns any record then it means the RCU didn’t drop the schemas properly.

Actually what happened in this case is the RCU schemas were not dropped using mdsschemamanager.pl script, it’s just dropped with normal schema delete and the resulting repository record for the schema is not clean. Keep in mind, this is just in case if you want to use same prefix. Otherwise, RCU will let you proceed to create new prefixed Schemas.

If the RCU schemas have been deleted incorrectly using the RCU drop user command, then we need to clean these entries before starting new repository schemas creation.

Solution:

To fix it, run the following SQL*Plus command as sys to complete the removal of the RCU schemas records in the repository database:

delete from System.SCHEMA_VERSION_REGISTRY$;

Once you confirmed there are no entries in System.SCHEMA_VERSION_REGISTRY$ table and start the RCU to create repository schemas with the prefix (DEV in my case). The RCU will go smooth and will not complain with any error.

Hope this helps you in your RCU issues troubleshooting.

 Thanks

OBIEE 11g Installation error : One or more entries are found in HSS_COMPONENT table

 

Oct24by Gaurav Chaudhary

Issue:
While installing OBIEE 11g in a system where OBIEE was previously installed, then uninstalled for any reasons with the same RCU schema, then we got this error. One or more entries are found in HSS_COMPONENT table
Cause:
While installing RCU, two RCU schemas are created BIPLATFORM,MDS. These schemas contain all the configuration tables. OBIEE 11g installation always inserts some data in HSS_COMPONET table. As the data is already present for the previous installation , it is showing this error.
Resolution:
There is no need to delete/uninstall RCU schemas. We can continue OBIEE 11g installation again with the same schema which we have already installed.
Step 1:
Login into SQLPLUS and connect BIPLATFORM Schema with the same credentials which we have given when we installed.
SQL> conn DEV_BIPLATFORM/password@connection_string
Step 2:
Once we connected with BIPLATFORM Schema delete the entry which is available in the HSS_COMPONENT table and commit the table.
SQL> DELETE FROM HSS_COMPONENT;
7-8 entries will deleted.
SQL> COMMIT;
Commit Complete;

Now start the installation and give the BIPLATFORM AND MDS schema details in its related steps. The error will no more exist.

N.B.: Do not forget to ‘COMMIT’ once we deleted the entry from HSS_COMPONENT table because ‘DELETE’ command will not be updated without commit.