Bookshelf Home | Contents | Index | Search | PDF

Siebel Data Warehouse Installation and Administration Guide > Administering and Troubleshooting the Siebel Data Warehouse > Administering the Informatica Repository >

Troubleshooting the ETL Process

---

To troubleshoot ETL

If the load process fails, stop it by right-clicking the batch name that is executing (for example, Refresh DataMart) and choosing Stop.
Check the log in \PowerMart Server\SessLogs. You should see the error in the log file.
If you receive the Server Manager error message, "The system cannot find the file specified," the session log files have not been set up properly.

You may need to change the text editor.

If the log does not show enough information to solve the problem, check the Event Viewer by going to Start > Control Panel > Administrative Tools > Event Viewer.
Click on Application Log and look at the most current messages.
Restart the batch process after fixing problems.
After fixing the problem, find the last entry of RestartNextBatch # before the failed session, and restart the batch process from that point. Continue monitoring the load process.

The process should start from the point it was stopped.

Deadlock or Timeout While Running ETL (DB2)

In DB2, a heavy read/write load on the OLTP database (Siebel transactional database) can cause deadlock or timeout problems in the ETL process. You can work around this problem by changing the registry settings on the Informatica server machine (Data Warehouse Server) so that Informatica can perform a "dirty read."

To change Data Warehouse Server registry settings in Windows

Run regedt32.
Go to the following path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ PowerMart\Parameters\MiscInfo

Click on Edit and select New String Value. Add Value as DB2Isolation.
Double-click on Set its value to 1.

To change Data Warehouse Server registry settings in UNIX

Open pmserver.cfg.
Add DB2Isolation=1.
Save and close pmserver.cfg.

NOTE:  It is important that this change be evaluated carefully. Even if you roll back an OLTP batch load process, the data may be loaded by the ETL process into the Siebel Data Warehouse. It is better to minimize OLTP load processes when ETL is in progress.

Bookshelf Home | Contents | Index | Search | PDF