LiteSpeed Engine for Oracle 1.3 User Guide - Quest Software

LiteSpeed ® Engine 

for Oracle (LEO) 

User Guide 

Release 1.3.0

© 2009 Quest Software, Inc. ALL RIGHTS RESERVED. 

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a 

software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the 

applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or 

mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written 

permission of Quest Software, Inc. 

If you have any questions regarding your potential use of this material, contact: 

Quest Software World Headquarters 

LEGAL Dept 

5 Polaris Way 

Aliso Viejo, CA 92656 

www.quest.com 

email: legal@quest.com 

Refer to our Web site for regional and international office information 

Disclaimer: The information in this document is provided in connection with Quest products. No license, express or implied, by 

estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. 

EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS 

PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY 

WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF 

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE 

LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, 

WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) 

ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE 

POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness 

of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time 

without notice. Quest does not make any commitment to update the information contained in this document. 

Trademarks 

Quest, Quest Software, and LiteSpeed are trademarks of Quest Software, Inc. Other trademarks and registered trademarks used in 

this guide are property of their respective owners. 

Third Party Contributions 

Please refer to the Release Notes for current 3 rd party contributors. 

LiteSpeed Engine for Oracle 1.3.0 

Updated: November 12, 2009

Table of Contents 

UNIX Installation, etc. .......................................................................................................................................... 1 

Installing ................................................................................................................................................................... 1 

Uninstalling ............................................................................................................................................................... 1 

Upgrading LEO ......................................................................................................................................................... 1 

Checking the installation status ................................................................................................................................ 1 

Windows Installation, etc. ................................................................................................................................... 3 

Installing ................................................................................................................................................................... 3 

Uninstalling ............................................................................................................................................................... 3 

Upgrading LEO ......................................................................................................................................................... 3 

Checking the installation status ................................................................................................................................ 3 

Understanding LEO concepts ............................................................................................................................ 5 

Compression levels .................................................................................................................................................. 5 

Encryption methods .................................................................................................................................................. 5 

Locating the UNIX installation directory ................................................................................................................... 5 

Locating the Windows installation directory ............................................................................................................. 5 

Using the Command Line Interface .......................................................................................................................... 6 

Launching the Command Line Interface on UNIX .................................................................................................... 6 

Launching the Command Line Interface on Windows .............................................................................................. 6 

Using the Windows Graphic User Interface ............................................................................................................. 6 

Oracle lib directory ................................................................................................................................................... 7 

Oracle bin directory .................................................................................................................................................. 7 

Understanding LEO configurations ................................................................................................................... 8 

Managing configurations .................................................................................................................................... 9 

Viewing configurations ............................................................................................................................................. 9 

Changing the default configuration .......................................................................................................................... 9 

Setting-up multiple configurations ............................................................................................................................ 9 

Editing the configuration settings for an ORACLE_SID ........................................................................................... 9 

Verifying a configuration ........................................................................................................................................... 9 

Removing the configuration for an ORACLE_SID ................................................................................................. 10 

Obtaining an encryption key for your password ..................................................................................................... 10 

Managing configurations with the Windows Configuration Editor ............................................................... 11 

Viewing configurations ........................................................................................................................................... 11 

Changing the default configuration ........................................................................................................................ 11 

Setting-up multiple configurations .......................................................................................................................... 11

Editing the configuration settings for an ORACLE_SID ......................................................................................... 11 

Viewing history, statistics, etc, ......................................................................................................................... 13 

Viewing history ....................................................................................................................................................... 13 

Viewing file statistics .............................................................................................................................................. 13 

Viewing the log file ................................................................................................................................................. 13 

Viewing the log file using the Windows Configuration Editor ................................................................................. 13 

Viewing catalogue contents for NetBackup ............................................................................................................ 13 

Viewing cache directory info for NetBackup ........................................................................................................... 13 

Manual file compression and encryption ........................................................................................................ 15 

Compressing files ................................................................................................................................................... 15 

Compressing and encrypting files .......................................................................................................................... 15 

Uncompressing files ............................................................................................................................................... 15 

Uncompressing and decrypting files ...................................................................................................................... 15 

Using EXP/IMP with LEO ................................................................................................................................... 16 

Exporting with EXP and LEO ................................................................................................................................. 16 

Configuring EXP file compression and encryption on-the-fly ................................................................................. 16 

Importing with IMP and LEO .................................................................................................................................. 17 

Using LEO with hot/cold backups .................................................................................................................... 18 

Using RMAN and LEO ....................................................................................................................................... 19 

Configuring RMAN to work with LEO ..................................................................................................................... 19 

Performing a backup with RMAN and LEO ............................................................................................................ 19 

Saving configuration parameters in the file name .................................................................................................. 19 

Restoring using RMAN and LEO ........................................................................................................................... 20 

Using Tivoli Storage Manager and LEO ........................................................................................................... 21 

Overview ................................................................................................................................................................ 21 

Pre-requisites ......................................................................................................................................................... 21 

Configuring LEO for use with TSM ......................................................................................................................... 21 

Configuring LEO for use with TSM using the Configuration Editor ........................................................................ 22 

Multiple Oracle instances and TSM configurations ................................................................................................ 23 

The LEO Client Options File on UNIX systems ...................................................................................................... 23 

The LEO Client Options File on Windows systems ................................................................................................ 23 

TSM and Duplex Copy ........................................................................................................................................... 24 

TSM Object Names ................................................................................................................................................ 24 

Archive vs. Backup ................................................................................................................................................. 24 

Using Symantec NetBackup and LEO ............................................................................................................. 25 

Overview ................................................................................................................................................................ 25 

The DPT Model [Disk-to-Pipe-to-Tape] ................................................................................................ 25 

The DDT Model [Disk-to-Disk-to-Tape] ................................................................................................ 26 

Configuring LEO for use with NetBackup ............................................................................................................... 26 

The NetBackup configuration file ........................................................................................................................... 27 

The NetBackup catalogue file ................................................................................................................................ 28 

Licensing ............................................................................................................................................................ 29

Viewing the license ................................................................................................................................................. 29 

Changing the license .............................................................................................................................................. 29 

Changing the license using the Windows Installation Manager ............................................................................. 29 

Troubleshooting ................................................................................................................................................. 30 

IMP-00037: "Character set marker unknown" error during restore ........................................................................ 30 

Creating a Support Bundle ............................................................................................................................... 30 

Looking-up error messages .............................................................................................................................. 31 

Appendix A: TSM PASSWORDAccess Prompt ................................................... Error! Bookmark not defined. 

About Quest Software, Inc. ............................................................................................................................... 48 

Contacting Quest Software .................................................................................................................................... 48 

Contacting Quest Support ...................................................................................................................................... 48

1 LiteSpeed Engine for Oracle 


UNIX Installation, etc. 

LEO is shipped as a single tar file called leo_version.tar. Prior to installation or upgrade you must un-tar this 

distribution. To un-tar, execute the following: 

$ tar –xvf leo_version.tar 

This will extract the LEO installation script and binaries into a directory named leo_version. 

The leo_version directory contains a script called leo.sh. This shell script is used to install, upgrade, un-install, 

and check the installation status of the product. This script must be run as the ORACLE user (the owner of the 

$ORACLE_HOME/bin/oracle binary). Prior to running this installation script, you must set the ORACLE_HOME 

environment variable. 

Prior to installation you may need to gather the following information: 

• ORACLE user login and password 

• Oracle instance against which the install is to be run 

• ORACLE_HOME directory for the Oracle instance against which the install is to be run 

• LEO licensing information 

Installing 

To install LEO, execute the following: 

$ sh leo.sh install 

Uninstalling 

To uninstall LEO, execute the following: 

$ sh leo.sh uninstall 

This will remove LEO, and all LEO logs and LEO history files; however, the configuration information is not 

removed. 

If you do not have the leo_version.sh script available, you can uninstall LEO using the following commands: 

$ cd $ORACLE_HOME/Quest/LEO 

$ ./uninstall.sh 

Note: 

Backups created with LEO require LEO to be installed on the target machine. The restore functionality is 

left in an operational state to ensure that all backups can be restored to any machine after the evaluation 

period has expired. The restore functionality is not tied to any licensing and is considered a freeware 

feature of the product. This ensures that any LEO backup can be restored to any Oracle database at any 

time. 

Upgrading LEO 

To upgrade to a new version, execute the following: 

$ sh leo.sh upgrade 

Checking the installation status 

To determine if LEO is installed, execute the following: 

$ sh leo.sh status



This will display a message as to whether LEO is currently installed, as well as a message about the LEO version 

contained within the installation script.



Windows Installation, etc. 

LEO is shipped as a Microsoft Windows installation and configuration wizard file called LiteSpeedOracle.msi or 

LiteSpeedOraclex64.msi. This wizard is used to install and un-install the product. This wizard must be run by a 

user that has Admin and DBA privileges. 

Prior to installation you may need to gather the following information: 

• Oracle instance against which the install is to be run 

• LEO licensing information 

• Installation directory for the Configuration Editor and Installation Manager files (optional) 

Installing 

There are 32-bit and 64-bit installations available for the Windows operating system. If you are running Windows 

on a 32-bit system, select the LiteSpeedOracle.msi Installation Manager. If you are running Windows on a 64- 

bit system, select the LiteSpeedOraclex64.msi Installation Manager. 

If you need to install the 32-bit version on a 64-bit OS because you have a 32-bit Oracle installation, you must 

perform a "Custom" install within the 64-bit Installation Manager to install the 32-bit version. 

To install LEO, launch the appropriate Installation Manager and follow the prompts. 

Note: 

If you have both 32-bit and 64-bit Oracle installed on the same system, both the 32-bit and the 64-bit 

versions of LEO may be installed. 

Note that the 32-bit installer does not have the bit version in the executable name; only the 64-bit 

installer is identified with a bit version number. 

Uninstalling 

To uninstall LEO, select LiteSpeed Engine for Oracle from the Add or Remove Programs option in the Control 

Panel. 

Note: 

Backups created with LEO require LEO to be installed on the target machine. The restore functionality is 

left in an operational state to ensure that all backups can be restored to any machine after the evaluation 

period has expired. The restore functionality is not tied to any licensing and is considered a freeware 

