Vous êtes sur la page 1sur 8

Bugs

Bug 22725263-The Slowly Changing Dimension IKM fails to update EFFECTIVE_TO_DT

Bug 23182595 - Delete processing support in-case of source uses SDS

Issue
1) We observe that this KM does not correctly calculate EFFECTIVE_TO_DT for type 2 dimensions in
a given use case.Consider the sample data below:

INTEGRATION_ID EFFECTIVE_FROM_DT EFFECTIVE_TO_DT ETL_PROC_WID CURRENT_FLG

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

PER~28364 01-MAR-09 01-JAN-14 4500 Y

PER~28364 01-JAN-12 01-JAN-14 2500 Y

The second row is inserted after full load, while the first row is inserted.

after incr load. however, the EFFECTIVE_TO_DT and CURRENT_FLG of the new row (i.e., first row) are not
correct.

Applies to
This is applicable to BI Apps 11.1.1.10.1

Steps to fix the issue


Note: Before making any changes to the KM components 'IKM BIAPPS Oracle Slowly Changing
Dimension, 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 Slowly Changing Dimension KM and select create version
option from the given menu list as shown below
Enter description for the version and click on OK button.
Step 2:

Download and unzip export_22725263.zip file that is there along with the tech note, for the KM fix file.
Once you unzip export_22725263.zip file you will now see
KM_IKM_BIAPPS_Oracle_Slowly_Changing_Dimension.xml patch files in the export_22725263 folder.

Import the provided KM patch file KM_IKM_BIAPPS_Oracle_Slowly_Changing_Dimension.xml by using


import replace option by right clicking on existing IKM ' IKM BIAPPS Oracle Slowly Changing Dimension,
KM in ODI as shown below

Once you click on Import Replace option you will be getting the below window. Choose KM patch file
KM_IKM_BIAPPS_Oracle_Slowly_Changing_Dimension.xml (.xml file) location and click ok button.
Step 3: Regenerate scenarios
Copy the regen_22725263.zip to the machine where the BIAPPS middleware
is installed.

Keep the following folder paths ready


<JAVA_HOME>
<ODI_HOME>
<MW_HOME>

If your ODI is setup for external authentication, then have the paths and names of
the JPSCONFIGFILE and SSOFILE ready.

Unzip the regen_22725263.zip on the machine where BIAPPS is installed.


Lets refer to that folder as <PATCH_REGEN_FOLDER>.

Once you unzip regen_22725263.zip file , you will be seeing


sceregenparams.properties file under regen_22725263\logs\ folder.

Open sceregenparams.properties file under both the folders in edit mode and
change LOG_FILE_DIR parameter path to use <PATCH_REGEN_FOLDER>/
regen_22725263/logs/ as shown below.
Verify that you have the following jars in the middleware home.
bia-odi.jar file in <MW_HOME>/Oracle_BI1/biapps/lib
bia-odi-util.jar file in <MW_HOME>/Oracle_BI1/biapps/biaodiutil/lib

Build the command that you need to run:


The command that ought to run is below

Windows:

<JAVA_HOME>\bin\java.exe -client -Xms32m -Xmx1024m -classpath


<ODI_HOME>\oracledi.sdk\lib\*;<ODI_HOME>\inventory\Scripts\ext\jlib\*;<ODI_HO
ME>\modules\oracle.idm_11.1.1\*;<ODI_HOME>\ modules
oracle.jps_11.1.1\*;<MW_HOME>\Oracle_BI1\biapps\lib\*;\*;<MW_HOME>\Oracle_BI1\biap
ps\biaodiutil\lib\bia-odi-util.jar oracle.apps.biaodiutil.Import MODE=SCEREGEN
FILEDIR=<PATCH_REGEN_FOLDER>\ regen_22725263 PLV=BIA_11
JPSCONFIGFILE=<JPSCONFIGFILE> SSOFILE=<SSOFILE>

