Oracle Business Intelligence Applications

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

ODI-1529 Refresh of variable "BIAPPS.13P_CALENDAR_ID" failed (ORA-00942)

Received Response
21
Views
6
Comments

Hi All,

Recently did Production BI Apps installation. When I execute initial domain load plan,  I am facing the below issue immediately at refresh variable step itself.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ODI-1519: Serial step "Start Load Plan (InternalID:390520)" failed because child step "Global Variable Refresh (InternalID:391520)" is in error.

ODI-1529: Refresh of variable "BIAPPS.13P_CALENDAR_ID" failed :

select CASE WHEN 'Global Variable Refresh' in (select distinct group_code from C_PARAMETER_VALUE_FORMATTER_V where PARAM_CODE= '13P_CALENDAR_ID')

THEN (select param_value

from C_PARAMETER_VALUE_FORMATTER_V

where PARAM_CODE=  '13P_CALENDAR_ID'

and group_code='Global Variable Refresh'

and datasource_num_id = '#BIAPPS.WH_DATASOURCE_NUM_ID')

ELSE

(select param_value from C_GL_PARAM_VALUE_FORMATTER_V where PARAM_CODE=  '13P_CALENDAR_ID' and datasource_num_id = '#BIAPPS.WH_DATASOURCE_NUM_ID')

END

from Dual

942:42000:java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Probable cause:      Few objects(synonyms) are missing in BIACOMP schema & not configured properly during BI Apps Installation.

Is there any way to fix this issue without reverting or re doing the installation?

Any suggestion would be more helpful us.

Thanks in Advance,

Sekar

Welcome!

It looks like you're new here. Sign in or register to get started.

Answers

  • Rank 3 - Community Apprentice

    Have you completed or are you in the process of completing the post-install instructions in the installation guide? If so, open ODI Studio and log in. Go to your topology navigator tab, expand Physical Architecture > Technologies > Oracle > XX_BIACOMP (Where XX is PROD or whatever name you gave during the RCU installation). Double click on the blue icon and verify that the data server user is XX_BIACM_IO (Again, where XX is PROD or whatever) and the password entered during the RCU setup. Go to the JDBC tab and make sure the JDBC Url connection details are correct and then click the Test Connection text at the top. This will verify your connection is successful or if you have an issue with the actual connection to your DB and schema.

  • Rank 3 - Community Apprentice

    Also, while I'm thinking about it, double check that all of the perl patching completed successfully and the PSA.sh(bat) completed correctly each time (ATG, FSM, BIApps). For the perl patching, check the log by following the steps below.

    Log file location

    If you remember, you set a WORKDIR path in the apply_patches_import.txt file during installation. In that directory is where you will find the following log files:

    1. final_patching_report.log
    2. biappshiphome_generic_patches.log
    3. odi_generic_patches.log
    4. oracle_common_generic_patches.log
    5. weblogic_patching.log

    Open the final_patching_report.log to determine first if all patches were applied and identify ones that were not successful.

    cd $WORKDIR

    vi final_patching<em>_</em>report.log

  • Rank 2 - Community Beginner

    Hello Wagner,

    Thanks a lot for your reply.

    As mentioned above:

    1.   We completed Post Installation steps. Also test connection was successful under XX_BIACM_IO schema in topology.

    2.    Also we checked those work_dir files once after applying patches. Though we will review again for confirmation.

    Examining the SQL query in Error, we found that few synonyms are missing under "BIACOMP".

        " C_PARAMETER_VALUE_FORMATTER_V "

    By cross checking with Test environment, It is a view in XX_BIACOMP Schema, which in turn created as a synonym in XX_BIACM_IO schema by default during installation process.

    We doubt that there should be a problem in Dump files used for schemas. (OBIA, ODI, BIACOMP). (May not be configured properly)

    If so, we need to redo the installation from beginning. Kindly suggest a recommended solution at this stage.

    Best Regards,

    DB

  • Rank 3 - Community Apprentice

    I am thinking maybe just re-running the OBIA rcu, to drop and then readd those schemas would work. I've on a couple occasions had to back out and restart an installation again about halfway through. I've successfully dropped the OBIEE rcu schemas and readded them without issue after an install. However, the OBIA rcu schemas I've not dropped and readded. There could be some internal GUIDs (I'm thinking like in the odi repo snp tables and such)in the db tables that are going to be broken in this process. It could go a couple of ways. You can start by seeing how many of the synonyms are missing and attempting to manually create them if it is just a couple. If you want a 100% clean PROD install, which since it is production, I'd probably lean this way, start by backing out the rcu schemas by running the rcu again. There is an excellent Oracle guide to back out and refinish the last few steps of the install (config.sh and configapps.sh). I would probably end up re-copying the three .dmp files to make sure they aren't the issue, and then follow these steps from this support.oracle.com Doc ID - OBIA 11g How Can I re-run the configApps process? (Doc ID 1951077.1)

    Keep us posted!

  • Rank 2 - Community Beginner

    HI,

    Sorry for delay in reply!

    The actual problem in my case was the usage of old BI Apps RCU version. We then manually imported the all objects(w/o data) using DB scripts from Test to Prod environment fixed the issue.

    Though the suggestions mentioned above also will be possible fix for this type of error.


    Thanks a lot Wagner.Cheers

  • Rank 2 - Community Beginner

    We did not export/Import all three schema which is not recommended after installation.

    - BIACOMP - we created few missing synonym

    - DW - Exported all the table / sequences to Prod DW

    - ODI REPO - No changes made. Everything was fine.

Welcome!

It looks like you're new here. Sign in or register to get started.