SSAUDIT, SSAUDITR

Parameters

SSAUDIT and SSAUDITR enable spreadsheet update logging. The two settings are identical in function except that SSAUDITR automatically clears update log files after archiving, and SSAUDIT appends log files after archiving. The ENDARCHIVE ESSCMD command signals SSAUDITR to clear the log files.

Syntax

The syntax is identical for both settings, so this section uses SSAUDIT for syntax description.

SSAUDIT audit_appname audit_dbname log_path

audit_appname	Application name.
audit_dbname	Database name.
log_path	Directory where you want the information stored.

Default behavior:

• If SSAUDIT is not specified, spreadsheet update logging is not enabled.
• If SSAUDIT is issued with no arguments, Hyperion Essbase activates spreadsheet logging for all databases in all applications on the server, and puts the log in the default directory: ARBORPATH \app\ audit_appname audit_dbname.

You can use a wildcard, xxxxx, to indicate "all" for any argument.

You can issue up to ten (total) SSAUDIT and SSAUDITR statements per application.

Description

SSAUDIT enables Hyperion Essbase to log successfully completed spreadsheet update transactions. The resulting log files can be used as a source of input data upon recovery after archive operations or other server interruptions.

Example

SSAuditR demo

enables logging with refresh (clear) for all databases belonging to the Demo application. The log is stored in the default directory.

SSAudit xxxxx xxxxx c:\sslog

enables logging for all applications and databases, storing the log file in the path c:\sslog. This example assumes that you do not have duplicate database names (see Notes below).

Notes

• For SSAUDIT: If you have duplicate database names in different applications, do not store their error logs in the same directory. If you do, the log file for one database will be replaced by the log file for any subsequent database with the same name.
• SSAUDIT | SSAUDITR creates two log files for each database:
  • audit_dbname.atx, which stores the update transaction records that can be used as the input source for data load
  • audit_dbname.alg, which stores history records from every update transaction, including user name, time stamp, and number of updated rows

• Hyperion Essbase ensures that if you enable spreadsheet logging, updates do not take place without getting logged. If Hyperion Essbase cannot write to the update log files for any reason, Hyperion Essbase fails the update transaction and issues an error message.

See Also

BEGINARCHIVE (ESSCMD)

ENDARCHIVE (ESSCMD)

The Hyperion Essbase Database Administrator's Guide

Copyright (c)1991-2000 Hyperion Solutions Corporation. All rights reserved.