HP 3000 Manuals HP 3000 Manuals
GET AUDITPOINT
Determines the current audit point information and places it in a file.
Scope
SQLAudit Only
SQLAudit Syntax
SQLAudit >> GE[T] AUDIT[POINT] Audit Point File >> FileName Lock Log
for Audit Point (n/y) >> {n[o] } Display Audit Point Information (n/y)
{y[es]}
>> {n[o] }
{y[es]}
Parameters
FileName is the name of the audit point file to be
created. If the file already exists, you are
prompted whether to purge and overwrite the file.
Enter FileName in all uppercase letters if you
wish to see the file from within SQLAudit.
NO or YES respond NO if you do not want to lock the log
files; respond YES if you do want to lock the log
files with the current audit point information.
NO or YES respond NO if you do not want to view the audit
information; respond YES if you do want to view
the current audit information.
Description
* This command is used to retrieve the current audit point
information and place it into a file. This command can be used
while the DBEnvironment is in use.
* Audit information is retrieved for all partitions in the
DBEnvironment that have had transactions committed. Identifying
information is also placed in the audit point file.
* When the file is created, the file permissions are set to restrict
access to other users. In other words the file is created such
that it is readable only by the user who created it. If the DBA
who created the file wishes to allow others to access the file, it
will be up to the DBA to change the files' permissions.
* If desired, you can lock the log files according to the current
audit point information. If locked, all transactions committed
after this command are protected from being overwritten until the
lock is changed or removed. Log locks can be changed through the
commands GET AUDITPOINT and LOCK AUDITPOINT. Log locks can be
removed through the command UNLOCK AUDITPOINT, or using the SQL
command START DBE NEWLOG.
* If you specify that the log files are to be locked, any previously
defined log locks are replaced by the new audit point log lock.
In other words, only one audit point can be locked in the log
files at any one time.
* 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 issues a warning and automatically issues the
SET DBENVIRONMENT command.
Authorization
You must have DBA authorization in order to use this command.
Example
SQLAudit >> get auditpoint
Audit Point File >> STARTPT
Lock Log for Current Audit Point (n/y) >> yes
Display Current Audit Point Information (n/y) >> no
SQLAudit >>
Refer to the SHOW AUDITPOINT command for an example of the display of
current audit point information.