Bookshelf v7.5.2: Performing a Refresh Load of the Siebel Data Warehouse

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

Performing a Refresh Load of the Siebel Data Warehouse

Once the full extract and load has completed, you can do a refresh load. This saves time because only the General tables and the Hierarchy tables are truncated and reloaded. The Refresh load extracts only data modified or created after the previous extract from the Siebel Transaction Database.

NOTE: Make sure all your mobile users have synchronized their data before running a load. If they have not synchronized, the load will not contain their data. Any data synchronized late will be captured in later loads.

Incremental Load Optimizer Settings in Oracle

When doing incremental loads with Oracle Data Warehouse only, the optimizer rule should be switched to Cost based in the init.ora parameters after analyzing all the data warehouse W_* tables (that is, OPTIMIZER_MODE ALL_ROWS.).

To do a refresh load

Make sure the Informatica service is up and running.

Make sure that no clients are accessing reports.

Run the Informatica Server Manager and connect to the repository using the Administrator account.

Open the Siebel_DW_Rep folder.

(Optional, but recommended.) Right-click the batch named Exception_Reports and start it. When it completes, view the results in the Siebel Analytics' Analytics Administration view. For more information, read Using the Exception Report and Diagnostic Views.

Repeat Steps 7-10 for each of the following batches.

Refresh_Extract_Siebel_DW_Dimensions

Refresh_Load_Siebel_DW_Dimensions

Refresh_Load_Siebel_DW_Facts

Refresh_Load_Siebel_SCD (Optional, if you want to track the Dimensions described in Table 6 by the attributes)

Load_Aggregates

Load_Pipeline (Optional, but running this once a week is recommended)

Visibility_Refresh (Optional, if you want data level security to be refreshed)

Right-click the batch and start it.

Monitor the load process. For information on monitoring, read Informatica's Administrator Guide.

If the load process fails, stop it by right-clicking the batch name and choosing Stop. Check the log and fix 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.

Using the Informatica Server Manager, you can schedule the refresh loads to occur at specific intervals, such as daily, weekly, monthly, or any desired time period.