Issues and Workarounds for Installation, Upgrade, and Documentation

These issues and workarounds are for specific areas, such as installation, upgrade, security, and documentation.

Installation

This applies to issues regarding installing Oracle BI Applications.

Unable to Detect Machine Platform or JVM Bits

This issue applies to Oracle BI Applications installation.

When installing Oracle BI Applications, do not install WLS1036 on Windows with NFS JDK Path; instead use a local JDK location. If you use NFS JDK path, then during Oracle BI Applications configuration, the following error appears: 
Unable to detect machine platform or JVM bits.

Workaround

If you install the WLS by JDK from NFS, then replace all NFS JDK locations to local JDK location in the following two files:

C:\work\biapps10.1dw\biappsmw1\wlserver_10.3\.product.properties
C:\work\biapps10.1dw\biappsmw1\wlserver_10.3\common\bin\commEnv.cmd

Find all JDK path like \\adcnas418\farm_fmwqa\java\win64\jdk6 and replace them to path like c:\work\jdk.

Upgrade

These issues involve upgrading Oracle BI Applications.

SDE_ORA_ProductTransactionFact_Delete_UPG Package Fails in Upgrade BIApps 111192 to 1111101 EBS 1213 Load Plan

This issue applies to Oracle E-Business (EBS) users using EBS release 12.1.3 applications as a data source along with Supply Chain Management and Manufacturing Oracle BI Applications offerings and upgrading from Oracle BI Applications Release 11.1.1.9.2 to 11.1.1.10.1.

The SDE_ORA_ProductTransactionFact_Delete_UPG package is failing in the Upgrade BIApps 111192 to 1111101 EBS 1213 load plan.

Workaround

Note:

Ensure that you have access to the ODI Studio and an account with developer access to be able to patch the mappings.
  1. Open the ODI Studio and log in to the ODI Master Repository using a developer account.
  2. Click View, click ODI Designer Navigator to go to the Designer tab. Expand BI Apps Project by clicking Mappings.
  3. Scroll down to the Upgrade folder and open the relevant subfolder as follows:
    Data Source EBS Release Upgrade Mapping Folder Name
    EBS R12 SDE_ORAR12_11.1.1.9.2_to_11.1.1.10.1_Upgrade
    EBS R12.1.1 SDE_ORAR1211_11.1.1.9.2_to_11.1.1.10.1_Upgrade
    EBS R12.1.2 SDE_ORAR1212_11.1.1.9.2_to_11.1.1.10.1_Upgrade
    EBS R12.1.3 SDE_ORAR1213_11.1.1.9.2_to_11.1.1.10.1_Upgrade
    EBS R12.2 SDE_ORAR122_11.1.1.9.2_to_11.1.1.10.1_Upgrade
  4. Expand the SDE_ORA_ProductLotTransactionFact_Delete_UPG package.
  5. Edit the SDE_ORA_ProductLotTransactionFact_Delete_UPG.W_PRODUCT_LOT_XACT_F interface.
  6. Select the Key check box for target columns DATASOURCE_NUM_ID and INTEGRATION_ID.
  7. Click Target Datastore Header and set the Update Key drop-down to <Undefined> .
  8. Save the mapping and regenerate the scenario.

Upgrade Issue from 11.1.1.10.1 to 11.1.1.10.2

This issue applies while upgrading from 11.1.1.10.1 to 11.1.1.10.2.

In 11.1.1.10.1, the index was disabled; however, the index is enabled in 11.1.1.10.2 and hence is getting created. This is causing a duplicate failure as there is data in the FLEX XML file for one of the key flexfields that is violating this constraint. This is fixed in 11.1.1.10.2 but since the 11.1.1.10.1 data warehouse already has this data, the upgrade load plan will fail.

Workaround

Run the following command in the 11.1.1.10.1 data warehouse and continue with the upgrade load plan. Take a backup of the table before you run the following command.

delete from W_FLEX_SRC_ATTRIB_G where rowid not in (select min(rowid) from  
W_FLEX_SRC_ATTRIB_G group by  
FLEX_SRC_CODE,FLEX_SRC_ATTRIB,DATASOURCE_NUM_ID,SOURCE_TYPE
having count(*) > 1);
commit;

Errors in Dashboards After Upgrade From 11.1.1.10.1 to 11.1.1.10.2

This issue applies to the upgrade from 11.1.1.10.1 to 11.1.1.10.2

After upgrading from 11.1.1.10.1 to 11.1.1.10.2, you might notice errors in dashboards which is expected behavior after an upgrade.

Workaround

To prevent these errors, run the incremental ETL after the upgrade.

Issues Due to Incorrect DATASOURCE_NUM_ID and DATA_SERVER_TYPE Values

This issue applies to the missing ODI scenario’s from the generated load plan.

Few Oracle Data Integrator (ODI) scenarios (tasks) are missing in the generated load plan that loads the W_GL_BALANCE_FS table. This is due to the ODI logical schema flexfield (DATASOURCE_NUM_ID) mismatch in the ODI Topology configuration and the incorrect flexfield value for DATA_SERVER_TYPE for the PeopleSoft 91 ODI logical schema.

Workaround

  1. Launch ODI Studio, navigate to the Topology, and go to the logical architecture.
  2. Open the logical schema DW_BIAPPS11G, go to the flexfields tab, and change the DATASOURCE_NUM_ID flexfield value from -1 to 999.

    Note:

    Ignore this instruction if you see 999 as the value for the flexfield.
  3. Open the logical schema DS_PSFT91HR, go to the flexfields tab, change the DATA_SERVER_TYPE flexfield value from PSFT_9_1 to PSFT_9_1_HR, and save the changes.
  4. Open the logical schema DS_PSFT91HR_SDS, go to the flexfields tab, change the DATA_SERVER_TYPE flexfield value from PSFT_9_1 to PSFT_9_1_HR, and save the changes.

    Note:

    After updating the values, save, close, and open again to ensure that the updates are reflected correctly.
  5. Regenerate the load plan.

Documentation Corrections

This information provides corrections and additions for documentation and Help for Oracle BI Applications.

General Documentation Issues

There are currently no documentation errors.