TRANSACTIONLOGLOCATION

This Essbase configuration setting specifies whether to enable write transaction logging, and specifies an existing directory on Essbase Server for the transaction log store.

Transaction logging and replay facilitates recovery of an Essbase block storage cube. Transaction logging and replay does not apply to aggregate storage cubes.

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 cubes in the specified application.

To enable the setting for a specific cube, you must specify an application and cube.

If you do not specify an application, you cannot specify a cube. If you do not specify an application and cube, the setting is global and applies to all databases on Essbase Server.
dbname—Optional. Specifies the database (cube), 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.

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

On Windows, you can specify the location using Uniform Naming Convention (UNC) syntax, which is \\ComputerName\SharedFolder\Resource. Use UNC syntax only if <Application Directory> is also specified in UNC. Mixed path types are not supported.
NATIVE—A reserved field. Do not change this value.
ENABLE | DISABLE—Specifies whether to enable or disable transaction logging.

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

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 configuration, 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:\logs\trlogs NATIVE ENABLE

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

TRANSACTIONLOGLOCATION logs/trlogs NATIVE ENABLE
TRANSACTIONLOGLOCATION Sample logs/trlogs NATIVE DISABLE

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

TRANSACTIONLOGLOCATION Sample logs/trlogs/Sample NATIVE ENABLE
TRANSACTIONLOGLOCATION Sample Basic logs/trlogs/Sample NATIVE DISABLE

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

TRANSACTIONLOGLOCATION Sample Basic \\machine-name\shared\loglocation NATIVE ENABLE

Enables transaction logging for Sample Basic and writes the log store to the specified shared location.