feature of the product. This ensures that any LEO backup can be restored to any Oracle database at any 

time. 

Upgrading LEO 

To upgrade to a new version of LEO on a Windows system, run the Installation Manager. For more information on 

running the Installation Manager please refer to the Windows Installation, etc. section. 

Checking the installation status 

To view the installation status, per Oracle instance, select the Installation Manager option from 

Start|Programs|Quest Software|LiteSpeed Engine for Oracle. This will launch a window that will display the 

installation status for each of the Oracle instances on the database server. 

If you would like to determine the version of the LEO installation, launch the Configuration Editor from 

Start|Programs|Quest Software|LiteSpeed Engine for Oracle. Select the About LiteSpeed Engine for Oracle 

from the Help menu option.


User Guide



Understanding LEO concepts 

LEO provides on-the-fly compression and encryption for Oracle RMAN and EXP/IMP. 

Compression levels 

LEO supports five (5) levels of compression, including no compression as a Level 0. The default compression 

setting is Level 1. 

Using Level 1 compression provides reasonably good compression, while keeping CPU consumption reasonably 

low, and with minimal impact on runtime (or possibly improved runtime). 

Compression levels 2-4 use the same proprietary algorithm as Level 1, with each higher level providing better 

compression. However, producing higher compression levels comes at the expense of higher CPU usage. 

The following table suggests which level to use based on your needs: 

Level 

Level 0 

Level 1 

Level 4 

Description 

No compression. Use Level 0 if you only plan to use LEO's encryption 

feature and do not want to compress the data. 

This is the default setting. This uses a proprietary algorithm and normally 

provides the best balance of compression and CPU utilization. 

Use Level 4 if you have significant CPU resources available and would like 

to achieve slightly better compression. 

Encryption methods 

LEO provides five (5) encryption methods. Encryption is not enabled by default and must be configured prior to use. 

The following table contains a list of the available encryption methods: 

Level 

None 

AES128 

AES192 

AES256 

3DES 

Description 

Not encrypted. 

Advanced Encryption Standard (AES) using 128 bit key with 10 rounds. 

The supplied key is first hashed using either Secure Hash Standard (SHA) 

256 bit or 512 bit. 







Tripled Data Encryption Standard using 192 bit key with 16 rounds. The 

supplied key is first hashed using either Secure Hash Standard (SHA) 256 

bit or 512 bit. 

Locating the UNIX installation directory 

LEO is installed, in the $ORACLE_HOME/Quest/LEO directory, once per ORACLE_HOME. All of the binaries, 

configuration information, history information, and log files, etc. are stored within this directory. 

Locating the Windows installation directory 

By default, LEO is installed, in the C:\Program Files\Quest Software\LiteSpeed\Oracle directory.



Additional files are installed in the \Quest\LEO directory, once per ORACLE_HOME. This 

directory contains binaries, configuration information, history information, log files, etc. 

Launching the Command Line Interface on UNIX 

LEO provides a command line interface (CLI) via the LEO program. This program is accessible via a symbolic link 

in the $ORACLE_HOME/bin directory. From the prompt, type leo and press the Enter key. This will launch 

LEO in interactive mode. 

Launching the Command Line Interface on Windows 

LEO provides a command line interface (CLI) accessible via the Configuration Editor from 

Start|Programs|Quest Software|LiteSpeed Engine for Oracle. From the Configuration Editor, the user may 

launch the CLI by clicking on the Go To… button on the Configuration tab. In the resulting DOS window, type 

leo and press the Enter key. This will launch LEO in interactive mode. 

Notes about using the Go To… button: 

- the current working directory is set to the bin directory of the selected ORACLE_HOME 

- the Quest\LEO directory is prepended to the PATH environment variable. 

- the environment variable is set to the selected ORACLE_HOME directory, for that DOS 

session only. 

- other environment variables, other than the ORACLE_HOME and PATH, are not set. 

From this DOS window, RMAN, SQLPlus and LEO can be launched without changing directories. Further, the 

versions of these files that are executed will correspond to the selected ORACLE_HOME. 

Using the Command Line Interface 

LEO may be run interactively or via the command line by passing optional arguments. 

If you invoke LEO without any arguments, it will operate in interactive mode or command line interface (CLI) 

mode, whereby you may enter commands at the leo > prompt. 

For example, use the following syntax to launch LEO in interactive mode or CLI mode: 

$ leo 

Or 

C:\\Quest\LEO\>leo 

LiteSpeed(R) Engine for Oracle 1.2.0.10938 

Copyright 2009 Quest Software, Inc. ALL RIGHTS RESERVED. 

leo > 

To exit interactive mode or command line interface mode, use the exit command. 

To pass commands to LEO via the command line, leo is followed by the command option. For example, to pass the 

version command in the command line, execute the following: 

$ leo version 

Or 

C:\\Quest\LEO\>leo version 

LEO will execute this command and exit. 

To obtain a list of available commands, use the help command. 

Using the Windows Graphic User Interface 

LEO provides a graphic user interface (GUI) for the Windows platform. This application may be accessed by 

selecting the Configuration Editor from Start|Programs|Quest Software|LiteSpeed Engine for Oracle.



Oracle lib directory 

LEO integrates with RMAN via Oracle’s Media Management Layer (MML). Media Managers are implemented as a 

shared library that Oracle dynamically loads at runtime. 

On UNIX systems, LEO supports both 32-bit and 64-bit Oracle versions, so the LEO Media Manager is distributed 

as libleo32.so and libleo64.so. These files are located under the $ORACLE_HOME/Quest/LEO directory. 

During installation, LEO creates a symbolic link at ORACLE_HOME/lib/libobk.so to point to the appropriate 

LEO Media Manager. 

Note: 

The file extension for a shared library depends on the UNIX platform. This may be: .so, .sl or .a. 

On Windows systems, LEO also supports both 32-bit and 64-bit Oracle versions. The Installation Manager 

identifies whether the Oracle installation is 32-bit or 64-bit, and copies the appropriate Media Manager library to 

\bin\orasbt.dll. 

Oracle bin directory 

On UNIX systems, LEO places a symbolic link in $ORACLE_HOME/bin/ to point to the LEO command line 

utility. This is done so that users do not have to add $ORACLE_HOME/Quest/LEO to their search path. 

On Windows system, LEO does not create a link or shortcut to point to the LEO command line utility. Windows 

users should add \Quest\LEO to their search path. The Windows installation program does not 

modify the search path.



Understanding LEO configurations 

LEO’s configuration determines the destination for storage (local disk, Tivoli Storage Manager, Symantec 

NetBackup, etc.), as well as the compression level and encryption type. LEO, by default, is configured to back up to 

local disk using Compression Level 1 without encryption. You may change this configuration at any time. 

LEO has the following general configuration parameters: 

Name Supported Values Meaning 

Target Type 

DISK 

TSM 

NBU 

Controls the destination for storage. This may be configured for DISK 

to store files on local disk, TSM to store files on a Tivoli Storage 

Manager server, or NBU for Symantec NetBackup. 

Compression Level 0-4 Controls the degree of data compression. Level 0 is no compression, 

Level 4 is maximum compression. 

Encryption Type 

NONE 

AES128 

AES192 

AES256 

3DES 

Controls the encryption algorithm used to encrypt data. Specifying 

NONE means that data will not be encrypted. 

Encryption Password 16 characters or less This parameter is only set when data is encrypted. This is the clear text 

password used for encryption. 

The LEO configuration file also contains parameters specific to Tivoli Storage Manager and NetBackup. More 

information on these parameters can be found in their respective sections, Using Tivoli Storage Manager and LEO 

and Using Symantec NetBackup and LEO.



Managing configurations 

Viewing configurations 

To view the current configuration, execute the following: 

$ leo show config 

Or 

C:\\Quest\LEO\>leo show config 

LEO will display the default configuration and list any other available configuration files. 

To view the configuration for a specific ORACLE_SID, execute the following: 

$ leo show config ORACLE_SID 

Or 

C:\\Quest\LEO\>leo show config ORACLE_SID 

Changing the default configuration 

To change the default configuration, execute the following: 

$ leo configure 

Or 

C:\\Quest\LEO\>leo configure 

Setting-up multiple configurations 

Leo can operate using a single default configuration file or it can create and use multiple configuration files, one per 

Oracle instance. If no specific configuration is created for an Oracle SID, that instance will use the default 

configuration. 

Please refer to the Editing the configuration settings for an ORACLE_SID section for information on setting-up an 

ORACLE_SID specific configuration. 

Tip: 

Implementing multiple configuration files is particularly useful when more than one Oracle instance 

shares a single ORACLE_HOME and there is a need to set-up different compression and/or encryption 

settings for each instance. 

Editing the configuration settings for an ORACLE_SID 

To change the configuration for a specific ORACLE_SID, execute the following: 

$ leo configure ORACLE_SID 

Or 

C:\\Quest\LEO\>leo configure ORACLE_SID 

This command will prompt you for the target type, compression level, and encryption mode. You will also be 

prompted for any target specific parameters. 

Verifying a configuration 

This command will test the compression/backup and decompression/restore process with a 1MB-sized temporary 

file that is created (and removed) for the purposes of this test. The following is a list of the functionality that is 

tested: 

1. compression and/or encryption (as configured)



2. transportation (to the configured remote storage) 

3. restoration—which includes decompression and/or decryption of transported file (as configured) 

4. deletion of file from remote storage 

To test the configuration prior to use, execute the following: 

$ leo verify config 

Use of this command will ensure that the current configuration and the environment are ready for deployment. 

Note: 

Please note that the verify config command is not currently supported on Windows platforms. 

Removing the configuration for an ORACLE_SID 

To remove the configuration for a specific instance, execute the following: 

$ leo deconfigure ORACLE_SID 

Or 

C:\\Quest\LEO\>leo deconfigure ORACLE_SID 

LEO will delete the configuration file for the specified ORACLE_SID. 

Obtaining an encryption key for your password 

You must first convert the plain text password into an encryption key. This can be accomplished using the LEO 

encrypt command: 

$ leo encrypt password 

Or 

C:\\Quest\LEO\>leo encrypt password 

This will convert a plain text password into an encryption key. The encryption key is an encrypted form of the plain 

