Oracle Analytics Publisher

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Publisher

Categories

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

Migrating from BIP 12c to OAS/OAP 7.0

Accepted answer
142
Views
7
Comments
User_IHX67
User_IHX67 Rank 1 - Community Starter
in Oracle Analytics Publisher

Hi there,

I'm reaching out to the community to see if anyone has encountered this scenario and to learn the best way to handle it. Your suggestions are greatly appreciated.

Currently we are using BIP 12c which is integrated with Siebel for Reporting.

We are migrating from one OS to another (from Windows Server 2016 to Windows Server 2022) for both the database and the application. Simultaneously, we are upgrading from BIP 12c to OAP 7.0. How can we accomplish this? Clearly, I need to install OAP on the new host when migrating the platform.

For the Database (MS SQL Server), we are using a cloned database that already contains the BIP 12.2.1.2.0 schema, which means the database host name is different, and this needs to be updated in COMPONENT_SCHEMA_INFO. (SQL: SELECT DB_HOSTNAME, DB_SERVICE, DB_PORTNUMBER FROM VEC_STB.COMPONENT_SCHEMA_INFO;) How do we do that?

I installed WebLogic 12.2.1.4.0/OAS 7.0 on the new host and tried running RCU with the existing database schema prefix, but it failed with the following errors:

Error: "RCU-6015: Component validation failed. Cause: RCU-6015: No component was selected or specified. Action: RCU-6015: Select or specify at least one component."

Consequently, I considered using the upgrade assistant to upgrade the database schema, but for that, I need the domain created beforehand.

When I tried to create the domain using the existing schema and OAP as a standalone product, it resulted in the following error:

Error: "Schemas for RCU prefix 'VEC_STB' have already been used. Re-run RCU to create clean schemas."

Without these steps, I am unable to upgrade the existing 12c schema to OAS/OAP 7.0. I'm eager to understand how we can complete this migration while retaining the existing schema in the database and upgrading it to OAP 7.0.

Thanks, AJ

Best Answer

Answers

  • User_IHX67
    User_IHX67 Rank 1 - Community Starter

    Hi @Mallikarjuna Kuppauru-Oracle,

    Thanks for the comment.
    Yes, I came across this article (Doc ID 2802991.1), and it helps in scenarios where the application is already configured against a database and you want to change the database host later.

    However, in our scenario, we are installing WebLogic/OAS on a new host, and at the moment, it does not have the properties files configured. We want to map it to the new database, which has the existing 12c schema, and upgrade it to OAS 7.0.

    When we try to run the RCU or Domain Config by selecting the existing prefix/schema to upgrade the database schema to 7.0, it doesn't allow us to proceed further, as mentioned in the original post.

    Thanks,
    AJ

  • Gianni Ceresa
    Gianni Ceresa Mod

    I'm maybe missing something, but it sounds like you are doing a out-of-place upgrade while trying to perform an in-place upgrade. It's one or the other.

    You are moving to a new server, therefore forget in-place upgrade. Your 12c schemas will not be upgraded, you can't upgrade them, they don't belong to a product being upgraded from 12c to OAS.

    You are installing a new OAS, you should configure it fully and then migrate the content as a typical out-of-place upgrade process. Because you can't install OAS, configure it, then point it to a 12c schema and try to use it as if it was a 12c requiring to go through an in-place upgrade.

    Keep your upgrade process clean and simple: it will avoid you future errors and surprises in the future.

  • User_IHX67
    User_IHX67 Rank 1 - Community Starter

    Thanks @Gianni Ceresa, for the comment.

    In this case, dropping the 12c RCU schema from the database and recreating the OAS/OAP 7.0 schema with an New OAS installation is the only way I believe. Future upgrades can be done in place, provided that we are not changing the database/platform.

    Thanks, AJ

  • Gianni Ceresa
    Gianni Ceresa Mod

    Well, dropping is maybe "extreme" (ok, you said you cloned the database, therefore somewhere else you will still have the real 12c schemas).

    Can't you just use a different prefix?

    And yes, when picking a prefix keep in mind what you just said: future upgrades in-place mean the schemas will stay, therefore don't add the version in the prefix ;-)

    So far, each release of OAS did support in-place upgrade nicely. In the future it's difficult to say what it will be. If Oracle will drastically change the architecture of the product (for whatever reason), in-place will maybe not be possible, but there will be a migration process available to make the move easy anyway.

  • Mallikarjuna Kuppauru-Oracle
    Mallikarjuna Kuppauru-Oracle Rank 8 - Analytics Strategist

    Hi @User_IHX67

    For your case Out of Box Approach is the correct solution.

    Regards,

    Arjun

  • User_IHX67
    User_IHX67 Rank 1 - Community Starter
    edited Sep 25, 2024 9:27PM

    Thanks, @Gianni Ceresa , @Mallikarjuna Kuppauru-Oracle

    Yes, I agree that the future upgrade process might change depending on the versions we have or if there have been changes to the product architecture etc.

    The reason we wanted to explore the options for upgrading the existing 12c schema is that we use MS SQL Server, and DB Collation is a concern (Error for OPSS Component on MS SQL Server Database Having Case Insensitive Collation (Doc ID 2763661.1)). So, we have performed a manual, tedious job of altering it for the time being until the schema is created (During 12c Upgrade) and then revert it.
    We thought that upgrading an existing schema might reduce a bit of that work, though not completely.

    I mentioned that we drop the current 12c schema and recreate it for OAS 7.0 just to keep the database clean and nice and to avoid any duplicates. We install OAP as a standalone product and integrate it with Siebel for reporting. (We have taken the necessary backups of 12c on a different database.)

    Thanks.