Example:
C:\Java64\jdk1.6.0_35\bin\java.exe \-client \-Xms32m \-Xmx1024m \-classpath
C:\oracle\product\odi11.1.1.7\oracledi.sdk\lib\*;C:\oracle\product\odi11.1.1.7\invento
ry\Scripts\ext\jlib\*;C:\oracle\product\odi11.1.1.7\modules\oracle.idm_11.1.1\*;C:\ora
cle\product\odi11.1.1.7\modules\oracle.jps_11.1.1\*;C:\obia\Oracle_BI1\biapps\lib\*;
C:\obia\Oracle_BI1\biapps\biaodiutil\lib\bia-odi-util.jar oracle.apps.biaodiutil.Import
MODE=SCEREGEN FILEDIR=C:\tmp\Bug22290524_1111101_Generic\
regen_22725263 PLV=BIA_11 JPSCONFIGFILE=C:\Temp\extauth\export\jps-config-
jse.xml SSOFILE=C:\Temp\extauth\export\cwallet.sso

Unix:
<JAVA_HOME>/bin/java \-client \-Xms32m \-Xmx1024m \-classpath
<ODI_HOME>/oracledi.sdk/lib/*:<ODI_HOME>/inventory/Scripts/ext/jlib/*:<ODI_
HOME>/modules/oracle.idm_11.1.1/*:<ODI_HOME>/ modules
/oracle.jps_11.1.1/*:<MW_HOME>/Oracle_BI1/biapps/lib/*;/*:<MW_HOME>/Oracl
e_BI1/biapps/biaodiutil/lib/bia-odi-util.jar oracle.apps.biaodiutil.Import
MODE=SCEREGEN FILEDIR=<PATCH_REGEN_FOLDER>/ regen_22725263
PLV=BIA_11 JPSCONFIGFILE=<JPSCONFIGFILE> SSOFILE=<SSOFILE>

Example:

/scratch/poramali/work/mw701/Oracle_BI1/jdk/bin/java \-client \-Xms32m


\-Xmx1024m \-classpath
"/scratch/poramali/work/mw701/odi9667/oracledi.sdk/lib/*:/scratch/poramali/w
ork/mw701/odi9667/inventory/Scripts/ext/jlib/*:/scratch/poramali/work/mw701/
odi9667/modules/oracle.idm_11.1.1/*:/scratch/poramali/work/mw701/odi9667/
modules/oracle.jps_11.1.1/*:/scratch/poramali/work/mw701/Oracle_BI1/biapps/l
ib/*:/*:/scratch/poramali/work/mw701/Oracle_BI1/biapps/biaodiutil/lib/bia-odi-
util.jar" oracle.apps.biaodiutil.Import MODE=SCEREGEN
FILEDIR=/scratch/poramali/patch/22725263/Bug22725263_1111101_Generic/
regen_22725263 PLV=BIA_11
JPSCONFIGFILE=/scratch/poramali/work/mw701/user_projects/domains/bifoun
dation_domain/odi-client-config/embedded/jps-config-jse.xml
SSOFILE=/scratch/poramali/work/mw701/user_projects/domains/bifoundation_
domain/odi-client-config/embedded/cwallet.sso

Now open a command line on the machine where OBIA is installed and go to
the <PATCH_REGEN_FOLDER>. Then paste the command that you have
prepared above.
It will prompt for the ODI Connection details (Note: These are the same
values you would provide in ODI studio to connect to the ODI repository)

Enter Master Repository JDBC URL: Enter the JDBC Url to connect to the ODI
repository. This is same as the URL you would have in ODI Studio to connect
to the ODI repository.
Sample Value: jdbc:oracle:thin:@hostname:1521:orcl

Enter Master Repository JDBC Driver: JDBC driver to connect to the ODI
repository.
Sample Value: oracle.jdbc.OracleDriver

Enter Work Repository Name: Name of the work repository.


Sample Value: BIAPPS_WORKREP

Enter Master Rep DB Username: Oracle database user for ODI repository
Enter Master Rep DB password: Oracle database password for ODI repository
Enter ODI Username: ODI user name. Please an admin/supervisor user
Enter ODI Password: ODI password

Sample screenshot shown below:

You can monitor the run from the command line messages and the logs in the
<PATCH_REGEN_FOLDER>/regen_22725263/logs folder
Depending on your hardware configuration this step can take 30 min to
couple of hours to complete.

Steps to Revert back the fix


Please follow the below mentioned steps to restore saved KM versions.

Step 1:

Right click on ' IKM BIAPPS Oracle Slowly Changing Dimension, 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 the scenarios again using the same process as mentioned in


Step3: Regenerate Scenarios

Vous aimerez peut-être aussi