text password. The encryption key is only useable on the host where it was generated. If the encryption key is stolen 

it cannot be used to restore the file without information about the host that generated the encryption key. 

Tip: 

For a list of supported encryption types, please refer to the ncryption section of these notes.



Managing configurations with the 

Windows Configuration Editor 

Viewing configurations 

To view the current configuration, launch the Configuration Editor from Start|Programs|Quest 

Software|LiteSpeed Engine for Oracle. Select the appropriate ORACLE_HOME and ORACLE_SID from the 

combo box lists provided. When the user selects an ORACLE_HOME, LEO will display the default configuration 

and list any other saved ORACLE_SID specific configuration files. 

Please note that after selecting an ORACLE_HOME from the combo box, the default configuration is displayed 

and the Oracle SID combo box will show, until the user saves a configuration to a specific ORACLE 

SID. After which, the Oracle SID combo box list will include the name of the Oracle SID, in addition to the default 


Changing the default configuration 

To change the default configuration, launch the Configuration Editor from Start|Programs|Quest 


combo box lists provided. If you would like to change the settings in a configuration, please refer to the Editing the 

configuration settings for an ORACLE_SID section. 

Setting-up multiple configurations 

Leo can operate using a single default configuration file or it can create and use multiple configuration files, one per 

Oracle instance. If no specific configuration is created for an Oracle SID, that instance will use the default 


If you would like to change the settings in a configuration, please refer to the Editing the configuration settings 

for an ORACLE_SID section. 

Tip: 

Implementing multiple configuration files is particularly useful when more than one Oracle instance 

shares a single ORACLE_HOME and there is a need to set-up different compression and/or encryption 

settings for each instance. 

Editing the configuration settings for an ORACLE_SID 

To change the settings for a configuration, launch the Configuration Editor from Start|Programs|Quest 


combo box lists provided. Modify the configuration and select the Save option from the File menu. You will be 

prompted to save the change(s) as the default configuration for the selected ORACLE_HOME or to save the 

changes for a specific Oracle instance. You can select either option from the Instance Name combo box. This 

saved configuration will override the default configuration for the Oracle SID against which it was saved. 

Note: 

Please note that you can only have one configuration file per Oracle instance, and the name of the 

configuration must match the ORACLE SID when performing a backup or restore. 

A configuration can be saved with a custom name by highlighting the text in the Instance Name field, in the 

dialogue box, and overwriting the entry. Backups and restores require that the Instance Name field match the 

ORACLE SID. As a result, saving a configuration to a custom name is generally only useful for creating a 

configuration for an Oracle SID that has yet to be created.



Note: 

Please note that when you manually enter a custom ORACLE SID name when saving a configuration, 

the next time you launch the Configuration Editor, LEO will NOT remember the manually entered 

ORACLE SID name. Please make a note of the custom name and manually enter it in the ORACLE SID 

field to view the settings for that configuration.



Viewing history, statistics, etc, 

Statistical information is stored in the compressed backup file itself, as well as in a history.dat file in the LEO 

installation directory. 

Viewing history 

To view historical statistics, execute the following: 

$ leo show history 

Or 

C:\\Quest\LEO\>leo show history 

To view a more detailed history, execute the following: 

$ leo show history detailed 

Or 

C:\\Quest\LEO\>leo show history detailed 

Viewing file statistics 

To view the statistical data stored within a LEO backup file, execute the following: 

$ leo stat {file name} 

Or 

C:\\Quest\LEO\>leo stat {file name} 

Viewing the log file 

To view the log file, navigate to the $ORACLE_HOME/Quest/LEO (or \Quest\LEO) 

directory, and open the log.txt file. 

Viewing the log file using the Windows Configuration Editor 

To view the log file using the Windows Configuration Editor, launch the Configuration Editor from 

Start|Programs|Quest Software|LiteSpeed Engine for Oracle. Select the appropriate ORACLE_HOME and 

ORACLE_SID from the combo box lists provided. Select the View Log tab. 

Viewing catalogue contents for NetBackup 

To view a list of the contents for the LEO catalogue file: 

$ leo list cat 

Note: 

The list cat output, entries are presented in ascending order of the Catalogue Entry name. 

Note: 

The list cat command is not currently supported on Windows platforms, as NetBackup is only supported 

on UNIX platforms. 

Viewing cache directory info for NetBackup 

This command will list entries in the catalogue that are locally cached. 

To view a list of the contents for the LEO cache directory: 

$ leo list cache



Note: 

The list cache output is ordered according to when the cached files were last accessed: oldest to most 

recent. This is also the order in which they will be deleted, according to the user-specified retention 

policy. 

Note: 

The output for the list cache command will vary depending on the caching model selected during 


Note: 

The list cache command is not currently supported on Windows platforms, as NetBackup is only 

supported on UNIX platforms.



Manual file compression and encryption 

You may use the LEO CLI to compression and/or encrypt, as well as uncompress and/or decrypt, any file (including 

existing native Oracle backups). However, the LEO CLI will not decompress an RMAN backup created with LEO. 

You will need to restore LEO backups with the LEO media manager. 

Compressing files 

To compress a file, execute the following: 

$ leo compress source_file target_file 

Or 

C:\\Quest\LEO\>leo compress source_file target_file 

This will read and compress the source_file and write a compressed version of the file, using the configured 

compression level, to the target_file. 

Optionally, you may compress the file at a different compression level by specifying the compression level in the 

command line. For example, to compress a file at compression Level 4, execute the following: 

$ leo compress source_file target_file level=4 

Or 

C:\\Quest\LEO\>leo compress source_file target_file level=4 

Compressing and encrypting files 

You may encrypt a file by specifying the encryption algorithm in the command line. The following command will 

encrypt source_file, using AES 128, and using KEY as an encryption key without any data compression. 

$ leo compress source_file target_file level=0 crypto=AES128 key=KEY 

Or 

C:\\Quest\LEO\>leo compress source_file target_file level=0 

crypto=AES128 key=KEY 

If you do not specify an encryption key the default will be taken from the configuration file. If you specify a key, 

this is an encryption key as opposed to a plain text password. You can convert a plain text password to a key using 

the encrypt command. 

Uncompressing files 

To uncompress a file, execute the following: 

$ leo uncompress source_file target_file 

Or 

C:\\Quest\LEO\>leo uncompress source_file target_file 

This will read the compressed source_file and write an uncompressed version of it to the target_file. 

Uncompressing and decrypting files 

If the file was encrypted it will be decrypted using the encryption key contained in the configuration file. If the file 

was encrypted using a different encryption key, then you must specify the encryption key: 

$ leo uncompress source_file target_file key=value 

Or 

C:\\Quest\LEO\>leo uncompress source_file target_file 

key=value



Using EXP/IMP with LEO 

LEO can compress and/or encrypt EXP files. 

Exporting with EXP and LEO 

To accomplish this, place the leo command in front of the EXP command. 

For example, a simple export without LEO would look like: 

exp scott/tiger owner=scott file=expdat.quc 

To export using LEO, add the leo prefix to the command line: 

$ leo exp scott/tiger owner=scott file=expdat.quc 

Or 

C:\\Quest\LEO\>leo exp scott/tiger owner=scott 

file=expdat.quc 

Behind the scenes, LEO creates a named pipe and hands that name to EXP. EXP writes to the pipe, LEO reads from 

the pipe, compresses the data on-the-fly and writes to the file. 

When using EXP with multiple configurations, LEO will use the current ORACLE_SID environment variable to 

determine which configuration to use. If ORACLE_SID is not set then the default configuration will be used. 

Warning: If you execute EXP using LEO, you must also use IMP with LEO. Failure to do so will generate an 

"IMP-00037: Character set marker unknown" error. 

Configuring EXP file compression and encryption on-the-fly 

It is possible to specify any of the following options, or combination of options, in the EXP/IMP command line: 

• compression level (level) 

• encryption algorithm (crypto) 

• encryption password (key) 

Note: 

Configuring compression and/or encryption on-the-fly will override the LEO configuration settings for 

the current action only. 

For example: 

$ leo exp scott/tiger owner=scott file=expdat.quc crypto=aes128 

key=Pn1Q3vGfl+Jd7t8A 

Or 

C:\\Quest\LEO\>leo exp scott/tiger owner=scott 

file=expdat.quc crypto=aes128 key=Pn1Q3vGfl+Jd7t8A 

The above example will encrypt the data using AES128 and utilize the given encryption key. 

Note: 

You must first convert the plain text password into an encryption key. This can be accomplished using 

the LEO encrypt command. For information on obtaining an encryption key please refer to the 

Obtaining an encryption key for your password section.



Importing with IMP and LEO 

To import using LEO, add the leo prefix to the command line: 

$ leo imp scott/tiger file=expdat.quc full=y 

Or 

C:\\Quest\LEO\>leo imp scott/tiger file=expdat.quc full=y 

Warning: If you execute EXP using LEO, you must also use IMP with LEO. Failure to do so will generate an 

"IMP-00037: Character set marker unknown" error. 

When using IMP with multiple configurations, LEO will use the current ORACLE_SID environment variable to 

determine which configuration to use. If ORACLE_SID is not set then the default configuration will be used.



Using LEO with hot/cold backups 

LEO may be used to back up the data control and log files created during a user managed backup. To accomplish 

this, simply replace the cp command with LEO's compress command. 

For example: 

$ leo compress /oradata/PROD/system01.dbf /backup/system01.quc 

Or 

C:\\Quest\LEO\>leo compress \oradata\PROD\system01.dbf 

\backup\system01.quc 

The above example will make a copy of the system01.dbf file and compress it on-the-fly. The parameters used for 

compression and/or encryption will default to the current configured settings. These settings may be overridden by 

specifying alternate settings in the command line. 

To restore from a LEO user managed backup, replace the normal cp command with LEO's uncompress command. 

For example: 

$ leo uncompress /backup/system01.quc /oradata/PROD/system01.dbf 

Or 

C:\\Quest\LEO\>leo uncompress \backup\system01.quc 

\oradata\PROD\system01.dbf



Using RMAN and LEO 

Configuring RMAN to work with LEO 

To use LEO with RMAN, install and configure LEO. You will need to configure RMAN to back up to tape, rather 

than disk. 

