SQL-BackTrack™ For Oracle Messages Manual Version 3.2.70

SQL-BackTrack™
for Oracle
Messages Manual
Version 3.2.70
June 30, 2000

Copyright © 2000 BMC Software, Inc., as an unpublished work. All rights reserved.
BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered
trademarks or trademarks of BMC Software, Inc. IBM and DB2 are registered trademarks of International
Business Machines Corp.; Oracle is a registered trademark, and the Oracle product names are registered
trademarks or trademarks of Oracle Corp. All other registered trademarks or trademarks belong to their respective
companies.
Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. UNPUBLISHED–RIGHTS RESERVED UNDER THE
COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure by the U.S. Government is
subject to restrictions set forth in FAR Section 52.227-14 Alt. III (g)(3), FAR Section 52.227-19, DFARS
252.227-7014 (b), or DFARS 227.7202, as amended from time to time. Send any contract notices to
Contractor/Manufacturer:
BMC Software, Inc.
2101 CityWest Blvd.
Houston TX 77042-2827
USA
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain
general information about the company, its products, special events, and career opportunities. For a complete
list of all BMC Software offices and locations, go to http://www.bmc.com/corporate/offices.html.
USA and Canada Outside USA and Canada
Address BMC Software, Inc. Telephone (01) 713 918 8800
2101 CityWest Blvd.
Houston TX 77042-2827 Fax (01) 713 918 8000
Telephone 713 918 8800 or
800 841 2031
Fax 713 918 8000
Customer Support
You can obtain technical support by using Response Online™ (support from the Web) or Response On
Demand™. To expedite your inquiry, please see “Before Contacting BMC Software,” below.
Response Online
You can obtain technical support from BMC Software 24 hours a day, seven days a week by accessing the
technical support Web site at http://www.bmc.com/support.html. From this site, you can
• read overviews about support services and programs that BMC Software offers
• find the most current information about BMC Software products
• search a database for problems similar to yours and possible solutions
• order or download product documentation
• report a problem or ask a question
• subscribe to receive e-mail notices when new product versions are released
• find worldwide BMC Software support center locations and contact information, including e-mail addresses,
fax numbers, and telephone numbers
Response On Demand
In the USA and Canada, if you need technical support and do not have access to the Web, call 800 537 1813.
Outside the USA and Canada, please contact your local support center or your local sales office for assistance.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that a technical support analyst
can begin working on your problem immediately:
• product information
— product name
— product version (release number)
— license number and password (trial or permanent)
• operating-system and environment information
— machine type
— operating system type, version, and service pack or program temporary fix (PTF)
— system hardware configuration
— serial numbers
— related software (database, application, and communication) including type, version, and service pack or
PTF
• sequence of events leading to the problem
• commands and options that you used
• messages received (and the time and date that you received them)
— product error messages
— messages from the operating system, such as file system full
— messages from related software
BMC Software, Inc., Confidential and Proprietary Information
iii
iv SQL-BackTrack for Oracle Messages Manual

Contents
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Chapter 1 Overview
SQL-BackTrack Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Message Look-Up Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
References to Oracle Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Product Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Installation Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Program Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Chapter 2 Error Messages

DT-01000 to DT-01999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
DT-02000 to DT-02999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
DT-03000 to DT-03999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
DT-04000 to DT-04999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
DT-05000 to DT-05999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
DT-06000 to DT-06999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
DT-09000 to DT-09999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
DT-20000 to DT-20999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
DT-21000 to DT-21999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82
DT-39000 to DT-39999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83
Appendix A Solving License Manager Problems

SQL-BackTrack Licensing Overview . . . . . . . . . . . . . . . . . . . . . . . A-2
License Manager Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Customized dtlicense Binaries . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Port Number Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Contents v
Procedures for Invoking the License Manager . . . . . . . . . . . . . . . . A-7
Starting the License Manager Using Inetd . . . . . . . . . . . . . . . . . . . A-8
Oracle Parallel Server Licensing Issues . . . . . . . . . . . . . . . . . . . . . A-11
License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Port Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Checking dtlicense Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Index
vi SQL-BackTrack for Oracle Messages Manual

About . . .
About This Book
This book contains detailed information about the SQL-BackTrack™ for

Oracle product and is intended for system administrators and database
administrators (DBAs) who are responsible for Oracle databases.
The SQL-BackTrack for Oracle Messages Manual contains detailed

information about information, warning, and error messages that are used
by SQL-BackTrack for Oracle.
This guide is a work in progress. It is updated with each major release of

the SQL-BackTrack product at a minimum. This document attempts to
address the most commonly occurring error messages. It does not cover
every error message that might be displayed from any version of the
SQL-BackTrack product. Also, return codes are explained in this
document but return codes are not specified for specific messages.
This guide should be used with the SQL-BackTrack for Oracle User
Guide, which describes how to use SQL-BackTrack to perform database
backups and recoveries.
In this release, BMC Software has combined some of the

SQL-BackTrack for Oracle on Unix and SQL-BackTrack for Oracle on
Microsoft Windows documentation. The combined Unix and Microsoft
Windows books include the following:
• The SQL-BackTrack for Oracle Guide to Understanding Backup and

Recovery describes basic concepts that are useful to know before you
execute procedures using the SQL-BackTrack product to perform
database backup and recovery.
About This Book vii

• The SQL-BackTrack for Oracle User Guide provides detailed
instructions on how to use the SQL-BackTrack product to perform
database backup and recovery.
• The SQL-BackTrack for Oracle Reference Manual provides

command syntax and usage information to assist you in using the
SQL-BackTrack product to perform database backup and recovery.
• The SQL-BackTrack for Oracle Messages Manual contains detailed

information about SQL-BackTrack information, warning, and error
messages.
Note that the Unix and Microsoft Windows installation guides,

pre-installation checklists, and release notes will remain separate.
Note
This guide assumes you are familiar with Oracle system administration
and your operating system commands and privileges. It also assumes that
you have already installed Oracle and SQL-BackTrack. You should know
how to perform basic actions in a window environment, such as choosing
menu commands and dragging and dropping icons.
For information on how to install and license SQL-BackTrack, see the

SQL-BackTrack for Oracle on Unix Installation Guide or the
SQL-BackTrack for Oracle on Microsoft Windows Installation Guide. If
you do not have copies, you can find them on the BMC Software home
page at http://www.bmc.com.
viii SQL-BackTrack for Oracle Messages Manual

How This Book Is Organized
This book is organized as follows:
Chapter/Appendix Description
Chapter 1, “Overview” provides information about message formats, log files,
and return codes
Chapter 2, “Error Messages” provides a list of error messages and possible causes
and responses
Appendix A, “Solving License Manager describes SQL-BackTrack licensing issues
Problems”
“Index” lists index entries
Related Documentation
BMC Software products offer the following types of documentation:
• online and printed books

• online Help
• release notes
In addition to this book and the online Help, you can find useful
information in the publications listed in the following table. As “Online
and Printed Books” on page xi explains, these publications are available
on request from BMC Software.
About This Book ix

Category Document Description
Installation SQL-BackTrack for describes how to install SQL-BackTrack for Oracle on
Documents Oracle on Unix the supported Unix platforms.
Installation Guide
SQL-BackTrack for describes how to install SQL-BackTrack for Oracle on
Oracle on Microsoft the Microsoft Windows platform.
Windows Installation
Guide
SQL-BackTrack for describes information you should know before you begin
Oracle on Unix a new install or upgrade SQL-BackTrack for Oracle on
Pre-installation Unix.
Checklist
SQL-BackTrack for describes information you should know before you begin
Oracle on Microsoft a new install or upgrade SQL-BackTrack for Oracle on
Windows Microsoft Windows.
Pre-installation
Checklist
Core Documents SQL-BackTrack for provides information on basic concepts that is useful to
Oracle Guide to know before you execute procedures.
Understanding
Backup and
Recovery
SQL-BackTrack for provides detailed instructions on using SQL-BackTrack
Oracle User Guide to perform backup and recovery.
SQL-BackTrack for provides information on command syntax and usage
Oracle Reference and the catalog directory structure.
Manual
SQL-BackTrack for describes information, warning, and error messages
Oracle Messages that are used by SQL-BackTrack.
Manual
x SQL-BackTrack for Oracle Messages Manual

Category Document Description
Supplemental SQL-BackTrack OBSI describes how to integrate SQL-BackTrack with leading
Documents Module User Guides storage management products.
SQL-BackTrack for describes features and limitations of this version of the
Oracle on Unix SQL-BackTrack for Oracle on Unix product plus
Release Notes, last-minute changes to product information.
Flashes, or Technical
Bulletins
SQL-BackTrack for describes features and limitations of this version of the
Oracle on Microsoft SQL-BackTrack for Oracle on Microsoft Windows
Windows Release product plus last-minute changes to product information.
Notes, Flashes, or
Technical Bulletins
Online and Printed Books

The books that accompany BMC Software products are available in
online format and printed format. You can view online books with
Acrobat Reader from Adobe Systems. The reader is provided at no cost,
as explained in “To Access Online Books.” You can also obtain
additional printed books from BMC Software, as explained in “To
Request Additional Printed Books.”
To Access Online Books
Online books are formatted as Portable Document Format (PDF) files.

You can view them, print them, or copy them to your computer by using
Acrobat Reader 3.0 or later. You can access online books from the
documentation compact disc (CD) that accompanies your product or
from the World Wide Web.
In some cases, installation of Acrobat Reader and downloading the

online books is an optional part of the product-installation process. For
information about downloading the free reader from the Web, go to the
Adobe Systems site at http://www.adobe.com.
About This Book xi

To view any online book that BMC Software offers, visit the support
page of the BMC Software Web site at http://www.bmc.com/support.html.
Log on and select a product to access the related documentation. (To log
on, first-time users can request a user name and password by registering
at the support page or by contacting a BMC Software sales
representative.)
To Request Additional Printed Books
BMC Software provides a core set of printed books with your product
order. To request additional books, go to
http://www.bmc.com/support.html.
Release Notes
Printed release notes accompany each BMC Software product. Release
notes provide up-to-date information such as
• updates to the installation instructions

• last-minute product information
The latest versions of the release notes are also available on the Web at
http://www.bmc.com/support.
xii SQL-BackTrack for Oracle Messages Manual

Conventions
The following conventions are used in this book:
• This book includes special elements called notes, warnings,

examples, and tips:
Note
Notes provide additional information about the current subject.
Warning
Warnings alert you to situations that can cause problems, such as loss of
data, if you do not follow instructions carefully.
Example
Examples clarify a concept discussed in text.
Tip
Tips provide useful information that may improve product performance
or make procedures easier to follow.
• All syntax, operating system terms, and

literal examples are presented in this
typeface.
• In instructions, boldface type highlights information that you enter.

File names, directories, and Web addresses also appear in boldface
type.
• The symbol => connects items in a menu sequence. For example,

Actions => Create Test instructs you to choose the Create Test
command from the Actions menu.
• The symbol » denotes one-step instructions.
About This Book xiii

• In syntax, path names, or system messages, italic text represents a
variable, as shown in the following examples:
The table table_name is not available.
system/instance/file_name (Unix)
• In syntax, the following additional conventions apply:
— A vertical bar ( | ) separating items indicates that you must

choose one item. In the following example, you would choose a,
b, or c:
a | b | c
— An ellipsis ( . . . ) indicates that you can repeat the preceding

item or items as many times as necessary.
— Square brackets ( [ ] ) around an item indicate that the item is

optional.
xiv SQL-BackTrack for Oracle Messages Manual

1
Overview 1
This chapter describes some information about the error messages you
can receive while using the SQL-BackTrack™ for Oracle product. This
chapter includes the following topics:
• “SQL-BackTrack Message Format” on page 1-2

• “Message Look-Up Utility” on page 1-3
• “References to Oracle Messages” on page 1-4
• “Log Files” on page 1-4
— “Product Log Files” on page 1-5
— “Installation Log Files” on page 1-5
• “Program Return Codes” on page 1-6
Overview 1-1
SQL-BackTrack Message Format
All SQL-BackTrack messages follow a standard format that contains the
message number and the message text.
The message number is a five-digit number preceded by the characters

“DT-” and followed by a single character message type. There are five
different types of messages:
Character Message Type

F Fatal messages
E Error messages
W Warning messages
I Informational messages
D Debug messages
The message text may contain variables that are replaced by values
provided by SQL-BackTrack. The following table lists these variables
and the type of information they represent:
Variable Description
%1 - %7 Represents a string that is passed through, such as
a file name, table name, index name, and so forth.
These numbers increment by one within each
message. For example, the first occurrence of a
variable is represented by %1, the second
occurrence by %2, and so on. For example:
>message 3705 dtlink_unlink_error
%<prog>1: unlink() failed for file
’%<patch-file>2’ [%E]. ##
1-2 SQL-BackTrack for Oracle Messages Manual

Variable Description
%E Represents a Unix error message that is passed
through. For example:
>message 3705 dtlink_unlink_error
%<prog>1: unlink() failed for file
’%<patch-file>2’ [%E]. ##
%% Represents a number that is passed through. For
example:
>message 5406
kMAXIMUM_STRIPE_ERROR
<number>1 stripes specified;
maximum stripes allowed:
%<MAXNUMBER>2.
Message Look-Up Utility

If you receive a status message while using SQL-BackTrack, you can
refer to the Message Look-Up Utility for more information. This utility
displays online information about status messages. When you receive a
message, you can enter the message number into the utility and it will tell
you the cause and response for the message, if one is available.
To look up a message using the Message Look-Up Utility:
» Insert your specific message number or tag information into the

following dtomessage syntax:
dtomessage <message_num | message_tag> [-msgfile

<filename>]
Example
For example, dtomessage <5699> [-msgfile <tre1840>].
Overview 1-3
You receive a message similar to the following:
Message #: 5699
************* Message Text and Comments *************
Error occured while trying to backup ‘%<tablespace>1’
tablespace.
Cause: During a hot backup, an attempt to put a

tablespace into backupmode failed.
Response: Check the ORA- message and take action

accordingly.
References to Oracle Messages

Many of the SQL-BackTrack messages include references to Oracle
messages.
References to Oracle messages begin with the keyword ORA and are
followed by the message number, for example, [ORA-04002]. For more
information about these messages, see the Oracle Server Messages
manual.
Log Files
SQL-BackTrack uses log files to store different kinds of information.
The log files record, output from the SQL-BackTrack programs, can help
you diagnose problems during backup and recovery operations.
The general format for log file entries is:
entry time program [process ID/parent process ID.

internal number]: message return code

For example:
16:23:41.06 dtodump[27664/26936.916358900]: ending on

01/14/1999, rc=0
The final entry for a program contains the return code. If no errors
occurred during execution, the return code is zero (shown in the entry as
rc=0). Any other return code indicates a warning or an error. For more
information, see “Program Return Codes” on page 1-6.
Product Log Files

The datatools.log file is located in the $DTBASE/obacktrack directory.
This file records information about SQL-BackTrack backup and recovery
processes.
Installation Log Files

