Oracle Analytics Cloud and Server

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

Categories

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

Getting error while upgrading OBIEE 11.1.1.7.0 to OBIEE 12.2.x

Received Response
11
Views
5
Comments
Anirban1
Anirban1 Rank 4 - Community Specialist
edited Aug 13, 2024 5:20PM in Oracle Analytics Cloud and Server

Hi,

We are trying to upgrade OBIEE 11.1.1.7.0 to 12.2.2.0 version. We are able to upgrade successfully in Dev and Preprod environment but while trying to do the same in production environment we are getting below error while trying to create export.jar file through command prompt.

We are using Microsoft Server 2012 R2.

Error Message : Calling migrate policy store with parameters.

Severe: Failed on running migrate policy store. Script returned non zero value.

Can you please let me know if I am missing anything or how can I fix this problem. All the configuration currently same in DEV, Preprod and Prod except space.

Thanks

Anirban

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner 
    Anirban1 wrote:Hi,We are trying to upgrade OBIEE 11.1.1.7.0 to 12.2.2.0 version.

    What is the "12.2.2.0" version?! That version doesn't exist.

  • Anirban1
    Anirban1 Rank 4 - Community Specialist

    Hello Christian,

    Sorry for the wrong information.

    The exact version is 12.2.1.3.0.

    Thanks

    Anirban

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

    You're aware that 12.2.1.3 is out of error correction support, right?

    See MOS Doc ID 2070465.1

  • Anirban1
    Anirban1 Rank 4 - Community Specialist

    Hello Christian,

    Thanks for the information.

    Just need to check I am doing any wrong thing ?  As this is successfully completed in Dev and PreProd instance I hope there might be some problem with  configuration, is there any way from where I can get the error log. Also I found out that while running bi-migration-tool, it is able to successfully complete RPD and Webcat but it is not able to write anything in system-jazn-data-migration file.

    Thanks

    Anirban

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

    It means that your PROD contains invalid content which breaks the export when compared to the other envs. You're not providing enough detail to make any statement though.

    In general when migrating, only PROD is migrated to the new version and then deployed inside the "12 family" from dev to test to preprod to prod in order to prevent issues like you have.