If both RMAN and LEO compression are used there will be negligible, if any, gain in compression. However, there 

will typically be much greater CPU utilization and a corresponding increase in backup and recovery time. 

If RMAN's encryption is enabled, LEO will be compressing encrypted data. Encrypted data is much more random 

than un-encrypted data and will not compress as well. Additionally, it will most likely consume more CPU during 

compression. 

Warning: RMAN's compression and encryption are disabled by default. You should not enable RMAN's 

compression or encryption when using LEO. 

Performing a backup with RMAN and LEO 

Once LEO is installed and configured on your database server, there are no special syntax requirements to perform a 

backup. 

The following example RMAN syntax should produce a backup of the asdf tablespace, once LEO is installed and 

the configuration settings are in order: (Note that there are no special LEO commands or parameters.) 

RMAN> backup tablespace asdf format='/backups/backup%U.dat’; 

Or 

RMAN> backup tablespace asdf format='C:\backups\backup%U.dat’; 

Saving configuration parameters in the file name 

It is possible to specify LEO parameters as part of the file name in RMAN. RMAN parses the information and 

passes it to LEO. 

To use this option, you must specify a backup file name using the leo:// format, as seen in the example below: 

RMAN> backup tablespace asdf 

format='leo://crypto=aes128/backups/backup%U.dat’; 

Or 


format='leo://crypto=aes128/C:\backups\backup%U.dat’; 

If you are performing an RMAN backup using this method, the file name, including the parameters, will be recorded 

into the RMAN catalog. By using this method, the parameters will also be selected during a restore based on this file 

name. 

Note: 

Please note that parameters supplied in the file name override the default LEO configuration and any 

SID-specific configuration file that exists. 

It is possible to specify any number of parameters. Any parameter that can be set in the param.txt file can be saved 

in the file name. If you set more than one parameter, separate them by a colon and ensure that the path to the 

backup file appears at the end, after the LEO parameters, and that it is preceded by the colon separator and a forward 

slash. In the example below that would be: /backups/backup%U.dat



In the example below, the encryption type and key are specified in the file name. This overrides the encryption type 

and the encryption key overrides the password setting in the LEO configuration. Note that RMAN records the file 

name with the LEO parameters specified directly as the full file name. Consequently, the restore has the parameters 

embedded in the file name so that the LEO default configuration doesn’t need to be changed before the restore. 

RMAN> backup tablespace asdf format='leo://crypto=aes128: 

key=Pn1Q3vGfl+Jd7t8eQ-3NygAA/backups/backup%U.dat’; 

Or 

RMAN> backup tablespace asdf format='leo://crypto=aes128: 

key=Pn1Q3vGfl+Jd7t8eQ-3NygAA/C:\backups\backup%U.dat’; 

Note that the encryption key is not a plain text password. Instead this is an encrypted form of a plain text password. 

This is required for security reasons. This encryption key will be recorded in the RMAN catalog and may appear in 

scripts or other plan text files. For information on obtaining an encryption key please refer to the Obtaining an 

encryption key for your password section. 

The format to use when specifying parameters in the filename is: 

= 

Please keep in mind that multiple parameters are separated by a colon, “ : “, and without spaces. If the path starts 

with a slash, there will be two slashes, as in the following example where the path is /backups/backup%U.dat:: 


format='leo://crypto=aes128//backups/backup%U.dat’; 

Note: 

Please note that if only the path is to be set, i.e. no LEO parameters are being set, then use a standard 

RMAN format statement without leo://, as is explained in the Performing a backup with RMAN and 

LEO section. 

Tip: 

This technique provides a useful feature when performing encrypted backups. If you are encrypting your 

backups you may want to periodically change the encryption password. This can be done by changing the 

LEO configuration. However, if you need to restore from a backup performed prior to the password 

change then you would need to change the password back in the LEO configuration prior to restore. This 

feature provides another method. 

Restoring using RMAN and LEO 

No special steps or syntax are generally required to restore with LEO. The only caveats are that LEO must be 

installed and that the backup files must be on the configured target. LEO will then automatically decompress and/or 

decrypt the backup file on-the-fly. 

LEO must be installed in order to restore an RMAN backup file written using LEO.



Using Tivoli Storage Manager and LEO 

LEO interfaces with Tivoli Storage Manager (TSM) through the TSM API allowing users to conduct backups 

directly to TSM using RMAN, EXP, or the LEO command line. 

Using LEO with TSM combines the small, secure, and rapid backups of LEO with the state-of-the-art storage and 

retrieval system of TSM. 

Overview 

The following diagram shows a very simple, high-level overview of how LEO and TSM are interfaced. 

RMAN 

LEO 

Tivoli Storage Manager 

Server 

Oracle 

TSM backups conducted through LEO are transferred to, and then stored in and/or managed by, the Tivoli Storage 

Manager. LEO can compress the backup before transfer, ensuring minimal network traffic when backing up across a 

network. TSM handles the LEO backup file from then on, managing expiration date, storage location, etc. The 

functions of TSM are not discussed here – please refer to the product documentation for further details. 

In a typical environment: 

• Users who want to send LEO backups to TSM will have the machine from which LEO is run set up as a TSM 

Client Node. 

• Because TSM works in a Client-Server implementation, this Client Node will point to the TSM Server. The 

client uses a configuration file, called client option file, to locate the TSM server. Generally the TCP/IP address 

of the TSM Server and the port number that it is listening on are stamped in the client option file. 

• The user conducts the backup/restore from RMAN. 

• LEO processes the backup and restore requests from RMAN, translating them into TSM backup and restore 

requests. 

Pre-requisites 

If you plan to use the Tivoli Storage Manager features of LEO you must first: 

• Install the TSM Backup-Archive Client and API files. See ‘Install and Configure the Backup-Archive Client’ 

for details. Please refer to the System Requirements section of the Release Notes for information on minimum 

version requirements for TSM. 

• Register the TSM Client Node with the TSM Server. For instructions, refer to ‘IBM Tivoli Storage Manager 

Implementation Guide’ available at www.redbooks.ibm.com. 

Configuring LEO for use with TSM 

This section may be used to configure LEO for use with TSM on UNIX systems or on Windows systems using the 

LEO Command Line Interface.



To configure LEO to back up and restore from TSM, run the LEO configure command. 

• When prompted for Target Type, enter, TSM. 

• When prompted for TSM PASSWORDAccess, press Enter to accept the default, GENERATE, or type 

PROMPT. If you are setting this to PROMPT, you will be asked for the TSM Client node and the TSM 

Owner password. 

• When prompted for the Management Classes you may leave these blank or enter a valid TSM 

Management Class. 

In the following example, the TSM PASSWORDAccess is set to PROMPT: 

$ leo configure 

Or 

C:\\Quest\LEO\>leo configure 

Setting default configuration 

Please enter the following values. Type "?" for help. 

Target Type 

[Disk]: TSM 

Compression Level (0-4) [1]: 

Encryption Type 

[None]: 

Client options file 

[/oracle/ora64/920/Quest/LEO/leo.opt]: 

TSM PASSWORDAccess 

[GENERATE]: PROMPT 

TSM Client node 

[]: IRVSMSU14 

TSM Owner password : 

Management Class 1 []: 




The above example configuration will back up and restore to TSM using compression Level 1 with no encryption. 

The default Management Classes will be used. 

Note: 

If you are not planning to override the TSM Client System Options File, accept the default Client 

options file location during the configuration process. 

Note: 

If you are planning to override configured parameters in the TSM Client System Options File, accept the 

default Client options file location during the configuration process and edit this file with the server and 

overrides. Please refer to The LEO Client Options File section for information on using the LEO Client 

Options File. 

LEO is now configured to back up and restore data directly to TSM. 

Configuring LEO for use with TSM using the Configuration Editor 

Using the LEO Configuration Editor on Windows systems, you may specify the GENERATE 

PASSWORDAccess option by checking the box next to, Use PASSWORDAccess GENERATE from TSM 

configuration file. 

To set PASSWORDAccess to PROMPT, do not check the above box. You must provide information for the 

Client node and Client owner password fields.



Multiple Oracle instances and TSM configurations 

Users running multiple Oracle instances from the same ORACLE_HOME who would like to back up each instance 

to a separate Tivoli server or node may do so by creating a separate Client Options File for each Oracle instance and 

specifying the server or node within each file. When you configure each instance, you will be prompted for the full 

path of the Client Options File, be that the TSM Client Options File or an alternate file. For more information on 

server designation in a Client Options File, refer to The LEO Client Options File on UNIX systems or The LEO 

Client Options File on Windows systems. 

To configure LEO for each Oracle instance, use the leo configure ORACLE_SID command or, on Windows 

systems, use the Configuration Editor. 

The LEO Client Options File on UNIX systems 

When TSM is installed and the TSM Client System Options File, dsm.sys, is configured, it is typically done by 

root. Not all DBA users have root privileges and may find it necessary to override some of the configured 

parameters. To address this issue, LEO has its own Client Options File. 

During the installation of LEO, an empty LEO Client Options File is created and it may be edited, as needed. You 

will find the LEO Client Options File, leo.opt, in the $ORACLE_HOME/Quest/LEO directory. 

Note: 

If you do not plan to override the TSM Client Systems Options File, you should not edit the leo.opt file. 

To make use of the LEO Client Options File, leo.opt, add the appropriate server designation to this file. The 

syntax for the server designation is as follows: SERVERNAME server_name. As in the example that follows: 

SERVERNAME alv_ora_11g 

You may add any overrides to the file using the same syntax employed in the TSM dsm.opt file. 

Please note that the LEO Client Options File can be saved with any file name. This is particularly useful when 

working with multiple instances that back up to different locations. 

If you have multiple instances that backup to different servers it is necessary to create/edit a unique LEO Client 

Options File for each instance. You may save the LEO Client Options File with any name and to any location. Add 

to this file the appropriate server designation, and if applying overrides, use the syntax employed in the TSM 

dsm.opt file. Please refer to the Multiple Oracle instances and TSM configurations section for information on 

configuring LEO for multiple instances. 

Note: 

If the path to a LEO Client Options File is supplied for a configuration, not only does this file and its 

contents override what is in dsm.opt, but the dsm.opt is not used by LEO at all. As such, the LEO 

