TRANSACTIONLOGDATALOADARCHIVE

Specifies the type of data to archive when logging transactions. By default, Essbase archives only data load and rules files for client data loads.

During transaction logging, Essbase creates archive copies of data load and rules files in the following directory:

ARBORPATH/app/appname/dbname/Replay

These files are then used during the replay of a logged transaction.

To enable transaction logging and replay, use the TRANSACTIONLOGLOCATION configuration setting.

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

TRANSACTIONLOGDATALOADARCHIVE [appname [dbname]] [OPTION]

appname—Optional. Specifies the application for which to archive the data and rules associated with logged transactions.
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 to archive the data and rules associated with logged transactions.
If you specify a value for dbname but do not specify a value for appname, your specification is ignored.

OPTION—Valid values are as follows:

CLIENT: (Default) Archives data load and rules files for client data loads.

SERVER: Archives data load and rules files on the server and SQL-server data loads.

Caution!

Server data loads are replayed using the data load and rules files that are archived on the server in the Replay directory. Do not rename these files. Also, if the contents of the data load and rules files are changed before the replay operation, the modified data is used during replay. Therefore, the data in the recovered database will not be the same as the original data.

SERVER_CLIENT: Archives server and client data.
NONE: No data is archived.
If you select NONE and use client data, Essbase cannot replay the data load. In this case, to recover transactions, you must manually load the client data before you replay the remaining transactions.
If you use server or SQL data, and the data and rules files are not archived in the Replay directory (for example, you did not use the SERVER or SERVER_CLIENT option), Essbase replays the data that is currently in the data source, which may or may not be the data that was originally loaded.

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

Example

TRANSACTIONLOGDATALOADARCHIVE SERVER_CLIENT

Archives server and client data for all databases on Essbase Server.