SSAUDITR configuration applies only to block storage (BSO) databases, and does not apply to aggregate storage (ASO) databases.

Syntax

SSAUDITR appname [dbname [log_path]]

• appname—Application name.

• dbname—Optional. Database (cube) name.

• log_path— Optional. Full directory path where you want the information stored. Do not specify a log_path value unless you have also provided a value for dbname.

Default behavior:

• If SSAUDITR (or SSAUDIT) is not specified, grid update logging is not enabled.

• If SSAUDITR (or SSAUDIT) is specified with no arguments, Essbase activates grid update logging for all cubes in all applications on the Essbase Server, and puts the log in the default directory: <Application Directory>/app/appname/dbname.

  See Environment Locations in the Essbase Platform for information about directory locations in Essbase.

Use the value xxxxx to indicate "all" for any argument.

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

Notes

• SSAUDITR creates two logs for each cube: dbname.atx, which stores the update transaction records that can be used as the input source for data load, and dbname.alg, which stores history records from every update transaction, including user name, time stamp, and number of updated rows.

• Essbase ensures that if you enable grid update logging, updates do not take place without getting logged. If Essbase cannot write to the update logs for any reason, the update transaction failes and an error message is issued.

• SSAUDITR may slow grid client data-update operations.

• The update log file will not be cleared if the cube is shut down during archive mode. The cube is expected to remain running while in archive mode.

Example

SSAuditR demo

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

See Also

SSAUDIT, which does not clear the logs after archive.

Alter Database begin | end archive (MaxL)