Client Options File must contain everything that is in the dsm.opt file, plus whatever servers and 

overrides are required to configure the LEO backups. 

Note: 

Servers listed in the leo.opt file must exist in the TSM dsm.sys file. 

The LEO Client Options File on Windows systems 

The TSM client configuration is stored in a Client Options File. You must have a valid TSM Client Options File 

before configuring LEO to use TSM. By default TSM uses the 

C:\Program Files\Tivoli\TSM\baclient\dsm.opt file as the Client Options File.



Unlike on UNIX systems where users create a LEO Client Options File, Windows users are encouraged to make use 

of the TSM Client Options File, as there should not be the same file permission issues. Optionally, you may create 

an alternate Client Options file and configure LEO to use that file. 

If you elect to create an alternate Client Options File, please note that unlike on UNIX systems where the dsm.sys 

file contains server definitions, there is no dsm.sys file. This means that the server definition must be included in 

the alternate Client Options File. (For simplicity, you can start by copying the contents of the dsm.opt file into the 

alternate Client Options File and begin editing from there.) You may add any overrides to the file using the same 

syntax employed in the TSM dsm.opt file. 

If you have multiple instances that back up to different servers it is necessary to create/edit a unique LEO Client 

Options File for each instance. You may save the LEO Client Options File with any name and to any location. Add 

to this file the appropriate server designation, and if applying overrides, use the syntax employed in the TSM 

dsm.opt file. Please refer to the Multiple Oracle instances and TSM configurations section for information on 

configuring LEO for multiple instances. 

Note: 

If the path to a LEO Client Options File is supplied for a configuration, not only does this file and its 

contents override what is in dsm.opt, but the dsm.opt is not used by LEO at all. As such, the LEO 

Client Options File must contain everything that is in the dsm.opt file, plus whatever servers and 

overrides are required to configure the LEO backups. 

TSM and Duplex Copy 

RMAN has a feature called Duplex Copy. Using this feature allows RMAN to simultaneously create multiple copies 

of a backup file. This may be used to enhance recoverability in the event that one of the copies is destroyed or 

damaged. 

Typically, if using this feature with TSM, you will want to store the multiple copies on different physical devices in 

order to protect from device failure. LEO facilitates this by allowing you to assign a different Management Class to 

each copy. TSM may be configured to store backup data for different Management Classes on different devices. If 

you do not plan to use this feature, all of your backups will be assigned to Management Class 1. 

TSM Object Names 

TSM stores backups and archives as TSM Objects. Objects in TSM are identified by a three-part name containing 

file system name, high level name, and low level name. For LEO, the file system name is always “/LEO”. The highlevel 

name is set to “LEO”. 

For an RMAN backup, the file name used by RMAN becomes the low-level name for the TSM Object. If no 

directory is supplied for the file name, LEO places the low-level name at the root directory in TSM. 

For EXP and Command Line Compression, the low-level name is the fully qualified path to the output file. 

LEO stores two objects for each backup. The first contains the backup data itself; the second contains LEO metadata 

about the backup. The LEO metadata file has the same low-level name as the backup file with “.header” appended to 

the file name. 

Archive vs. Backup 

RMAN backups are stored as Backup Objects in TSM. EXP and Command Line Compression files are stored as 

Archive Objects in TSM.



Using Symantec NetBackup and LEO 

LEO interfaces with NetBackup using an agent-based system where native Symantec client programs are launched 

on the local host in order to facilitate file transfers to and from the NetBackup server. The data transfer is 

