1. Scripting Reference for Oracle Essbase
  2. MaxL
  3. MaxL Statements
  4. MaxL Statement Reference
  5. Export LRO

Export LRO

The MaxL export lro statement helps you export linked-reporting-object information, and binary files if the Essbase cube has file-type LROs, to a directory.

Syntax


Description of exportlr.gif follows
Description of the illustration exportlr.gif

You can export LRO information from a cube in the following ways using export lro.

Keywords

to server directory

Export the LRO information to a directory you specify on the Essbase Server to which you are connected.

to local directory

Export the LRO information to a directory you specify.

Notes

  • This statement requires the cube to be started.

  • MaxL creates exactly one export directory; it does not create a directory structure. For example, if c:\temp exists, MaxL will create c:\temp\exports, but not c:\temp\exports\to\this\long\path.

  • If the specified export directory already exists, the export LRO statement will fail. This is a safeguard against overwriting existing export directories.

  • If you do not specify a full path for an export directory to be created on the client or server, MaxL uses your short directory specification (DBS-EXPORT-DIR) as a suffix, and creates the destination export-directory in the <Application Directory>/app directory with a prefix of appname-dbname-. If you do specify a full path, MaxL creates whatever directory you specify.

    If you do not know where Application Directory is in your environment, refer to Environment Locations in the Essbase Platform.

  • Relative paths (for example, '../exports/lros') are not supported.

  • The export directory and .exp file are visible on the Essbase server machine, but are not in the Files catalog in Essbase web interface.

  • When MaxL exports LROs from a cube, if the cube is from a Unicode-mode application, the exported LRO-catalog file is encoded in UTF-8. You cannot use UTF-8-encoded export files from a Unicode-mode application to import LROs to a non-Unicode mode application.

  • The exported lros can be imported into a cube using import lro.

Example

export database sample.basic lro to server directory '/scratch/exports/lros';

Exports LRO-catalog information, and binary files if the cube has file-type LROs, to a server directory lros, under /scratch/exports/. The statement will fail unless /scratch/exports/ already exists. The directory contains file-type LROs, if applicable, and the LRO-catalog export file lros.exp. These can be brought back into a cube using import lro. The export directory and .exp file are visible on the Essbase server machine, but are not in the Files catalog in Essbase web interface.

The example will work only once, because MaxL will not overwrite the existing directory. 

export database sample.basic lro to server directory 'exportedLROs';

Exports LRO-catalog information, and binary files if the cube has file-type LROs, to a server directory <Application Directory>/app/sample-basic-exportedLROs. The directory contains file-type LROs, if applicable, and the LRO-catalog export file named sample-basic-exportedLROs.exp. These can be brought back into a cube using import lro.

The example will work only once, because MaxL will not overwrite the existing directory. 

export database sample.basic lro to local directory 'C:\\EssbaseMaxL\\myexports';

The example above exports LROs to a local directory on a Windows MaxL client. The statement succeeds only if directory C:\EssbaseMaxL exists.