TRANSACTIONLOGLOCATION

Specifies whether to enable write transaction logging and specifies an existing directory on Essbase Server for the transaction log store.

Transaction logging and replay, used with the automated backup and restore feature, facilitates recovery of an Essbase block storage database. Transaction logging and replay does not apply to aggregate storage databases. See the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide.

Syntax

TRANSACTIONLOGLOCATION [appname [dbname]] LOGLOCATION NATIVE ENABLE | DISABLE

appname—Optional. Specifies the application for which transaction logging and replay is to be enabled.
If you specify a value for appname and do not specify a value for dbname, the setting applies to all databases in the specified application.
To enable the setting for a specific database, you must specify an application and database.
If you do not specify an application, you cannot specify a database. If you do not specify an application and database, the setting is global and applies to all databases on Essbase Server.
dbname—Optional. Specifies the database, in the application specified by appname, for which transaction logging and replay is to be enabled.
If you specify a value for dbname but do not specify a value for appname, your specification is ignored.
LOGLOCATION—Specifies the directory in which the transaction log store is written.
Oracle recommends specifying multiple log locations.
Note:
Oracle recommends using a physical disk other than the disk on which the ARBORPATH directory or disk volumes reside.
NATIVE—Specifies a reserved field.
Note:
Do not change the NATIVE value.
ENABLE | DISABLE—Specifies whether to enable or disable transaction logging.

You must restart Essbase Server to initialize any change to the configuration file.

Description

You can use multiple TRANSACTIONLOGLOCATION statements to enable transaction logging at a more global level and, at the same time, disable logging at a more granular level. In the essbase.cfg file, the more global enabling statement must precede the more granular disabling statement for the override to take effect.

Note:

If transaction logging is enabled for an application or database that you later rename or copy, you must enable logging for the renamed or copied application or database and you must use the same path that is specified in the TRANSACTIONLOGLOCATION setting.

Example

TRANSACTIONLOGLOCATION Sample C:\Hyperion\trlog NATIVE ENABLE

Enables transaction logging for all databases associated with the Sample application and writes the log store to the trlog directory.

TRANSACTIONLOGLOCATION Hyperion/trlog NATIVE ENABLE
TRANSACTIONLOGLOCATION Sample Hyperion/trlog NATIVE DISABLE

The first statement enables transaction logging for all applications and their associated databases on Essbase Server; the second statement disables transaction logging for all databases associated with a specific application (Sample).

TRANSACTIONLOGLOCATION Sample Hyperion/trlog/Sample NATIVE ENABLE
TRANSACTIONLOGLOCATION Sample Basic Hyperion/trlog/Sample NATIVE DISABLE

The first statement enables transaction logging at the application level (Sample); the second statement disables transaction logging for a specific database (Basic) in the application.