accomplished using a named pipe ((in the Disk-to-Pipe-to-Tape, or DPT, model) or by caching files to the local 

system before transfer to or from the remote repository (in the Disk-to-Disk-to-Tape, or DDT, model). 

In a typical environment: 

• The user conducts native backup/restore using RMAN. 

• LEO processes the backup and restore requests from NetBackup seamlessly and transparently. 

Note: 

LEO-NetBackup functionality is only available on UNIX/Linux platforms. 

Overview 

There are two caching models the user may select from when configuring LEO for use with NetBackup. The 

following diagrams give a very simple, high-level overview of the LEO and NetBackup interfaces for each of the 

options. 

Note: 

Once selected, the caching model (DPT vs. DDT) may only be changed at the considerable risk of loss of 

backup data. If you are unsure of which option is best suited for your environment, please contact Quest 

Support. 

The DPT Model [Disk-to-Pipe-to-Tape] 

Files are not cached locally. File- transfer, to and from remote storage, is facilitated through named-pipes, and is 

consequently a little more efficient than in the DDT model. Restore times; however, have to account for the time 

that it takes to import the file from remote storage. 

RMAN 

LEO 

Catalog 

Named 

Pipe 

NetBackup 

Server 


The DPT Model



The DDT Model [Disk-to-Disk-to-Tape] 

Files, in addition to being consigned to the remote repository, are cached, subject to a configurable decay- policy, 

locally. Restore times are much faster in this scheme, but at the cost of disk space. Backup times have to account for 

the time that it takes to transfer whole files to remote storage. 

RMAN 

LEO 

Catalog 

Catalogued 

Disk Cache 

NetBackup 

Server 

Local Disk 


The DDT Model 

Configuring LEO for use with NetBackup 

This section may be used to configure LEO for use with NETBACKUP on UNIX systems or on Windows systems 

using the LEO Command Line Interface. 

Note: 

LEO-NetBackup functionality can be individually configured for multiple configurations. Please refer to 

the Setting-up multiple configurations section for more information on managing multiple 

configurations. 

1. To configure LEO to back up and restore with NETBACKUP, run the leo configure command. 

When prompted for Target Type, enter, NBU. 

2. You will need to have the following information available for the next several prompts: 

• Compression Level (Levels 0-4) 

• Encryption Type 

• NBU Master Server (Fully qualified host name or IP Address of the master NetBackup server) 

• NBU Client Name (NetBackup client name that identifies the current node) 

• NBU Restore Client Name (source /restoration NetBackup client name) 

• NBU Policy Name (name of the NetBackup policy with which this client complies) 

• NBU Commands directory (directory containing the NetBackup client executables) 

Note: 

Any NetBackup policy you select for use with LEO must have a Policy Type of “Standard” and must 

specify a retention period of sufficient length to accommodate any restoration request issued by RMAN, 

i.e., is at least as long as the RMAN file retention period.



3. When prompted for the LEO Cache Mode, please select from the following options: 

• DDT [Disk-to-Disk-to-Tape]: Files, in addition to being consigned to the remote repository, are 

cached, subject to a configurable decay-policy, locally. Restore times are much faster in this 

scheme, but at the cost of disk space. Backup times have to account for the time that it takes to 

transfer whole files to the remote storage. 

• DPT [Disk-to-Pipe-to-Tape]: Files are not cached locally. File-transfer, to and from remote 

storage, is facilitated through named-pipes, and is consequently a little more efficient than in the 

DDT model. Restore times must account for the time that it takes to import the file from remote 

storage. 

4. If you select the DDT option you will need to have the following information available for the next several 

prompts. (If you selected DPT, please skip this step.) 

• LEO Configuration file name 

Accept the recommended default unless expressly instructed to do otherwise by Quest support. 

• LEO Cache directory 

This is designed to serve as the local file-cache. Make sure you have enough free disk-space to 

fulfill the retention policy you will be stipulating in the following steps. 

Note: The cache directory must reside on the local file-system; it may NOT reside on a Network 

File-system (NFS). 

• Cache files for at least (days) 

This value determines the minimum number of days (since they were last accessed) that files will 

be cached locally. This parameter, by default, is set to 0 and files are cached indefinitely. 

• Age cached files out after (days) 

This setting determines the maximum number of days for which files shall be cached, space 

permitting. Files deleted from the cache are NOT deleted from the NetBackup repository. 

(Storage of files in the repository is dictated by the NetBackup policy under which they are 

governed.) 

5. If you select the DPT option you will need to have the following information available for the next several 

prompts. (If you selected DDT, please skip this step.) 

• LEO Configuration file name 

Accept the recommended default unless expressly instructed to do otherwise by Quest support. 

• LEO Named Pipe Directory 

This is the directory in which LEO creates named pipes to facilitate data-transfer with the 

NetBackup server. While disk space is not a consideration (named pipes result only in an attrition 

of inodes, and not disk space), this specification, once made, may only be changed at considerable 

risk of loss of backup data. This is because LEO performs a name translation of files being 

backed up prior to sending them to the NetBackup server. Translated names are relative to the 

named-pipe directory: Changing this directory will effectively render all files backed up prior to 

this setting changing inaccessible. 

Note: The named pipe directory must reside on the local file-system; it may NOT reside on a 

Network File-system (NFS). 

LEO is now configured to back up and restore data directly to NetBackup. 

The NetBackup configuration file 

The NetBackup configuration file is comprised of two (2) sections: 

• Environment Variable definition: 

Define all environment variables referenced by the "Commands" section (described next). Variable 

definition takes the form:



Variable: Value 

Variables, once defined, may be accessed as shell variables: 

$Variable 

LEO comes with a set of built-in variables (those which begin with LEO_ and LEOS_) that are initialized 

to values with which LEO was configured for NetBackup access. They are consequently commented out in 

the variable definition section of the configuration file. Of these variables, only those which begin with 

LEOS_ may be overridden (overrides to the built-in variables that begin with LEO_ will be ignored). Use 

extreme caution while overriding these built-in variables. 

The following precedence rules apply to the process of resolving a variable reference (from highest to 

lowest): 

1. Overrides in this configuration file; 

2. Overrides in the environment of the LEO process; and, 

3. Values with which LEO was configured. 

• Command descriptions: This section contains the command skeleton, using environment variables, and is 

used by the engine. Please do not attempt to override these unless expressly instructed to do so by Quest 

Support. 

The NetBackup catalogue file 

LEO maintains a catalogue [TOC] of all files it exports to the NetBackup server. This file is saved to the 

$ORACLE_HOME/Quest/LEO directory. A new version of the file is generated with each set of changes made to 

the catalogue. 

Each time a new version of the file is generated, the file name (NBU.toc) is appended with a file version number: 

NBU.toc. 

Older versions of the file are not retained. 

If LEO is configured for a specific Oracle SID, the catalogue file name will include the Oracle SID: 

NBU@ORACLE_SID.toc.. 

Note: 

The version numbers assigned to the catalogue file are generated by another LEO file, the NBU.gen file. 

This file is located in the same directory as the catalogue file. Its use protects the catalogue file against 

corruption that could result from concurrent access from multiple channels, e.g. running RMAN from 

multiple locations. This generator file uses the same naming conventions as the catalogue file. 

Warning: It is possible that you may encounter multiple TOC files. These files may be used to reconsolidate the 

master TOC file. Do NOT delete any TOC related files.



Licensing 

You may use the following commands to view and change license information. 

Viewing the license 

To view the license, execute the following: 

$ leo show license 

Or 

C:\\Quest\LEO\>leo show license 

Changing the license 

To replace the current license key, execute the following: 

$ leo set license 

Or 

C:\\Quest\LEO\>leo set license 

Note: 

If you are updating the license information on a Windows system, please use the instructions in the 

Changing the license using the Windows Installation Manager section. 

Changing the license using the Windows Installation Manager 

To change the license key, launch the Installation Manager from Start|Programs|Quest Software|LiteSpeed 

Engine for Oracle. Proceed as follows: 

1. Select the appropriate ORACLE_HOME by clicking on the corresponding check box in the Install column. 

2. Click on the Change License Key button in the lower left corner. 

3. Provide the requested license details in the resulting window and click Ok when you are finished. 

4. Click the Install button in the wizard. 

5. When the process is complete, verify that the license information was accepted by reviewing the Status 

column in the Installation Manager. 

Note: 

Please ensure that your license information is valid and entered accurately. 

If the license information is invalid, the license file(s) in the \Quest\LEO directory will 

not be updated. However, the license file in the C:\Program Files\Quest 

Software\LiteSpeed\Oracle\Engine directory will be updated. 

Note: 

If you are using a Beta license and it has expired you will still be able to uncompress files, but you will 

not be able to compress files.



Troubleshooting 

IMP-00037: "Character set marker unknown" error during restore 

If you encounter this error, it is likely that you have exported data using LEO, but are attempting to import without 

using LEO. This may happen if: 

• you forget to prefix IMP with the leo command 

• LEO was uninstalled 

• the export file name or location is no longer in a LEO configured directory 

• the file was moved or renamed 

• the LEO configuration was changed between the time of the export and the time of the import 

• Oracle has been patched or upgraded without uninstalling and re-installing LEO. 

Ensure that LEO is installed in: $ORACLE_HOME/Quest/LEO (or \Quest\LEO). If not, install 

LEO. 

Creating a Support Bundle 

A support bundle is a collection of system information. Quest Support may ask you to generate a Support Bundle 

and send it to them to help troubleshoot product issues. 

To generate a Support Bundle on UNIX: 

1. Set the ORACLE_HOME environment variable. 

2. Execute the following: 

$ cd $ORACLE_HOME/Quest/LEO 

3. Execute the following: 

$ ./bundle.sh > /tmp/bundle.txt 

4. This will create a Support Bundle in the /tmp directory. The support bundle file, bundle.txt, is an ASCII file. 

Note: 

There is currently no shell script to create a Support Bundle on Windows systems. Please contact Quest 

Support directly for additional information. For information on contacting Quest Support, please refer to 

the Contacting Quest Support section.



Looking-up error messages 

The following table lists the messages that LEO may return. Many of these are informational and do not indicate an 

error condition. These messages may appear during installation or while running the LEO command line utility. 

These messages may also appear in the LEO log.txt file. 

The LEO command line may also be used to display this information. Use the following to display information 

about an error number, where number is the LEO error number: 

$ ./leo help msg number 

Or 

C:\\Quest\LEO\>leo help msg number 

LEO-00014 

Cause: 

Action: 

Installation completed successfully. 

Informational message displayed when installation completes successfully. 

No action required. 

LEO-00015 

Cause: 

Action: 

Upgrade completed successfully. 

Informational message displayed when upgrade completes successfully 


LEO-00016 

Cause: 

Action: 

Uninstall completed successfully. 

Informational message displayed when uninstall completes successfully. 


LEO-00017 

Cause: 

Action: 

LEO version %s is installed in %s. 

Informational message that appears when the installation status is requested. 


LEO-00018 

Cause: 

Action: 

LEO is not installed on this system. 



LEO-00019 

Cause: 

Action: 

This installation script contains LEO version %s. 



LEO-00020 

Installing LEO version %s (%s) build %s.



Cause: 

Action: 

Informational message that is logged when LEO is installed. 


LEO-00021 

Cause: 

Action: 

Upgrading LEO to version %s (%s) build %s. 

Informational message that is logged when LEO is upgraded. 


LEO-00100 

Cause: 

Action: 

Starting LEO version %s. 

Informational message that is logged when LEO starts up. 


LEO-00105 

Cause: 

Action: 

Opening file %s for reading. 

Informational message that appears when LEO opens a file for reading. 


LEO-00106 

Cause: 

Action: 

Opening file %s for writing. 

Informational message that appears when LEO opens a file for writing. 


LEO-00107 

Cause: 

Action: 

Deleting %s. 

Informational message that appears when LEO deletes a file. 


LEO-00700 Command driver initialized: %s 

Cause: 

Action: 

Informational message that appears when the command driver for the configured external 

[command-line] agent is initialized. 


LEO-10000 

Cause: 

Action: 

The ORACLE_HOME environment variable has not been set. 

The ORACLE_HOME environment variable is required by this command. It has not been set. 

Set the ORACLE_HOME environment variable to the correct location and execute the command 

again. 

LEO-10001 

The ORACLE_HOME directory specified does not exist.



Cause: 

Action: 

The ORACLE_HOME environment variable points to a directory that does not exist. 


again. 

LEO-10002 

Cause: 

Action: 

The directory specified by the ORACLE_HOME environment variable is invalid. 

The ORACLE_HOME environment variable points to a directory that does not contain a 

subdirectory called bin with a binary called oracle or the ORACLE_HOME directory does not 

contain a lib subdirectory. The specified ORACLE_HOME must point to an installation of Oracle. 


again. 

LEO-10003 

Cause: 

Action: 

LEO is not supported on this platform. 

You are trying to install LEO on an unsupported platform. 

Please check the User Guide to ensure that this platform is supported. If you feel this warning was 

issued in error, or if you would like to request support for this platform, please contact Quest 

Technical Support. 

LEO-10004 

Cause: 

Action: 

This installation must be run as %s. It cannot be run as %s. 

You are trying to run the LEO install script as someone other than the Oracle user. 

Log in to the system as the Oracle user and run the LEO installation again. 

LEO-10008 

Cause: 

Action: 

Failed to create the %s directory. 

The installation script could not create the referenced directory. This is likely due to a permission 

issue. 

Attempt to create the directory manually to determine why the directory could not be created. 

LEO-10009 

Cause: 

Action: 

LEO version %s is already installed for the specified ORACLE_HOME. 

An attempt was made to install LEO when LEO is already installed for the current 

ORACLE_HOME. 

If you wish to install this version of LEO on top of the existing version of LEO, please use the 

UPGRADE option instead of install. 

LEO-10010 Invalid directory specification %s 

Cause: 

Action: 

Specified entity is either not a directory, or cannot be read. 

Examine the accompanying system error message for the reason for failure. Resolve the condition 

(if a permission issue), or specify a different directory. 

LEO-10011 Warning: Directory not empty %s



Cause: 

Action: 

Specified catalog directory is not empty. 

LEO exercises an age-based retention policy to remove files from the configured cache directory. 

This message is intended to serve as a reminder of this fact. Ignore this message if your decision to 

specify a populated directory as the LEO cache directory was a deliberate one. 

LEO-10012 Invalid cache decay specification: Cannot be less than %d 

Cause: 

Action: 

Specified cache-file retention period is either not supported, or could lead to inconsistencies. There 

are two values--minimum- and maximum-retention--that go to determine cache-file retention: a 

value of 0 for minimum-retention implies that files are to be retained indefinitely. The minimumretention 

period has may not be less than 0. The maximum-retention period has to be specified as a 

value that is greater than the configured minimum-retention period. 

Specify acceptable minimum- and maximum-retention values. 

LEO-10013 Unable to create cache generation file %s 

Cause: 

Action: 

The cache generation file could not be created for the specified catalogue-based storage service. 

Examine the accompanying system error message for the reason for failure. Resolve the condition, 

and reconfigure LEO. 

LEO-10014 Unable to create cache semaphore %s 

Cause: 

Action: 

The cache semaphore could not be created for the specified catalogue- based storage service. 

Examine the accompanying system error message for the reason for failure. Resolve the condition, 

and reconfigure LEO. Contact Quest Technical Support if the problem persists. 

LEO-10015 

Cause: 

Action: 

Invalid Cache Model specification 

Valid choices are DDT, or DPT. 

In the DDT model, a copy of the exported file is maintained locally, subject to user-defined laws of 

decay, reducing restoration times at the cost of disk space. In the DPT model, files are not cached 

locally. File transfer is facilitated through named-pipes, resulting in slightly faster backup, and 

slightly slower restore times compared to the DDT model, without incurring the overhead of 

additional disk space to maintain a local cache. 

LEO-10016 Invalid NetBackup configuration file %s 

Cause: 

Action: 

Specified file not found in LEO installation directory. 

The NetBackup Configuration file contains references to external programs and arguments that 

enable LEO to interact with the remote NetBackup server. This configuration file must reside in the 

LEO installation directory {ORACLE_HOME}/Quest/LEO. Contact Quest Support if the 

configuration file shipped with the installation is lost, or corrupted. 

LEO-10020 

Cause: 

LEO is not installed for the specified ORACLE_HOME. 

An attempt was made to upgrade or uninstall LEO when it is not installed for the current



ORACLE_HOME. 

Action: 

If you wish to install the product, use the INSTALL option of the installation script. If you are 

trying to upgrade or uninstall, verify that the ORACLE_HOME environment variable is properly 

set. 

LEO-10929 

Cause: 

Action: 

Failed to locate the %s system utility. 

The LEO installer could not find the referenced system utility. 

Ensure that the PATH environment variable is set so that it contains the path to this utility. If you do 

not have this utility installed on your system, please contact Quest Technical Support. 

LEO-10930 

Cause: 

Action: 

Failed to extract installation files. 

The LEO installer could not extract the installation package. This condition occurs if you are out of 

disk space or if the installation package has been corrupted. 

Check for available diskspace under ORACLE_HOME. If diskspace is a problem free up the 

required space and re-run the install or upgrade. Alternately, you may uninstall and re-install LEO. 

If you suspect that the installation package is corrupt, download a new version or contact Quest 


LEO-10931 

Cause: 

Action: 

LEO found a previous installation and will re-use the configuration parameter file from the 

previous installation. 

LEO is re-using the configuration parameters from a previous installation. 

When LEO is uninstalled is does not destroy the configuration parameters file. If LEO is reinstalled, 

it will use the parameters from the previous install. You may use the CONFIGURE command to 

modify the configuration parameter file. 

LEO-20000 

Cause: 

Action: 

Failed to read the configuration parameter file. 

LEO could not read the configuration parameter file. 

Check to see that the ORACLE_HOME environment variable is set correctly. Check the permissions 

on the ORACLE_HOME/Quest/LEO/param.txt file. Check that the LEO you are running is installed 

in ORACLE_HOME/Quest/LEO/leo. 

LEO-20001 

Cause: 

Action: 

Failed to write to the LEO configuration parameter file. 

LEO could not write to the parameter file. 

Check to see that the ORACLE_HOME environment variable is set correctly. Check the permissions 

on the ORACLE_HOME/Quest/LEO/param.txt file. Check that the LEO you are running is installed 

in ORACLE_HOME/Quest/LEO/leo. 

LEO-20002 

Cause: 

The compress (or uncompress) parameter specified, %s, is invalid. 

An invalid parameter was used with the compress or uncompress command.



Action: 

Use the HELP COMPRESS command for a list of compression parameters. 

LEO-20003 

Cause: 

Action: 

An invalid compression level was specified. 

An invalid compression level was specified. 

Valid compression levels are 0 (no compression) through 4 (maximum compression). Correct the 

compression level setting and re-execute the command. 

LEO-20004 

Cause: 

Action: 

An invalid encryption type was specified. 

An invalid encryption type was specified. 

See the User Guide for a list of supported encryption types. 

LEO-20005 

Cause: 

Action: 

The parameter option specified, %s, is not recognized. 

An unknown parameter option was specified. 

Refer to the User Guide for additional information about the command syntax. 

LEO-20006 

Cause: 

Action: 

Failed to open %s file for reading. 

Unable to open the referenced file for reading. 

Verify file existence and permission(s). 

LEO-20007 

Cause: 

Action: 

Failed to open %s file for writing. 

Unable to open the referenced file for writing. 

Verify directory existence and permission(s). 

LEO-20008 

Cause: 

Action: 

Unable to read %s file. 

Unable to read the referenced file. 

Attempt to diagnose the cause based on the associated LEO-90000 message. 

LEO-20009 

Cause: 

Action: 

Failed to write the %s file. 

Unable to write to the referenced file. 


LEO-20010 

Cause: 

Action: 

Failed to close the %s file. 

Unable to close the referenced file. 

Attempt to diagnose the cause based on the associated LEO-90000 message.



LEO-20011 

Cause: 

Action: 

Failed to delete the %s file. 

Unable to delete the referenced file. 


LEO-20012 

Cause: 

Action: 

Failed to seek the %s file. 

Unable to seek the referenced file. 


LEO-20013 

Cause: 

Action: 

Unable to give stats for the %s file. 

Unable to stat the referenced file. 


LEO-20017 

Cause: 

Action: 

The specified command is not fully implemented. 

This command has not been fully implemented. 

None. 

LEO-20018 

Cause: 

Action: 

The specified debug flag, %s, is not recognized. 

The specified debug flag name does not exist. 

List the debug flags to see which flags exist. 

LEO-20020 

Cause: 

Action: 

Failed to access the %s file. 

The referenced file does not exist or there is a permission problem with accessing the file. 

Verify the existence of the file. Verify the ownership and permission on every directory in the path. 

LEO-20023 

Cause: 

Action: 

The specified file, %s, is not a LEO file. 

LEO does not recognize the referenced file as one of its own files. 

If you feel that this is in error, please contact Quest Technical Support. 

LEO-20024 

Cause: 

Action: 

The specified file, %s, is not compatible with the installed version of LEO. 

LEO recognizes the referenced file as a LEO file, but the version number in the header is from a 

version of LEO that is not compatible with the installed version of LEO. This may happen if you are 

attempting to restore a file on a system with an older version of LEO than where it was created. 

Either upgrade LEO to the latest version or contact Quest Technical Support.



LEO-20025 

Cause: 

Action: 

The specified file, %s, appears to have been FTP'd as an ASCII file. Backup files should be 

It appears that the referenced file has been FTP'd between a Unix and Windows system using ASCII 

mode. Backup files by their nature are binary files and should be transferred as such. 

Locate a version of the file prior to the FTP. Contact Quest Technical Support. 

LEO-20026 

Cause: 

Action: 

The specified command contains an invalid argument or a syntax error. 

The specified command contains an invalid argument or a syntax error. 

Use the HELP command to view valid arguments and proper syntax. 

LEO-20028 

Cause: 

Action: 

The current license does not support compression and/or encryption. 

An attempt was made to compress and/or encrypt a file while the license is invalid or expired or this 

is a beat version that has expired. 

Use the SHOW LICENSE and SET LICENSE commands to correct the license. Contact Quest 

Technical Support for additional assistance or to obtain a valid license key or production version of 

LEO. 

LEO-20029 

Cause: 

Action: 

Failed to recognize the specified command. Type HELP for list of available commands. 

LEO failed to recognize the specified command. 

Type "help" to get a list of commands 

LEO-20032 

Cause: 

Action: 

The password specified exceeds the maximum length of 16 bytes. 

The password specified exceeds the maximum length of 16 bytes. 

Use a shorter password 

LEO-20033 

Cause: 

Action: 

The encryption key specified is invalid. 

The encryption key specified is not valid. This will happen if you specify a clear text password 

instead of an encryption key. The ENCRYPT command in the leo command line may be used to 

convert a plain text password to an encryption key. 

Supply a valid and correct encryption key. 

LEO-20034 

Cause: 

Action: 

Failed to encrypt password. 

The password specified could not be encrypted. 

Contact Quest Technical Support. 

LEO-20035 

Cause: 

No encryption key was specified. 

An encryption key is required when an encryption algorithm is specified.



Action: 

To utilize encryption, an encryption key and an encryption algorithm must be specified. 

LEO-20036 

Cause: 

Action: 

No encryption algorithm was specified. 

An encryption algorithm is required when an encryption key is specified. 

To utilize encryption, an encryption key and an encryption algorithm must be specified. 

LEO-20037 

Cause: 

Action: 

Failed to encrypt the data. 

The encryption algorithm failed. 


LEO-20038 

Cause: 

Action: 

Failed to decrypt the data. 

LEO was unable not decrypt the data. Ensure that the encryption key specified matches the key used 

to encrypt the data. 

Use the correct key. If you feel that this message is incorrect please contact Quest Technical 

Support. 

LEO-20042 

Cause: 

Action: 

Failed to rename the %s file to %s. 

LEO was unable to rename the referenced file. 

Verify file permissions. 

LEO-20043 

Cause: 

Action: 

Failed to parse parameter configuration file. There is a syntax error at line number %d. 

Failed to parse parameter configuration file. There is a syntax error at line number specified. 


LEO-20044 

Cause: 

Action: 

The encryption key specified in the parameter configuration file is invalid for %s. 

An encryption key in the parameter configuration file is invalid. This happens if you specify a clear 

text password instead of an encryption key. The ENCRYPT command in the leo command line may 

be used to convert a plain text password to an encryption key. 

Supply a valid and correct encryption key. 

LEO-20045 

Cause: 

Action: 

An invalid parameter name, %s, was set in the parameter configuration file at line number 

%d. 

The parameter name referenced is invalid and was set in the parameter configuration file at the 

referenced line number. 

Contact Quest Technical Support.



LEO-20046 

Cause: 

Action: 

An invalid parameter name, %s, was specified. 

The parameter name referenced is invalid. 


LEO-20051 

Cause: 

Action: 

An invalid target type was specified. 

The target type specified is invalid. 

Specify a valid target type. 

LEO-20052 

Cause: 

Action: 

Failed to connect to the LiteSpeed Compression Server. 

LEO could not verify the LCS connection parameters and failed to connect to the server. 

Ensure that the LiteSpeed Compression Server is installed prior to creating the target. Ensure that 

the hostname and port number match the server. Also, check network connectivity between the LEO 

host and the LCS host. 

LEO-20053 

Cause: 

Action: 

Invalid PASSWORDAccess type. 

PASSWORDAccess must either be GENERATE or PROMPT. 

Specify a valid PASSWORDAccess. 

LEO-20054 

Cause: 

Action: 

Invalid node name. 

TSM node name cannot be blank. 

Specify a valid TSM node name. 

LEO-20056 

Cause: 

Action: 

The ORACLE_SID environment variable has not been set. 

The ORACLE_SID environment variable is required to complete this command. It has not been set. 

Set the ORACLE_SID environment variable to the correct location and run the command again. 

LEO-20057 

Cause: 

Action: 

The version of the parameter configuration file does not match the expected version. 

The version field in the file header doesn't match the expected version number. 


LEO-20058 

Cause: 

Action: 

The client and server software versions are incompatible. The client protocol version %d is 

not in range (%d,%d). 

The version of the client protocol version is not compatible with the server protocol version. 

Upgrade the client and/or server to be compatible versions.



LEO-20059 

Cause: 

Action: 

Failed to create the compression thread. 

The operating system could not create a new thread for compression. 

The error message should indicate the reason for failure. The most likely cause is a lack of resources 

on the machine. Attempt to correct the problem and re-run the command. 

LEO-20060 

Cause: 

Action: 

The passwords specified do not match. 

The passwords specified by the user do not match. 

Re-enter the password. 

LEO-20061 

Cause: 

Action: 

No password was specified. The password field should not be blank. 

The password field was set to an empty string. 

Consider setting a password. If you must use a blank password, enter it three times and it will be 

accepted. 

LEO-20062 

Cause: 

Action: 

No history records available for the specified file. 

The history for the specified file is empty. 

No action required. If the history is lost, similar information is available via the "stat" command. 

LEO-20063 

Cause: 

Action: 

An invalid numeric value was specified. 

The value entered contains non-numeric characters. 

Please specify a value using numeric characters. 

LEO-20064 

Cause: 

Action: 

Failed to write the specified file. The file, %s, already exists. 

LEO attempted to write to the referenced file, which already exists. 

LEO will not overwrite an existing file. Either delete the file or specify a different file name. 

LEO-20065 

Cause: 

Action: 

The license key has expired. 

The current license key has expired. 

Enter a valid license using the SET LICENSE command. 

LEO-20066 

Cause: 

Action: 

The license key specified is invalid. 

An invalid license key or site message was specified. 

Ensure that the license key and site message were accurately entered.



LEO-20067 

Cause: 

Action: 

The license key was successfully validated. 

The license was accepted and the product is now licensed for use. 


LEO-20068 

Cause: 

Action: 

The license key specified was rejected. 

An invalid license key was specified. 

Ensure that the license key was accurately entered. Enter a valid license key using the SET 

LICENSE command. 

LEO-20069 

Cause: 

Action: 

This Beta version does not require a license key. 

An attempt was made to set the license for a Beta version. 

No action required. A license key is not required for a Beta version. 

LEO-20070 

Cause: 

Action: 

The current license key will expire in %d days. 

The current license is a trial license and will expire in the referenced number of days. 

Contact Quest Technical Support. To avoid an interruption of service a new license key must be 

obtained prior to the expiration date. 

LEO-20071 

Cause: 

Action: 

The license key, %s, failed with the following message: %#x. 

An internal license check failed for the referenced license key. 

No action required. This message is intended for interpretation by Quest Technical Support in 

diagnosing licensing issues. 

LEO-20072 

Cause: 

Action: 

Failed to write to the log file. All logging will only appear on the screen. 

The log.txt file write could not be written to. Messages will only appear on the screen. 

Ensure that there is not a permission issue with the log.txt file. 

LEO-20073 

Cause: 

Action: 

Failed to write to the history file. The history was not recorded. 

The history.dat file write could not be written to. The history was not recorded. 

Ensure that there is not a permission issue with the history.dat file. 

LEO-20074 

Cause: 

Action: 

Failed to locate custom parameters for specified ORACLE_SID. 

An attempt was made to de-configure an ORACLE_SID that does not have customized parameters. 

Check the configuration using the SHOW CONFIG command and try again with a corrected 

ORACLE_SID.



LEO-20075 

Cause: 

Action: 

Failed to de-configure the specified ORACE_SID. 

An attempt was made to de-configure an ORACLE_SID. LEO failed to remove a customized 

configuration file. 

Additional error messages should indicate why the file delete failed. 

LEO-20076 

Cause: 

Action: 

Failed to read the license file. 

LEO could not read and parse the license file. 

Use the set license command to re-set the license. If this does not clear the issue, contact Quest 


LEO-20077 

Cause: 

Action: 

Failed to write the license file. 

LEO could not write the license file. 

Additional error messages should indicate why the file write failed. 

LEO-20078 

Cause: 

Action: 

Invalid file specification 

Found the leo:// file prefix, but could not parse the filename correctly. 

Review User Guide for more information about the leo:// file format. 

LEO-30000 

Cause: 

Action: 

The license key specified is no longer valid or the license key was not set. 

The product is not licensed, the license has expired, or this is a Beta version and the Beta has 

expired. 

Check the license using the SHOW LICENSE command. If the product is not licensed or the license 

is expired add a valid license key using the SET LICENSE command. If this is an expired Beta 

version, contact Quest Technical Support. 

LEO-30001 

Cause: 

Action: 

Failed to compress the data. Unable to compress %d. 

The compression algorithm failed. 

Please contact Quest Technical Support. 

LEO-30002 

Cause: 

Action: 

Failed to decompress the data. Unable to decompress %d. 

The decompression algorithm failed. This may be caused by a corrupted file. 


LEO-30003 

Cause: 

Failed to encrypt the data. Unable to encrypt %d. 

The encryption failed.



Action: 


LEO-30004 

Cause: 

Action: 

Failed to decrypt the data. Unable to decrypt %d. 

The decryption failed. This is likely due to use of an invalid key. 


LEO-30005 

Cause: 

Action: 

Failed to decrypt data. The specified key is not the correct key. 

An attempt was made to decrypt a file using an incorrect key. 

Ensure that you are using the correct key when decrypting the file. 

LEO-30006 

Cause: 

Action: 

Failed to back up to LiteSpeed Engine for Oracle. The software is not properly licensed. 

The LiteSpeed Engine for Oracle Media Manager is not properly licensed. 

Check the license using the SHOW LICENSE command. If the product is not licensed or the license 

is expired add a valid license key using the SET LICENSE command. If this is an expired Beta 

version, contact Quest Technical Support. 

LEO-30007 

Cause: 

Action: 

Backups to DISK or other media manager is still possible. 

Backups to DISK or media managers other than LEO are still possible. 

If you must perform a backup before you are able to obtain a valid LEO license key, then you may 

configure RMAN to backup to DISK or any other media manager. Note that, even if LEO is not 

properly licensed it is still possible to restore using LEO. 

LEO-30008 

Cause: 

Action: 

Failed to compress the data. 

The compression algorithm failed. 


LEO-30009 

Cause: 

Action: 

Failed to decompress the data. 

The decompression algorithm failed. 


LEO-70000 

Cause: 

Action: 

%s: Error importing file %s from remote storage 

Network or configuration problems may be responsible for errors in importing files from remote 

storage. 

Examine the LEO configuration for anomalies: Ensure that all agent- specific parameters have been 

specified correctly (value and case). Enable agent-specific debug-tracing (if available), and examine 

all generated log files (including storage server-side logs) to identify and address the root cause of 

the problem.



LEO-70001 

Cause: 

Action: 

%s: Error exporting file %s to remote storage 

Network or configuration problems may be responsible for errors in exporting files to remote 

storage. 




the problem. 

LEO-70002 

Cause: 

Action: 

%s: Error scanning remote file %s for LEO header information 

Network or configuration problems may be responsible for errors in importing/scanning files from 

remote storage. 




the problem. 

LEO-70003 

Cause: 

Action: 

%s: Error consigning file %s to remote storage 

Network or configuration problems may be responsible for errors in consigning/exporting files to 





the problem. 

LEO-70004 

Cause: 

Action: 

%s: Error retrieving file statistics for %s from remote storage 

Network or configuration problems may be responsible for errors in consigning/exporting files to 





the problem. 

LEO-80000 TSM raised the following error: %s 

Cause: 

Action: 

The Tivoli Storage Manager API raised the referenced error. 

Diagnose and resolve the TSM issue; rerun the command. 

LEO-80001 

Cause: 

Action: 

The specified backup file, %s, does not exist on the TSM server. 

The backup file referenced does not exist on the TSM server. 

None required.



LEO-80002 

Cause: 

Action: 

Failed to connect to the TSM server. 

LEO failed to connect to the TSM server. 

Review LEO-80xxx errors to determine the root cause. Correct the problem and re-try the 

operation. 

LEO-80003 

Cause: 

Action: 

Failed to load the TSM library, %s. 

Unable to load the referenced TSM library. This may be encountered if the TSM API is not 

installed on this machine or the path to the TSM library is incorrect. 

Install the TSM API library if not already installed. To change the path to the library contact Quest 


LEO-80004 

Cause: 

Action: 

Failed to obtain the management class list from the TSM server. 

Unable to obtain management class list from the TSM server. 


LEO-80005 

Cause: 

Action: 

Failed to locate the specified TSM management class, %s. 

The Management Class referenced was not found on the TSM server. 

Provide a valid Management Class or leave blank to use TSM default. 

LEO-90000 The operating system raised the following error. %s : %s 

Cause: 

Action: 

The operating system error referenced was encountered while trying to perform an operating system 

call. This message is typically accompanied with additional information about the context of the 

operating system call. 

Correct the issue and rerun the operation. If you feel that this message is in error, or require 

assistance, please contact Quest Technical Support. 

LEO-90001 

Cause: 

Action: 

Oracle error encountered: ORA-%d 

The Oracle error referenced was encountered. 

Examine the Oracle error code. If possible, correct the problem and try again. Otherwise, contact 

Quest Technical Support. 

LEO-90002 

Cause: 

Action: 

LEO encountered an internal error at %s:%d. 

The internal error referenced has occurred. 


LEO-90003 

Additional information for internal error:



Cause: 

Action: 

This message contains additional information used to diagnose an internal error. 


LEO-90004 

Cause: 

Action: 

Out of memory. 

LEO was unable to allocate memory. 

Check the available memory on the system and try running the command again. If this still fails, 

please contact Quest Technical Support. 

LEO-99999 

Cause: 

Action: 

Internal trace message: 

These messages are generated when code tracing is enabled. 

To disable code tracing, cd to ORACLE_HOME/Quest/LEO and execute "./leo clear debug all".



About Quest Software, Inc. 

Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports 

smart systems management products—helping our customers solve every day IT challenges faster and easier. Visit 

www.quest.com for more information. 

Contacting Quest Software 

Email: info@quest.com 

Mail: Quest Software, Inc. 

World Headquarters` 

5 Polaris Way 

Aliso Viejo, CA 92656 

USA 

Web site: www.quest.com 

Refer to our Web site for regional and international office information. 

Contacting Quest Support 

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a 

commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with 

SupportLink, our web self-service. Visit SupportLink at: http://support.quest.com 

From SupportLink, you can do the following: 

• Quickly find thousands of solutions (Knowledgebase articles/documents). 

• Download patches and upgrades. 

• Seek help from a Support engineer. 

• Log and update your case, and check its status. 

View the Global Support Guide for a detailed explanation of support programs, online services, contact 

information, and policy and procedures. The guide is available, in English only, at: 

http://support.quest.com/pdfs/Global Support Guide.pdf

LiteSpeed Engine for Oracle 1.3 User Guide - Quest Software

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?