Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

schemas for RCU prefix have already been used

Received Response
467
Views
6
Comments
Adam Wickes
Adam Wickes Rank 6 - Analytics Lead

Hi all,

I am having a rotten time installing OBIEE 12c and seem to have come to a grinding halt.
The installation failed during the "Create Service Instance" section (77%).
Now when I try to re-run the configuration, i'm unable to use the schemas I created using RCU.
It gives me the following error:

"Schemas for RCU prefix 'XXXXX_STB' have already been used. Rerun RCU to create clean schemas."

Does anyone know whether it's possible to reset here without having to drop the schemas and start again?

I'm working late at night and don't have sysdba privs.

Thanks in advance,
Adam

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    That's always a nasty situation since you never know exactly what's in there already.

    So you can try truncating all the tables rather than dropping them.

    Normal procedure unfortunately is dropping, sorry.

  • Adam Wickes
    Adam Wickes Rank 6 - Analytics Lead

    Thanks for your reply Christian,
    Would you say the best step from here is to get the DBA team to drop the schemas (via the RCU), re-create the schemas and then re-run the config?

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Yes, absolutely

  • Being you I would not tell the DBA to drop the schemas, as it's not a real DB drop. The drop really need to be done by the RCU tool, as there are things added in other parts of the DB if not wrong (a system registry or whatever it is to list the existing RCU schemas etc.).

    So do not manipulate it as a simple DB object: RCU is created by the RCU tool and need to be dropped by the RCU tool, not by hand.

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    True that's what I meant. Run the wizard to drop things.

  • Adam Wickes
    Adam Wickes Rank 6 - Analytics Lead

    Hi guys,

    Yeah had already considered that luckily.
    I have just had the DBA drop the schemas via the RCU, recreated them and started the config again when I realised that it was going to fail again due to the following:

    https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=320530163175594&parent=EXTERNAL_SEARCH&sourceId=PROBLEM&id=2199128.1&_afrWindowMode=0&_adf.ctrl-state=5t1cdahr5_4


    This seems to be the error I had at 77% so will report back if changing the location of JAVA install helps.

    Thanks,
    Adam

    EDIT: Removing the space in the java install path fixed the issues when "adding default service instance" at 77% of install.