The output from the SQL-BackTrack installation script is logged in the
file named /tmp/obt_ins.log.<pid>.
The pid is the Unix process identifier of the installation script. If the
installation was unsuccessful, check the log file before contacting BMC
Software Product Support.
Overview 1-5
Program Return Codes
Return codes are returned by the SQL-BackTrack programs to indicate
the results of a specific operation. SQL-BackTrack uses the following
return codes in messages and log files:
Return Code Example Description

0 rc=0 The program completed successfully.
1 rc=1 The program completed with warnings.
2 rc=2 The program completed with errors.
3 and above rc=3, rc=105 The program completed with fatal
errors.

2
Error Messages 2
This chapter describes the messages that you might receive while using
the SQL-BackTrack product from BMC Software.
The error messages are arranged in numerical order, with the message
text immediately following the message number. An explanation of the
message and the suggested user response appear below the message. The
messages are listed in the following categories:
• “DT-01000 to DT-01999” on page 2-2

• “DT-02000 to DT-02999” on page 2-24
• “DT-03000 to DT-03999” on page 2-43
• “DT-04000 to DT-04999” on page 2-45
• “DT-05000 to DT-05999” on page 2-46
• “DT-06000 to DT-06999” on page 2-64
• “DT-09000 to DT-09999” on page 2-68
• “DT-20000 to DT-20999” on page 2-70
• “DT-21000 to DT-21999” on page 2-82
• “DT-39000 to DT-39999” on page 2-83
This list of error messages is updated regularly.
If you are viewing this document online, you can locate a message by
clicking on Edit => Find from your browser and entering the error
number.
For information on contacting BMC Software Technical Support, refer to

the copyright page at the front of this manual.
Error Messages 2-1

DT-01000 to DT-01999
DT-01002 Unable to open file <filename> no such file or directory.
Explanation: This is a generic error message. It is used when a file

cannot be found. The file not found is indicated as well.
User Response: This error can occur when a user accidentally removes
certain files that SQL-BackTrack expects to use. If files have not been
removed from the SQL-BackTrack product directories, then this may be
an internal error. If this is the case, contact BMC Software Technical
Support.
DT-01007 License error: <license_block> <message>.
Explanation: The license verification process returns an error if:
• the license file has an incorrect format

• this software license has expired
• the expiration date is 366 days for an evaluation copy
• no expiration date is set on an evaluation copy
• the format of the license key is invalid
The message that accompanies this error depends on the cause of the
problem. For example, if the license file format is incorrect, the following
error is displayed:
DT-1007F: License error:

DT-1007F: <license block information for that machine>
DT-1007F: License file must be upgraded using
'dtlicenseupgrade'.
DT-1007F: Please check your SQL-BackTrack License and
Installation Notes, or contact BMC Software product
support.

User Response: Check to make sure you have entered the correct serial
number and license key. If everything looks fine, then contact BMC
Software Technical Support. E-mail or fax the content of your
$DTBASE/obacktrack/ctl/license file to expedite the resolution of the
problem. If your temporary license has expired, contact BMC Software
Technical Support.
DT-01013 License error: <program> is missing serial number information.

Please customize it using 'dtcustom' and re-run.
Explanation: Each SQL-BackTrack binary is customized with the

serial number during the installation process. If the programs have not
been customized, the product is unable to complete the license
verification process and cannot be invoked.
User Response: To customize the binaries, follow these steps:
1. Change the directory to $DTBASE/obacktrack.

2. Execute install/dtoinstall customize.
To obtain the serial number for an upgrade, check your original

installation and use that serial number. If you still receive this message,
contact BMC Software Technical Support.
DT-01022 License error:

Serial number: <serial_num>
Server machine id: %2
Error: %3
There is no license information for server <servername>. Please
check your SQL-BackTrack License and Installation Notes.
Explanation: The license entered is not valid for the hostid of the
machine.
User Response: Check the host displayed with the error and compare it
to the hostid form executing the hostid command. If they are
different, contact BMC Software Licensing or Sales for a new license
key that is valid for the current host.
Error Messages 2-3

DT-01023 License error:
Serial number: <serial_num>
Error: <message>
Please check your SQL-BackTrack License and Installation Notes.
Explanation: This error is displayed if the product encounters

problems when attempting to perform license verification. The reason is
one of the following:
• license server not running

• unexpected end-of-file reading data from license server
• data error communicating with license server
• error reading data from license server
The actual error depends on the cause of the problem.
User Response: Make sure the license server is up and running.
DT-01025 Terminating program (user interaction disallowed if -no_prompt

specified).
Explanation: This error is displayed when the product needs to prompt

for user inputs, but the program is invoked with the -no_prompt option.
The SQL-BackTrack product may require additional inputs for one of the
following reasons:
• a tape problem exists

• access to Oracle using the login and password in the control file is
denied
User Response: Take one of the following actions:
• If your backup or recovery operation is using the tape Open Backup

Stream Interface (OBSI), verify that the tape volume has been
labeled using the dttape utility. Check whether the backup requires
more than one tape.

• Check to see whether the password given in the catalog directory has
been changed. If the password has been changed, use the obacktrack
program to update the encrypted password. Choose Synchronize
Database from the Database Catalog menu in the obacktrack program.
DT-01045 Record write error [Unix_error_message].
Explanation: SQL-BackTrack encountered a Unix error while writing

RDF records into the flat file.
User Response: This problem is usually caused by a lack of space on

the destination disk. See the associated Unix error message to determine
the exact cause of the problem and perform the necessary actions to
resolve it.
DT-01048 Unexpected End-Of-File reading record.
Explanation: SQL-BackTrack keeps track of incremental backups by

creating .stat files. One .stat file appears in the catalog directory for each
incremental backup of each datafile. This error appears if
SQL-BackTrack detects that one of these .stat files is missing or corrupt.
However, this error can have other causes.
User Response: Examine the datatools.log file and the other messages
that accompany this error to determine which datafile backup is
encountering the corruption, and then delete the corresponding .stat file
from the catalog directory. There is no harm in deleting these files.
However, doing so means that the next backup of the associated datafile
or datafiles will be a full backup even if incremental is selected, because
there are no .stat files for SQL-BackTrack to use when comparing
changed blocks.
Error Messages 2-5

DT-01107 Out of memory
Explanation: SQL-BackTrack failed to allocate the required dynamic

memory while executing a task. This error could occur is there is not
enough physical memory on the system on which SQL-BackTrack is
running.
User Response: Verify that there is adequate free space in the paging
files or increase the process size limit.
DT-01119 @@ protocol error, unexpected EOF.
Explanation: This is a generic error message. The SQL-BackTrack

parent and child processes communicate with each other using
@@messages, which are transmitted using @@protocol. When one of
the processes (most commonly the parent) dies, the communication
channel is broken and the other process receives this error message.
User Response: View $DTBASE/obacktrack-version/log/datatools.log

and look for earlier failures which may indicate the true cause of the
error.
DT-01120 @@Protocol error [<Unix_error_message>].
Explanation: This low-level Unix error indicates a communication

problem between SQL-BackTrack processes. In technical terms, the
Unix non-blocking read system command failed with either EINTR
(interrupt system call), or EAGAIN (resource temporary unavailable),
meaning that the Unix system itself is too busy to process the
non-blocking system read call.
One possible cause for this error is that a process (such as dtoarchmon)
failed and the pipe was reset, causing that process’s child processes to
fail as well.
User Response: This problem is complex and can have many causes. If
the problem is repeatable, contact BMC Software Technical Support.

DT-01160 ShMemInitialize: shmget error [%E].
Explanation: This error message is returned by the Unix system call

shmget while trying to obtain shared memory.
User Response: Consult your Unix system administrator and take the
proper corrective action appropriate for the error message displayed.
Note
Shared memory is only required for monitoring the progress of backup
and/or recovery actions. If you do not want to use the dtwatch command
to monitor these actions, it is possible to completely avoid this error. If
you set the DTSHMEM environment variable to NONE, SQL-BackTrack
will no longer attempt to access the shared memory area.
DT-01162 ShMemInitialize: semget error <Unix_error_message>.
Explanation: This error message indicates an insufficient number of

semaphores available on your system. The SQL-BackTrack product
requires 4K of shared memory and one semaphore set.
User Response: Contact your Unix system administrator about this

resource problem. If a Unix error is displayed at the end of the message
text, consult the man page for the semget function for more information.
Note
To avoid getting this message, set the environment variable DTSHMEM
to NONE. The side effect of this workaround is that the dtwatch utility
will no longer work.
Error Messages 2-7

DT-01164 @@Protocol error, bad line received.
Explanation: This error indicates a communication problem between

SQL-BackTrack processes. One possible cause of this error is that the
port number for the dtoarchmon process is used by another process on
the same system.
User Response: Edit the dthosts file and select a new port number for
the dtoarchmon process.
DT-01166 Lock file error [Unix_error_message].
Explanation: A Unix error occurred while SQL-BackTrack was trying

to create a lock file for the database in the SQL-BackTrack catalog
directory during a backup. This error usually means that another backup
is already running on the same database.
User Response: If another backup is running, allow it to complete or

end the backup before beginning a new one. If you are sure that no
backups are currently running, delete the 'lock' file present in the
<catalog_dir>/<dbname>.db/physical directory and continue with the new
backup operation.
DT-01190 Lock failed for '<file_name>' [Unix_error_message].
Explanation: A Unix error occurred while SQL-BackTrack was trying

to create a lock file for the database in the SQL-BackTrack catalog
directory during a backup. This error usually means that another backup
is already running on the same database.
User Response: If another backup is running, allow it to complete or

end the backup before beginning a new one. If you are sure that no
backups are currently running, delete the 'lock' file present in the
<catalog_dir>/<dbname>.db/physical directory and continue with the new
backup operation.

DT-01197 <device_name> Device full.
Explanation: The tape in the listed device is full. If you have enabled
tape spanning and set the tape size correctly, then the tape OBSI
automatically spans to the next tape. If you have not enabled tape
spanning and SQL-BackTrack encounters the end of the tape during a
backup, then the backup fails with this message.
User Response: For the current backup, enter a new tape and restart the
backup. Avoid this problem by enabling tape spanning and setting the
correct tape size in your tape backup pool definition. See the
SQL-BackTrack for Oracle User Guide for details on the backup pool
format for tapes.
DT-01211 Unable to do record I/O open (READ ERROR).
Explanation: This is a generic error message. It is used in places

where a low level IO error has occurred.
User Response: Look for other error or warning messages immediately

above or below this error. Since this is a low level error, other
surrounding messages will indicate higher level commands that the
program was trying to perform and indicate other pertinent information.
Retry the operation, if the problem persists, contact BMC Software
Technical Support with datatools.log information.
DT-01225 Tape on <device_name> is not an ANSI labeled tape.
Explanation: The SQL-BackTrack tape OBSI uses ANSI-labeled

tapes. If it is expecting an ANSI labeled tape and receives an unlabeled
tape, it issues this message.
User Response: Check to make sure that you have inserted a tape that
is labeled correctly. If you are writing a new backup to tape, use the
dttape command to label a blank tape. If you are trying to recover from a
SQL-BackTrack backup, then you have either inserted the wrong tape or
the tape has been corrupted or deleted. Try to recover from an earlier
backup.
Error Messages 2-9

DT-01232 I/O error after reading <n> blocks.
Explanation: During a recovery, SQL-BackTrack encounters an error

reading from tape. This may indicate a corrupted backup on tape.
User Response: Perform a dry run recovery using the same backup. If
the dry run recovery attempt fails at the same point, it indicates that the
backup is corrupted. Try to recover from an earlier backup instead.
DT-01246 Log write failed [log file not open].
Explanation: When a backup or recovery is performed, the

SQL-BackTrack product writes log records about the operation to an
error log file. By default, the log records are written to the datatools.log
file, which is located in the $DTBASE/obacktrack/log directory. This
error is displayed when the SQL-BackTrack product attempts to write to
the datatools.log file or an alternate log file specified on the command line
but the file is inaccessible.
User Response: Determine where the log records are being written.
Make sure that the permissions on the corresponding log file and its
parent directory are set to allow the user to write to this log file.
DT-01247 Log write failed [message limit for this program exceeded.]
Explanation: On commands executed with -logsize <n>, where <n> is

the limit on the number of log messages written by this caller, the limit
has been exceeded. This can happen if the limit is set too low. It may
happen if tracing is turned on.
User Response: Increase the limit on -logsize if appropriate, after

reviewing the cause of the failure. If tracing is turned on, turn it off.

DT-01248 Log write failed system error: no space left on device.
Explanation: There is no space available to write on the device to

which data is being written.
User Response: Check the media and verify that there is enough space
available.
DT-01251 Interrupted <msg> on <time>.
Explanation: This is a warning message that an interrupt signal has

been detected. Most likely, you pressed Ctrl+c or sent the kill signal to
stop a backup process. SQL-BackTrack is updating its restart file so that
the backup can be restarted from the point of failure.
User Response: No response needed. Restart the backup as described

in the SQL-BackTrack for Oracle User Guide.
DT-01254 Program error <signal #> (signal message), saving core file in
<path>.
Explanation: A core dump has occurred. This message will identify

the signal that was trapped, the type of core dump, and the location
where the core dump file is saved.
User Response: Save the core file in a safe place. Do not use a
temporary directory. Write a note identifying the command that the
program was executing and forward the note, the core file, and the
datatools.log information to BMC Software Technical Support.
Error Messages 2-11

DT-01291 LOG OPEN FAILED
Unable to open log file ‘<log_file_name>’.
Logging will not be done for this invocation of program
‘<program_name>’.
Explanation: SQL-BackTrack cannot open the datatools.log file. The

program will continue, but no logging will be done.
User Response: Ensure that the DTBASE environment variable is set

correctly. If that does not work, use the chmod command to change the
permissions of the $DTBASE/obacktrack/log directory and the
datatools.log file so that the oracle user has permission to read and write
to both the file and the directory.
DT-01301 Internal error <msg>.
Explanation: An internal error has occurred.

above or below this error. This is a low level error. The surrounding
messages will show which associated higher level commands were
executing around this time and indicate other pertinent information.
Save any supporting information such as a core file, if present, and

datatools.log and contact BMC Software Technical Support.
DT-01304 Internal error: <Oracle_message_1> <Oracle_message_2>

<Oracle_message_3> <Oracle_message_4>
Explanation: This error occurs when SQL-BackTrack has a problem

parsing the output from the Oracle query application. This usually
indicates that SQL-BackTrack is having trouble accessing the
application.
User Response: Use the Oracle error messages and error codes in this
message to determine the appropriate course of action. If you cannot
diagnose the problem based on this error message, call BMC Software
Technical Support.

