Upgrading Fusion V1 Adaptor ODI Artifacts to Use Fusion 9 Adaptor

Use these instructions to upgrade the source.

Ensure that you have performed the following:

  • Perform the upgrade steps. As part of the Upgrade process, you would have exported your connections, dropped and replaced the ODI repository, and then imported the connections back again.

  • Do not run any load plans during this process and deactivate the load plan schedules.

Oracle BI Applications release 11.1.1.10.1 supports multiple Fusion releases, thereby allowing the source to be either Fusion 9 or Fusion 10. When you upgrade from BI Applications Release 11.1.1.9.2 to 11.1.1.10.1, you need to set the DSN for the logical schemas DS_<modelCode>_SDS and DS_<modelCode>_SDS_DW (for example, DS_EBSR122_SDS, DS_EBSR122_SDS_DW) if SDS is deployed for a previously registered source.

To upgrade Fusion V1 adaptor ODI artifacts to use Fusion 9 adaptor:

Note:

If you do not import the connections from BI Applications Release 11.1.1.9.2 repository, then the rewiring process will not work. In this case, you will need to run the Fusion Upgrade load plan and not the Source Upgrade load plan.

Note:

Execute the standalone scripts from BI Oracle Home.
  1. Rewire the sources to ensure that all ODI connections that were earlier pointing to Fusion V1 logical schemas now move to corresponding Fusion 9 logical schemas. The DSN remains the same.

    Run UpgradePLV script to rewire PLV in Oracle BI Applications Configuration Manager (OBIACM).

    Usage

UpgradePLV.ksh <oracle home> <username> <password> <dns> <PLV code> [<hostname> <port number>]
 <oracle home>: Oracle Home
    <username>: Administrator username
    <password>: Administrator password
         <dns>: DNS of source instance which need to be upgraded
    <PLV code>: Upgrade PLV code
    <hostname>: Hostname of server where BIACM server is running (Optional, default: localhost)
 <port number>: Port number where BIACM server is running (Optional, default: 9704)

Example On Linux

cd /scratch/kdinaman/work/mw3607/Oracle_BI1/biapps/admin/provisioning/update
/bin/ksh UpgradePLV.ksh /scratch/kdinaman/work/mw3607/Oracle_BI1 Administrator1 Admin12345 205 FUSION_9_0

Example On Windows

cd C:\work\mw3607\Oracle_BI1\biapps\admin\provisioning\update
UpgradePLV.bat C:\work\mw3607\Oracle_BI1 Administrator1  Admin12345 205 FUSION_9_0

    Note:

    OBIACM binaries and schema should be upgraded and OBIACM web application is running. User passing in the command must have BIA_BIACM_SERVICE_PRIV privilege in order to access the BIACM web service.
  2. Regenerate the load plans to ensure that the generated load plan has scenarios or steps corresponding to Fusion 9 and not Fusion V1.
    Complete these steps to run source upgrade load plans after the Source Upgrade rewiring:

    Note:

    Ensure that all DB directories are created or mapped.

    1. Set JAVA_HOME, if not set already.

    2. Verify whether all these jars are available:

      • The jars otbiePatchTool.jar and patchToolHelper.jar, should be available under directory $ORACLE_BI/biacm/patch/lib.

      • The jars bia-db.jar and bia-odi.jar, should be available under directory $ORACLE_BI/biapps/lib..

      • The jar lpgengine.jar, should be available under directory $ORACLE_BI/biapps/lpg/jlib. .

      Run the odiPatch.sh from the directory : $ORACLE_BI/biapps/odi/patch.

      Example:

      Note:

      Replace all key's value with your data/credentials.
      sh odiPatch.sh 1 /scratch/nchowdhu/work/mw3459/odi7272 ODI_HOME /scratch/nchowdhu/work/mw3459/odi7272 ODI_CONTEXT GLOBAL BIACOMP_DB_DRIVER oracle.jdbc.OracleDriver ODI_JPS_CONFIG_PATH /scratch/nchowdhu/work/mw3459/odi7272/oracledi/client/odi/bin/jps-config-    jse.xml ODI_CWALLET_SSO_PATH /scratch/nchowdhu/work/mw3459/odi7272/oracledi/client/odi/bin/cwallet.sso ODI_DB_SYS_USER system ODI_SCHEMA_USER FA_BIA_ODIREPO ODI_WORKREP BIAPPS_WORKREP BIACOMP_SCHEMA_USER FA_BIACOMP ODI_BIAPPS_SYS_USER BIAppsSystemUser BIACOMP_JDBC_URL slc09ewk.us.oracle.com:15581/db5902.us.oracle.com ODI_BIAPPS_SYS_PASSWORD Ob5gfzmkaov1lice ODI_SCHEMA_TS_NAME FA_BIA_ODIREPO BIACOMP_SCHEMA_PASSWORD welcome1 ODI_JDBC_URL slc09ewk.us.oracle.com:15581/db5902.us.oracle.com ODI_DB_SYS_PASSWORD welcome1 BI_ORACLE_HOME /scratch/nchowdhu/work/mw3459/Oracle_BI1 ODI_SCHEMA_PASSWORD welcome1 ODI_DB_DRIVER oracle.jdbc.OracleDriver PATCH_LOCATION /scratch/patchorchestrator/patches/ptf_obiacm_cm_cm_bin_3005180122.zip PATCH_APPLICATION_ORACLE_HOME /scratch/nchowdhu/work/mw3459/Oracle_BI1 OPATCH_INV_PTR_LOC /scratch/nchowdhu/work/mw3459/Oracle_BI1/oraInst.loc PATCH_ID 3005180122 PATCH_PHASE backup LOG_LOCATION /scratch/logs//ODI SRC_UPGD_MODE Y ODI_LP_NAME_SRC_UPGD Test-Src-Upgd_2_20150624_000306

