Last Update: 28 April 2008
Product: SQDR Plus for iSeries
Version: 3.0 or later
Article ID: SQV00PL003
Restoring or migrating a database that is currently being monitored by SQDR Plus may result in higher than normal CPU usage on the iSeries system. The high CPU usage results from the journal receiver processing that must occur after the database is restored.
This document describes a technique that will help minimize the processing required after restoring or migrating a database that is being monitored by SQDR Plus. The procedures described below cause SQDR to run baseline replications of all the incremental replication subscriptions instead of processing all the journal receivers produced by the restore operation. This is much more efficient than allowing incremental replication changes to be applied after the entire database is replaced and will result in much less CPU utilization.
ENDSBS SBS(SQDR) OPTION(*CNTRLD)
DELETE FROM SQDR.SQ_READERS
Note: if executing the SQL statement using an interactive SQL session (STRSQL) set to the “*SYS” style naming convention, execute the following statement instead:
DELETE FROM SQDR/SQ_READERS
STRSBS SBSD(SQDR/SQDR)
The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization. The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.