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

By default, Essbase does not create a log file to track data loaded to renegade members. If RENEGADELOG is set to true, Essbase creates a log file in the Essbase logs directory. The log file name is renDataload_<filename>_<timestamp>.log for non-SQL data loads and renDataload_SQL_<timestamp>.log for SQL-based data loads.

The log file records the data value loaded to the renegade member. If more than one member in a given data load is missing for a dimension with renegade members enabled, the log file lists only one value. Information on the remaining missing data values is provided in comments.

Syntax

RENEGADELOG [appname [dbname]] TRUE | FALSE

• appname—Application name. Optional parameter for applying the TRUE or FALSE setting to one or all cubes within the application. 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. If you do not specify an application, you cannot specify a cube, and the setting applies to all applications and cubes on the Essbase Server.

• dbname—Database (cube) name. Optional parameter for applying the TRUE or FALSE setting to the specified cube within the specified application. If you do not specify a value for dbname, the setting applies to all cubes within the specified application. If appname is not specified, you cannot specify dbname.

• TRUE—Creates a log file to track data loaded to renegade members.

• FALSE—No log file is created. This is the default value.

Example

RENEGADELOG TRUE

See Also

RENEGADELOGLIMIT

Renegade Members in Aggregate Storage Data Loads