Where:
1 -> ODI home location

*PATCH_PHASE -> If backup then use : backup, If postphase then use : executePostPhase
 ODI_HOME -> ODI home location 
 BIACOMP_DB_DRIVER -> CM db driver name
 ODI_JPS_CONFIG_PATH -> ODI jps file location
 ODI_CWALLET_SSO_PATH -> ODI cwallet file location
 ODI_DB_SYS_USER -> DBA user name
 ODI_SCHEMA_USER -> ODI schema name
 ODI_WORKREP -> Odi workrepo name
 BIACOMP_SCHEMA_USER -> CM schema name
 ODI_BIAPPS_SYS_USER -> ODI studio user name
 BIACOMP_JDBC_URL -> CM db URL
 ODI_BIAPPS_SYS_PASSWORD -> ODI studio password
 ODI_SCHEMA_TS_NAME -> Odi schema tablespace name
 BIACOMP_SCHEMA_PASSWORD -> CM schema's password
 ODI_JDBC_URL -> ODI db URL
 ODI_DB_SYS_PASSWORD -> DBA password
 BI_ORACLE_HOME -> BI oracle home location
 ODI_SCHEMA_PASSWORD -> Odi schema's password
 ODI_DB_DRIVER -> Odi db driver name
 PATCH_LOCATION -> Any dummy location 
 PATCH_APPLICATION_ORACLE_HOME -> Any dummy location
 OPATCH_INV_PTR_LOC -> Any dummy location
 PATCH_ID -> Any dummy number
 LOG_LOCATION -> any existing location which stores logs
 SRC_UPGD_MODE -> Y
 ODI_LP_NAME_SRC_UPGD -> existing Source upgrade LP name

    You can also manually do this from BI Applications Configuration Manager (BIACM) user interface. Use BIACM user interface to generate a new load plan and also setup schedules for the new load plan.

  3. Run the Source Upgrade load plan (Upgrade BIApps 111192 to 1111101 FUSION 9) that gets the tables and data in sync with metadata in BI Applications Release 11.1.1.10.1. This is available under the Pre-Defined Load Plans in the upgraded repository.
    You will need to run the Upgrade Internal Tables Load plan first before running the Fusion load plan as is the case normally. If your Fusion source in on the Cloud, you will need to place full request files on the UCM/Storage Service for any VOs that are being reloaded as part of the Ugprade load plan. For that you can do either of the following:

    1. Look at the Request for Full Load Files Under Upgrade SDS >File to SDS Load Phase > Pre Load section of the load plan. Using the UI present on Fusion side, request for full load files for those VOs that are listed in the Cloud Table list parameter for that step.

    2. Alternatively run the step Request for Full Load Files in the load plan to generate the BATCHREQUEST File that needs to be uploaded to UCM/Storage Service. Then run a single extract on the FA Extractor side. It will download the BATCHREQUEST file and provide a full file for the VOs present in the BATCHREQUEST file.

After you have performed these steps, you can verify that the process ran fine:

  1. When you see the context, you should see all the physical Fusion Connections mapped to Fusion 9 logical schemas. Nothing should still point to Fusion V1 schemas.

  2. DSN against Fusion 9 should be the same DSN as earlier.

  3. In Generated Load plan, you should see all scenarios corresponding to Fusion 9 and not Fusion V1.

  4. All existing load plan schedules should be moved to the newly generated load plans.

  5. In W_ETL_LOAD_DATES table, you should see entries for Fusion 9 only and not V1 anymore.