MODIFY AUDITPOINT

Modifies the current audit point information for the DBEnvironment.

Scope

SQLAudit Only

SQLAudit Syntax

SQLAudit >> MOD [IFY] AUDIT [POINT] Audit Point File >> FileName Partition Number >> { ? @ PartNumber DEF [INITION] AUTH [ORIZATION] STOR [AGE] SECT [ION]} Modify Current Audit Point Information (n/y) >> { n [o] y [es]}

Parameters

FileName: is the name of the audit point file containing unloaded SCR (or transaction) information. This file would have been created by running SQLAudit on the master DBEnvironment. If no audit point filename is entered, SQLAudit will delete transaction (SCR) information for the specified list of partitions.
PartNumber: is the number for a partition for which you wish to modify the transaction information.
NO or YES: respond NO if you do not want to modify the current audit point information in the DBE; respond YES if you do want to modify the current audit point information in the DBE.

Description

This command should only be used for ALLBASE/REPLICATE DBEnvironments, and it should only be necessary during hard resynchronization of a given set of partitions. This command should not be necessary for audit only DBEnvironments that are not using ALLBASE/REPLICATE.
This command is used to modify the current audit point information to reflect new transaction information for the specified set of partitions. This command can be used in two different ways. The first way it can be used is to replace the transaction information for the given set of partitions with new transaction information from the audit point file entered. The second way it can be used is to delete transaction information for a given set of partitions. This command can be used while the DBEnvironment is in use.
If the user enters an audit point filename, SQLAudit will replace the DBEnvironment transaction (SCR) information with information from the audit point file (for the given set of partitions). This file is assumed to have been created by running SQLAudit against the master DBEnvironment (using the GET AUDITPOINT command). If no transaction information is found in the audit point file for a specified partition, the transaction information for the partition will be deleted from the DBEnvironment. The audit point information from the file will be used to list the current set of partitions.
If the user did not enter an audit point filename, SQLAudit will delete all transaction information for the user specified list of partitions. If no audit point filename is entered (the user just pressed RETURN), SQLAudit will retrieve the current audit point information from the DBEnvironment. This audit point information will be used to list the current set of partitions.
You must be connected to the DBEnvironment to use this command. If you have not connected to the DBE (using the SET DBENVIRONMENT command), SQLAudit will issue a warning and automatically issue the SET DBENVIRONMENT command on your behalf.

Authorization

You must have DBA authorization in order to use this command.

Example

   SQLAudit >> modify auditpoint



   Audit Point File >> MasterPt



   System Partitions are DEF[INITION], AUTH[ORIZATION], STOR[AGE] or SECT[ION].

   Please enter Partition Numbers or System Partitions.  Type @ for all,

   ? for a list of Partitions, or RETURN to quit.



   Partition Number >> 1

   Partition Number >> 2

   Partition Number >>

   Modify Current Audit Point Information (n/y) >> yes



   Current audit point information has been modified.



   SQLAudit >> 





   SQLAudit >> modify auditpoint



   Audit Point File >> 



   Audit point information will be deleted for the specified partitions.





   System Partitions are DEF[INITION], AUTH[ORIZATION], STOR[AGE] or SECT[ION].

   Please enter Partition Numbers or System Partitions.  Type @ for all,

   ? for a list of Partitions, or RETURN to quit.



   Partition Number >> 3

   Partition Number >>

   Modify Current Audit Point Information (n/y) >> yes



   Current audit point information has been modified.



   SQLAudit >>