Bugs

BUG 21198879 - SILOS_SIL_GLCOGSFACT_REVERSE_DIFFMANLOAD mapping failed

with ORA-20000: Error creating indexl

Issue
Caused By: java.sql.SQLException: ORA-20000: Error creating
indexes in parallel, see W_ETL_EVENT_LOG for details ORA-06512:
at line 119
IKM BIAPPS Oracle Fact Event Queue Delete Append KM code for creating indexes is
using DBMS_PARALLEL_EXECUTE package to create indexes in parallel. While
creating indexes, KM code is using DBMS_PARALLEL_EXECUTE.task_status
procedure to check the status of index creation and throw an exception if the status
code <> 6.
This works well with DW schema in Oracle 11g DB release data bases, but when
using Oracle 12c release ( 12.1.0.2.0) data base as DW schema, looks like there is a
change in status codes return by the DBMS_PARALLEL_EXECUTE.task_status
procedure. Hence we are ending up with an exception even if the index creation
goes well.
Below are the task status values in 11g are:1, 'CREATED',
2, 'CHUNKING',
3, 'CHUNKING_FAILED',
4, 'CHUNKED',
5, 'PROCESSING',
6, 'FINISHED',
7, 'FINISHED_WITH_ERROR',
8, 'CRASHED'
In 12c they are:1, 'CREATED',
2, 'CHUNKING',

3, 'CHUNKING_FAILED',
4, 'NO_CHUNKS',
5, 'CHUNKED',
6, 'PROCESSING',
7, 'FINISHED',
8, 'FINISHED_WITH_ERROR',
9, 'CRASHED'

Applies to
This fix is applicable to BI Apps 11.1.1.8.1 and only if you are using Oracle 12c
release (12.1.0.1.0) data base or higher db version as DW schema.

Steps to fix the issue

Note: Before making any changes to the KM component IKM BIAPPS Oracle Fact
Event Queue Delete Append , please create a version of the KM by following below
instructions. In case if there is a failure while applying the fix we can always go back
to the saved versions and restore it. Please refer to the section Steps to Revert
back the fix for restoring saved versions.
Step 1:
Right click on IKM BIAPPS Oracle Fact Event Queue Delete Append and
select create version option from the given menu list as shown below

Enter description for the version and click on OK button.

Click on OK button to create version.

Step 2:
Download and unzip export_21198879.zip file for the KM fix file. Once you
unzip export_21198879.zip file you will now see
KM_IKM_BIAPPS_Oracle_Fact_Event_Queue_Delete_Append.xml patch file.
Import the provided KM patch file by using import replace option by right clicking on
existing IKM BIAPPS Oracle Fact Event Queue Delete Append KM in ODI as shown
below

Once you click on Import Replace option you will be getting the below window.
Choose KM patch file (.xml file) location and click ok button.

Steps to regenerate scenario:

Once you are done with the above KM changes,we will have to regenerate
affected /failures scenarios .Below is the only one OOTB scenario which affected by
the above KM change. Incase if this KM had been used in any customization
interfaces; please regenerate customization scenarios as well to uptake the KM
change.

Right click on SILOS_SIL_GLCOGSFACT_REVERSE_DIFFMANLOAD scenario and

choose Regenerate option from the Menu as shown below.

Steps to Revert back the fix

Please follow the below mentioned steps to restore saved KM versions.
Step 1:
Right click on existing IKM BIAPPS Oracle Fact Event Queue Delete Append KM
and select Restore option from the given menu list as shown below

Now choose the required Version of KM from the given list to restore and click on OK
button as shown below.

regenerate scenarios
If you followed revert back steps to remove the provided fix then you should be
regenerating affected scenarios again in case if you are done with regenerating of
scenarios after applying the above fix. Please refer to the section

regenerate scenarios

for regenerating scenarios .

Steps to