Professional Documents
Culture Documents
uk
OBIA 7.9.6.2 Advanced Instructions Problems and Diagnostics By Shahed Munir & Krishna Mohan 1. Find Database Character sets for both source and destination databases this can be achieved by running a NLS_CHARACHTER_SET query from sql developer in both databases
CLICK ON
2. We need to login to The informatica Server and Create some variables and change some settings as below Login to Informatica Server
Next change ValidateDataCodePages to NO For this change the Informatica server operating mode might need to be changed to safe mode then change this property and Re-enable back to normal mode.
Make sure both the DAC Server and Informatica servers are bounced
PATCHES Next we need to apply a Patch to DAC to correct a few problems that will occur with the workflows Patch Number : 10052370 Cumulative Patch DAWSystem.jar file infa_command.xml The patch updates the above two files The dac server might need restarting a couple of times. You can now run the Relevant Subject Areas
Login to Here click on Click on Repository in Green GOTO EDIT IN TOP MENU AND TRUNCATE LOG To Check logs you must login to Informatica Workflow Monitor and view the relevant session logs. Double Click Integration service to view all run or running tasks
Then click on the cog icon Right Click Get Session Log
If the error is not here then we have to check the DAC Server Log
- Then find execution Plan that has failed or run Right Click Get Run Information Get Server Log This will generate a DAC Server log Very detailed log on any Index errors or duplicate value problems
Subject Area Problems on VIS HR Analytics - Workforce 1. We encountered a problem in Per_all_people_f where one employee has a duplicate problem this is covered in OBIA 7.9.6 Installation Paper 2. The Second Problem was with W_GEO_D Table where there are duplicate entries. You will have to find the source or delete the duplicate records in this table. 3. We did get some TNS Errors this might have been due to our servers running slow. We just re-submitted again after failure and it corrected itself.