DT-01312 Fork error process: tape, <path> [fork(): ERROR [msg][msg].
Explanation: A Unix fork() command failed.
User Response: Contact your system administrator for more

information.
DT-01330 Process inactive: '%<progname>1'
Explanation: This message is currently not used in SQL-BackTrack

for Oracle.
User Response: Ensure you have not mistyped the error number.
DT-01333 TIMEOUT - Transaction timed out after <sec> seconds (timeout ==

<sec>).
Explanation: This is a generic message. It identifies an operation that

has timed-out. This usually occurs when your system is extremely busy
and expected operations are not completing in the time allowed. Another
cause is some unusual environmental condition. For example, when the
Oracle server is not running, an operation may timeout because it is
unable to communicate with the Oracle server.
User Response: If the problem is related to your environment, as

explained above, then fix the environmental condition and restart the
operation.
DT-01335 EOF on read detected.
Explanation: An unexpected EOF on read has been detected.

above or below this error. This is a low level error. The surrounding
messages will show which associated higher level commands were
executing around this time and indicate other pertinent information.
Retry the operation, if the problem persists, contact BMC Software

Technical Support with datatools.log information.
Error Messages 2-13

DT-01340 Unable to open '<file_name>' [<Unix_error_message>]
Explanation: SQL-BackTrack cannot open a file. The file may not

exist, or the file name and path provided to SQL-BackTrack may be
incorrect.
User Response: Verify that the file name and path you provided to
SQL-BackTrack for this file are correct and that the file exists.
DT-01342 Unable to delete <msg> [item_to_be_deleted].
Explanation: Internally, the product will create and remove temporary

working files or directories. This is usually done transparently to the user.
The file or directory indicated in the error message has been changed or
removed during the operation.
User Response: Since the creation of the directory or file was

successful, the named file or directory was moved/removed during the
operation. Temporary files used by the product should not be removed.
DT-01343 Error reading '<block_number>' [<Unix_error_message>]
Explanation: SQL-BackTrack received a bad return code from a read

system call during operation, or SQL-BackTrack detected that the
number of bytes read from a datafile is less than the current block size.
This error can occur for many reasons, the most common being a media
failure and file corruption.
User Response: Check the status of your database and file system to
ensure that no corruption has occurred. Replace any bad media if
necessary.

DT-01344 Error writing to '<block_number>' [<Unix_error_message>]
Explanation: The file system has run out of space while

SQL-BackTrack was attempting to write a data block. This message can
also mean that SQL-BackTrack detected that the number of bytes read
from a datafile is less than the current block size. The latter explanation
indicates a possible media failure or file corruption problem.
User Response: Examine your file system to see if it has run out of
space, and add more disk space if necessary. Ensure that no media or file
corruption has occurred, and replace any bad disks if necessary. See the
associated Unix error message for the exact cause.
DT-01345 Cannot stat file or directory <msg>.
Explanation: A certain file or directory that the product is expecting

was not found.
User Response: Look for the directory or file and see if it is missing.
Most likely, it was an error during the catalog directory
creation/administration when a certain file was not correctly specified.
DT-01347 Unable to rename <file1> to <file2>
Explanation: The user does not have permission to rename the file.
User Response: Please check the file and directory permissions of the
files and directories that you are trying to access.
DT-01349 No such file or directory '<file_name>'
Explanation: Either the directory or file listed in the error message

does not exist, or SQL-BackTrack is unable to get information about the
directory or file from the file system.
User Response: Verify the path name of the directory or file listed in
the error message. Ensure that the file or directory exists.
Error Messages 2-15

DT-01350 Unable to copy '<file_name_1>' to '<file_name_2>'
[<Unix_error_message>]
Explanation: SQL-BackTrack received a Unix error while trying to

execute a file copy or rename operation. This error could result from a
lack of disk space. It could also mean that the SQL-BackTrack user
(usually oracle) does not have the correct permissions to copy the file to
the new location.
User Response: Check the SQL-BackTrack user’s file permissions to

make sure it has read/write access to that location. If the permissions are
correct, ensure that the new location has enough disk space.
DT-01352 Unable to get current working directory <Unix_error_message>.
Explanation: This error occurs when an internally-called function

(such as getcwd or getwd functions) returns a null value. This might be
caused by a problem in the directory structure. A Unix error message is
provided for your reference.
User Response: Execute the following command in the same directory

where the obacktrack command was invoked:
% ls -al
The output of this command should include a reference to the parent

directory.
If the reference does not exist, the current directory is an orphan

directory because it has lost the connection to its parent directory. One
solution is to reconnect the directories by using the following commands:
% cd <parent-directory>
% /etc/link . <orphan-directory>/..
If this command does not solve the problem, contact your Unix system
administrator for more information.

DT-01353 Error reading directory '<directory>' [<Unix_error_message>].
Explanation: This error occurs when SQL-BackTrack detects that an

expected directory is missing or that SQL-BackTrack does not have
permissions to read or write the directory. Some directories that might be
at fault include the directory specified by $DTTEMPDIR, the backup
destination (for disk backups), or the catalog directory. For instance, this
error might occur if a directory has been moved or if the SQL-BackTrack
command specified the catalog directory incorrectly.
User Response: Ensure that the catalog directory, the temporary

directory, and the backup destination exist and have not been moved.
Ensure that the command (for example, dtobackup or dtorestore)
specifies the correct catalog directory.
DT-01354 Error creating directory ‘<directory name>’ [OS error message]
Explanation: This error can occur when SQL-BackTrack does not

have permissions to read or write to the directory. It can also occur if the
specified directory already exists. A clue to the problem can be found in
the operating system error message that is returned as part of this
SQL-BackTrack error message.
User Response: The response would be to take the required steps (as
appropriate for the system error message) and try the command again.
DT-01362 RDF error during read
Explanation: When this error occurs with the SQL-BackTrack

message DT-01048, it means that the version of the OBSI Module that
you are using is incompatible with this version of SQL-BackTrack.
User Response: Verify that the OBSI Module you have is compatible
with this version of SQL-BackTrack. If necessary, upgrade the OBSI
Module, SQL-BackTrack, or both products. If the versions are
compatible, contact BMC Software Technical Support.
Error Messages 2-17

DT-1365E Error parsing contents of 'filename'
Explanation: This error can occur while parsing the contents of an

RDF file. The RDF file may be corrupted.
User Response: Contact BMC Software Technical Support.
DT-01368 RDF error: file not terminated by EOF record: <file_name>
Explanation: SQL-BackTrack stores its configuration and history

information in flat files in RDF format. This format is simply a text file
which contains some key value pairs stored in a begin/end block. The file
is always terminated by the line, ;; RDFEOF. If SQL-BackTrack finds
that some lines of one of its files are not in the expected RDF format, it
produces this error message.
This message means that the file is corrupted. Many events could cause
this corruption, but the most common are a system crash or the act of
killing a process with the kill -9 command.
User Response: If the file listed in the error message is a text file, make
sure there are no obvious errors in the file, such as a syntax error or a
missing end-of-file line (;;RDFEOF). If the file is a binary file, the file is
probably beyond repair and may need to be recreated depending upon the
scenario.
DT-01375 poolfile <filename>, backup_pool: <backup_pool_name>not found.
Explanation: Attributes describing pool information could not be

found. Most likely, the pool information was manually edited and certain
data is not properly formatted now.
User Response: Run Catalog Administration and re-enter the catalog

directory information.

DT-01380 Terminated by <msg> (signo = <number>).
Explanation: A terminating signal (signo, indicated in parenthesis) was

trapped, and the program has terminated.
User Response: Investigate where the signal originated—most likely

the user pressed Ctrl+c.
DT-01418 (892/menu.c): invalid command <entered command>
Explanation: The command provided for a prompted response is not a

valid selection.
User Response: Check the response and re-enter a valid response at the
prompt.
DT-01437 <host_name>: No response from license server.
Explanation: The dtlicense program was not running when

SQL-BackTrack or one of its component programs tried to connect to the
license server to perform an operation on a remote server. You should
only receive this error if you are using SQL-BackTrack in an Oracle
Parallel Server environment.
User Response: If the license server is not already running on the

remote server, start it using the dtlicense command (see the
SQL-BackTrack for Oracle on Unix User Guide for the complete
syntax). Ensure that the license server is running on the port specified in
the $DTBASE/obacktrack/ctl/dthosts file for that server.
Error Messages 2-19

DT-01457 Host information for <host_name> not found
Explanation: SQL-BackTrack was unable to retrieve the host name for

the server from the Unix system tables.
User Response: Use the appropriate command for your operating

system to obtain the host name for your server. The Unix command
nslookup is often helpful for finding the host name. If you cannot locate
the appropriate command, contact your system administrator.
DT-01459 <server_name>: Server down
Explanation: This error occurs when dtoarchmon fails to make a

connection to Oracle or another dtoarchmon process. This connection
could fail because of any one of the following problems:
• The Oracle instance is down.
• The TCP/IP port you specified in the dthosts file for dtoarchmon is
already in use.
• You entered the wrong password for the Oracle database during
configuration.
• Your database has reached the size limit specified by your

SQL-BackTrack license, and no more connections to the database are
allowed.
User Response: Ensure that none of the problems listed in the

explanation is affecting your database or SQL-BackTrack configuration.

DT-01470 Unknown output received from OBSI: %<output>1
Explanation: Either the version of the OBSI Module that you are
using is incompatible with this version of SQL-BackTrack or an internal
error has occurred.
User Response: Verify that the OBSI Module you have is compatible
with this version of SQL-BackTrack (see the SQL-BackTrack for Oracle
User Guide for more information). If necessary, upgrade the OBSI
Module, SQL-BackTrack, or both products. If the versions are
compatible, contact BMC Software Technical Support.
DT-01472 OBSI '<OBSI_type>' failed, status == <return_code>
Explanation: During a backup or recovery operation, several

SQL-BackTrack component programs must wait for the OBSI process to
complete before they can finish. If SQL-BackTrack receives a non-zero
return code from the OBSI process during this time, this error message
appears.
The reason for the failure of the OBSI process varies depending on the
OBSI you are using. For example, if you are using the disk OBSI, the
failure could be related to file permission problems or a full disk.
User Response: If the failure of the OBSI process is related to file

permission problems or a full disk (or any other media problem), remedy
the problem and restart the operation.
Error Messages 2-21

DT-01473 Unable to determine local host [Unix_error_message].
Explanation: SQL-BackTrack uses the Unix system calls

gethostbyname and sysinfo/gethostname to determine the full name of the
machine on which it is running. It uses this value to determine whether or
not the catalog directory belongs to the machine and stores the
information in several locations in the catalog directory and the dump
files.
The OS usually resolves the host name by looking into the DNS or NIS
tables (or a similar system). If those name resolution servers are down,
then SQL-BackTrack cannot determine the local host name and will
produce this error message.
User Response: Contact your OS system administrator to ensure that

the name resolution server is up and running.
DT-01592 Unable to locate MSGFile <message_file>

Using default language msgfile <file_name>.
Explanation: SQL-BackTrack reads a message file to print options and

error messages to the screen. If the operating system environment
variable LANG points to a non-English locale, then the language specific
message files will be opened. If the localized message files do not exist
or cannot be opened, this warning message appears and the English
message files are used by default.
User Response: Ensure that SQL-BackTrack supports the language

specified by the LANG environment variable. Contact your BMC
Software sales representative for a list of the available languages for this
product. If the language is not supported, BMC Software suggests that
you run the product in U.S. English mode.

DT-01594 ERROR: Unable to support LANG '<language_name>'.
Explanation: If available, Backtrack tries to use the message file. The

default language set in the LANG or DTLANGUAGE environment
variable will be used if there is no message file. The above error message
will be displayed if the incorrect language is set in the environment
variable.
User Response: Verify the above environment variables, and set

appropriately.
Error Messages 2-23

DT-02000 to DT-02999
DT-02015 Unable to establish Oracle version for <ORACLE_SID>.
Explanation: SQL-BackTrack tried to bring up sqldba to perform

some Oracle commands but failed.
User Response: Try to manually bring up sqldba, and if fails,

investigate to see if Oracle is running.
DT-02046 Unable to build directory: '<directory_name>'
Explanation: This error can occur if SQL-BackTrack is unable to

create the specified directory or directories (for example, if there is a
need to create a directory structure in the format /a/b/c, where one or
more of these directories does not already exist). The SQL-BackTrack
user (usually oracle) may not have the necessary permissions to create
the directory. A clue to the problem may also be found in the Unix error
message that is returned as part of this SQL-BackTrack error message.
User Response: Verify that the SQL-BackTrack user has read/write

permissions for this path and that the path name is correct. Then take the
required steps (as appropriate for the system error message) and try the
command again.
DT-02051 Oracle error: ‘<Oracle error message>’.
Explanation: This message is displayed when Oracle generates an

error and SQL-BackTrack encounters an Oracle error message.
SQL-BackTrack passes on the appropriate error message text. Oracle
error messages are documented in the Oracle product documentation set.
Some common Oracle error messages include:
• ORA-00955: name is already used by an existing object

• ORA-01034: Oracle not available
• ORA-03113: end-of-file on communication channel
User Response: For these common Oracle error messages, respond as

indicated below. Otherwise, see the Oracle product documentation set.

For ORA-00955: this is an SQL error. Select another name for the object.
For ORA-01034: this error appears if the Oracle database is down

(offline) during catalog directory creation. Restart the database and retry
the process.
For ORA-03113: this message appears when SQL-BackTrack is

incompatible with the Oracle version. See your release notes for details,
or contact BMC Software for a product upgrade.
DT-02055 Checksum mismatch in file '<file_name>'

block <block_number>: [<checksum_1>] vs. [<checksum_2>]
Please contact DataTools Technical Support at 1-800-243-9670.
Explanation: The datafile named in this message is probably corrupt.
DT-02056 Wrong statistics file given: '<file_name>'
Explanation: This message should not appear in this version of

SQL-BackTrack for Oracle. Its appearance means that an internal error
has occurred.
DT-02061 File <filename> is truncated.
Explanation: This is a generic message. It is returned whenever the

product tries to read or seek an Oracle datafile and finds that it cannot
read or seek to the desired location.
User Response: If Oracle is still functioning correctly, then it may be

an internal product error. Contact BMC Software Technical Support.
Error Messages 2-25

DT-02078 SQL-License Error: Server size (<nn> MB) exceeds size limit
allowed by license (<nn> MB). Machine ID: <machine_id>
Please contact DataTools, Inc. for a new license key.
Explanation: BMC Software licenses SQL-BackTrack according to

the size of the largest database to be backed up. Once the database
exceeds the size allowed by the license, SQL-BackTrack issues this error
message. (You are still able to perform backups when this message
appears.)
User Response: Contact BMC Software Sales for a new license that
supports larger databases.
DT-02095 Unable to find either svrmgrl or sqldba in <$ORACLE_HOME/bin>.
Explanation: SQL-BackTrack is unable to execute either the sqldba or

svrmgrl processes. It expects to find these programs in
$ORACLE_HOME/bin.
User Response: Check your SQL-BackTrack configuration to ensure

that you entered the correct value for the Oracle home directory
($ORACLE_HOME) during configuration. Ensure that this directory has
not been moved since you configured SQL-BackTrack.
DT-02096 DBA process inactive.
Explanation: SQL-BackTrack executed a SQL command that timed

out during execution.
User Response: Check the server response and rerun the operation.
DT-02097 Unable to start sqldba.
Explanation: SQL-BackTrack tried to bring up sqldba to perform

some Oracle commands, but it failed.
User Response: Try to bring up sqldba manually. Check the

permissions on the sqldba process. Ensure that you are trying to run
sqldba as the correct Unix user (usually oracle). If that fails, talk with
your database administrator to identify possible causes.

DT-02098 Unable to start SVRMGRL: this program has terminated.
Explanation: Our product tried to bring up svrmgrl to perform some

Oracle commands, but it failed.
User Response: Try to manually bring up svrmgrl, and if this fails,

investigate to see if Oracle is running.
DT-02101 Unable to mount database <database_SID>; Database may be

starting up or shutting down. Try the operation again in a few
minutes.
Explanation: SQL-BackTrack received an Oracle error while trying to

start the database using the STARTUP MOUNT command.
User Response: Shutdown and restart the database manually (or wait
for the database to start up if a STARTUP command was already in
progress), then restart the SQL-BackTrack operation.
DT-02102 Unable to execute SQL statement '<statement>' on <database_SID>:

<Oracle_error_message>
Explanation: SQL-BackTrack tried to execute a SQL statement on the

database named in the message, but the statement failed.
User Response: The cause for the failure is given in the Oracle error
message listed at the end of this message. Take appropriate action to
correct the problem and run the SQL-BackTrack operation again.
DT-02103 Unable to shut down database <SID>. <errmsg>.
Explanation: Our product tried to bring down Oracle using sqldba, but
the attempt failed. You might encounter this message in an Oracle
Parallel Server (OPS) installation if for some reason SQL-BackTrack is
unable to shut down one or more database nodes for a cold backup.
User Response: Retry the failed operation later. If this fails, contact
Oracle Technical Support. This is an Oracle error.
Error Messages 2-27

DT-02108 File <filename> is not a valid dbainfo file.
Explanation: The displayed file is not synchronized with the current

configuration for the database.
User Response: Remove the file from the DTTEMPDIR directory and
run a synchronization of the database and the SQL-BackTrack catalog
directory.
DT-02110 Unable to start database <SID> in exclusive mode. Make sure all
threads have been closed.
Explanation: Some database recoveries require starting the database in

exclusive mode. This message occurs if SQL-BackTrack is unable to
start a database in exclusive mode.
User Response: Be sure all threads for the database are closed. Try
starting up the database in exclusive mode using Server Manager. If the
problem persists, contact Oracle Technical Support.
DT-02112 Unable to read archive log destination directory: <directory>.
Explanation: SQL-BackTrack generates this message if there is a

problem reading the archive log destination directory. The dtoarchmon
process must be able to read the archive log destination directory to
perform backups. You may get this message if:
• the permissions for the directory are not set correctly

• the archive log destination directory has been changed
• the destination directory was entered incorrectly when creating the
catalog directory
User Response: Check the location of the archive log destination

directory. Make sure that the account running SQL-BackTrack (and the
dtoarchmon process) has access to that directory. Check that the archive
log directory is listed correctly in the dbprofile file in the catalog
directory (<catalog>/<dbname>.db/physical/dbprofile.rdf).

DT-02113 Bad block number: <block_number>; expected: <block_number>.
File may be corrupt.
Explanation: Oracle block numbers are supposed to be in sequential

order. SQL-BackTrack has detected a block number that is out of
sequence which suggests the datafile may be corrupt.
User Response: Run Oracle’s offline database verification utility, dbv,

against the database. For more information about dbv, see the Oracle
Server Utilities manual for your version of Oracle. If dbv does not detect
an integrity problem with the database, contact BMC Software Technical
Support.
DT-02114 SQL-BackTrack License Error:

Not licensed for Oracle Parallel Server. Machine ID: <machine_id>.
Explanation: You are trying to use SQL-BackTrack on an Oracle

Parallel Server installation without a license key enabled for Oracle
Parallel Server.
User Response: Contact your BMC Software sales representative for a

new license key.
DT-02128 This block does not contain table data.
Explanation: This message can appear in the following situations:
• logical extraction is not enabled

• there is no information in this tablespace for logical extraction
• logical extraction is not supported (it is unavailable for the SQL
Backtrack for Oracle Parallel Server product)
User Response: If you are not running SQL-BackTrack for Oracle

Parallel Server, verify that logical extraction is enabled. If it is not
enabled, enable it.
Error Messages 2-29

DT-02130 Oracle type has invalid length: <length>
Explanation: The data returned to SQL-BackTrack from a SELECT

statement has a length larger than Oracle allows for its type. This error
should not occur.
DT-02132 Corrupted (fractured) block found (block == <block_number>).
Explanation: SQL-BackTrack has found an Oracle database block that

is corrupted or fractured.
User Response: Check the state of your database using the DB Verify
tool (dbv) or another tool that can scan for corrupted blocks. If you find
corrupt or fractured blocks, call Oracle Technical Support to resolve the
problem. If you do not find any corrupt or fractured blocks, contact BMC
Software Technical Support.
DT-02136 Unable to shut down database <SID>:

Automatic shutdown of Oracle Parallel Server not supported.
Explanation: The instance identified by the system ID, which resides

on an Oracle Parallel Server, cannot be shutdown automatically.
User Response: Manually shutdown every Oracle Parallel Server on

each host.
DT-02141 Version of Oracle not supported: %<version>1
Explanation: The version of Oracle that you are running is not

supported by the version of SQL-BackTrack for Oracle that you are
running.
User Response: You need to upgrade to a supported

Oracle/SQL-BackTrack for Oracle combination. Please contact
BMC Software Technical Support for more details.

DT-02142 Invalid reset-logs-count found: <time>
Explanation: During backup, SQL-BackTrack queries certain Oracle

views (x$kccdi for Oracle7 and v$database for Oracle8) to get the time
when the last reset log occurred. If the time it receives is invalid,
SQL-BackTrack produces this error message . This event should not
occur very often.
User Response: Check the consistency of the views mentioned in the

explanation. If you do not know how to repair the views, call Oracle
technical support to resolve the problem.
DT-02346 Mismatch found in incarnation numbers for block <block number>:

Block incarnation = <1*x> and change incarnation = <1*y>.
Explanation: When applying redo log records to roll forward or roll

backward changes to datafiles, SQL-BackTrack found inconsistencies;
so, the application of redo logs was reversed.
User Response: The particular roll forward or rollback cannot be

performed to this point in time. Choose another point in time.
DT-02354 Table '<schema>.<table_name>' is not in the data dictionary.
Explanation: SQL-BackTrack attempted to issue a query on a table

that cannot be found in the database.
User Response: Use the obacktrack program to synchronize the

SQL-BackTrack catalog directory with the database and run the
operation again. If the problem occurs again, contact BMC Software
Technical Support.
DT-02363 Unable to update block <block_number>: not enough free space --

need <number> bytes, and only <number> bytes available.
Explanation: During logical extraction, SQL-BackTrack detected a

problem with one of the blocks in a table. This is a very rare error and
may represent an internal error.
Error Messages 2-31

DT-02460 Encountered conflicting values '<value_1>' and '<value_2>' for
parameter <parameter>.
Explanation: SQL-BackTrack has encountered two different values for

the same parameter. For instance, this message will appear if different
values are encountered for the USERID parameter stored in the
export/import
<catalog_dir>/<dbname>.db/export/<profile>.exp/options.rdf file.
User Response: Ensure that non-conflicting values have been provided

for the parameter and rerun the operation. If the problem persists, call
BMC Software Technical Support.
DT-02470 Unable to determine version of datafile block <block_num>.

It may be corrupt.
Explanation: SQL-BackTrack issues this error if it detects a data file

corruption when reading a database for a backup. This error indicates
that the data file is probably corrupt. This message indicates the block
number at which the corruption was detected. This message would
generally occur with DT-02480, which indicates the name of the
corrupted data file.
User Response: If the database is corrupt, you will need to contact

Oracle Technical Support. You can also try recovering from a previous
backup and seeing if the corruption persists.
DT-02480 Unable to determine block version of Oracle file <filename>.

It may be corrupt.
Explanation: SQL-BackTrack issues this error if it detects a data file

corruption when reading a database for a backup. This error indicates
that the data file is probably corrupt. This message indicates name of the
corrupted data file. It generally occurs with error DT-02470, which
indicates the location of the suspect block.
User Response: If the database is corrupt, you will need to contact

Oracle Technical Support. You can also try recovering from a previous
backup and seeing if the corruption persists.

DT-02485 DTOARCHMON(<host_name>:<port_number>) not responding.
Explanation: Archive log monitoring is set to on in SQL-BackTrack,

but the archive log monitoring program, dtoarchmon, is not running on
that server. Either dtoarchmon is not running, or the TCP/IP port is not
active.
User Response: If dtoarchmon is up, shut it down and restart it. Make
sure that the port it is running on is available and active. If dtoarchmon is
down, start it using the dtoarchmon command. For complete syntax, see
the SQL-BackTrack for Oracle User Guide.
DT-02622 Invalid column specification for “<owner>.<table>”.
Explanation: Two events might trigger this error: an internal error or a

user definition error.
• If you used the obacktrack Main Menu interface to generate the

logical extraction parameter file and receive this error, then this is an
internal error.
• If you supplied the extraction file and receive this error, then you
made an error when defining the TABLEDEF entry in the logical
extraction parameter file.
TABLEDEF={ownername.table_name(column1,column2,....)}
User Response: Each type of error has a specific solution.
If this is an internal error, the user should contact BMC Software

Technical Support.
If this is a syntax error, the user should review and correct the command
syntax.
Error Messages 2-33

DT-02623 Missing ASOF value in logical extraction parameter file.
Explanation: SQL-BackTrack did not find a value for the ASOF

parameter in the logical extraction parameter file. This parameter
specifies the time to which to recover the table or tables you selected. If
you used the obacktrack Main Menu to perform logical extraction, this
problem should not occur.
User Response: If you created or edited the logical extraction

parameter file in a text editor, open the file and add the ASOF parameter.
Refer to the SQL-BackTrack for Oracle User Guide for the syntax.
If you used the obacktrack Main Menu to enter the logical extraction
parameters and did not edit the parameters file directly, contact BMC
DT-02624 Missing tablespace name in logical extraction parameter file.
Explanation: SQL-BackTrack did not find a value for the

TABLESPACE parameter in the logical extraction parameter file. This
parameter specifies the tablespace into which to insert the extracted table
or tables. If you used the obacktrack Main Menu to perform logical
extraction, this problem should not occur.

parameter file in a text editor, open the file and add the TABLESPACE
parameter. Refer to the SQL-BackTrack for Oracle User Guide for the
syntax.

DT-02625 Cannot use “<character>” as both Delimiter and Enclosing
character in extracted data.
Explanation: You entered the same value for the DELIMITER and
ENCLOSURE parameters in the logical extraction parameter file. These
parameters specify two separator characters used to format the extracted
data. If you used the obacktrack Main Menu to perform logical
extraction, this problem should not occur.

parameter file in a text editor, open the file and change the value of either
the DELIMITER or ENCLOSURE parameter. Refer to the
SQL-BackTrack for Oracle User Guide for the syntax.
DT-02626 Table at index “<table_index>” not found in logical extraction

parameter file.
Explanation: SQL-BackTrack cannot find the table you chose to

extract in the TABLEDEF parameter in the logical extraction parameter
file. This parameter specifies the tables that will be extracted when you
run dtoextract. This error should never occur.
DT-02627 Table “<table_name>” not found in logical extraction parameter file.
Explanation: SQL-BackTrack cannot find the table you chose to

extract in the TABLEDEF parameter in the logical extraction parameter
file. This parameter specifies the tables that will be extracted when you
run dtoextract. This error should never occur.
Error Messages 2-35

DT-02628 Error creating table “<table_name>”
Explanation: This warning message occurs when a CREATE TABLE

SQL statement fails while SQL-BackTrack is loading an extracted table
into a database. This warning usually occurs if the table being loaded
already exists in the database.
User Response: To prevent this error from occurring again, use the
Oracle error message displayed before this message to debug the
problem.
DT-02630 Undefined format of Oracle files.
Explanation: SQL-BackTrack (specifically, the dtoextract program)

cannot determine the format of the Oracle datafiles based on the version
of Oracle you are running.
User Response:
DT-02633 The IO buffer is too small: <size_in_kbytes> -- must be equal to or

larger than the data block size: <size_in_kbytes>.
Set the ‘iobuffer_size’ parameter to a higher value.
Explanation: The value for the parameter iobuffer_size in the

$DTBASE/obacktrack/ctl/parameters file is smaller than the size of an
Oracle block.
User Response: Increase the value of the iobuffer_size parameter to be

at least as large as the Oracle data block size.

DT-02634 Unknown logical extraction parameter: <parameter_name>
Explanation: This error is caused by a syntax error in the logical

extraction parameter file.
User Response: If you created your own logical extraction parameter

file in a text editor, check the syntax. Refer to the SQL-BackTrack for
Oracle User Guide for the complete syntax of this file.
If you ran the logical extraction process through the obacktrack Main
Menu, SQL-BackTrack should have automatically created this parameter
file based on the responses you entered. If you have not edited this file,
call BMC Software Technical Support.
DT-02651 Logical extraction is not available for OPS databases.
Explanation: This is an informational message indicating that logical

extraction is not available for the OPS version of the SQL-BackTrack for
Oracle product.
User Response: None required.
DT-02652 Archived log ‘<log_file_name>’ is truncated or is still being written.

The archived log file cannot be backed up at this time.
Explanation: SQL-BackTrack cannot back up the archive log file

specified in the message because Oracle is still writing to that archive
log. This is a warning message and will not stop the backup process for
the remaining archive logs and datafiles. This message will only occur if
you try to force SQL-BackTrack to back up all archive logs by using the
-archivelogs option with the dtobackup command.
User Response: None required.
Error Messages 2-37

DT-02653 The diskgroups block is missing from the procconfig.rdf file. This
block must be present for successful parsing of the file.
Explanation: The process configuration file

(<catalog_dir>/<dbname>.db/config/procconfig.rdf) is corrupted or
contains an invalid entry.
User Response: Edit the procconfig.rdf file to correct the problem. See
the SQL-BackTrack for Oracle User Guide for information on the
appropriate format of this file.
DT-02654 The redo_logs block is missing from the procconfig.rdf file. This

DT-02655 The archive_logs block is missing from the procconfig.rdf file. This


DT-02656 The parm_files block is missing from the procconfig.rdf file. This

DT-02657 The control_files block is missing from the procconfig.rdf file. This

DT-02658 A pool which is not defined in the POOL file has been specified in
the procconfig.rdf file or as a default.
Explanation: An invalid backup pool was specified in one of the

following places:
• a “pool=” parameter in config/procconfig.rdf

• the “default_backup_pool=” parameter in physical/options.rdf
• the “logical_backup_pool=” parameter in physical/options.rdf
• the “default_backup_pool=” parameter in export/options.rdf
Each of these parameters must indicate a single backup pool or

poolgroup that is correctly defined in the <catalog_dir>/poolinfo/POOLS
file. A list of pools is not acceptable. If you want to direct a backup to
multiple pools, you must create a poolgroup.
Error Messages 2-39

The pool must first be defined in the POOLS file, before it can be
specified in the proconfig.rdf file.
User Response: Determine which parameter is causing the error, then

do one of the following: change the pool specification to correctly define
the backup pool or add a matching backup pool using the obacktrack
Main Menu.
DT-02659 An invalid RDF block with key = <key_name> has been detected in
the procconfig.rdf file. This is a syntax error.
Explanation: The <catalog_dir>/<dbname>.db/config/procconfig.rdf file

contains a syntax error.
User Response: Check the syntax of the key causing the error. Refer to
the SQL-BackTrack for Oracle User Guide for the complete syntax of the
procconfig.rdf file.
DT-02660 The numeric file specifier ‘<file_ID>’ listed in the procconfig.rdf file
cannot be mapped to a datafile in the dbprofile.rdf file.
Explanation: A numeric file ID listed in the

<catalog_dir>/<dbname>.db/
config/procconfig.rdf file cannot be mapped to one of the datafiles listed in
the <catalog_dir>/<dbname>.db/physical/dbprofile.rdf file. Unique Oracle
file IDs are sometimes given instead of a datafile name in the diskgroups
section of the procconfig.rdf file. These file IDs must match the ones
automatically collected by SQL-BackTrack and stored in the
dbprofile.rdf file (which you should never edit manually).
User Response: Update the file IDs in the procconfig.rdf file with the
most current values from the database.

DT-02661 Unable to start dtoarchmon on node(s): ‘<node_list>’
Please check your archivelog backups .
Fix the problem on the node(s) and take archivelog backup.
Explanation: This warning message occurs when dtoarchmon cannot

be started on an Oracle Parallel Server node. Usually, this means that
either dtlicense or dtoarchmon is using a TCP/IP port that is already being
used on that node. If you do not restart dtoarchmon, the archive logs on
that node will not get backed up until the next database backup.
User Response: Check for dtlicense and dtoarchmon port conflicts on

the node. These ports are stored in the $DTBASE/obacktrack/ctl/dthosts
file. The default TCP/IP port assignments are documented in the
SQL-BackTrack for Oracle User Guide.
DT-02919 Can't stat %<oracle>1
Explanation: The filename in the error message does not exist.
User Response: Try to bring the filename in the required location
DT-02925 Unexpected EOF <program_name>
Explanation: SQL-BackTrack starts several child processes to perform

backup and recovery. If one of the child processes terminates
prematurely, then the parent process produces this error message. This
message is a symptom of another problem.
User Response: Look for the corresponding messages in the

$DTBASE/obacktrack/log/datatools.log file to determine why the child
process terminated prematurely and take action to resolve the problem.
DT-02928 dtoquery write error, %<errno>1
Explanation: The program encountered a system error preventing a

write action.
User Response: Please check the error returned by the system and take
appropriate action.
Error Messages 2-41

DT-02929 Query state not ready
Explanation: SQL-BackTrack was unable to connect to the database.
User Response: Check the condition of your database and all related
environment variables and run the SQL-BackTrack operation again.
DT-02945 Invalid Msg: %<kArch_MasterDB>1 %<rdfColstring>2
Explanation: The dtoarchmon command receives a message to

become master. The database name and Oracle SID should be in the
prompt of the BECOME_MASTER message.
User Response: This error message is received when the prompt which
requests dtoarchmon to become master has no database name or Oracle
SID in it.
DT-02949 The Oracle locale environment variable NLS_LANG

(<Oracle_locale>) and the system locale environment variable
LANG (<system_locale>) does not represent the same locale.
Explanation: The LANG and NLS_LANG environment variables are

inconsistent with each other. These two environment variables should
always be set to the same locale.
User Response: If these two environment variables are set, ensure that
they refer to the same locale. NLS_LANG has the format
<language_territory>.<character_set>. LANG has the format
<language_code>. (Use the Unix command locale to view your current
LANG setting.)
DT-02979 Failed in verifying if uid of SQL-Backtrack process is same as

oracle uid
Explanation: The user ID of the SQL-Backtrack process is not the

same as the user ID of the Oracle installation.
User Response: Check the /etc/passwd and /etc/nsswitch.conf and verify

that the user ID of the SQL-Backtrack process is the same as the Oracle
user ID.

DT-03000 to DT-03999
DT-03009 Cannot migrate physical profile for <dbname> to specified catalog
directory. Would overwrite existing catalog.
Explanation: During migration, our product has detected an existing

database in the catalog directory and would not overwrite it.
User Response: Perhaps the migration utility has been run already, or
the product has been run on the <database>, then the migration is then
run.
DT-03266 Can’t start OBSI.
Explanation: This error message indicates the SQL-BackTrack

product’s attempt to spawn a process to write information to the selected
backup pool. Insufficient operating system resources is one possible
cause.
User Response: Contact the Unix system administrator to review and

correct the problem.
DT-03404 Error binding stream socket on port <portnum> <error_msg>.
Explanation: The license manager, dtlicense, attempted to access a

port number to initiate the license verification process, but failed. The
reason for the failure will be cited within the brackets. One common
reason is that the port number is being used by another process.
User Response: Change the dtlicense port number in the dthosts file, as
described in the SQL-BackTrack for Oracle User Guide.
DT-03410 Unrecognized option.
User Response: The license manager, dtlicense, has detected the use of
an unrecognized option during execution of the dtlicense program.
User Response: Retry the command and use only supported options.
Error Messages 2-43

DT-03600 Shared memory for activity display is not available.
Explanation: Backup and recovery activities can be monitored by

executing the dtwatch utility. This program displays entries put into
shared memory by the SQL-BackTrack product. For dtwatch to function
properly, the product requires the following system resources:
• 4K of shared memory
• 1 semaphore set
• 25 semaphores
If dtwatch cannot obtain the resources, this error message is displayed.

The error is usually preceded by a warning. For example,
% dtwatch
DT-01162W: ShMemInitialize: semget error [No space
left on device].
DT-03600F: Shared memory for activity display is not
available.
User Response: Contact your Unix system administrator so that

adjustments can be made to the appropriate operating system parameters.
To avoid getting this resource message, you can disable dtwatch by
setting the environment variable DTSHMEM to NONE. The side effect
of this workaround is that dtwatch will no longer work.
DT-03807 <program_name>: open failed for file '<file_name>'

[<Unix_error_message>].
Explanation: SQL-BackTrack has encountered an error in trying to

open a file for customizing.
User Response: Ensure that the SQL-BackTrack user (usually oracle)

has read/write permissions for the file listed in the message. Adjust the
permissions accordingly and restart the operation.

DT-04000 to DT-04999
DT-04384 OBSI driver returned file name when backup process had already
completed.
Explanation: This message occurs when a dtobackup process has

terminated abnormally. The OBSI is unaware of the termination and
passes the name. This message is always preceded by messages
indicating the cause of the backup failure.
User Response: Respond to the message received prior to the failure

that indicate the cause of the backup failure.
Error Messages 2-45

DT-05000 to DT-05999
DT-05001 The following are invalid arguments: <argument_list>
Explanation: The SQL-BackTrack program that produced this error

was called with the command option or options in <argument_list>, but
these arguments are not valid for this program.
User Response: Run the program again using a valid set of arguments.
See the SQL-BackTrack for Oracle User Guide for a complete list of the
syntax for each component program.
DT-05005 Conflicting options: ‘<option_1>’ and ‘<option_2>’
Explanation: SQL-BackTrack has detected that two conflicting option

parameters are being passed to a SQL-BackTrack program.
User Response: Ensure that the SQL-BackTrack options are correct.

Rerun the configuration process through the obacktrack Main Menu if
necessary. If you detect a conflicting option, replace it and restart the
operation.
DT-05011 You are running as user ‘username1’. You must run as ‘username2’
for physical backup or recovery.
Explanation: This error can occur if the user running backup and
recovery operations is not user “Oracle”.
User Response: Run the backup or recovery operation as user

“Oracle”. This is the requirement to run backup and recovery tasks
through SQL-BackTrack for Oracle.

DT-05062 <dbname>: Invalid backup user and/or password. A valid
user/password must be given in order to perform unattended
backup.
Explanation: The user and password stored in the SQL-BackTrack

catalog directory did not work when connecting to the Oracle database.
This usually happens when the password for the database has changed
but you have not updated the SQL-BackTrack catalog directory.
User Response: Use the obacktrack program to update the password.

You will be prompted to enter the new password.
DT-05077 OBSI completed with error status = '<argument>'

Will send SIGTERM(15) to terminate all child process relating to this
task
Explanation: A SQL-BackTrack OBSI Module process encountered

an error that may cause backup or recovery to fail.
This message is generated whenever the OBSI Module fails (either

during backup or recovery). There is always a backup or recovery
process associated with each OBSI process (dtodump in the case of
backup and dtoload in the case of restore). The backup process supplies
data to the OBSI Module for writing to the backup media; the recovery
process takes data out of the OBSI Module and writes it to the
destination. When the OBSI Module process fails, the related backup or
recovery process is cleaned up by SQL BackTrack for Oracle.
User Response: This is an informative message. No action needs to be

taken.
DT-05096 Cannot determine non-null value for pool.
Explanation: SQL-BackTrack cannot find any pools for backup or

recovery.
User Response: Ensure that the pools are properly specified in the files
<catalog_dir>/dbname.db/config/procconfig.rdf and
<catalog_dir>/poolinfo/POOLS and restart the operation.
Error Messages 2-47

DT-05122 You did not enter the same encryption key both times.
Explanation: When configuring encrypted backups with the

obacktrack program, you are prompted twice for the encryption key to be
sure that you have typed it correctly. You get this message if the second
encryption key you type does not match the first one.
User Response: You will be prompted again to enter an encryption key.

Be careful to type it the same way both times, and to remember this key.
DT-05136 <obsiname> is an unrecognized OBSI device name.
Explanation: You have specified a OBSI device that is unavailable.
User Response: Make sure that you have entered the OBSI device
name correctly. Check the OBSI device to see that it is installed
correctly; and, make sure that there is a valid link to it in the
$DTBASE/obacktrack-<version>/links directory.
DT-05242 Backup pool '%<pool>1' is already defined.
Explanation: This message is generated when a given backup pool

name is already defined in the catalog.
User Response: Use a different name for the backup pool.
DT-05306 Offline dump of SYSTEM tablespace not allowed; must be cold or

online.
Explanation: SQL-BackTrack was instructed to do an offline backup

of the SYSTEM tablespace. The SYSTEM tablespace cannot be taken
offline; it must be backed up in an online or cold backup.
User Response: Perform an online or cold backup of the SYSTEM

tablespace instead.

DT-05308 No output file given.
Explanation: The dtodump command was started without an output

file.
User Response: This is an internal error; try re-running the backup.
DT-05309 Cannot dump redo logs; must be a cold backup.
Explanation: A redo log backup was attempted without first shutting

down the database. Redo logs can only be backed up when the database
is shut down (during a cold backup).
User Response: Use a cold backup to back up redo logs. You can use
the obacktrack command to generate an appropriate backup script or to
perform the backup.
DT-05310 Offline dump of active rollback segment not allowed; must be cold
or online.
Explanation: You have tried to perform an offline backup on a

tablespace containing active rollback segments. You cannot take a
tablespace offline if it has active rollback segments.
User Response: Either use a different type of backup (online or cold)

or take the rollback segment offline before performing the offline backup.
DT-05311 Must specify one of the following: -datafile, -controlfile, -redolog,

-archivelog, -parmfile, or -logicalfile.
Explanation: The dtodump command lacks the argument that specifies

the type of file to back up.
User Response: Provide the type of file to back up using one of the
following options on the dtobackup command: -datafiles, -archivelogs,
-controlfiles, -redologs, or -parmfiles. If you still get an error, it is an
internal error; contact BMC Software Technical Support.
Error Messages 2-49

DT-05330 No source file given.
Explanation: The dtoload command was invoked without the -from

option.
User Response: This is an internal error; contact BMC Software

Technical Support.
DT-05331 Unknown dump type.
Explanation: On recovery, the dtoload command cannot determine

what type of file was backed up. This is usually a version problem; an
earlier version of dtoload might be trying to read data backed up with a
later version of SQL-BackTrack.
User Response: Be sure you are using the latest version of

SQL-BackTrack to perform a recovery.
DT-05333 Cannot log switch during a cold backup.
Explanation: The -logswitch argument was provided for a cold

backup.
User Response: Do not try to switch logs during a cold backup. You
can switch logs during an online backup.
DT-05337 No Oracle datafiles given.
Explanation: The dtodump command was invoked without any

datafiles to back up.
User Response: Provide the names of the datafiles to back up using the
-datafiles option on the dtobackup command. If you still get this error,

DT-05339 Cannot find Oracle control files.
Explanation: The dtodump command was unable to locate the Oracle

control files.
User Response: This message might indicate that the database needs
recovery; make sure that the control files are present. If they are, verify
that the oraclehome, oraclesid, and initora values are set correctly in the
opsconfig.rdf file in the catalog directory
(<catalog_dir>/<dbname>.db/config/opsconfig.rdf).
DT-05340 No Oracle redo log files given.

redo logs.
User Response: This message might indicate that the database needs
recovery; make sure that the redo logs are present. If they are, verify that
the oraclehome, oraclesid, and initora values are set correctly in the
opsconfig.rdf file in the catalog directory
DT-05341 Cannot find Oracle parameter files.

parameter files.
User Response: Make sure that the oraclehome, oraclesid, and initora
values are set correctly in the opsconfig.rdf file in the catalog directory
(catalog/dbname.db/config/opsconfig.rdf).
DT-05342 Following arguments are invalid with <argument>: <values>.
Explanation: The dtodump command received invalid arguments, as

described in the message. This is an internal error, as dtodump is not a
user-callable program.
Error Messages 2-51

DT-05351 Database alive; continue?
Explanation: A restore operation has started while the database is

running.
User Response: If there is no danger of corruption, then continue.

Otherwise, or if you are unsure, type n to stop the current operation. Use
the obacktrack command to create an appropriate recovery script for the
current situation.
DT-05355 This is not a user-callable program.
Explanation: You have tried to invoke an internal program from the

command line. Internal programs include dtodump and dtoload.
User Response: Use the obacktrack command to create scripts or

execute commands, or use the higher level dtobackup and dtorestore
commands.
DT-05400 Multiple values for tablespace argument.
Explanation: This is an internal error. The dtodump command

received too many values for the -tablespace argument.
DT-05401 Multiple values for source file argument.
Explanation: This is an internal error. The dtoload command received

too many values for the -logicalsrc_file argument.

DT-05402 Missing data dictionary source file.
Explanation: The name of the file containing the data dictionary

information has not been provided as a -logicalsrc_file option on the
dtoload command.
User Response: Supply the name of the data dictionary file, using the
-datadict option on the dtorestore command. If the problem persists,
DT-05403 No list of tables to extract.
Explanation: You have attempted to do a logical extraction without

providing a list of tables to extract.
User Response: Use the obacktrack command to create the logical

extraction.
DT-05404 No value for end RBA.
Explanation: The argument -end_rba is missing from the command

line for the dtoload command. This argument is required for logical
extraction. This is an internal error.
User Response: If you received this error using dtorestore or the

obacktrack command, contact BMC Software Technical Support.
DT-05405 Destination filename must be specified for source file <filename>.
Explanation: SQL-BackTrack was directed to do a logical extraction

of data, but there is no filename for the extracted data file.
User Response: Use the obacktrack command to put together a correct

logical extraction. If the error persists, contact BMC Software Technical
Support.
Error Messages 2-53

DT-05411 <file_name>: <file_handle>: OBSI driver names cannot begin with
slash.
Explanation: The OBSI Module driver specified for this operation has
a name beginning with a slash in the obsi=<driver> key in the
<catalog_dir>/poolinfo/POOLS file. OBSI Module driver names in this
key cannot begin with slashes (/).
User Response: Change the value of the obsi=<driver> key to an

acceptable value. Acceptable values include disk for the disk OBSI and
tape for the tape OBSI. If you have a third-party OBSI, see your OBSI
Module user guide for the appropriate name.
DT-05439 Can't do -online or -offline backup when database is in

NOARCHIVELOG mode. Use -cold and -shutdown options.
Explanation: You attempted to run a type of backup which requires

that the database be in ARCHIVELOG mode, but your database is in
NOARCHIVELOG mode.
User Response: Use the -cold and -shutdown options when backing up
this database, or run the database in ARCHIVELOG mode.
DT-05469 Backup pool error: <Unix_error_message>
Explanation: An error occurred while SQL-BackTrack was trying to

use the <catalog_dir>/poolinfo/POOLS file. There are many possible
causes for this error. For example, the permissions of the POOLS file
might be set such that the user that is running SQL-BackTrack (usually
oracle) cannot open the file.
User Response: See the Unix error message at the end of this error
message for details about your particular problem and take appropriate
steps to resolve the problem.

DT-05471 Can't do cold backup of online database.
Use -shutdown option to shut down database.
Use -online option for online backup.
Explanation: You attempted to perform a cold backup of an online

database.
User Response: If you want to perform a cold backup, use the

-shutdown option with the dtobackup command to shut down the
database before the backup begins. If you want the database to remain
online, use the -online option to perform an online backup.
DT-05472 Can't do online backup when database is shut down.

Use the -cold option or start up the database.
Explanation: The dtobackup command attempted to do an online

backup of a database that is not currently online. The backup fails in this
case. (This only occurs when the dtobackup command is issued from a
script; the obacktrack program will not let you attempt an online backup
of a database that is not available.)
User Response: Restart the database and re-issue the command. Or,
change the -online option on the dtobackup command to -cold, to
perform a cold backup of a database that has already been shut down.
Use the obacktrack command to see what kinds of backups are available
to you.
DT-05504 -asof <date_time>: invalid date/time specification
Explanation: You used an invalid format for the date and time in the
-asof option of the dtorestore command.
User Response: Run the dtorestore command again using a valid

date/time format in the -asof option. For a list of valid date/time formats,
see the SQL-BackTrack for Oracle User Guide.
Error Messages 2-55

DT-05505 You cannot use both -asof and -scn on dtorestore command
Explanation: You issued a dtorestore command with both the -asof and
-scn options, which are incompatible. You cannot perform a point-in-time
recovery based on both the time and the System Change Number (SCN).
User Response: Run the dtorestore command again using only one of
these two command options..
DT-05506 Can't create destination directory: <directory_name>

Explanation: SQL-BackTrack received an operating system error

while attempting to create a directory.
User Response: Examine the operating system error message at the end
of this message and take steps to resolve the problem.
DT-05577 No output file handle was provided by OBSI driver

Backup information can not be recorded in file <file_name>

for Oracle.
User Response: Ensure you have not mistyped the error number. This
message is not being used any more.
DT-05601 Backup of the online redo logs must be part of a COLD backup.

for Oracle.
User Response: Ensure you have not mistyped the error number.

DT-05603 Unable to determine available disk space for ‘<directory_name>’.
Explanation: A system call by SQL-BackTrack to determine the

available space for the directory specified in this message failed. This is a
warning message and should not prevent the operation from continuing.
User Response: No response required.
DT-05604 Can only use one of -archive_scn_range, -archive_asof_range, or

-archive_thread_range.
Explanation: When you ran the dtorestore command, you provided

two or more of the options listed in this message. These three options are
incompatible with each other.
User Response: Run the dtorestore command again using only one of
these options.
DT-05607 Must use -destdir when restoring a data-dictionary file.
Explanation: You attempted to restore data-dictionary information

without using the -destdir option in the dtorestore command. The -destdir
option specifies the directory to which this information will be restored.
User Response: Run the dtorestore command again using the -destdir
option. For more information about the syntax of dtorestore, see the
SQL-BackTrack for Oracle User Guide.
DT-05608 Database unavailable -- unable to backup data-dictionary

information.
Explanation: When you have enabled logical extraction and the

database is down during the backup, you will receive this warning. The
database must be up to generate the data dictionary information required
for logical extraction. You will not be able to extract logical objects from
this backup.
User Response: Make the database available.
Error Messages 2-57

DT-05609 Unable to determine the current redo-block-address needed for
logical extraction.
Explanation: In the unlikely event that you receive this error, it implies
that your redo log files have been corrupted.
User Response: Contact BMC Software Technical Support if you need

help to confirm that the redo log files are corrupt. If they are corrupt, you
may have to recover them from backups before attempting the logical
extraction procedure again.
DT-05610 No dumps available for parameter files.
Explanation: You attempted to restore a datafile for which no backups

are registered in the SQL-BackTrack backup history.
User Response: Confirm that there are no backups available for this
datafile. If there are none available, then it is impossible to recover this
file.
DT-05611 No level zero dumps available for <file>.
Explanation: Attempted to restore a database file for which there are

no level zero dumps registered in the backup history.
User Response: Confirm that there are no level zero dumps available
for this file. If in fact there are none; then, it is impossible to recover this
file.
DT-05613 Unable to backup online redologs: Database is online.
Explanation: You attempted to back up the online redo logs with

database online. The online redo logs are constantly changing while the
database is receiving transactions and cannot be backed up to a consistent
state.
User Response: Shut down the database and retry the backup
operation.

DT-05614 The backup history of ORACLE_SID <sid> for <filename> is in use
by another program.
Explanation: Another program has locked the backup history of the

named Oracle instance for the file stated in the error message.
User Response: Look for other processes that may be locking the
backup history information contained in the SQL-BackTrack catalog
directory. If you find a likely candidate, wait for it to complete before
retrying the operation that generated the message. Otherwise, contact
BMC Software Technical Support for help in unlocking the backup
history file.
DT-05615 Skipping backup of <filename>.
Explanation: SQL-BackTrack was unable to perform the backup listed

because the backup history was locked (another program is locking it).
retrying the backup. Otherwise, contact BMC Software Technical
Support for help in unlocking the backup history file.
DT-05616 Unable to restore <filename>.
Explanation: SQL-BackTrack was unable to restore a file. This error

occurs when the backup history information is locked (another program
is locking it).
retrying the restoration. Otherwise, contact BMC Software Technical
Support for help in unlocking the backup history file.
Error Messages 2-59

DT-05618 No mode given to dtorutil.
Explanation: The dtorutil command was invoked without a required

mode option.
User Response: If you were invoking the dtorutil command from the
command line or within a script, re-run the command with one of the
following options: -recover, -syncnames, -syncredo, -online, or -offline.
DT-05628 Backup in progress for <database_name>. Unable to continue...
Explanation: SQL-BackTrack does not support taking multiple

backups of a single database at the same time. In other words, if one
backup is running against a database, you cannot start another backup of
the same database.
Archive log backups are an exception. Archive log backups can take
place while any type of physical backup is going on (except another
archive log backup).
User Response: Wait for the earlier backup to complete before you
continue with the current backup.
DT-05631 No profile defined for database <dbname>.
Explanation: There is no profile defined in the SQL-BackTrack

catalog directory for the named database.
User Response: Use the obacktrack command to create a profile for the
database.
DT-05632 No profile defined for database <dbname> as of '<time>'.
Explanation: There is no profile available in the SQL-BackTrack

catalog directory for the named database as of the required time.
database in question. If a profile already exists, use the Database option
in the Database Catalog options menu to update the database profile.

DT-05633 No profile defined for database <dbname> as of change '<scn>'.

catalog directory for the named database with the appropriate SCN
number.
database in question. If a profile already exists, use the Synchronize
Database option in the Database Catalog options menu to update the
database profile.
DT-05634 No profile defined for database <dbname> with reset id <reset>.

catalog directory for the database named in the message with the
appropriate reset id.
database in question. If a profile already exists, use the Synchronize
Database option in the Database Catalog options menu to update the
database profile.
DT-05682 No data dictionary dumps available.
Explanation: SQL-BackTrack attempted to restore Oracle data

dictionary information (in the process of extracting a table from a
physical backup), but it could not find any data dictionary backups in the
backup history.
User Response: To enable automatic data dictionary backups, you must

enable the logical extraction feature when you create or modify the
physical profile. Logical table extraction requires a valid backup of the
data dictionary.
To enable logical extraction, use the -tablespace_dict option with the

dtobackup command, or answer y to the following configuration
question:
Enable logical extraction? (y/n) [n]
Error Messages 2-61

DT-05684 Catalog and command line have conflicting values for the
-incremental option catalog has NO INCREMENTAL set, but
command line specifies the -incremental option with value greater
than zero: catalog prevails, full backup will be forced.
Explanation: This warning appears if NO INCREMENTALS was

specified at the time of catalog directory creation but while taking a
backup from the command line (running dtobackup from the OS
prompt), the user specifies the -incremental option or the -level option
with a level number greater than 0. The NO INCREMENTALS option in
the catalog directory overrides the command line parameter.
User Response: If you want an incremental backup, change the entry in

the catalog directory. See the SQL-BackTrack for Oracle User Guide for
instructions on creating or modifying an export profile.
DT-05686 READ ONLY Tablespace <tablespace_name> dictionary will be

skipped in this backup
Explanation: Backtrack skips read-only tablespaces, if the

-skip_readonly_ts switch is turned on during backup. The corresponding
dictionary information is also skipped for such tablespaces.
User Response: This is just informative warning message.
DT-05687 READ ONLY Datafile <datafile_name> will be skipped in this backup
Explanation: Backtrack skips read-only tablespaces, if the

-skip_readonly_ts switch is turned on during backup.
User Response: This is just a warning message.
DT-05906 Unable to perform recovery.
Explanation: SQL-BackTrack is unable to initialize itself to start the

recovery. This may be due to an internal error or corruption in the catalog
directory.

Error Messages 2-63

DT-06000 to DT-06999
DT-06613 Error starting database <sid>: <msg>.
Explanation: SQL-BackTrack was unable to start the database

instance listed in the error message. The Oracle error generated is
included in the message.
User Response: Check the Oracle error message. Try starting the
database instance, and contact Oracle Technical Support if necessary.
DT-06614 Unable to read backup pool file <file>: <errmsg>.
Explanation: SQL-BackTrack was unable to read the backup pool file.
User Response: Check the error message. Check to see if the POOLS
file (<catalog_dir>/poolinfo/POOLS) is corrupted.
DT-06619 Unable to proceed with backup.
Explanation: The backup was interrupted.
User Response: Look for associated error messages, or use the dtwatch
command to see the most recent status and error messages for the
backup.
DT-06621 Backup failed.
Explanation: An attempted backup has failed. This message should

occur with other error messages that provide the cause of the failure.
User Response: Examine the associated error messages to determine

the problem. If you need help, save these messages and contact BMC

DT-06623 Dryrun backup failed.
Explanation: A dry-run backup failed. This message should occur

with other error and status messages that provide a reason for the failure.
User Response: Examine the status and error messages to determine

the source of the problem. If you are unsure, save these messages and
call BMC Software Technical Support.
DT-06625 Unable to run dtocheck to check the consistency of the database

profile.
Explanation: The obacktrack program is not able to run the dtocheck

utility to check the consistency of the database. This error might occur if
the database instance is not up. This message may occur with other error
messages.
User Response: Be sure the database is up and running.
DT-06639 Unable to access SYSTEM tablespace for database <dbname>.
Explanation: SQL-BackTrack was unable to access the SYSTEM

tablespace for the database. In most cases, this is because the
user/password provided for the backup or recovery does not have the
appropriate access.
User Response: Check the user name and password used to access the
database and make sure it has adequate privileges.
DT-06689 Unable to restore <file> to the original location.
Explanation: During a restore, a target directory into which the restore

will be copied is specified; however, during this operation, some error
has prevented the restore from succeeding.
User Response: Make sure the restore directory exists and ensure that
it has the proper permission.
Error Messages 2-65

DT-06715 <oraclehome> is not a directory.
Explanation: The $ORACLE_HOME value specified to

SQL-BackTrack is not a directory.
User Response: Check that the value listed in the error message is in
fact the ORACLE_HOME directory. If not, change the value of the
oraclehome key in the opsconfig.rdf file
DT-06890 No extract data for tablespace <tablespace-name>.
Explanation: There is no extract data for the given tablespace. Either

the tablespace does not contain any extractable tables.
User Response: Verify that tables are available for logical extraction
and verify that the logical extraction option is turned on before you
re-initiate the backup.
DT-06904 Column ('col_name') is an unsupported (or unknown) column type.

Exclude column and continue with extraction?
Explanation: The dtoextract process in SQL-BackTrack generates this

error message when you try to perform a logical extraction of a table
containing unsupported data types. Unsupported data types include:
• abstract data types

• variable length data types, such as LOBs, BLOBs, and CLOBs
User Response: You can still extract the columns that do not contain
the unsupported data types by typing y at the prompt to continue the
extraction. Typing n at the prompt cancels the current operation.

DT-06906 An unknown column data type (<type>) was detected during logical
extraction.
Explanation: SQL-BackTrack encountered an unknown data type

during a logical extraction. Unsupported data types include:
• abstract data types

• variable length data types, such as LOBs, BLOBs, and CLOBs
User Response: Check the data type in question. If it is unsupported,

then try the extraction again without the column in question. Contact
BMC Software Technical Support if you need assistance.
Error Messages 2-67

DT-09000 to DT-09999
DT-09001 Need archived log file for thread <thread> and sequence
<sequence>; [type "STOP" to stop][<RET>=<log>].
Explanation: The dtoextract command issues this prompt when it

needs to apply a redolog file that cannot be retrieved from the default
archive log destination or from the available physical backups. This error
typically occurs when a user tries to perform a logical extraction as of a
time later than the current time.
User Response: If the required redo log exists in a different location,

enter its complete filename at this prompt. If the redo log cannot be
found, or has not yet been generated by Oracle, type STOP to stop
applying redo log files to the extracted data.
DT-09002 The following arguments are invalid for dtoextract: <argument>.
Explanation: Invalid command line options (arguments) were passed

to the dtoextract command.
User Response: Verify the command syntax by typing help dtoextract

and try again. Or, use the obacktrack program to perform the logical
extraction.
DT-09014 There are no extract files open for given operation.
Explanation: The dtoextract command cannot find the extract files

generated from the physical backup. You will receive other error
messages along with this message.

DT-09100 Missing logical extraction parameter file.
Explanation: The dtoextract parameter file argument was not passed to

the dtoextract command. This error only occurs when calling the
dtoextract command from the command line.
User Response: Use the -parmfile option on the dtoextract command

to pass the name of the dtoextract parameter file. Or, use the obacktrack
command to create an extraction script with the appropriate options.
DT-09104 Unable to find log for thread <thread>, sequence <sequence>.
Explanation: This error indicates that the dtoextract program was

unable to find an archive/redo log file for the specified thread and
sequence number.
User Response: SQL-BackTrack should always prompt for a redo log

before issuing this error. If you do get this error, make sure all of the
appropriate log files are available.
Error Messages 2-69

DT-20000 to DT-20999
DT-20003 Directory <directory> already exists, and is not a catalog directory.
Explanation: The directory listed in the error message does not appear
to be a SQL-BackTrack catalog directory. Most likely, the .oracatalog file
is corrupted or missing from the catalog directory.
User Response: If you are trying to create a new catalog directory, the
directory must not already exist. Remove the directory and try again, or
put the catalog directory somewhere else. If this is an existing
SQL-BackTrack catalog directory, contact BMC Software Technical
Support.
DT-20009 Can't create directory: %<dir>1 [%E]
Explanation: The program could not create the directory mentioned.
User Response: Please check the error returned by the system and take
appropriate action.
DT-20012 Not a dump record: <begin_block>;
Explanation: SQL-BackTrack checks for appropriate begin header

information in its catalog directory RDF files. If this information is
different from the expected entry, the above error message is displayed.
This problem may be caused by corruption of the RDF files.
User Response: Restore the SQL-BackTrack catalog directory files

from a backup copy. If that is not possible, you will need to recreate them
by building a new catalog directory in the obacktrack Main Menu
interface using the configuration tools. Sometimes, corrupt RDF files can
be fixed by editing them in a text editor. See the SQL-BackTrack for
Oracle User Guide for information about how these RDF files should be
structured.

DT-20017 Datfile '<file_name>' not in dbprofile.
Explanation: You requested a datafile name that is not in the

SQL-BackTrack catalog directory.
User Response: Manually synchronize the catalog directory with the

database using the obacktrack Main Menu. Normally, the catalog
directory is synchronized automatically before every backup operation.
DT-20028 File <filename> is not a sequence file.
Explanation: The file listed in the error message is an invalid sequence

file.
User Response: Contact BMC Software Technical Support for

assistance repairing the file.
DT-20029 Invalid export definition: <exportname>.
Explanation: An invalid or nonexistent export profile was listed on the

command.
User Response: Check that you did not misspell the export profile
name. Check that the database listed does have a profile of that name by
looking at the contents of the <catalog_dir>/<dbname>.db/export
directory. There should be a subdirectory for each defined export profile.
DT-20041 Nothing to restart - job file missing: <dumpdir>

Job file is deleted on merge or rollback.
Explanation: This error occurs if you attempt to restart an interrupted

backup or recovery operation and the job file (required to restart
operations) is missing. The job file would be missing if the process was
interrupted before the job file could be written or if the process
completed successfully.
User Response: If the process completed successfully, no further action

is required. If the process was interrupted before creating a job file, start
the process again from the beginning (without the -restart option).
Error Messages 2-71

DT-20044 Invalid restart request for noarchivelog mode database.
Database SCN changed since last backup (SCN-SCN).
Job <jobid> is invalid and will be rolled back.
Explanation: This message arises if a database in NOARCHIVELOG

mode is restarted between the time SQL-BackTrack started a cold
backup (shutting down the database) and the time the failed backup was
restarted using the -restart option.
User Response: If you get this message, you must restart the backup
from the beginning (without the -restart option). If the problem persists,
DT-20045 Unknown export type: <type>.
Explanation: The options.rdf file for the export profile has an invalid
export_type entry. This is only likely to occur if you have edited this file
manually.
User Response: Edit the options.rdf file for the export profile being
called (<catalog_dir>/<dbname>.db/export/<profile>.exp/options.rdf).
Replace the export_type entry with a valid entry. Valid entries are: full,
owner, table, or incremental.
DT-20046 <profilename>: wrong profile type -- <type1> instead of <type2>.
Explanation: The .oracatalog file in the catalog directory is corrupt.

This is a required file.
User Response: Edit the .oracatalog file in the directory listed in the
error message. The first line should be:
type=type
Change the type in this line to the expected type listed in the error
message (type2).

DT-20047 Host <hostname> is not defined.
Explanation: The host name listed in the error message is not listed in
the OPS Configuration File
User Response: If you are running Oracle Parallel Server, edit the
opsconfig.rdf file and add all OPS nodes. See the SQL-BackTrack for
Oracle User Guide for more information on the OPS Configuration File.
If you are performing a disaster recovery (with or without OPS) and have
copied a SQL-BackTrack catalog directory to a new machine, edit the
opsconfig.rdf file and change the node name entry to match the node
name where you are currently running SQL-BackTrack.
DT-20048 File <filename> is not a valid jobfile: missing ‘begin job’ block.
Explanation: The job file is used to restart backup or recovery

operations. This message indicates that the job file listed in the message
is corrupt.
User Response: Rerun the failed backup or recovery operation from the
beginning (without the -restart option). If the problem persists, contact
DT-20049 File <filename> is not a valid jobfile: missing ‘begin files’ block.
Explanation: The job file is used to restart backup or recovery

operations. This message indicates that the job file listed in the message
is corrupt.
User Response: Rerun the failed backup or recovery operation from the
beginning (without the -restart option). If the problem persists, contact
Error Messages 2-73

DT-20051 No physical backup profile defined for database <dbname>.
Explanation: The dbprofile.rdf file for the database named in the

message is missing from the SQL-BackTrack catalog directory.
User Response: Use the obacktrack command to create a new physical

profile for the database. SQL-BackTrack will preserve any existing dump
history.
DT-20052 Operation restricted to Oracle owner <username>.

Running as user <username>.
Explanation: The user attempting to execute a SQL-BackTrack

command does not have the proper authority for the operation.
User Response: Make sure that the account running the command is
logged on as the correct user. See the SQL-BackTrack for Oracle User
Guide for more information on access privileges. Also, consult the log
file (datatools.log in the datatools directory) for other informational
messages related to this error.
DT-20055 No tablespaces defined for database <dbname>.
Explanation: SQL-BackTrack could not find any tablespaces in the

dbprofile.rdf file for the database within the SQL-BackTrack catalog
directory. This typically indicates that the dbprofile.rdf file is corrupt.
User Response: Run the dtocheck command with the SQL-BackTrack

catalog directory to resynchronize the catalog directory with the current
database schema. If the problem persists, contact BMC Software
Technical Support.

DT-20056 No datafile entries were found in the dbprofile.rdf file.
Explanation: SQL-BackTrack could not find any data files in the

dbprofile.rdf file for the database within the SQL-BackTrack catalog
directory. This typically indicates that the dbprofile.rdf file is corrupt.
User Response: Run the dtocheck command with the SQL-BackTrack

catalog directory to resynchronize the catalog directory with the current
database schema. If the problem persists, contact BMC Software
Technical Support.
DT-20057 Invalid jobid: nnnn.
Explanation: An invalid (or non-numeric) jobid was specified on a

command, typically a dtobackup command with the -restart and -jobid
options.
User Response: If you were trying to restart a job with a jobid, make
sure you did not mistype the jobid. If you were not issuing a dtobackup
-restart command with a jobid, then this is an internal error. Contact
DT-20060 Invalid backup order keyword <value>.
Explanation: This error may occur if you have manually edited the
options.rdf file. It is caused by an invalid entry (listed in the message) in
the backup_order section of the options.rdf file.
User Response: Edit the options.rdf file (located in

<catalog_dir>/<dbname>.db/physical/options.rdf) and remove the entry
listed in the error message.
Error Messages 2-75

DT-20061 Duplicate backup order keywords: <value>.
Explanation: This error may occur if you have manually edited the
options.rdf file. It is caused by a duplicate entry (listed in the message) in
the backup_order section of the options.rdf file.
User Response: Edit the options.rdf file (located in

<catalog_dir>/<dbname>.db/physical/options.rdf) and remove the
duplicate entry.
DT-20066 Invalid time found in '<value>=<time>'.
Explanation: An invalid time was found in a dump history file. This

indicates that the dump history file may be corrupt. If you edit the dump
history file, you may get this message.
DT-20068 Dump history is currently locked.
Explanation: An error was detected when attempting to lock the dump

history file.
User Response: Make sure that you do not have multiple backup or
expiration processes running against the same database at the same time.
Run the operation again. If the error still persists, contact BMC Software
Technical Support. Have a copy of the datatools.log file available for
DT-20077 Missing profile file: '<filename>'.
Explanation: The directory (or file) listed in the error message is not a
valid component of a SQL-BackTrack catalog directory. This is an
internal error that indicates that your catalog directory is corrupted.

DT-20079 Missing OPS config file: '<filename>'.
Explanation: The OPS configuration file specified in the error message

file is missing. This file is required for every installation, not only OPS
installations. It contains information about the Oracle home directory,
Oracle SID, thread number, and init.ora file location for each node of a
system.
User Response: Either restore the file from a previous file system
backup, or create a new file in
<catalog_dir>/<dbname>.db/config/opsconfig.rdf. For information on
the format of the file, see the SQL-BackTrack for Oracle User Guide.
DT-20080 Missing process config file: '<filename>'.
Explanation: The process configuration file (specified in the error

message) is missing. The process configuration file is a required file in
the SQL-BackTrack catalog directory. It resides in the config directory as
the file procconfig.rdf.
User Response: Either restore a previous copy of the process

configuration file (<catalog_dir>/<dbname>.db/config/procconfig.rdf)
from a file system backup, or create a new file. For information on
creating a new file, see the SQL-BackTrack for Oracle User Guide.
DT-20081 Thread <num> not found in the catalog.
Explanation: If encountered during a backup, this error indicates that

there are no valid entries for a redo thread in the SQL-BackTrack catalog
directory. If encountered during recovery, it means that SQL-BackTrack
cannot find entries in the catalog directory for a redo thread that is
required for recovery; the catalog directory may be corrupt or otherwise
invalid.
User Response: If you encounter this error during a backup, run the
dtocheck command with the catalog directory name to resynchronize the
catalog directory to the database, then retry the backup. If the error
persists, contact BMC Software Technical Support. If you encounter this
error during recovery, contact BMC Software Technical Support.
Error Messages 2-77

DT-20216 Catalog directory specified, '<path>', does not exist.
Explanation: The catalog directory listed in the error message does

not exist.
User Response: If you mistyped the catalog directory name on the

command, correct it. Otherwise, use the obacktrack command to create a
catalog directory. (Do not try to create the directory manually.)
DT-20245 Datafile in tablespace %<ts>1 attribute %<attr1>2 updated from

%<old2>3 to %<new3>4 in Backtrack Catalog.
Explanation: This message informs the user that a particular datafile

attribute has been changed (for example, the block count and block size).
This is an informational message.
User Response: None necessary.
DT-20500 Invalid value given for '<argument>: <value>'.
Explanation: You have specified an invalid parameter on the dtoexpire

command, as listed in the error message. See the dtoexpire man page for
information on syntax.
User Response: Re-run the dtoexpire command with the correct

argument.
DT-20501 You must indicate which files to expire when expiring by id; i.e.
when using -dumpid or -jobid.
Explanation: You have entered an invalid expiration parameter on the

dtoexpire command. See the dtoexpire man page for details.
User Response: Re-run the dtoexpire command with the correct

expiration parameters.

DT-20565 Responding with errors [host ‘hostname’, port nnn].
Explanation: (For OPS installations) A slave dtoarchmon process has

encountered an error.
User Response: Make sure the dtoarchmon processes are running on all
OPS nodes and the configuration parameters are set correctly.
DT-20570 Unable to become master-dtoarchmon for DATABASE: no access to

catalog.
Explanation: SQL-BackTrack could not access the catalog directory.
User Response: Check the operating system privileges of the account

under which SQL-BackTrack runs.
DT-20575 dtoarchmon is not responding on host ‘hostname’.
Explanation: This error can occur if the archivelog monitoring process

(dtoarchmon) is not running on the specified host.
User Response: Start dtoarchmon process on the specified host.
DT-20597 Error running dtoarchmon in background.
Explanation: The dtoarchmon process tried to fork itself into the

background and the fork failed.
User Response: Contact your system administrator to identify and

resolve the system problem that prevented the fork operation.
Error Messages 2-79

DT-20598 Port <portnum> already in use, assuming DTOARCHMON already
running. This program will exit.
Explanation: The dtoarchmon process attempted to start listening on a

port already in use by another program. SQL-BackTrack assumes that the
other program is a dtoarchmon process, which will do the work of the
process which has failed.
User Response: If the other process on the listed port is a dtoarchmon

process, then no action is required. If it is a different process, then you
should kill the program using the dtoarchmon port and restart
dtoarchmon. To prevent port contention from occurring again, either list a
new port for dtoarchmon in the dthosts file or change the port for the
other process.
DT-20994 When specifying -datafile <datafilename>, you must also provide

dumpid <dumpidvalue>.
Explanation: The dtoexpire command was invoked without a -dumpid

value. See the dtoexpire man page for details.
User Response: Re-run the command with the -dumpid value.
DT-20996 dtoexpire must be invoked with either the -database <dbname> or

-rmdatabase <dbname> flag set.
Explanation: The dtoexpire command was invoked without either the

-database or -rmdatabase flag set. See the dtoexpire man page for
details.
User Response: Re-run the dtoexpire command with the appropriate

-database or -remdatabase value.

DT-20997 The specified pool does not exist in the current profiles.
Explanation: The software attempted to look up a backup pool that

does not exist in the pool file for the catalog directory
(<catalog_dir>/poolinfo/POOLS).
User Response: Make sure that any pools specified in a command or in

a configuration file also exist in the POOLS file. Use the obacktrack
program to create a new backup pool, or edit the POOLS file manually.
Error Messages 2-81

DT-21000 to DT-21999
DT-21000 Invalid <value> value <data> specified.
Please specify valid numeric value.
Explanation: An invalid numeric or time value was specified for the

dtoreport option listed in the error message.
User Response: Check the value reported in the error message. Consult
the dtoreport man page for valid values for each option, or use the
obacktrack program to construct the report options.
DT-21018 Datafile: <filename> is not part of the profiles.

Please use the correct datafile name to generate reports.
Explanation: You have requested a report for a specific data file, and
the data file does not exist in the database. In most cases, this indicates
that you have mistyped the data file name.
User Response: Correct the data file name carefully and re-try the
report. Or use the obacktrack program to generate the report.
DT-21019 Tablespace: <tablespace> is not part of the profiles.

Please use the correct tablespace name to generate reports.
Explanation: You have requested a report for a tablespace that does

not exist in the specified database. In most cases, this means that you
have mistyped the tablespace name.
User Response: Correct the tablespace name and rerun the report.

DT-39000 to DT-39999
DT-39029 Requested thread not found.
Explanation: This error message is issued when redolog or parameter

file information for a thread cannot be found.
User Response: This is an internal error. Please contact BMC Software

Technical Support.
Error Messages 2-83


A
Solving License Manager Problems A
This appendix is designed to help you troubleshoot and solve license

errors that are not caused by an invalid or expired license key.
This appendix contains the following topics:
• “SQL-BackTrack Licensing Overview” on page A-2

• “License Manager Requirements” on page A-2
— “Customized dtlicense Binaries” on page A-3
— “Port Number Selection” on page A-5
• “Procedures for Invoking the License Manager” on page A-7
• “Starting the License Manager Using Inetd” on page A-8
• “Oracle Parallel Server Licensing Issues” on page A-11
— “License Keys” on page A-11
— “Port Assignments” on page A-11
— “Checking dtlicense Status” on page A-12
Solving License Manager Problems A-1

SQL-BackTrack Licensing Overview
You need one license key for each CPU where SQL-BackTrack will be
installed.
If you have already installed the product and need to enter a license key
(or provide an upgraded license key), do the following:
Change to the obacktrack product directory ($DTBASE/obacktrack) and

execute the dtoinstall command with the license option:
% cd $DTBASE/obacktrack
% install/dtoinstall license
First, the dtoinstall program will display your serial number and company
information. Press Return to leave this information unchanged. Then,
enter the license key when prompted.
License Manager Requirements

The license manager requires the following components to function
properly:
• customized dtlicense binaries during the installation process

• a Unix port number that is not being used by other processes
• procedures for invoking the license manager
The license manager is invoked by executing a program called dtlicense

in the $DTBASE/utilities/bin directory.
The license manager can be invoked in the following ways:
• The dtlicense program can be executed manually before performing

backup or recovery. The license manager continues to run until the
process is explicitly terminated by the user.
A-2 SQL-BackTrack for Oracle Messages Manual

• The license manager can be invoked whenever the host is rebooted
by adding the command to execute dtlicense into the operating
system startup script. The name and format of this script vary
according to the operating system used. The program will continue to
run until it is terminated by the user or until the system is rebooted.
• The license manager can be invoked through the inetd process. When
the SQL-BackTrack product is invoked, a request is sent to the
operating system to start the license manager when appropriate. The
process is automatically terminated after the license verification is
completed.
Note
The license manager will not start if one of the components is missing or
set up incorrectly. The following sections discuss the proper setup for
each component.
Customized dtlicense Binaries

As mentioned in “License Manager Requirements” on page A-2, the
dtlicense binaries exist in two separate locations. There is a hard link
between the files. The customization process is generally performed on
all the binaries in the $DTBASE/obacktrack/bin directory.
Occasionally, the link is broken and customization is performed only on

one of the files. If the link is broken, the dtlicense program in the
$DTBASE/dtlicense directory is not customized. This prevents the
license manager from functioning if it is invoked using the binary in the
$DTBASE/dtlicense directory.

Determining If a Link Exists
A simple test to determine whether this is the problem follows:
Step 1 Change directory to $DTBASE/dtlicense.
Step 2 Execute the ls -lai dtlicense command, which returns something

similar to the following:
139753 -rwxr-xr-x 2 oracle nobody 690904 Oct 16 09:34 dtlicense*
The number that appears after the permissions indicates the number of
links to the inode number, in the first column of the output. If the link
exists (the number should be 2) and the inode number of this dtlicense
binary is the same as that of the dtlicense binary in the
$DTBASE/obacktrack/bin directory, then customization must have been
performed during installation.
Fixing a Broken Link
If your output indicates that the link is broken, relink the files as follows:
Step 1 Rename dtlicense in the $DTBASE/dtlicense directory to dtlicense.old.
Step 2 Create a hard link to the dtlicense program in the

$DTBASE/obacktrack/bin directory as follows:
% ln $DTBASE/obacktrack/bin/dtlicense dtlicense
Step 3 Attempt the backup or recovery again.
If the operation is successful, you can delete the dtlicense.old file.

Port Number Selection
By default, SQL-BackTrack uses the following ports assignments:
• 4444 for dtlicense

• 5555 for dtoarchmon
The license manager will not function if its assigned port number is
being used by other processes. There are three ways to determine
whether a particular port number is in use:
Step 1 Check the /etc/services file to see whether there is an entry in the file
indicating that other processes may be using the same port number.
Step 2 Check with your Unix system administrator if you think that the
information in the /etc/services file may not be accurate.
Step 3 Attempt to access that port using the following procedure:
% telnet localhost ####
where #### is your assigned port number
When you receive the following messages, type test:
Trying 127.0.0.1 ...

Connected to localhost.
Escape character is '^]'.
You should get an error indicating that an illegal license request was
made. This indicates that the dtlicense program is using this port.
Otherwise, the port may be used by another process.
Once you determine that this port number is in use, you must select a
different port number.

If the license manager is invoked manually, it needs to be restarted on the
new port number. If the license manager is invoked through inetd, the
port number for dtlicense in the /etc/services file needs to be changed and
the inetd process must be restarted before performing the next backup or
recovery.
If you are using a port other than 4444 for dtlicense, or 4444 for
dtoarchmon, you need to create a dthosts file (or edit one if it already
exists). To do so:
Step 1 Create or open the dthosts file with a text editor:
% emacs $DTBASE/obacktrack/ctl/dthosts
Step 2 Enter the port assignments in the following format:
Begin dtlicense=4444
end dtlicense
begin dtoarchmon=5555
end dtoarchmon
Step 3 Save the file.

Procedures for Invoking the License Manager
This section describes starting the license manager manually or
automatically when the machine is rebooted.
The command to start the license manager on the command line is
% $DTBASE/dtlicense/dtlicense -start -port nnnn
If the error that you receive when you try to invoke the license manager
with the above command is unclear, execute the command again with the
-debug option:
% $DTBASE/dtlicense/dtlicense -start -port nnnn -debug
This command will generate debugging output which may be helpful in

diagnosing the problem.
If the problem is caused by a port number that is in use, see “Port

Number Selection” on page A-5 for more information.

Starting the License Manager Using Inetd
If you start the license manager through the inetd process, you need to
add an entry to the /etc/inetd.conf and the /etc/services files. This
modification is usually performed during installation. Add the following
entries:
/etc/inetd.conf
dtlicense stream tcp nowait sybase $DTBASE/dtlicense/dtlicense
dtlicense -inetd -msgfile
$DTBASE/obacktrack-3.2/msgs/utilities.english -nolog
/etc/services
dtlicense nnnn/tcp # DataTools license manager
(nnnn is a port number)
It is strongly recommended that you use the dtmodsys script instead of

manually modifying the files. If you suspect there are problems with the
entries, the entries can be removed and reentered as follows:
Step 1 Log in as root.
Step 2 Change to the $DTBASE/obacktrack directory.
Step 3 Execute deinstall/dtrestoresys.
Step 4 Execute install/dtmodsys.
When you add the entries using the dtmodsys script, the SQL-BackTrack
product automatically restarts the inetd process. However, if you edit the
files manually, you need to restart the inetd process for the changes to
take effect. The command to restart the inetd process is platform-specific.
The following table shows the operating system and the corresponding
commands:

Table A-1 Operating System Commands to Start inetd Process
Operating System Command

AIX, NCR, Solaris, and kill-HUP nnnn (where nnnn is the inetd process id)
SunOS
HP-UX /etc/inetd -cd
If you are running NIS, you need to modify the /etc/inetd.conf and
/etc/services files on the NIS server machine. In addition, a new NIS map
needs to be built. The following table lists the operating system and the
corresponding commands:
Table A-2 NIS Operating System Commands to Start inetd Process
Operating System Command

AIX, NCR, Solaris, and cd /var/yp; make services
SunOS
HP-UX /usr/etc/yp/ypmake
If you are running on Solaris, the following items need to be verified:
• a symbolic link from /etc/services to /etc/inet/services
• a symbolic link from /etc/inetd.conf to /etc/inet/inetd.conf
• location of the entry services: in the /etc/nsswitch.conf file
• If services is set to files, then the /etc/services file should have the
following entry:
dtlicense 4444/tcp
• If services is set to nis or nisplus, then check YP or NIS+

servers.

• If services is set to nisplus [NOTFOUND=return] files, it means
that if an entry is not found on the NIS+ server, the operating
system will not look for it in the /etc/services file. In this case, the
port number information can either be added to the NIS+ server
or the entry in /etc/nsswitch.conf can be changed to
services: nisplus files
• This tells the operating system to look in the /etc/services file if

the NIS+ server does not contain the information.
The license manager may fail to come up because of permission

problems. The login specified on the dtlicense entry in the /etc/inetd.conf
file must be the owner of the dtlicense program in the $DTBASE/dtlicense
directory, or the owner must have the read and execute permission to
dtlicense and its parent directories.
If removing and reentering the entries do not solve the problem, remove
the entries again and start the license manager manually with the -debug
option to obtain diagnostic information.
If the problems are related to port number or the dtlicense device, refer to
the appropriate sections for more information. If the problem persists, try
starting the license manager manually and contact BMC Software
Product Support.

Oracle Parallel Server Licensing Issues
The following section covers licensing issues specifically related to
Oracle Parallel Server. Please note that a SQL-BackTrack license key for
a standard Oracle installation will not work on an OPS system; you must
have an OPS-enabled license key.
License Keys
You need a license key for every OPS node on the system. If you have a
site license, you can use this. Otherwise, enter license keys for each
node. The license file can be found in $DTBASE/obacktrack/ctl/license.
Use a local text editor to edit the file.
This file must be copied to each OPS node on the system.
Port Assignments
The dtoarchmon and dtlicense programs must run on each OPS node to
provide distributed backup and recovery operations and ongoing archive
log monitoring and backup.
By default, SQL-BackTrack uses the port 4444 for dtlicense and 5555 for
dtoarchmon on each node. If you need to change these port assignments,
create a dthosts file. To do this:
Step 1 Create or open the dthosts file with a text editor:
% emacs $DTBASE/obacktrack/ctl/dthosts
Step 2 Enter the port assignments in the following format:
end dtlicense
end dtoarchmon

If different nodes need different ports, include the hostname=port lines
between the begin and end clauses for each section:
hostname=port
hostname=port
end dtlicense
hostname=port
hostname=port
end dtoarchmon
Step 3 Save the file.
Checking dtlicense Status

To check if the dtlicense program is running on a specific node, use the
following command:
dtlicense -ping -host hostname

Index
Index
C E
conventions xiii error log files 1-4
customizing dtlicense A-3 installation log files 1-5
determining if a link exists A-4 product log files 1-5
fixing a broken link A-4 error messages
message types 1-2
variables 1-2
D
documentation, related ix F
online and printed books xi
release notes xii files, dthosts A-6
dthosts file A-6 files, dthosts (OPS example) A-12
dthosts file (OPS example) A-12
dtlicense program A-2
port number assignment A-5 I
dtlicense, customizing A-3
determining if a link exists A-4 inetd process A-3
fixing a broken link A-4 inetd, using to start license manager A-8
dtmodsys script A-8 invoking the license manager A-7
dtoarchmon program
port number assignment A-5
dtoinstall program A-2 L
license manager
invoking A-7
starting using inetd A-8
Index 1
license manager requirements A-2
licensing issues, OPS A-11
R
checking dtlicense status A-12 related documentation ix
license keys A-11 online and printed books xi
port assignments A-11 release notes xii
licensing overview A-2 release notes xii
log files 1-4
installation log files 1-5
product log files 1-5 S
scripts, dtmodsys A-8
M
message look-up utility 1-3 U
message types 1-2
message variables 1-2 utility, message look-up 1-3
O
online books xi
OPS (Oracle Parallel Server) licensing
issues A-11
checking dtlicense status A-12
license keys A-11
port assignments A-11
Oracle messages, references to 1-4
P
port assignments
for OPS A-11
port numbers, selecting A-5
printed books xi
processes, inetd A-3
programs
dtlicense A-2
dtoinstall A-2
2 SQL-BackTrack for Oracle Messages Manual

Notes
*100032183*
*100032183*
*100032183*
*100032183*
*100032183*

SQL-BackTrack™ For Oracle Messages Manual Version 3.2.70

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SQL-BackTrack™ For Oracle Messages Manual Version 3.2.70

Enviado por

Direitos autorais:

Formatos disponíveis

SQL-BackTrack™

June 30, 2000

Restricted Rights Legend

Contacting BMC Software

Before Contacting BMC Software

BMC Software, Inc., Confidential and Proprietary Information

iv SQL-BackTrack for Oracle Messages Manual

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 2 Error Messages

Appendix A Solving License Manager Problems

BMC Software, Inc., Confidential and Proprietary Information

BMC Software, Inc., Confidential and Proprietary Information

vi SQL-BackTrack for Oracle Messages Manual

About This Book

This book contains detailed information about the SQL-BackTrack™ for

The SQL-BackTrack for Oracle Messages Manual contains detailed

This guide is a work in progress. It is updated with each major release of

In this release, BMC Software has combined some of the

• The SQL-BackTrack for Oracle Guide to Understanding Backup and

BMC Software, Inc., Confidential and Proprietary Information

About This Book vii

• The SQL-BackTrack for Oracle Reference Manual provides

• The SQL-BackTrack for Oracle Messages Manual contains detailed

Note that the Unix and Microsoft Windows installation guides,

For information on how to install and license SQL-BackTrack, see the

BMC Software, Inc., Confidential and Proprietary Information

viii SQL-BackTrack for Oracle Messages Manual

• online and printed books

BMC Software, Inc., Confidential and Proprietary Information

About This Book ix

BMC Software, Inc., Confidential and Proprietary Information

x SQL-BackTrack for Oracle Messages Manual

Online and Printed Books

To Access Online Books

Online books are formatted as Portable Document Format (PDF) files.

In some cases, installation of Acrobat Reader and downloading the

BMC Software, Inc., Confidential and Proprietary Information

About This Book xi

To Request Additional Printed Books

• updates to the installation instructions

BMC Software, Inc., Confidential and Proprietary Information

xii SQL-BackTrack for Oracle Messages Manual

• This book includes special elements called notes, warnings,

• All syntax, operating system terms, and

• In instructions, boldface type highlights information that you enter.

• The symbol => connects items in a menu sequence. For example,

• The symbol » denotes one-step instructions.

BMC Software, Inc., Confidential and Proprietary Information

About This Book xiii

The table table_name is not available.

• In syntax, the following additional conventions apply:

— A vertical bar ( | ) separating items indicates that you must

— An ellipsis ( . . . ) indicates that you can repeat the preceding

— Square brackets ( [ ] ) around an item indicate that the item is

BMC Software, Inc., Confidential and Proprietary Information

xiv SQL-BackTrack for Oracle Messages Manual

• “SQL-BackTrack Message Format” on page 1-2

BMC Software, Inc., Confidential and Proprietary Information

The message number is a five-digit number preceded by the characters

Character Message Type

BMC Software, Inc., Confidential and Proprietary Information

1-2 SQL-BackTrack for Oracle Messages Manual