Load staging table data into operational tables

After there are no errors in integrity checks, you can load data into operational tables from staging tables.

Before you begin

Perform these tasks after integrity checks succeed for all records except for logical units of work (LUW) records in the exclusion table. Then, delete the LUWs that relate to records in the exclusion table. At this point, you can load data from the staging tables into the operational tables used by PolicyCenter.

Procedure

  1. Update the database statistics for the staging tables. Use the TableImportAPI web service method updateStatisticsOnStagingTablesAsBatchProcess or the table_import command prompt tool. For example, run the following command at a command prompt. 
    table_import -password password -updatedatabasestatistics -batch
    Note: The -batch option does not wait until the started process completes before returning. Instead, it returns immediately and prints the ID of the started process (PID). The process caller is responsible for waiting for the process to complete before taking further action.
  2. In a cluster installation, shut down all PolicyCenter servers except one. Use the system_tools command prompt tool or the web service SystemToolsAPI.scheduleShutdown method.
  3. Set the one running PolicyCenter server to the maintenance run level. Use the system_tools command prompt tool or the web service SystemToolsAPI.setRunLevel method.
  4. Load staging table zone data into operational zone tables. To load only zone table data, use a method that begins with integrityCheckZoneStagingTableContentsAndLoadZoneSourceTables on the TableImportAPI web service API. Alternatively, use the table_import command prompt tool with the -integritycheckandload option. PolicyCenter inserts data rows into the operational zone tables and results information into the load history table.
    • For an Oracle database, take instrumentation snapshots before and after running the integrity check and load. Generate database instrumentation reports to identify performance problems.
    • For an Oracle database, if the operational tables contain no records or few records, use the load option to estimate database statistics, as shown in the following command.
      table_import -password password -integritycheckandload -estimateorastats -zonedataonly
    • For a non-Oracle database or an Oracle database that already contains many records, use the following command.
      table_import -password password -integritycheckandload -zonedataonly
  5. Set the server to the multiuser run level. Set each PolicyCenter server to the multiuser run level by using the system_tools command prompt tool or the web service SystemToolsAPI.setRunLevel method.