Table import tips and troubleshooting

The following items describe important information concerning importing data using the staging tables.

• The staging table import commands that perform integrity checks require the server to be at the maintenance run level. This run level prevents users from logging in to the PolicyCenter application.
• PolicyCenter runs the load process inside a single database transaction to be able to roll back if errors occur. The load process may require a large rollback space. Run the import in smaller batches, for example, a few thousand records at time, if you are running out of rollback space.
• As with any major database change, make a backup of your database prior to running a major import.
• After loading staging tables, update database statistics on the staging tables. Update database statistics on all the operational tables after a successful import. After a successful import, PolicyCenter provides table-specific update database statistics commands in the cc_loaddbstatisticscommand table. You can selectively update statistics on only the tables that actually had data imported, rather than for all tables.
• Always run database consistency checks on the operational database tables both before and after table imports. If there were no consistency errors before importing, new consistency errors after importing data indicate that the staging table data contained errors that integrity checks did not detect.
• During PolicyCenter upgrade, the PolicyCenter upgrader tool may drop and recreate staging tables. This activity occurs for any staging table for which the corresponding operational table changed and requires upgrade.

  Never rely on data in the staging tables remaining across an upgrade. Never perform a database upgrade during your import process.