Bookshelf: Informatica and Loading Issues

Siebel Data Warehouse Installation and Administration Guide > Troubleshooting the Siebel Data Warehouse > Running the Data Migration Workflow for Preconfigured Siebel Industry Applications Content >

Informatica and Loading Issues

Double-click the workflow to view the log file details.

Problem. Double-clicking the workflow yields a Workflow Manager error message: "The system cannot find the file specified."

Probable Cause. The session log files are not set up properly. You also may need to change the text editor.

Problem. Using Oracle, some mappings hang when running when performance statistics are switched on.

Probable Cause. When running some Informatica mappings for loading the Siebel Data Warehouse, turning on the Performance Statistics can cause the mapping to hang. The only workaround is to increase the values of the LMSharedMemory and MaxSessions variables in Informatica. The risk of increasing the LMSharedMemory too much is that it may start to have a serious effect on overall performance of the machine that the Informatica server is running on.

Problem. When you execute a workflow on the Informatica Workflow Manager, you get the following error message:

"Request to start workflow (workflow name) on server (server name) not successful."

Probable cause. This can happen due to a server time-out property that is usually set to 20 or 40 seconds. When you try to run a large workflow, every session in that workflow is fetched into the server's memory. If this takes longer than the server time-out property, the server returns a message that the workflow was unable to run. However, the workflow is running, but the server just needs time to complete fetching the sessions into memory. Double-click the workflow to view the log file details.

Problem. When running Full_Extract_Siebel_DW or Refresh_Extract_Siebel_DW, Informatica returns errors similar to:

TE_7007 Transformation Evaluation Error; current row skipped...

TE_7007 [<<Transformation Error>> [to_date]: Date function error to_date('19010101', 'DD-MON-YYYY')

Probable cause. Incorrect date entry in the SME Date Format field in the System Preferences. The format is YYYYMMDD.

Problem. When running Full_Load_Siebel_DW, Informatica returns errors similar to:

CMN_1014 Error creating semaphore...

TM_6006 Error initializing DTM for session...

TM_6006 [s_CR18a1. Load W_PROG_DM_TMP - Program Records]

Probable cause. Insufficient semaphores allocated. Allocate more semaphores on the Data Warehouse Server. The change becomes effective when you reboot.

Problem. Informatica (RDBMS is DB2) gives this error message:

Error occurred unlocking [SDE_ServiceRequestDimension1].

An error occurred while accessing the repository[[IBM][CLI Driver][DB2/6000] SQL0955C

Sort memory cannot be allocated to process the statement. Reason code = "".

SQLSTATE=57011]

DB2 Fatal Error[FnName: ExecuteDirect -- SQLSTATE=57011 [IBM][CLI Driver][DB2/6000]

Probable cause. The DB2 parameter "SHEAPTHRES" is too small.

Problem. Informatica produces the error "Unable to connect to the server" when running a full load of the Siebel Data Warehouse (Full_Load_Siebel_DW_Dimensions).

Probable cause. The last Designer session was not validated. Part of the development process of working with Designer is to always validate any changes to Informatica mappings definitions and sessions after the change is saved in repository.

Problem. When loading the data warehouse, Informatica reports a lock problem.

Probable cause. Either someone has a session open or there is a dead session. Make sure no one has any open sessions. If no sessions are open, then follow the Informatica documentation on removing locks caused by dead sessions.

Problem. After changing an Informatica mapping, you may get an error message when trying to execute "Full_Load_Siebel_DW_Facts." The error message is "Unable to connect to the server."

Probable Cause. This is due to Informatica mapping objects that have been modified and this does not automatically validate the session objects. You must validate all changes to any existing mappings in the Informatica repository.

Problem. Session SDE_RecordLoadStart fails due to unique constraint error while executing Full_Load_Siebel_DW_Dimensions or Full_Load_Siebel_DW_Facts.

Probable Cause. This could be because the previous full load did not complete successfully. Fix the problem that caused the previous load session to fail. Make sure you start the process from last entry of Load_RestartNextWorkflow # before the failed session, and restart the workflow process from that point.

If you have to reextract the data from the Siebel transactional database because something had to be fixed in source database to resolve the load error then you must restart the ETL process. Truncate S_ETL_INC_STAT in the Siebel transactional database, then enable the Extract and Load workflows and rerun them.

Problem. Session SDEINC_RecordExtractStart fails due to unique constraint error while executing a Refresh workflow.

Probable Cause. This could be because the previous load or refresh did not complete successfully. Fix the problem that caused the previous refresh session to fail. Make sure you start the process from last entry of %RestartNextWorkflow # before the failed session, and restart the workflow process from that point.

Problem. The session fails and you receive the following error code:

Error "TE_7042 Aggregate Error: File Operation Error

Probable Cause. This is due to a disk space limitation. Check the /Informatica/PowerMart/Cache/Check directory for available disk space, also check the limits (ulimit) of the account used to start PowerMart.

Problem. Informatica sessions get deadlocked and eventually fail when they try to do a "select" from the repository table OPB_OBJECT_LOCKS. This problem sometimes occurs on MSSQL server databases.

Probable Cause. This is possibly caused by a limited number of resources on the MSSQL Database Server. The workaround is to execute the following MSSQL specific SQL command on the Siebel Data Warehouse:

DROP INDEX OPB_OBJECT_LOCKS.OPB_OBJ_LOCKS_IDX

DROP INDEX OPB_OBJECT_LOCKS.OPB_OBJ_LOCKS_IDX2

DROP INDEX OPB_OBJECT_LOCKS.OPB_OBJ_LOCKS_IDX3

Upon completion of executing these commands, proceed executing the workflow processes to load the Siebel Data Warehouse.

Problem. An error may occur when trying to send a post session email notification using MS Outlook 2000. Refer to Informatica release notes for further information.

Probable Cause. After installing Informatica Server on Windows, copy the file mapi32.dll from winnt\\system32 to the bin folder where the Informatica Server is installed, overwriting the existing mapi32.dll in that directory. Start the Informatica Server so that the Informatica Server can use the new mapi32.dll.

The Extended MAPI Error. MAPILogonEx failed[2147746065] error indicates that the logon is not configured correctly. Check the following:

Under Services > Informatica> Logon, make sure the login (domain\username) and password are correct.
Under Control Panel > Mail (it may also be called Mail and Fax or Exchange) > Services > Show Profiles, make sure the mail profile is correct.
Under Programs> Informatica Server > Informatica Server Setup> Miscellaneous, make sure the MS Exchange profile is correct.

Problem. While creating a custom session, bulk load mode does not work properly with SQL Server.

Probable Cause. Change the mode to "normal" in Informatica repository for the session. The "normal" mode must be used everywhere for SQL Server in all of your custom sessions.

Problem. When running IMR, you may receive an error message box which states "The evaluation period for this Oracle ODBC driver has expired. Please call Merant to obtain a production version of this Oracle ODBC driver."

Probable Cause. This is caused by a down-level ODBC driver license key. Rename or move ivodbc.lic, lvodbc.lic (if it exists), and lvdw.lic (if it exists). Make sure you have only one license file named ivdw.lic in winnt\system32. This eliminates the problem.

Problem. Outlook closes when sending out a notification of finishing the ETL process.

Probable Cause. Informatica is closing Outlook. This issue is known to Informatica and is scheduled to be resolved in an upcoming release. Until then, create a second profile in Outlook and add that profile name to the Informatica server setup.

Siebel Data Warehouse Installation and Administration Guide
Published: 11 March 2004