Top Banner
  • IBM Tivoli Storage Manager

    MessagesVersion 5 Release 1

    GC32-0767-01

  • IBM Tivoli Storage Manager

    MessagesVersion 5 Release 1

    GC32-0767-01

  • Note!Before using this information and the product it supports, be sure to read the general information under Appendix E,Notices on page 929.

    Second Edition (September 2002)

    This edition applies to Version 5 Release 1 of the IBM Tivoli Storage Manager and IBM Tivoli Storage ManagerExtended Edition for AIX, HP-UX, Linux, Sun Solaris, Windows, OS/390 OS/400 PASE and z/OS (5698-ISM,5697-ISM, 5698-ISX); IBM Tivoli Storage Manager for Space Management (5698-HSM); IBM Tivoli Storage Managerfor Storage Area Networks (5698-SAN); IBM Tivoli Storage Manager for Mail (5698-APE); IBM Tivoli StorageManager for Databases (5698-APD); IBM Tivoli Storage Manager for Application Servers (5698-APW); IBM TivoliStorage Manager for Hardware (5698-APH); IBM Tivoli Storage Manager for Enterprise Resource Planning(5698-APR). and to any subsequent releases until otherwise indicated in new editions or technical newsletters.

    Order publications through your sales representative or the branch office serving your locality.

    Your feedback is important in helping to provide the most accurate and high-quality information. If you havecomments about this book or any other Tivoli Storage Manager documentation, please see Contacting CustomerSupport on page viii.

    Copyright International Business Machines Corporation 1993, 2002. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

  • Contents

    Preface . . . . . . . . . . . . . . . vMessages Not Appearing in This Publication . . . vSoftcopy Publications . . . . . . . . . . . vIBM Tivoli Storage Manager Publications . . . . . vReferenced OS/390 and z/OS System Publications viiRelated IBM Hardware Products Publications. . . viiiIBM International Technical Support CenterPublications (Redbooks) . . . . . . . . . . viiiReferenced Publications . . . . . . . . . . viiiIBM Tivoli Storage Manager Web Site . . . . . viiiContacting Customer Support . . . . . . . . viii

    Reporting a Problem . . . . . . . . . . ixTranslations. . . . . . . . . . . . . . . x

    Part 1. Introduction . . . . . . . . . 1

    Chapter 1. Introduction . . . . . . . . 3Understanding Messages . . . . . . . . . . 3

    Message Format . . . . . . . . . . . . 4

    Chapter 2. Obtaining Help for IBM TivoliStorage Manager . . . . . . . . . . . 7Internet and IBMLink Assistance . . . . . . . 7

    Internet . . . . . . . . . . . . . . . 7IBMLink/ServiceLink . . . . . . . . . . 7

    Describing the Error with Keywords . . . . . . 7Component Identification Keyword. . . . . . 8Type-of-Failure Keyword . . . . . . . . . 8Command Keyword . . . . . . . . . . . 9Function Keyword . . . . . . . . . . . 9

    Obtaining Online HELP (Get Help on ErrorMessages) . . . . . . . . . . . . . . . 9Contacting Your Service Representative . . . . . 9

    Running Trace Commands. . . . . . . . . 9Messages That Do Not Appear in This Publication. . 9

    Part 2. Server Messages . . . . . . 11

    Chapter 3. Common and PlatformSpecific Messages(ANR0100ANR9999). . . . . . . . . 13

    Chapter 4. Client Events Logged toServer (ANE40004999) . . . . . . . 581

    Part 3. Client and Data Protectionfor Lotus Notes Messages . . . . 587

    Chapter 5. Client and Data Protectionfor Lotus Notes Messages(ANS0100ANS9999) . . . . . . . . 589

    Part 4. Data Protection ProductsMessages . . . . . . . . . . . . 721

    Chapter 6. Data Protection for LotusDomino (ACD0000ACD9999) . . . . 723

    Chapter 7. Data Protection forMicrosoft Exchange Server(ACN0000ACN9999) . . . . . . . . 743

    Chapter 8. Data Protection forMicrosoft SQL Server(ACO0000ACO9999) . . . . . . . . 759

    Chapter 9. Data Protection for Oracle(ANU0000ANU9999) . . . . . . . . 775

    Chapter 10. Data Protection for R/3 forDB2 UDB (BKI0000BKI9999) . . . . 787

    Chapter 11. Data Protection for R/3 forOracle (BKI0000BKI9999) . . . . . . 797

    Chapter 12. Tivoli Data Protection forR/3 File Manager Error Messages . . . 811

    Chapter 13. Data Protection for EMCSymmetrix for R/3 (IDS0000IDS0999) . 813

    Chapter 14. Data Protection forEnterprise Storage Server for R/3 forDB2 UDB (IDS1000IDS2999). . . . . 819

    Chapter 15. Data Protection forEnterprise Storage Server for R/3 forOracle (IDS1000IDS1999) . . . . . . 833

    Chapter 16. Data Protection forEnterprise Storage Server Databasesfor DB2 UDB (EEP0000EEP9999) . . 843

    Chapter 17. Data Protection forEnterprise Storage Server Databasesfor Oracle (EEO0000EEO9999) . . . 859

    Chapter 18. Data Protection forWebSphere Application Server(DKP0000DKP0999) . . . . . . . . 873

    Copyright IBM Corp. 1993, 2002 iii

  • Part 5. Appendixes . . . . . . . . 887

    Appendix A. API Return Codes withExplanations. . . . . . . . . . . . 889

    Appendix B. Allocating AdditionalServer Memory. . . . . . . . . . . 915

    Appendix C. I/O Error CodeDescriptions for Server Messages . . 917Completion Code and Operation Code Values . . 918

    Completion Code Values Common to All DeviceClasses . . . . . . . . . . . . . . 918Completion Code Values for Media Changers 919

    Completion Code Values for Tape and OpticalDrives . . . . . . . . . . . . . . . 920Operation Code Values for Tape Library Devices 921

    Common Values for ASC and ASCQ Codes . . . 921Windows NT Event Log Entries . . . . . . 924

    Appendix D. Device Errors in AIXSystem Error Log . . . . . . . . . 927

    Appendix E. Notices . . . . . . . . 929Programming Interface . . . . . . . . . . 930Trademarks . . . . . . . . . . . . . . 931

    Glossary . . . . . . . . . . . . . 933

    iv IBM Tivoli Storage Manager: Messages

  • Preface

    IBM Tivoli Storage Manager (ITSM) (Storage Manager) is a client/server programthat provides storage management services to customers in a multivendorcomputer environment. Storage Manager provides an automated, centrallyscheduled, policy-managed backup, archive, and space management facility for fileservers and workstations.

    This publication contains explanations and suggested actions for messages issuedby the IBM Tivoli Storage Manager server program for storage managementservices, the administrative client graphical user interface, administrative commandline client, backup-archive client, API, HSM, and Data Protection products.

    Messages Not Appearing in This PublicationThis manual does not include the messages for the High Speed Data Accessfeature. Contact a service representative for assistance with these messages, whoseprefix is FTX.

    Message numbers in the range ANR01000120, and any with 9999 are notpublished in this manual. They are considered severe errors and should berecorded and included in a problem report when contacting the servicerepresentative.

    Message number ANR7831I and numbers in the range ANR79008199 are AS/400

    platformspecific messages and are not published in this manual. You can obtainthe explanation for these messages using AS/400 commands such as WRKMSGDto get to the "Work with Message Descriptions" panel.

    Softcopy PublicationsThe Storage Manager library is available in softcopy on the following CD-ROM:

    Title Order Number

    IBM Tivoli Storage Manager Publications Version 5 CD-ROM SK3T-8176

    IBM Tivoli Storage Manager PublicationsThe following table lists Storage Manager server publications.

    Publication Title Order Number

    IBM Tivoli Storage Management Products License Information GH09-4572

    IBM Tivoli Storage Manager Messages GC32-0767

    IBM Tivoli Storage Manager for AIX Administrators Guide GC32-0768

    IBM Tivoli Storage Manager for AIX Administrators Reference GC32-0769

    IBM Tivoli Storage Manager for AIX Quick Start GC32-0770

    IBM Tivoli Storage Manager for HP-UX Administrators Guide GC32-0772

    IBM Tivoli Storage Manager for HP-UX Administrators Reference GC32-0773

    IBM Tivoli Storage Manager for HP-UX Quick Start GC32-0774

    Copyright IBM Corp. 1993, 2002 v

  • Publication Title Order Number

    IBM Tivoli Storage Manager for Linux Administrators Guide GC23-4690

    IBM Tivoli Storage Manager for Linux Administrators Reference GC23-4691

    IBM Tivoli Storage Manager for Linux Quick Start GC23-4692

    IBM Tivoli Storage Manager for OS/390 and z/OS Administrators Guide GC32-0775

    IBM Tivoli Storage Manager for OS/390 and z/OS AdministratorsReference

    GC32-0776

    IBM Tivoli Storage Manager for OS/390 and z/OS Quick Start GC32-0777

    IBM Tivoli Storage Manager for OS/400 PASE Administrators Guide GC23-4694

    IBM Tivoli Storage Manager for OS/400 PASE Administrators Reference GC23-4695

    IBM Tivoli Storage Manager for OS/400 PASE Quick Start GC23-4696

    IBM Tivoli Storage Manager for Sun Solaris Administrators Guide GC32-0778

    IBM Tivoli Storage Manager for Sun Solaris Administrators Reference GC32-0779

    IBM Tivoli Storage Manager for Sun Solaris Quick Start GC32-0780

    IBM Tivoli Storage Manager for Windows Administrators Guide GC32-0782

    IBM Tivoli Storage Manager for Windows Administrators Reference GC32-0783

    IBM Tivoli Storage Manager for Windows Quick Start GC32-0784

    The following table lists Storage Manager storage agent publications.

    Publication Title Order Number

    IBM Tivoli Storage Manager for AIX Managed System for SAN StorageAgent Users Guide

    GC32-0771

    IBM Tivoli Storage Manager for HP-UX Managed System for SANStorage Agent Users Guide

    GC32-0727

    IBM Tivoli Storage Manager for Linux Managed System for SAN StorageAgent Users Guide

    GC23-4693

    IBM Tivoli Storage Manager for Sun Solaris Managed System for SANStorage Agent Users Guide

    GC32-0781

    IBM Tivoli Storage Manager for Windows Managed System for SANStorage Agent Users Guide

    GC32-0785

    The following table lists Storage Manager client publications.

    Publication Title Order Number

    IBM Tivoli Space Manager for UNIX: Using the Hierarchical StorageManagement Clients

    GC32-0794

    IBM Tivoli Storage Manager for Macintosh: Backup-Archive ClientsInstallation and Users Guide

    GC32-0787

    IBM Tivoli Storage Manager for NetWare: Backup-Archive ClientsInstallation and Users Guide

    GC32-0786

    IBM Tivoli Storage Manager for UNIX: Backup-Archive ClientsInstallation and Users Guide

    GC32-0789

    IBM Tivoli Storage Manager for Windows: Backup-Archive ClientsInstallation and Users Guide

    GC32-0788

    IBM Tivoli Storage Manager Using the Application Program Interface GC32-0793

    vi IBM Tivoli Storage Manager: Messages

  • The following table lists Tivoli Data Protection publications.

    Publication TitleOrderNumber

    IBM Tivoli Data Protection for EMC Symmetrix for R/3 Installation and UsersGuide

    SC33-6386

    IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (DB2 UDB) Installation and Users Guide

    SC32-9060-00

    IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (Oracle) Installation and Users Guide

    SC32-9061-00

    IBM Tivoli Data Protection for IBM ESS for R/3 Installation and Users Guide SC33-6387

    IBM Tivoli Data Protection for Informix Installation and Users Guide SH26-4095

    IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forUNIX and OS/400 Installation and Users Guide

    SC32-9056-00

    IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forWindows Installation and Users Guide

    SC32-9057-00

    IBM Tivoli Data Protection for Lotus Domino, S/390 Edition Licensed ProgramSpecifications

    GC26-7305

    IBM Tivoli Data Protection for Lotus Notes on AIX Installation and Users Guide SH26-4067

    IBM Tivoli Data Protection for Lotus Notes on Windows NT Installation andUsers Guide

    SH26-4065

    IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft ExchangeServer Installation and Users Guide

    SC32-9058-00

    IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQLServer Installation and Users Guide

    SC32-9059-00

    IBM Tivoli Data Protection for Oracle for UNIX Installation and Users Guide SH26-4112

    IBM Tivoli Data Protection for Oracle for Windows Installation and Users Guide SH26-4113

    IBM Tivoli Data Protection for R/3 Installation and Users Guide for Oracle SC33-6340

    IBM Tivoli Data Protection for R/3 Installation and Users Guide for DB2 UDB SC33-6341

    IBM Tivoli Data Protection for R/3 Installation and Users Guide SC33-6389

    IBM Tivoli Data Protection for WebSphere Application Server Installation andUsers Guide

    SC33-6399

    IBM Tivoli Data Protection for Workgroups for NetWare Users Guide GC32-0444

    Referenced OS/390 and z/OS System PublicationsThe following table lists referenced OS/390 and z/OS publications.

    Publication Title Order Number

    DFSMS/MVS DFSMSrmm Guide and Referencee SC26-4931

    DFSMS/MVS DFSMSrmm Implementation and Customization Guide SC26-4932

    OS/390 Security Server (RACF) Security Administrators Guide SC28-1915

    z/OS SecureWay Security Server RACF Security Administrators Guide SA22-7683

    Preface vii

  • Related IBM Hardware Products PublicationsThe following table lists related IBM hardware products publications.

    Title Order Number

    IBM Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279

    IBM 3490E Model E01 and E11 Users Guide GA32-0298

    IBM 3495 Tape Library Dataserver Models L20, L30, L40, and L50Operators Guide

    GA32-0235

    IBM Magstar MP 3570 Tape Subsystem Operators Guide GA32-0345

    IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers:Installation and Users Guide

    GC35-0154

    IBM TotalStorage Enterprise Tape System 3590 Operator Guide GA32-0330

    IBM Magstar 3494 Tape Library Dataserver Operator Guide GA32-0280

    IBM International Technical Support Center Publications (Redbooks)The International Technical Support Center (ITSC) publishes redbooks, which arebooks on specialized topics such as using Storage Manager to back up databases.You can order publications through your IBM representative or the IBM branchoffice serving your locality. You can also search for and order books of interest toyou by visiting the IBM Redbooks home page on the World Wide Web at thisaddress:

    http://www.redbooks.ibm.com/redbooks

    Referenced PublicationsThe following table lists other publications referenced in this manual:

    Title Order Number

    IBM 3494 Tape Library Dataserver Users Guide: Media Library Device Driverfor AS/400

    GC35-0153

    IBM Local Area Network Technical Reference SC30-3383

    LAN Technical Reference IEEE 802.2 & NETBIOS APIs SC30-3587

    AS/400 System API Reference SC41-3801

    IBM Tivoli Storage Manager Web SiteStorage Manager publications are available on the Storage Manager home page onthe World Wide Web at the following address:

    http://www.tivoli.com/support/storage_mgr/tivolimain.html

    By accessing the Storage Manager home page, you can keep up-to-date with thenewest product information.

    Contacting Customer SupportFor support for this or any Tivoli product, you can contact Tivoli CustomerSupport in one of the following ways:v Visit the Storage Manager technical support Web site at

    http://www.tivoli.com/support/storage_mgr/tivolimain.html.

    viii IBM Tivoli Storage Manager: Messages

    http://www.redbooks.ibm.comhttp://www.tivoli.com/support/storage_mgr/tivolimain.htmlhttp://www.tivoli.com/support/storage_mgr/tivolimain.html

  • v Submit a problem management record (PMR) electronically atIBMSERV/IBMLINK. You can access IBMLINK athttp://www2.ibmlink.ibm.com.

    v Submit a problem management record (PMR) electronically athttp://www.tivoli.com/support. See Reporting a Problem for details.

    v Send e-mail to [email protected].

    Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). Forproduct numbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511.

    International customers should consult the Web site for customer supporttelephone numbers.

    You can also review the Customer Support Handbook, which is available on our Website at http://www.tivoli.com/support/handbook/.

    When you contact Tivoli Customer Support, be prepared to provide identificationinformation for your company so that support personnel can readily assist you.Company identification information may also be needed to access various onlineservices available on the Web site.

    The support Web site offers extensive information, including a guide to supportservices (the Customer Support Handbook); frequently asked questions (FAQs);and documentation for all Tivoli products, including Release Notes, Redbooks, andWhitepapers. The documentation for some product releases is available in bothPDF and HTML formats. Translated documents are also available for some productreleases.

    You can order documentation by e-mail at [email protected]. Please provide thepublication number, part number, or order number of the desired document.Alternatively, you can provide the document title, version number, and date ofpublication.

    We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you havecomments or suggestions about our documentation, please contact us in one of thefollowing ways:v Send e-mail to [email protected] Complete our customer feedback survey at

    http://www.tivoli.com/support/feedback/.

    Reporting a ProblemPlease have the following information ready when you report a problem:v The Storage Manager server version, release, modification, and service level

    number. You can get this information by entering the QUERY STATUS command atthe Storage Manager command line.

    v The Storage Manager client version, release, modification, and service levelnumber. You can get this information by entering dsmc at the command line.

    v The communication protocol (for example, TCP/IP), version, and release numberyou are using.

    v The activity you were doing when the problem occurred, listing the steps youfollowed before the problem occurred.

    v The exact text of any error messages.

    Preface ix

    http://www2.ibmlink.ibm.comhttp://www.tivoli.com/supporthttp://www.tivoli.com/support/handbook/http://www.tivoli.com/support/feedback/

  • TranslationsSelected Storage Manager publications have been translated into languages otherthan American English. Contact your service representative for more informationabout the translated publications and whether these translations are available inyour country.

    x IBM Tivoli Storage Manager: Messages

  • Part 1. Introduction

    Copyright IBM Corp. 1993, 2002 1

  • 2 IBM Tivoli Storage Manager: Messages

  • Chapter 1. Introduction

    IBM Tivoli Storage Manager (Storage Manager) is an enterprise-wide storagemanagement application for the network. It provides automated storagemanagement services to multivendor workstations, personal computers, and localarea network (LAN) file servers. Storage Manager includes the followingcomponents:v Serverv Administrative clientv Backup-archive clientv Space Manager (Hierarchical storage management (HSM) client)v Application programming interface (API)v Data Protection product

    This chapter contains information to help you understand the messages issued bythese components.

    Messages can appear on the server console, the administrative client, an operatorterminal, the administrative graphical user interface, the backup-archive client, thespace-management client, or the application clients.

    Storage Manager provides an activity log to help the administrator track serveractivity and monitor the system. The activity log contains messages generated bythe server, and is stored in the database. The server automatically deletes messagesfrom the activity log after they have passed the specified retention period. Anymessages sent to the server console are stored in the activity log. Examples of thetypes of messages stored in the activity log include:v When client sessions start or endv When migration starts or endsv When backed up files are expired from server storagev Any output generated from background processes

    See the IBM Tivoli Storage Manager Administrators Guide.

    Understanding MessagesThe following examples illustrate the format used in this publication to describeStorage Manager messages:v Messages that begin with prefix ANE and are in range 40004999 originate from

    the backup-archive client. These messages (or events) are sent to the server fordistribution to various event logging receivers.

    v The client may send statistics to the server providing information about abackup or restore. These statistics are informational messages that may beenabled or disabled to the various event logging receivers. These messages arenot published in this manual.

    v Messages that begin with prefix ANR originate from the server.v Messages that begin with prefix ANS are from one of the following clients:

    Administrative clients Application program interface clients Backuparchive clients Space Manager (HSM) clients

    Copyright IBM Corp. 1993, 2002 3

  • Data Protection for Lotus Notes

    v Messages that begin with prefix ACD are from Data Protection for LotusDomino.

    v Messages that begin with prefix ACN are from Data Protection for MicrosoftExchange Server.

    v Messages that begin with prefix ACO are from Data Protection for MicrosoftSQL Server.

    v Messages that begin with prefix ANU are from Data Protection for Oracle.v Messages that begin with prefix BKI are from Data Protection for R/3 for DB2

    UDB and Data Protection for R/3 for Oracle.v Messages that begin with prefix DKPand are in range 00019999 are from Data

    Protection for WebSphere Application Server.v Messages that begin with prefix EEO and are in range 00009999 are from Data

    Protection for ESS for Oracle.v Messages that begin with prefix EEP and are in range 00009999 are from Data

    Protection for ESS for DB2 UDB.v Messages that begin with prefix IDS and are in range 00000999 are from Data

    Protection for EMC Symmetrix for R/3.v Messages that begin with prefix IDS and are in range 10001999 are from Data

    Protection for IBM ESS for R/3.

    Message FormatThe following examples describe the Storage Manager message format:

    The callouts to the right identify each part of the format.

    Server installation complete.

    ANR 0992 I

    Message PrefixMessage NumberMessage Type*

    Message Text

    Explanation

    System Action

    User Response

    Explanation: The server installation procedurehas completed successfully. The server is nowavailable for normal operation.

    System Action: Server completes installationprocessing.

    User Response: None.

    I = InformationE = ErrorS = Severe ErrorW = WarningK = Kernel message that originates from thehierarchical storage management (HSM) client

    *

    Message variables in the message text appear in italics. The server and clientmessages fall into the following categories:v Common messages that pertain to all Storage Manager server platforms

    4 IBM Tivoli Storage Manager: Messages

  • v Platform specific messages that pertain to each operating environment for theserver and the client

    v Messages that pertain to application clients

    How to Read a Return Code MessageMany different commands can generate the same return code. The followingexamples are illustrations of two different commands issued that result in the samereturn code; therefore, you must read the descriptive message for the command.

    Example One for QUERY EVENT Command:

    Example Two for DEFINE VOLUME Command:

    Chapter 1. Introduction 5

  • 6 IBM Tivoli Storage Manager: Messages

  • Chapter 2. Obtaining Help for IBM Tivoli Storage Manager

    This section describes the following:v How to obtain help with processing errors by using Internet and

    IBMLink/ServiceLinkv How to describe errors with keywordsv How to obtain online message helpv What information to have available when you contact your service

    representative

    Internet and IBMLink AssistanceStorage Manager message help explanations may suggest that you contact yourservice representative for additional help with processing errors.

    Online help is available through Internet and IBMLink/ServiceLink.

    InternetYou can get additional information through an anonymous FTP server,ftp.software.ibm.com. Tivoli Storage Manager information is in the/storage/tivoli-storage-management directory.

    A newsgroup, [email protected], is implemented by a third party. IBM supportsthis newsgroup on a best-effort basis only.

    IBMLink/ServiceLinkIf your installation has access to IBMLink/ServiceLink, an interactive onlinedatabase program, you can:v Search for an existing authorized program analysis report (APAR) that is similar

    to your problem.v Search for an available program temporary fix (PTF) for the existing APAR.v Order the PTF if it is available.v Create an Electronic Technical Response (ETR) problem report to get assistance

    from an Storage Manager service representative.

    Describing the Error with KeywordsWhen you use IBMLink/Servicelink or call your service representative, accuratelydescribe the problem so that the service representative may quickly help you solvethe problem. Identify the processing error with a full set of keywords wheneverpossible. A keyword is a word or an abbreviation used to describe a single aspectof a program failure. Each keyword describes an aspect of a processing error.

    The following example displays the necessary set of keywords:

    56480200n R312 type command function

    Where Represents56480200n Component identification keyword

    Copyright IBM Corp. 1993, 2002 7

  • Where RepresentsR312 Release level keywordtype Type-of-failure keywordcommand Command keywordfunction Function keyword

    Component Identification KeywordThe component identifiers for Storage Manager are 5698-ISM and 5698-ISX, withthe exceptions listed below:

    Component Component IDSpace Manager (HSMclients)

    5698-HSM

    Managed System forSAN

    5698-SAN

    High Speed DataAccess for LANfree toDisk

    5698-SAN

    Storage Manager forMail

    5698-APE

    Storage Manager forDatabases

    5698-APD

    Storage Manager forApplication Servers

    5698-APW

    Storage Manager forHardware

    5698-APH

    Storage Manager forEnterprise ResourcePlanning

    5698-APR

    Type-of-Failure KeywordThe following keywords identify the type of failure that may occur:

    Keyword DescriptionABENDxxx Use this keyword when the system ends abnormally.INCORROUT Use this keyword when incorrect output is received or expected

    output is missing.LOOP Use this keyword if a part of the program code runs endlessly;

    include situations in which a part of the output repeatscontinuously.

    MSGANRnnnnt (or)MSGANSnnnnt

    Use this keyword when a message:

    v Indicates an internal program errorv Is issued in a set of conditions that should not cause it to be

    issued

    v Contains invalid or missing dataSee Understanding Messages on page 3 for a description of themessage format.

    WAIT Use this keyword when you receive no response within areasonable time that can be perceived as poor response or poorperformance.

    8 IBM Tivoli Storage Manager: Messages

  • Keyword Descriptionxxxxxxxxxx(Documentation)

    Use this keyword when a programming problem appears to becaused by incorrect, missing, or ambiguous information in one ofthe Storage Manager publications. Enter the order number of thepublication in place of xxxxxxxxxx. Include the letter prefix andversion number, but omit all hyphens, for example, GC35040500.Refer to IBM Tivoli Storage Manager Publications on page v for alist of the Storage Manager publications.

    PERFM Use this keyword as a closing code for an APAR.

    Command KeywordBuild keywords based on Storage Manager commands. Refer to AdministratorsReference for a list of the commands.

    Function KeywordUse keywords that refer to basic Storage Manager functions such as backup,retrieve, archive, recover, migrate, and export-import.

    Obtaining Online HELP (Get Help on Error Messages)Use the HELP command on the server console or administrative command lineclient to display information about server and administrative command line clientmessages. Use the HELP command on the backup-archive client to displayinformation about backup-archive client messages.

    The Help error message number command displays the help text specific to the errormessage. You can get help information on server messages (prefixed by ANR), andadministrative command line and backup-archive client messages (prefixed byANS or ANE) except those specific to the administrative graphical user interfaceclient.

    Contacting Your Service RepresentativeWhen you contact your service representative after the proper diagnosticprocedures have been followed and user specifications have been checked foraccuracy, you should have on hand the information listed in Reporting aProblem on page ix.

    Running Trace CommandsYour service representative may request that you run trace commands to performdiagnostic functions. The output from the trace commands is classified asDiagnosis, Modification, and Tuning Information.

    Messages That Do Not Appear in This PublicationSee Messages Not Appearing in This Publication on page v for information aboutmessages that appear online but are not documented in this publication.

    Chapter 2. Obtaining Help for IBM Tivoli Storage Manager 9

  • 10 IBM Tivoli Storage Manager: Messages

  • Part 2. Server Messages

    Copyright IBM Corp. 1993, 2002 11

  • 12 IBM Tivoli Storage Manager: Messages

  • Chapter 3. Common and Platform Specific Messages(ANR0100ANR9999)

    This chapter contains the common and platform-specific server messages. Theorganization of the messages are grouped by the message prefix ANR anddocumented in ascending numeric order. If a message is platform specific and aduplicate, the appropriate platform name is added after the message number andit is also documented alphabetically by platform name.

    ANR0100E Source file(line number): Error error codecreating table table name.

    Explanation: An internal error has occurred in anattempt to create a server database table. This messagealways accompanies another error message andprovides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0101E Source file(line number): Error error codeopening table table name.

    Explanation: An internal error has occurred in anattempt to access a server database table. This messagealways accompanies another error message andprovides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0102E Source file(line number): Error error codeinserting row in table table name.

    Explanation: An internal error has occurred in anattempt to add data to a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0103E Source file(line number): Error error codeupdating row in table table name.

    Explanation: An internal error has occurred in anattempt to update data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0104E Source file(line number): Error error codedeleting row from table table name.

    Explanation: An internal error has occurred in anattempt to remove data from a server database table.This message always accompanies another errormessage and provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0105E Source file(line number): Error settingsearch bounds for table table name.

    Explanation: An internal error has occurred in anattempt to access data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0106E Source file(line number): Unexpected errorerror code fetching row in table tablename.

    Explanation: An internal error has occurred in anattempt to access data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0107W Source file(line number): Transactiontransaction ID was not committed due toan internal error.

    Explanation: An internal error was detected duringtransaction commit. This message should be precededby another error message which provides more detailabout that error.

    Copyright IBM Corp. 1993, 2002 13

  • System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0108E Source file(line number): could not start anew transaction.

    Explanation: An error occurred while attempting tostart a new transaction. Possibly there is not enoughmemory.

    System Action: The activity that generated this errorfails.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory.

    ANR0110E An unexpected system date has beendetected; the server is disabled. Use theACCEPT DATE command to establishthe current date as valid.

    Explanation: The server has noted that the currentsystem date is suspect. It is earlier than the serverinstall date or has suddenly moved into the future by30 days or more.

    System Action: The server is disable for client access.Server expiration will not execute.

    User Response: If the current system date is not valid,reset the date. Use the ACCEPT DATE command toestablish the current date as valid on the server. Afterexecuting this command, you can use the ENABLESESSIONS command to enable the server for clientsessions.

    ANR0130E DiagnosticID: Server LOG spaceexhausted.

    Explanation: There is no space to write data to theserver recovery log.

    System Action: The activity that generated this errorfails.

    User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes by using the DEFINE LOGVOLUMEcommand, and extend the size of the log by using theEXTEND LOG command.

    ANR0131E DiagnosticID: Server DB space exhausted.

    Explanation: There is no space to write data to theserver database.

    System Action: The activity that generated this errorfails.

    User Response: To increase the amount of databasespace available to the server, an authorized

    administrator can add database volumes by using theDEFINE DBVOLUME command, and extend the size ofthe database by using the EXTEND DB command.

    ANR0132E DiagnosticID: Memory allocation failed:object object name, size size.

    Explanation: The server cannot obtain enoughmemory to create the object named.

    System Action: The activity that generated this errorfails.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory.

    ANR0133E Error loading module modname: errorstring

    Explanation: The error specified by error stringoccurred when the server attempted to load modulemodname

    System Action: Server operation continues, but thefunction provided by the module is not available.

    User Response: Refer to the error string and correctthe condition causing the load to fail.

    ANR0195W Attempting to remove extraneousdatabase entries for volume volume name.

    Explanation: The server is attempting to removeextraneous database entries for the specified volume.

    System Action: TSM will attempt to remove theextraneous database entries for this volume.

    User Response: Review the completion messages forthis volume to determine if the removal of theextraneous database entries was successful or if anerror was encountered.

    ANR0196I Removal of extraneous database entriesfor volume volume name was successful.

    Explanation: The server successfully removedextraneous database entries for the specified volume.

    System Action: System operation continues and futureoperations on the specified volume should worknormally.

    User Response: The server successfully repaired thespecified volume.

    ANR0108E ANR0196I

    14 IBM Tivoli Storage Manager: Messages

  • ANR0197E Removal of extraneous database entriesfor volume volume name failed due tocontention with other server processesor activities.

    Explanation: The server was not able to removeextraneous database entries for the specified volume.This was due to contention with another server processor activity.

    System Action: System operation continues and thisvolume still has extraneous database entries.

    User Response: It is possible that future serveractivities or processes will select this volume andattempt to repair it. If this occurs and the futureattempt is successful, no further action is needed. Theserver administrator should review the activity log forthe time that the repair was attempted and try todetermine what caused the contention. If you areunable to determine the cause of the contention of theproblem persists, please contact your servicerepresentative for additional assistance.

    ANR0198E Removal of extraneous database entriesfor volume volume name failed.

    Explanation: The server was not able to removeextraneous database entries for the specified volume.

    System Action: System operation continues and thisvolume still has extraneous database entries.

    User Response: The server administrator shouldreview the activity log for the time that the repair wasattempted and try to determine the cause of the failure.If you are unable to determine the cause of thecontention of the problem persists, please contact yourservice representative for additional assistance.

    ANR0199W Not possible to repair volume volumename due to other database references tothis volume.

    Explanation: The server was not able to removeextraneous database entries for the specified volumebecause other database references to this volume exist.

    System Action: System operation continues.

    User Response: The volume repair operation for thisvolume is not able to take any action because otherunexpected database references to this volume exists.For additional assistance contact your IBM servicerepresentative.

    ANR0200I Recovery log assigned capacity is sizemegabytes.

    Explanation: The amount of space allocated to therecovery log is shown.

    System Action: None.

    User Response: None.

    ANR0201I Database assigned capacity is sizemegabytes.

    Explanation: The amount of space allocated to thedatabase is shown.

    System Action: None.

    User Response: None.

    ANR0202W Database volume volume name variedoffline due to excessive read errors.

    Explanation: The database volume shown has beenvaried offline because too many read errors have beenencountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the read errors.

    ANR0203W Database volume volume name variedoffline due to excessive write errors.

    Explanation: The database volume shown has beenvaried offline because too many write errors have beenencountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the write errors.

    ANR0204W Recovery log volume volume name variedoffline due to excessive read errors.

    Explanation: The recovery log volume shown hasbeen varied offline because too many read errors havebeen encountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the read errors.

    ANR0205W Recovery log volume volume name variedoffline due to excessive write errors.

    Explanation: The recovery log volume shown hasbeen varied offline because too many write errors havebeen encountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the write errors.

    ANR0197E ANR0205W

    Chapter 3. Common and Platform Specfic Messages 15

  • ANR0206W Partial write detected on databasevolume volume name, logical page logicalpage number (physical page physical pagenumber).

    Explanation: During a write of a database page, anerror occurred so that the page was not completelywritten to disk.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0207E Page address mismatch detected ondatabase volume volume name, logicalpage logical page number (physical pagephysical page number); actual: logical pagenumber.

    Explanation: During a read of a database page, thepage does not contain the expected page address.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0208W Partial write detected on recovery logvolume volume name, logical page logicalpage number (physical page physical pagenumber).

    Explanation: During a write of a recovery log page,an error occurs so that the page is not completelywritten to disk.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0209E Page address mismatch detected onrecovery log volume volume name, logicalpage logical page number (physical pagephysical page number); actual: logical pagenumber.

    Explanation: During a read of a recovery log page, thepage does not contain the expected page address.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0210S Inconsistency found in LVM data pagepage number - partial write detected.

    Explanation: During a write of an LVM internal page,an error occurs so that the page is not completelywritten to disk.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0211S Inconsistency found in LVM data pagepage number - page address mismatch(actual page number).

    Explanation: During a read of an LVM internal page,the page does not contain the expected page address.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0212E Unable to read disk definition file filespecification.

    Explanation: At startup, the server cannot read theindicated file in order to obtain a list of disk volumesto mount.

    System Action: Server initialization fails.

    User Response: Use a text editor to recreate the file; itshould contain one line with the name of a single logor database volume. Then restart the server.

    ANR0213W Unable to rewrite disk definition file.

    Explanation: An error occurs trying to update the diskdefinition file.

    System Action: None.

    User Response: Attempt to determine the cause of thewrite error and correct it.

    ANR0214W Database volume volume name is in theoffline state - VARY ON required.

    Explanation: At system startup, the server finds thatthe specified database volume is in the offline state.

    System Action: The volume is not accessed.

    User Response: Determine the reason for the volumebeing offline; if possible, vary it online.

    ANR0206W ANR0214W

    16 IBM Tivoli Storage Manager: Messages

  • ANR0215W Recovery log volume volume name is inthe offline state - VARY ON required.

    Explanation: At system startup, the server finds thatthe recovery log volume shown is in the offline state.

    System Action: The volume is not accessed.

    User Response: Determine the reason for the volumebeing offline; if possible, vary it online.

    ANR0216I Database volume volume name is in thestale state - synchronization processstarted.

    Explanation: At system startup, the server finds thatthe database volume shown is not synchronized.

    System Action: A process is started to synchronize thevolume.

    User Response: None.

    ANR0217I Recovery log volume volume name is inthe stale state - synchronizationprocess started.

    Explanation: At system startup, the server finds thatthe recovery log volume shown is not synchronized.

    System Action: A process is started to synchronize thevolume.

    User Response: None.

    ANR0218I Unable to install database volumevolume name - capacity must be at least 5megabytes.

    Explanation: An attempt has been made to add adatabase volume that is smaller than the serverminimum.

    System Action: The volume is not added.

    User Response: Increase the size of the volume orsupply another larger volume.

    ANR0219I Unable to install recovery log volumevolume name - capacity must be at least 5megabytes.

    Explanation: An attempt has been made to add arecovery log volume that is smaller than the serverminimum.

    System Action: The volume is not added.

    User Response: Increase the size of the volume orsupply another larger volume.

    ANR0220I Synchronization of database volumevolume name started as process process ID.

    Explanation: A background process was started tosynchronize the contents of the database volume shownwith its copy volume. The background process wasassigned the process ID shown.

    System Action: The background process starts tosynchronize the volume and server operation continues.

    User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process by using theCANCEL PROCESS command.

    ANR0221I Synchronization of recovery log volumevolume name started as process process ID.

    Explanation: A background process was started tosynchronize the contents of the recovery log volumeshown with its copy volume(s). The backgroundprocess was assigned the process ID shown.

    System Action: The background process starts tosynchronize the volume and server operation continues.

    User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process by using theCANCEL PROCESS command.

    ANR0222E Error action disk definition file filespecification.

    Explanation: An error occurred creating or changingthe disk definition file.

    System Action: None.

    User Response: Attempt to determine the cause of thewrite error and correct it.

    ANR0223E Error writing list of disks to diskdefinition file.

    Explanation: The disk definition file cannot bewritten.

    System Action: Installation ends.

    User Response: Determine the cause of the write errorand correct it.

    ANR0224E Volume volume name is specified morethan once - server installation failed.

    Explanation: The specified volume name wasspecified more than once in the server installationexecution.

    System Action: Installation ends.

    User Response: Reinitialize the server install

    ANR0215W ANR0224E

    Chapter 3. Common and Platform Specfic Messages 17

  • specifying a unique name for each database andrecovery log volume.

    ANR0230E Synchronization process failed fordatabase volume volume name.

    Explanation: The process that was attempting tosynchronize the database volume shown has failed.

    System Action: The volume is in the stale state.

    User Response: See accompanying messages for moreinformation.

    ANR0231E Synchronization process failed forrecovery log volume volume name.

    Explanation: The process that was attempting tosynchronize the recovery log volume shown has failed.

    System Action: The volume is in the stale state.

    User Response: See accompanying messages for moreinformation.

    ANR0232I Synchronization process canceled fordatabase volume volume name.

    Explanation: The process that was attempting tosynchronize the database volume shown has beencanceled.

    System Action: The volume is in the stale state.

    User Response: If desired, issue a VARY ONLINEcommand to start another synchronize process.

    ANR0233I Synchronization process canceled forrecovery log volume volume name.

    Explanation: The process that was attempting tosynchronize the database volume shown has beencanceled.

    System Action: The volume is in the stale state.

    User Response: If desired, issue a VARY ONLINEcommand to start another synchronize process.

    ANR0234I Synchronization complete for databasevolume volume name.

    Explanation: The synchronization process for thedatabase volume named has finished successfully.

    System Action: The volume is varied online.

    User Response: None.

    ANR0235I Synchronization complete for recoverylog volume volume name.

    Explanation: The synchronization process for therecovery log volume named has finished successfully.

    System Action: The volume is varied online.

    User Response: None.

    ANR0240E Deletion process failed for databasevolume volume name.

    Explanation: The process that was attempting todelete the database volume shown has failed.

    System Action: The volume is not deleted.

    User Response: See accompanying messages for moreinformation.

    ANR0241E Deletion process failed for recovery logvolume volume name.

    Explanation: The process that was attempting todelete the recovery log volume shown has failed.

    System Action: The volume is not deleted.

    User Response: See accompanying messages for moreinformation.

    ANR0242I Deletion process canceled for databasevolume volume name.

    Explanation: The process that was attempting todelete the database volume shown has been canceled.

    System Action: The volume is not deleted.

    User Response: None.

    ANR0243I Deletion process canceled for recoverylog volume volume name.

    Explanation: The process that was attempting todelete the recovery log volume shown has beencanceled.

    System Action: The volume is not deleted.

    User Response: None.

    ANR0244I Deletion complete for database volumevolume name.

    Explanation: The delete process for the databasevolume named has finished successfully.

    System Action: The volume is deleted.

    User Response: None.

    ANR0245I Deletion complete for recovery logvolume volume name.

    Explanation: The delete process for the recovery logvolume named has finished successfully.

    System Action: The volume is deleted.

    User Response: None.

    ANR0230E ANR0245I

    18 IBM Tivoli Storage Manager: Messages

  • ANR0246E Error reading logical page logical pagenumber (physical page physical pagenumber) from database volume volumename.

    Explanation: An error has been encountered whenattempting to read a page from the specified databasevolume.

    System Action: The failed I/O operation is retried ona mirrored volume, if available.

    User Response: See accompanying messages forinformation about the volume in error. If the errorpersists and another mirrored copy of the volume isavailable, the failing volume should be taken offline byusing the VARY OFF command, and repaired.Otherwise, halt the server and repair the volume. Thenrestart the server.

    ANR0247I Database page logical page numbersuccessfully read from an alternate copyon volume volume name.

    Explanation: After a read error, the server is able toread the desired page from another synchronizedmirrored volume.

    System Action: Processing continues.

    User Response: None.

    ANR0248E Unable to read database page logical pagenumber from any alternate copy.

    Explanation: After a read error, the server is unable toread the desired page from another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

    ANR0249E Error reading logical page logical pagenumber (physical page physical pagenumber) from recovery log volumevolume name.

    Explanation: An error has been encountered whenattempting to read a page from the specified recoverylog volume.

    System Action: The failed I/O operation is retried ona mirrored volume, if available.

    User Response: See accompanying messages forinformation about the volume in error. If the errorpersists and another mirrored copy of the volume isavailable, the failing volume should be taken offline, byusing the VARY OFF command, and repaired.

    ANR0250I Recovery log page logical page numbersuccessfully read from an alternate copyon volume volume name.

    Explanation: After a read error, the server is able toread the desired page from another synchronizedmirrored volume.

    System Action: Processing continues.

    User Response: None.

    ANR0251E Unable to read recovery log page logicalpage number from any alternate copy.

    Explanation: After a read error, the server is unable toread the desired page from another mirrored volumebecause no other mirrored volume was in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

    ANR0252E Error writing logical page logical pagenumber (physical page physical pagenumber) to database volume volume name.

    Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

    System Action: If a mirrored volume is available thenthe failing volume is forced into the offline state.

    User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0253E Unable to write database page logicalpage number to any alternate copy.

    Explanation: After a write error, the server is unableto write the desired page to another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: Repair the failed volume.

    ANR0254E Error writing logical page logical pagenumber (physical page physical pagenumber) to recovery log volume volumename.

    Explanation: An error has been encountered whenattempting to write a page to the specified recovery logvolume.

    System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.

    ANR0246E ANR0254E

    Chapter 3. Common and Platform Specfic Messages 19

  • User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0255E Unable to write recovery log page logicalpage number to any alternate copy.

    Explanation: After a write error, the server is unableto write the desired page to another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

    ANR0256E Error writing physical page physical pagenumber to restart/checkpoint area ondatabase volume volume name.

    Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

    System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.

    User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0257E Error writing physical page physical pagenumber to restart/checkpoint area onrecovery log volume volume name.

    Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

    System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.

    User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0258E Unable to write completerestart/checkpoint information to disk.

    Explanation: While writing restart/checkpointinformation to disk, the server encounters an errorwriting to a database or recovery log volume for whichno synchronized mirrored copy is available. Thismessage is normally preceded by a message indicatingwhich volume failed.

    System Action: Processing is ended.

    User Response: Repair the failing volume.

    ANR0259E Unable to read completerestart/checkpoint information from anydatabase or recovery log volume.

    Explanation: During server restart, the server isunable to read a complete set of restart/checkpointinformation from any of the defined database orrecovery log volumes.

    System Action: Server restart is ended.

    User Response: Ensure that all defined database andrecovery log volumes are available for use by theserver.

    ANR0260I Database page logical page numbersuccessfully resynchronized.

    Explanation: After detecting a partially-writtendatabase page, the server is able to rewrite the page byusing a synchronized mirror copy.

    System Action: Processing continues.

    User Response: None.

    ANR0261I Recovery log page logical page numbersuccessfully resynchronized.

    Explanation: After detecting a partially-writtenrecovery log page, the server is able to rewrite the pageby using a synchronized mirror copy.

    System Action: Processing continues.

    User Response: None.

    ANR0265E Log disk processing failed: sufficientmemory is not available.

    Explanation: At server installation, the server isunable to process the server log disks due toinsufficient memory.

    System Action: Server installation stops.

    User Response: Restart the server installation processwith more memory available.

    ANR0266E Database disk processing failed:sufficient memory is not available.

    Explanation: At server installation, the server isunable to process the server database disks due toinsufficient memory.

    System Action: Server installation stops.

    User Response: Restart the server installation processwith more memory available.

    ANR0255E ANR0266E

    20 IBM Tivoli Storage Manager: Messages

  • ANR0267E Log volume volume name is not available.

    Explanation: The specified volume cannot be foundduring installation.

    System Action: Server installation stops.

    User Response: Determine the reason the disk isunavailable, and correct the problem. Restart the serverinstallation process.

    ANR0268E Database volume volume name is notavailable.

    Explanation: The specified volume cannot be foundduring installation.

    System Action: Server installation stops.

    User Response: Determine the reason the disk isunavailable, andcorrect the problem. Restart the server.

    ANR0269E Process for Log volume volume nameterminated - thread resource notavailable.

    Explanation: During installation for the indicatedvolume, the server cannot start a thread to service I/Orequests.

    System Action: Server installation stops.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory. Restart the serverinstallation process.

    ANR0270E Process for Database volume volumename terminated - thread resource notavailable.

    Explanation: During installation for the indicatedvolume, the server cannot start a thread to service I/Orequests.

    System Action: Server installation stops.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory. Restart the serverinstallation process.

    ANR0271E Maximum number of recovery logvolumes exceeded.

    Explanation: More recovery log volumes have beenspecified than the server can manage.

    System Action: Server installation stops.

    User Response: Reduce the number of recovery logvolumes specified. Restart the server installationprocess.

    ANR0272E Maximum number of database volumesexceeded.

    Explanation: More database volumes have beenspecified than the server can manage.

    System Action: Server installation stops.

    User Response: Reduce the number of databasevolumes specified. Restart the server installationprocess.

    ANR0285I Database page shadowing started usingfile file name.

    Explanation: The database page shadowing functionwas started. The file specified is used to store theshadowed database pages.

    System Action: None.

    User Response: None.

    ANR0286W Database page shadowing using file filename failed to start.

    Explanation: The database page shadowing functioncould not start. An error has been encounteredaccessing the page shadow file specified.

    System Action: None.

    User Response: Verify that there is enough space forthe page shadow file. That page shadow file requiresapproximately 65 kilobytes of space, if this space is notavailable a new location for the file should be specified.

    ANR0287W Contents of the page shadow file filename are not valid.

    Explanation: The database page shadowing functioncould not use the contents of the existing file. Restartrecovery using this file is not possible.

    System Action: The server attempts to start withouthaving the database page shadow file available.

    User Response: The database page shadow filecontents are not valid. This can be caused by: a partialwrite to the page shadow file itself, the file beingmanipulated by a process outside of the server, the filebeing overlayed by a different file, or the file couldhave been erased.

    ANR0288W One or more database pages in the lastbatch written is corrupt - contents ofdatabase page shadow file will be usedto fix the page or pages.

    Explanation: One or more pages from the last batch ofpages written to the server database has been detectedto be corrupt. The server will attempt to use thecontents of database page shadow file and replace thecorrupted database page.

    ANR0267E ANR0288W

    Chapter 3. Common and Platform Specfic Messages 21

  • System Action: Server startup continues.

    User Response: A corruption of a database pagewithin the server database, is typically caused by apartial write. A partial write may occur when theserver is brought down external to normal serverprocessing. If the server terminated without a haltcommand being issued or if the machine the server isrunning on crashed unexpectedly, this may account forthe partial write. Other possible causes of a partialwrite are a disk drive failure, improperly terminatedscsi bus, or a failure in a device controller. Please try toidentify the cause of the partial write and take theappropriate action to prevent this from occurring in thefuture.

    ANR0289W Damaged database pages weresuccessfully replaced using contents ofpage shadow file.

    Explanation: The damaged database pages werereplaced using the corresponding pages from the pageshadow file. The pages were successfully replaced.

    System Action: The server continues to restart.

    User Response: None.

    ANR0290W Failure occurred attempting to replaceone or more damaged database pagesusing the contents of the page shadowfile.

    Explanation: The damaged database pages could notbe replaced using the corresponding pages from thepage shadow file.

    System Action: The server continues to restart.

    User Response: None.

    ANR0291E Error writing to db page shadow file -restart will be attempted.

    Explanation: The server encountered an error writingto the database page shadow file. The page shadowingfor the server is currently disabled.

    System Action: The server will attempt to restart thedatabase page shadowing for the server once a minuteuntil it is restarted or until the server is halted.

    User Response: Check the file specified as thedatabase page shadow file. It may be that there is notenough space for the file. If enough space is available,check the filesystem, drive, or disk that it resides on foran indication of the error. Once the error preventing theserver from writing to the page shadow file has beenresolved, the server will recovery and begin writing tothe page shadow file again.

    ANR0292W Database page shadow file file name doesnot exist.

    Explanation: The server attempted to use the pageshadow file referenced but was unable to open the file.The file does not exist.

    System Action: The server will continue to operateand will attempt to create this as a new database pageshadow file.

    User Response: None.

    ANR0300I Recovery log format started; assignedcapacity count megabytes.

    Explanation: Initial formatting of the server recoverylog has started.

    System Action: The log is formatted for use by theserver.

    User Response: None.

    ANR0301I Recovery log format in progress; countmegabytes of count.

    Explanation: The amount of the server recovery logshown has been successfully formatted.

    System Action: Formatting continues.

    User Response: None.

    ANR0302I Recovery log formatting took msecondsmilliseconds.

    Explanation: Formatting of the recovery log hascompleted and took the number of milliseconds shown.

    System Action: None.

    User Response: None.

    ANR0303I Format rate: rate pages/second.

    Explanation: During formatting, the formatterprocessed the number of pages indicated each second.

    System Action: None.

    User Response: None.

    ANR0304I Page service time: rate ms.

    Explanation: During formatting, the formatterrequired the number of milliseconds indicated toprocess each page.

    System Action: None.

    User Response: None.

    ANR0289W ANR0304I

    22 IBM Tivoli Storage Manager: Messages

  • ANR0305I Recovery log format complete.

    Explanation: Formatting of the server recovery logcompleted successfully.

    System Action: None.

    User Response: None.

    ANR0306I Recovery log volume mount in progress.

    Explanation: During restart, the server is mountingrequired recovery log volumes.

    System Action: None.

    User Response: None.

    ANR0307I Recovery log extend in progress; countmegabytes of count formatted.

    Explanation: As a result of an EXTEND LOGcommand, the additional recovery log pages are beingformatted.

    System Action: Formatting continues.

    User Response: None.

    ANR0309I Recovery log extend terminated -process canceled.

    Explanation: The process started as a result of anEXTEND LOG command and has been canceled.

    System Action: The EXTEND command is ended.

    User Response: None.

    ANR0311I Recovery log reduce in progress; countmegabytes of count moved.

    Explanation: As a result of a REDUCE LOGcommand, the amount of data from the recovery logshown has been moved.

    System Action: The REDUCE LOG commandcontinues.

    User Response: None.

    ANR0313I Recovery log reduce terminated -process canceled.

    Explanation: The process started as a result of aREDUCE LOG command and has been canceled.

    System Action: The REDUCE command is ended.

    User Response: None.

    ANR0314W Recovery log usage exceeds utilizationpercentage % of its assigned capacity.

    Explanation: This message is issued to notify theadministrator that the server recovery log utilizationexceeds 90% or more of its assigned capacity.

    System Action: Server operation continues.

    User Response:v If the server is operating in NORMAL log mode,

    depending upon the size of your recovery log, addrecovery log volumes, or extend the recovery log, orboth, before it fills completely. Refer to the DEFINELOGVOL, and EXTEND LOG commands for moreinformation on these operations.

    v If the server is operating in ROLLFORWARD logmode: backup the database, or define a database backup trigger if one is not

    already defined, or lower the database backup trigger if one is

    defined

    Refer to the DEFINE DBBACKUPTRIGGER orUPDATE DBBACKUPTRIGGER commands.

    ANR0350I Recovery checkpoint started.

    Explanation: During server initialization, the processof bringing the server database back to a state ofconsistency has begun.

    System Action: None.

    User Response: None.

    ANR0351I Recovery checkpoint complete.

    Explanation: During server initialization, the processof bringing the server database back to a state ofconsistency has completed successfully.

    System Action: None.

    User Response: None.

    ANR0352I Transaction recovery complete.

    Explanation: During server initialization, the processof recovering any incomplete transactions hascompleted successfully.

    System Action: None.

    User Response: None.

    ANR0353I Recovery log analysis pass in progress.

    Explanation: During server initialization, the processof analyzing the server recovery log has begun.

    System Action: None.

    User Response: None.

    ANR0305I ANR0353I

    Chapter 3. Common and Platform Specfic Messages 23

  • ANR0354I Recovery log redo pass in progress.

    Explanation: During server initialization, the processof committing incomplete transactions has begun.

    System Action: None.

    User Response: None.

    ANR0355I Recovery log undo pass in progress.

    Explanation: During server initialization, the processof rolling back incomplete transactions has begun.

    System Action: None.

    User Response: None.

    ANR0356I Recovery log compression started.

    Explanation: The process of removing unneeded datafrom the server recovery log has begun.

    System Action: None.

    User Response: None.

    ANR0357I Recovery log compression ended.

    Explanation: The process of removing unneeded datafrom the server recovery log has completed.

    System Action: None.

    User Response: None.

    ANR0358E Database initialization failed: sufficientmemory is not available.

    Explanation: During server initialization, the serverdatabase fails initialization because sufficient servermemory is not available.

    System Action: Initialization fails.

    User Response: Make more memory available to theserver.

    ANR0359E Database initialization failed: unable toread database restart record.

    Explanation: During server initialization, the serverdatabase initialization fails because the required restartrecord cannot be read.

    System Action: Initialization fails.

    User Response: Contact your service representative.

    ANR0360E Database initialization failed: databasesize mismatch; LVM size = size, expectedsize = size.

    Explanation: During server initialization, the serverdatabase initialization fails because the size of thedatabase does not match its prior size.

    System Action: Initialization fails.

    User Response: Contact your service representative.

    ANR0361E Database initialization failed: errorinitializing database page allocator.

    Explanation: During server initialization, the serverdatabase initialization fails because the page allocatorcannot be started.

    System Action: Initialization fails.

    User Response: Contact your service representative.

    ANR0362W Database usage exceeds utilizationpercentage % of its assigned capacity.

    Explanation: This message is issued to notify theadministrator that the server database utilizationexceeds 80% or more of its assigned capacity.

    System Action: Server operation continues.

    User Response: Depending upon the size of yourdatabase, add database volumes, or extend thedatabase, or both, before it fills completely. The serverexpiration process may also free up database spacemaking it available to other server processes. Refer tothe EXPIRE INVENTORY, DEFINE DBVOL, andEXTEND DB commands for more information on theseoperations.

    ANR0363I Database was automatically upgraded tothe server program level.

    Explanation: This message is issued to notify theadministrator that the server database wasautomatically upgraded to the current server programlevel. The upgrade is performed when theUPGRADEDB parameter is specified at server start-upand the server is started over a database that waswritten by a down-level version of the server program.

    System Action: Server operation continues.

    User Response: None. The UPGRADEDB parameterdoes not need to be specified during future serverstart-ups.

    ANR0364W Server has detected a zero bit mismatcherror.

    Explanation: This message is issued to notify theadministrator that the server has detected a zero bitmismatch error during a RESTORE DB process. Therecovery process is the database must be restored witha process that includes a DSMSERV FORMAT. Eitherthe data base volumes must be formatted then aDSMSERV RESTORE DB performed from a data basebackup that does not have this problem, or aDSMSERV UNLOADDB followed by the formatting,then a DSMSERV LOADDB. Do not use DSMSERVDUMPDB on the data base for this recovery.

    ANR0354I ANR0364W

    24 IBM Tivoli Storage Manager: Messages

  • System Action: Server RESTORE DB continues.

    User Response: Perform one of the data base recoveryactions after the RESTORE DB completes.

    ANR0380W The database buffer pool recoveredfrom an overcommit of number of pagespages. Consider increasing your bufferpool size by kilobytes needed kilobytesunder current server load.

    Explanation: During normal processing, additionalbuffer pool space is required beyond that specified inthe BUFPOOLSIZE in the server options file. Theadditional kilobytes of buffer pool space that arerequired are indicated in the message.

    System Action: Server operation continues; theadditional buffer pool space is obtained from availableserver memory.

    User Response: If the current server load is typical,consider increasing the size specified for yourBUFPOOLSIZE option by the number of kilobytesspecified in the message. To do this, you must halt theserver, change the options file, and then restart theserver.

    ANR0381I Bufferpool statistics were successfullyreset.

    Explanation: Bufferpool statistics, such as the CacheHit Ratio, have been reset by the RESET BUFPOOLcommand.

    System Action: Server operation continues.

    User Response: The QUERY DB command(FORMAT=DETAILED) can be used to to display thecurrent values for the buffer pool statistics.

    ANR0382I The database maximum utilizationstatistic was successfully reset.

    Explanation: The database maximum utilizationstatistic has been reset by the RESETDBMAXUTILIZATION command to the currentutilization.

    System Action: Server operation continues.

    User Response: The QUERY DB command(FORMAT=DETAILED) can be used to display thecurrent value for the maximum utilization.

    ANR0383I The recovery log maximum utilizationstatistic was successfully reset.

    Explanation: The recovery log maximum utilizationstatistic has been reset by the RESETLOGMAXUTILIZATION command to the currentutilization.

    System Action: Server operation continues.

    User Response: The QUERY LOG command(FORMAT=DETAILED) can be used to display thecurrent value for the maximum utilization.

    ANR0384I The recovery log consumption statisticwas successfully reset.

    Explanation: The recovery log consumption statistichas been reset by the RESET LOGCONSUMPTIONcommand.

    System Action: Server operation continues.

    User Response: The QUERY LOG command(FORMAT=DETAILED) can be used to display thecurrent value for recovery log consumption.

    ANR0385I Could not free sufficient buffers toreach reduced BUFPoolsize.

    Explanation: A reduction in the database buffer poolsize was requested. However, too many buffers were inuse to reach the lower buffer pool size.

    System Action: Server operation continues. Whateverbuffer pool size reduction that could be achieved is ineffect. The new bufpoolsize is written to the options filefor use on the next server startup.

    User Response: None.

    ANR0386I The BUFPoolsize has been changed tobuffer pool size.

    Explanation: The BUFPoolsize option has beenchanged to the indicated value.

    System Action: Server operation continues.

    User Response: None.

    ANR0390W A server database deadlock situation hasbeen encountered: lock request fortransaction transaction ID will be deniedto resolve the deadlock.

    Explanation: The server detected a deadlock situationbetween a number of processes attempting to accessdatabase information. A lock request for one of theprocesses will be denied to resolve the databasedeadlock. When server processes encounter a databasedeadlock, they usually reattempt the function that wasin progress when the deadlock was encountered. Notall process can explicitly re-try an operation. Forexample, migration and reclamation will eventuallyretry. However, something like a delete volume run in amacro will only retry if the delete command is reissuedeither in the macro or the command line.

    System Action: A lock request fails for one of thedeadlocked processes. Server operation continues.

    User Response: If a process can retry (like migration),then monitor the re-try attempt to see if it succeeds or

    ANR0380W ANR0390W

    Chapter 3. Common and Platform Specfic Messages 25

  • not. If it fails, contact a service representative. If theprocess or command is not able to retry on its own,then reissue the command or macro that caused theaction to occur. If it fails again, contact a servicerepresentative for further assistance to better isolate thedeadlock condition.

    ANR0400I Session session number started for nodenode name (client platform) (communicationmethod).

    Explanation: A new client session has been initiatedby the specified node. The session number, clientplatform type and communication method used by thissession are included in the message.

    System Action: The server begins a communicationssession to service the client node.

    User Response: None.

    ANR0401I Session session number started for nodenode name (client platform) (communicationmethod) (WDSF client).

    Explanation: A new WDSF client session has beeninitiated by the specified node. The session number,client platform type and communication method usedby this session are included in the message.

    System Action: The server begins a communicationssession to service the client node.

    User Response: None.

    ANR0402I Session session number started foradministrator administrator ID(administrators platform) (communicationmethod).

    Explanation: A new administrator client session hasbeen initiated by the specified administrator. Thesession number, administrators platform type andcommunication method used by this session areincluded in the message.

    System Action: The server begins a communicationssession to service the administrator client.

    User Response: None.

    ANR0403I Session session number ended for nodenode name (client platform).

    Explanation: A client session has completed normally.

    System Action: Server operation continues.

    User Response: None.

    ANR0404I Session session number ended for nodenode name (client platform) (WDSF client).

    Explanation: A WDSF client session has completednormally.

    System Action: Server operation continues.

    User Response: None.

    ANR0405I Session session number ended foradministrator administrator ID (clientplatform).

    Explanation: An administrative client session hascompleted normally.

    System Action: Server operation continues.

    User Response: None.

    ANR0406I Session session number started for nodenode name (client platform) (communicationmethod communication address).

    Explanation: A new client session has been initiatedby the specified node. The session number, clientplatform type, communication method and addressused by this session are included in the message.

    System Action: The server begins a communicationssession to service the client node.

    User Response: None.

    ANR0407I Session session number started foradministrator administrator ID(administrators platform) (communicationmethod communication address).

    Explanation: A new administrator client session hasbeen initiated by the specified administrator. Thesession number, administrators platform type,communication method and address used by thissession are included in the message.

    System Action: The server begins a communicationssession to service the administrator client.

    User Response: None.

    ANR0408I Session session number started for serverserver name (servers platform)(communication method) for purpose.

    Explanation: A new server session has been initiatedby the specified server for the specified purpose. Thesession number, servers platform type andcommunication method used by this session areincluded in the message.

    System Action: The server begins a communicationssession to service the administrator client.

    User Response: None.

    ANR0400I ANR0408I

    26 IBM Tivoli Storage Manager: Messages

  • ANR0409I Session session number ended for serverserver name (client platform).

    Explanation: A server has completed normally.

    System Action: Server operation continues.

    User Response: None.

    ANR0410E EXPORT operation to server server namerejected - administrator administrator isnot authorized to perform the importoperation on the target server.

    Explanation: An export operation to the named serverwas rejected, because the administrator issuing theexport command is not defined on the target server ordoes not have sufficient authority to perform theimport operation on the target server.

    System Action: Server operation continues.

    User Response: None.

    ANR0411I Session session number for administratoradministrator name logged in as node nodename restored or retrieved object typeobject: node node name, filespace filespacename, object object name.

    Explanation: This message logs information about anobject that was restored or retrieved by anadministrator logged in for a node.

    System Action: Server operation continues.

    User Response: None.

    ANR0412I Session session number for node nodename restored or retrieved object typeobject: node node name, filespace filespacename, object object name.

    Explanation: This message logs information about anobject that was restored or retrieved by anadministrator logged in for a node.

    System Action: Server operation continues.

    User Response: None.

    ANR0413I Session session number for administratoradministrator name logged in as node nodename is restoring backup set: node nodename, set filespace name.

    Explanation: This message logs information about abackup set restored by an administrator logged in for anode.

    System Action: Server operation continues.

    User Response: None.

    ANR0414I Session session number for node nodename is restoring backup set: node nodename, set filespace name.

    Explanation: This message logs information about abackup set restored by a node.

    System Action: Server operation continues.

    User Response: None.

    ANR0418W Session session number for administratoradministrator name (client platform) refused- invalid password submitted.

    Explanation: The server refuses a request to start aclient session because an invalid password has beensubmitted by the client during sign-on processing. Theserver will continue to deny access attempts by thisclient until a valid password is submitted.

    System Action: Server operation continues.

    User Response: Enter the proper password. If thepassword has been forgotten by the user, an authorizedadministrator can assign a new password by using theUPDATE ADMIN command.

    ANR0419W Administrative client useridadministrative ID cannot be used whenauthentication is on.

    Explanation: The server refuses a request for a client(administrative) session because the user ID specifiedcannot be used when authentication of IDs is in effect.SERVER_CONSOLE is an administrative ID that hasthis restriction.

    System Action: Server operation continues.

    User Response: Use an administrative ID that wasregistered for this server and that has a password.

    ANR0420W Session session number for node nodename (client platform) refused - serverdisabled for user access.

    Explanation: The server refuses a request for a client(backup-archive) session because the server is currentlydisabled for client access.

    System Action: Server operation continues.Administrative clients are permitted access to theserver.

    User Response: An authorized administrator mustissue the ENABLE command before client nodes arepermitted access to the server.

    ANR0409I ANR0420W

    Chapter 3. Common and Platform Specfic Messages 27

  • ANR0421W Session session number for node nodename (client platform) refused - sign-onprotocol violation.

    Explanation: The server refuses a request for a clientsession because sign-on protocol has been violated.

    System Action: Server operation continues.

    User Response: This error is usually the result of aclient programming error in which the sign-on verb hasbeen incorrectly formatted and delivered to the server.This error can also result when the server is contactedby an application that is not a part of this product.

    ANR0422W Session session number for node nodename (client platform) refused - nodename not registered.

    Explanation: The server refuses a request to start aclient session because the client node name is notregistered in the server database.

    System Action: Server operation continues.

    User Response: Register the node name with theserver before establishing a session. If the server isrunning with OPEN registration, no action is required;the client prompts the user for a password andregisters the client with the server. If CLOSEDregistration is in effect on the server, an authorizedadministrator must use the REGISTER NODEcommand to register the client node name with theserver.

    ANR0423W Session session number for administratoradministrator ID (client platform) refused -administrator name not registered.

    Explanation: The server refuses a request to start anadministrative session because the administrator nameis not registered in the server database.

    System Action: Server operation continues.

    User Response: Register the administrator name withthe server before establishing a session. An authorizedadministrator must use the REGISTER ADMINcommand to register the administrator with the server.

    ANR0424W Session session number for node nodename (client platform) refused - invalidpassword submitted.

    Explanation: The server refuses a request to start aclient session because an i

IBM Tivoli Storage Manager: Messages · Preface IBM Tivoli Storage Manager (ITSM) (Storage Manager) is a client/server program that provides storage management services to customers

Apr 01, 2018

Download

Documents

phungphuc
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • IBM Tivoli Storage Manager

    MessagesVersion 5 Release 1

    GC32-0767-01

  • IBM Tivoli Storage Manager

    MessagesVersion 5 Release 1

    GC32-0767-01

  • Note!Before using this information and the product it supports, be sure to read the general information under Appendix E,Notices on page 929.

    Second Edition (September 2002)

    This edition applies to Version 5 Release 1 of the IBM Tivoli Storage Manager and IBM Tivoli Storage ManagerExtended Edition for AIX, HP-UX, Linux, Sun Solaris, Windows, OS/390 OS/400 PASE and z/OS (5698-ISM,5697-ISM, 5698-ISX); IBM Tivoli Storage Manager for Space Management (5698-HSM); IBM Tivoli Storage Managerfor Storage Area Networks (5698-SAN); IBM Tivoli Storage Manager for Mail (5698-APE); IBM Tivoli StorageManager for Databases (5698-APD); IBM Tivoli Storage Manager for Application Servers (5698-APW); IBM TivoliStorage Manager for Hardware (5698-APH); IBM Tivoli Storage Manager for Enterprise Resource Planning(5698-APR). and to any subsequent releases until otherwise indicated in new editions or technical newsletters.

    Order publications through your sales representative or the branch office serving your locality.

    Your feedback is important in helping to provide the most accurate and high-quality information. If you havecomments about this book or any other Tivoli Storage Manager documentation, please see Contacting CustomerSupport on page viii.

    Copyright International Business Machines Corporation 1993, 2002. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

  • Contents

    Preface . . . . . . . . . . . . . . . vMessages Not Appearing in This Publication . . . vSoftcopy Publications . . . . . . . . . . . vIBM Tivoli Storage Manager Publications . . . . . vReferenced OS/390 and z/OS System Publications viiRelated IBM Hardware Products Publications. . . viiiIBM International Technical Support CenterPublications (Redbooks) . . . . . . . . . . viiiReferenced Publications . . . . . . . . . . viiiIBM Tivoli Storage Manager Web Site . . . . . viiiContacting Customer Support . . . . . . . . viii

    Reporting a Problem . . . . . . . . . . ixTranslations. . . . . . . . . . . . . . . x

    Part 1. Introduction . . . . . . . . . 1

    Chapter 1. Introduction . . . . . . . . 3Understanding Messages . . . . . . . . . . 3

    Message Format . . . . . . . . . . . . 4

    Chapter 2. Obtaining Help for IBM TivoliStorage Manager . . . . . . . . . . . 7Internet and IBMLink Assistance . . . . . . . 7

    Internet . . . . . . . . . . . . . . . 7IBMLink/ServiceLink . . . . . . . . . . 7

    Describing the Error with Keywords . . . . . . 7Component Identification Keyword. . . . . . 8Type-of-Failure Keyword . . . . . . . . . 8Command Keyword . . . . . . . . . . . 9Function Keyword . . . . . . . . . . . 9

    Obtaining Online HELP (Get Help on ErrorMessages) . . . . . . . . . . . . . . . 9Contacting Your Service Representative . . . . . 9

    Running Trace Commands. . . . . . . . . 9Messages That Do Not Appear in This Publication. . 9

    Part 2. Server Messages . . . . . . 11

    Chapter 3. Common and PlatformSpecific Messages(ANR0100ANR9999). . . . . . . . . 13

    Chapter 4. Client Events Logged toServer (ANE40004999) . . . . . . . 581

    Part 3. Client and Data Protectionfor Lotus Notes Messages . . . . 587

    Chapter 5. Client and Data Protectionfor Lotus Notes Messages(ANS0100ANS9999) . . . . . . . . 589

    Part 4. Data Protection ProductsMessages . . . . . . . . . . . . 721

    Chapter 6. Data Protection for LotusDomino (ACD0000ACD9999) . . . . 723

    Chapter 7. Data Protection forMicrosoft Exchange Server(ACN0000ACN9999) . . . . . . . . 743

    Chapter 8. Data Protection forMicrosoft SQL Server(ACO0000ACO9999) . . . . . . . . 759

    Chapter 9. Data Protection for Oracle(ANU0000ANU9999) . . . . . . . . 775

    Chapter 10. Data Protection for R/3 forDB2 UDB (BKI0000BKI9999) . . . . 787

    Chapter 11. Data Protection for R/3 forOracle (BKI0000BKI9999) . . . . . . 797

    Chapter 12. Tivoli Data Protection forR/3 File Manager Error Messages . . . 811

    Chapter 13. Data Protection for EMCSymmetrix for R/3 (IDS0000IDS0999) . 813

    Chapter 14. Data Protection forEnterprise Storage Server for R/3 forDB2 UDB (IDS1000IDS2999). . . . . 819

    Chapter 15. Data Protection forEnterprise Storage Server for R/3 forOracle (IDS1000IDS1999) . . . . . . 833

    Chapter 16. Data Protection forEnterprise Storage Server Databasesfor DB2 UDB (EEP0000EEP9999) . . 843

    Chapter 17. Data Protection forEnterprise Storage Server Databasesfor Oracle (EEO0000EEO9999) . . . 859

    Chapter 18. Data Protection forWebSphere Application Server(DKP0000DKP0999) . . . . . . . . 873

    Copyright IBM Corp. 1993, 2002 iii

  • Part 5. Appendixes . . . . . . . . 887

    Appendix A. API Return Codes withExplanations. . . . . . . . . . . . 889

    Appendix B. Allocating AdditionalServer Memory. . . . . . . . . . . 915

    Appendix C. I/O Error CodeDescriptions for Server Messages . . 917Completion Code and Operation Code Values . . 918

    Completion Code Values Common to All DeviceClasses . . . . . . . . . . . . . . 918Completion Code Values for Media Changers 919

    Completion Code Values for Tape and OpticalDrives . . . . . . . . . . . . . . . 920Operation Code Values for Tape Library Devices 921

    Common Values for ASC and ASCQ Codes . . . 921Windows NT Event Log Entries . . . . . . 924

    Appendix D. Device Errors in AIXSystem Error Log . . . . . . . . . 927

    Appendix E. Notices . . . . . . . . 929Programming Interface . . . . . . . . . . 930Trademarks . . . . . . . . . . . . . . 931

    Glossary . . . . . . . . . . . . . 933

    iv IBM Tivoli Storage Manager: Messages

  • Preface

    IBM Tivoli Storage Manager (ITSM) (Storage Manager) is a client/server programthat provides storage management services to customers in a multivendorcomputer environment. Storage Manager provides an automated, centrallyscheduled, policy-managed backup, archive, and space management facility for fileservers and workstations.

    This publication contains explanations and suggested actions for messages issuedby the IBM Tivoli Storage Manager server program for storage managementservices, the administrative client graphical user interface, administrative commandline client, backup-archive client, API, HSM, and Data Protection products.

    Messages Not Appearing in This PublicationThis manual does not include the messages for the High Speed Data Accessfeature. Contact a service representative for assistance with these messages, whoseprefix is FTX.

    Message numbers in the range ANR01000120, and any with 9999 are notpublished in this manual. They are considered severe errors and should berecorded and included in a problem report when contacting the servicerepresentative.

    Message number ANR7831I and numbers in the range ANR79008199 are AS/400

    platformspecific messages and are not published in this manual. You can obtainthe explanation for these messages using AS/400 commands such as WRKMSGDto get to the "Work with Message Descriptions" panel.

    Softcopy PublicationsThe Storage Manager library is available in softcopy on the following CD-ROM:

    Title Order Number

    IBM Tivoli Storage Manager Publications Version 5 CD-ROM SK3T-8176

    IBM Tivoli Storage Manager PublicationsThe following table lists Storage Manager server publications.

    Publication Title Order Number

    IBM Tivoli Storage Management Products License Information GH09-4572

    IBM Tivoli Storage Manager Messages GC32-0767

    IBM Tivoli Storage Manager for AIX Administrators Guide GC32-0768

    IBM Tivoli Storage Manager for AIX Administrators Reference GC32-0769

    IBM Tivoli Storage Manager for AIX Quick Start GC32-0770

    IBM Tivoli Storage Manager for HP-UX Administrators Guide GC32-0772

    IBM Tivoli Storage Manager for HP-UX Administrators Reference GC32-0773

    IBM Tivoli Storage Manager for HP-UX Quick Start GC32-0774

    Copyright IBM Corp. 1993, 2002 v

  • Publication Title Order Number

    IBM Tivoli Storage Manager for Linux Administrators Guide GC23-4690

    IBM Tivoli Storage Manager for Linux Administrators Reference GC23-4691

    IBM Tivoli Storage Manager for Linux Quick Start GC23-4692

    IBM Tivoli Storage Manager for OS/390 and z/OS Administrators Guide GC32-0775

    IBM Tivoli Storage Manager for OS/390 and z/OS AdministratorsReference

    GC32-0776

    IBM Tivoli Storage Manager for OS/390 and z/OS Quick Start GC32-0777

    IBM Tivoli Storage Manager for OS/400 PASE Administrators Guide GC23-4694

    IBM Tivoli Storage Manager for OS/400 PASE Administrators Reference GC23-4695

    IBM Tivoli Storage Manager for OS/400 PASE Quick Start GC23-4696

    IBM Tivoli Storage Manager for Sun Solaris Administrators Guide GC32-0778

    IBM Tivoli Storage Manager for Sun Solaris Administrators Reference GC32-0779

    IBM Tivoli Storage Manager for Sun Solaris Quick Start GC32-0780

    IBM Tivoli Storage Manager for Windows Administrators Guide GC32-0782

    IBM Tivoli Storage Manager for Windows Administrators Reference GC32-0783

    IBM Tivoli Storage Manager for Windows Quick Start GC32-0784

    The following table lists Storage Manager storage agent publications.

    Publication Title Order Number

    IBM Tivoli Storage Manager for AIX Managed System for SAN StorageAgent Users Guide

    GC32-0771

    IBM Tivoli Storage Manager for HP-UX Managed System for SANStorage Agent Users Guide

    GC32-0727

    IBM Tivoli Storage Manager for Linux Managed System for SAN StorageAgent Users Guide

    GC23-4693

    IBM Tivoli Storage Manager for Sun Solaris Managed System for SANStorage Agent Users Guide

    GC32-0781

    IBM Tivoli Storage Manager for Windows Managed System for SANStorage Agent Users Guide

    GC32-0785

    The following table lists Storage Manager client publications.

    Publication Title Order Number

    IBM Tivoli Space Manager for UNIX: Using the Hierarchical StorageManagement Clients

    GC32-0794

    IBM Tivoli Storage Manager for Macintosh: Backup-Archive ClientsInstallation and Users Guide

    GC32-0787

    IBM Tivoli Storage Manager for NetWare: Backup-Archive ClientsInstallation and Users Guide

    GC32-0786

    IBM Tivoli Storage Manager for UNIX: Backup-Archive ClientsInstallation and Users Guide

    GC32-0789

    IBM Tivoli Storage Manager for Windows: Backup-Archive ClientsInstallation and Users Guide

    GC32-0788

    IBM Tivoli Storage Manager Using the Application Program Interface GC32-0793

    vi IBM Tivoli Storage Manager: Messages

  • The following table lists Tivoli Data Protection publications.

    Publication TitleOrderNumber

    IBM Tivoli Data Protection for EMC Symmetrix for R/3 Installation and UsersGuide

    SC33-6386

    IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (DB2 UDB) Installation and Users Guide

    SC32-9060-00

    IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (Oracle) Installation and Users Guide

    SC32-9061-00

    IBM Tivoli Data Protection for IBM ESS for R/3 Installation and Users Guide SC33-6387

    IBM Tivoli Data Protection for Informix Installation and Users Guide SH26-4095

    IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forUNIX and OS/400 Installation and Users Guide

    SC32-9056-00

    IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forWindows Installation and Users Guide

    SC32-9057-00

    IBM Tivoli Data Protection for Lotus Domino, S/390 Edition Licensed ProgramSpecifications

    GC26-7305

    IBM Tivoli Data Protection for Lotus Notes on AIX Installation and Users Guide SH26-4067

    IBM Tivoli Data Protection for Lotus Notes on Windows NT Installation andUsers Guide

    SH26-4065

    IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft ExchangeServer Installation and Users Guide

    SC32-9058-00

    IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQLServer Installation and Users Guide

    SC32-9059-00

    IBM Tivoli Data Protection for Oracle for UNIX Installation and Users Guide SH26-4112

    IBM Tivoli Data Protection for Oracle for Windows Installation and Users Guide SH26-4113

    IBM Tivoli Data Protection for R/3 Installation and Users Guide for Oracle SC33-6340

    IBM Tivoli Data Protection for R/3 Installation and Users Guide for DB2 UDB SC33-6341

    IBM Tivoli Data Protection for R/3 Installation and Users Guide SC33-6389

    IBM Tivoli Data Protection for WebSphere Application Server Installation andUsers Guide

    SC33-6399

    IBM Tivoli Data Protection for Workgroups for NetWare Users Guide GC32-0444

    Referenced OS/390 and z/OS System PublicationsThe following table lists referenced OS/390 and z/OS publications.

    Publication Title Order Number

    DFSMS/MVS DFSMSrmm Guide and Referencee SC26-4931

    DFSMS/MVS DFSMSrmm Implementation and Customization Guide SC26-4932

    OS/390 Security Server (RACF) Security Administrators Guide SC28-1915

    z/OS SecureWay Security Server RACF Security Administrators Guide SA22-7683

    Preface vii

  • Related IBM Hardware Products PublicationsThe following table lists related IBM hardware products publications.

    Title Order Number

    IBM Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279

    IBM 3490E Model E01 and E11 Users Guide GA32-0298

    IBM 3495 Tape Library Dataserver Models L20, L30, L40, and L50Operators Guide

    GA32-0235

    IBM Magstar MP 3570 Tape Subsystem Operators Guide GA32-0345

    IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers:Installation and Users Guide

    GC35-0154

    IBM TotalStorage Enterprise Tape System 3590 Operator Guide GA32-0330

    IBM Magstar 3494 Tape Library Dataserver Operator Guide GA32-0280

    IBM International Technical Support Center Publications (Redbooks)The International Technical Support Center (ITSC) publishes redbooks, which arebooks on specialized topics such as using Storage Manager to back up databases.You can order publications through your IBM representative or the IBM branchoffice serving your locality. You can also search for and order books of interest toyou by visiting the IBM Redbooks home page on the World Wide Web at thisaddress:

    http://www.redbooks.ibm.com/redbooks

    Referenced PublicationsThe following table lists other publications referenced in this manual:

    Title Order Number

    IBM 3494 Tape Library Dataserver Users Guide: Media Library Device Driverfor AS/400

    GC35-0153

    IBM Local Area Network Technical Reference SC30-3383

    LAN Technical Reference IEEE 802.2 & NETBIOS APIs SC30-3587

    AS/400 System API Reference SC41-3801

    IBM Tivoli Storage Manager Web SiteStorage Manager publications are available on the Storage Manager home page onthe World Wide Web at the following address:

    http://www.tivoli.com/support/storage_mgr/tivolimain.html

    By accessing the Storage Manager home page, you can keep up-to-date with thenewest product information.

    Contacting Customer SupportFor support for this or any Tivoli product, you can contact Tivoli CustomerSupport in one of the following ways:v Visit the Storage Manager technical support Web site at

    http://www.tivoli.com/support/storage_mgr/tivolimain.html.

    viii IBM Tivoli Storage Manager: Messages

    http://www.redbooks.ibm.comhttp://www.tivoli.com/support/storage_mgr/tivolimain.htmlhttp://www.tivoli.com/support/storage_mgr/tivolimain.html

  • v Submit a problem management record (PMR) electronically atIBMSERV/IBMLINK. You can access IBMLINK athttp://www2.ibmlink.ibm.com.

    v Submit a problem management record (PMR) electronically athttp://www.tivoli.com/support. See Reporting a Problem for details.

    v Send e-mail to [email protected].

    Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). Forproduct numbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511.

    International customers should consult the Web site for customer supporttelephone numbers.

    You can also review the Customer Support Handbook, which is available on our Website at http://www.tivoli.com/support/handbook/.

    When you contact Tivoli Customer Support, be prepared to provide identificationinformation for your company so that support personnel can readily assist you.Company identification information may also be needed to access various onlineservices available on the Web site.

    The support Web site offers extensive information, including a guide to supportservices (the Customer Support Handbook); frequently asked questions (FAQs);and documentation for all Tivoli products, including Release Notes, Redbooks, andWhitepapers. The documentation for some product releases is available in bothPDF and HTML formats. Translated documents are also available for some productreleases.

    You can order documentation by e-mail at [email protected]. Please provide thepublication number, part number, or order number of the desired document.Alternatively, you can provide the document title, version number, and date ofpublication.

    We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you havecomments or suggestions about our documentation, please contact us in one of thefollowing ways:v Send e-mail to [email protected] Complete our customer feedback survey at

    http://www.tivoli.com/support/feedback/.

    Reporting a ProblemPlease have the following information ready when you report a problem:v The Storage Manager server version, release, modification, and service level

    number. You can get this information by entering the QUERY STATUS command atthe Storage Manager command line.

    v The Storage Manager client version, release, modification, and service levelnumber. You can get this information by entering dsmc at the command line.

    v The communication protocol (for example, TCP/IP), version, and release numberyou are using.

    v The activity you were doing when the problem occurred, listing the steps youfollowed before the problem occurred.

    v The exact text of any error messages.

    Preface ix

    http://www2.ibmlink.ibm.comhttp://www.tivoli.com/supporthttp://www.tivoli.com/support/handbook/http://www.tivoli.com/support/feedback/

  • TranslationsSelected Storage Manager publications have been translated into languages otherthan American English. Contact your service representative for more informationabout the translated publications and whether these translations are available inyour country.

    x IBM Tivoli Storage Manager: Messages

  • Part 1. Introduction

    Copyright IBM Corp. 1993, 2002 1

  • 2 IBM Tivoli Storage Manager: Messages

  • Chapter 1. Introduction

    IBM Tivoli Storage Manager (Storage Manager) is an enterprise-wide storagemanagement application for the network. It provides automated storagemanagement services to multivendor workstations, personal computers, and localarea network (LAN) file servers. Storage Manager includes the followingcomponents:v Serverv Administrative clientv Backup-archive clientv Space Manager (Hierarchical storage management (HSM) client)v Application programming interface (API)v Data Protection product

    This chapter contains information to help you understand the messages issued bythese components.

    Messages can appear on the server console, the administrative client, an operatorterminal, the administrative graphical user interface, the backup-archive client, thespace-management client, or the application clients.

    Storage Manager provides an activity log to help the administrator track serveractivity and monitor the system. The activity log contains messages generated bythe server, and is stored in the database. The server automatically deletes messagesfrom the activity log after they have passed the specified retention period. Anymessages sent to the server console are stored in the activity log. Examples of thetypes of messages stored in the activity log include:v When client sessions start or endv When migration starts or endsv When backed up files are expired from server storagev Any output generated from background processes

    See the IBM Tivoli Storage Manager Administrators Guide.

    Understanding MessagesThe following examples illustrate the format used in this publication to describeStorage Manager messages:v Messages that begin with prefix ANE and are in range 40004999 originate from

    the backup-archive client. These messages (or events) are sent to the server fordistribution to various event logging receivers.

    v The client may send statistics to the server providing information about abackup or restore. These statistics are informational messages that may beenabled or disabled to the various event logging receivers. These messages arenot published in this manual.

    v Messages that begin with prefix ANR originate from the server.v Messages that begin with prefix ANS are from one of the following clients:

    Administrative clients Application program interface clients Backuparchive clients Space Manager (HSM) clients

    Copyright IBM Corp. 1993, 2002 3

  • Data Protection for Lotus Notes

    v Messages that begin with prefix ACD are from Data Protection for LotusDomino.

    v Messages that begin with prefix ACN are from Data Protection for MicrosoftExchange Server.

    v Messages that begin with prefix ACO are from Data Protection for MicrosoftSQL Server.

    v Messages that begin with prefix ANU are from Data Protection for Oracle.v Messages that begin with prefix BKI are from Data Protection for R/3 for DB2

    UDB and Data Protection for R/3 for Oracle.v Messages that begin with prefix DKPand are in range 00019999 are from Data

    Protection for WebSphere Application Server.v Messages that begin with prefix EEO and are in range 00009999 are from Data

    Protection for ESS for Oracle.v Messages that begin with prefix EEP and are in range 00009999 are from Data

    Protection for ESS for DB2 UDB.v Messages that begin with prefix IDS and are in range 00000999 are from Data

    Protection for EMC Symmetrix for R/3.v Messages that begin with prefix IDS and are in range 10001999 are from Data

    Protection for IBM ESS for R/3.

    Message FormatThe following examples describe the Storage Manager message format:

    The callouts to the right identify each part of the format.

    Server installation complete.

    ANR 0992 I

    Message PrefixMessage NumberMessage Type*

    Message Text

    Explanation

    System Action

    User Response

    Explanation: The server installation procedurehas completed successfully. The server is nowavailable for normal operation.

    System Action: Server completes installationprocessing.

    User Response: None.

    I = InformationE = ErrorS = Severe ErrorW = WarningK = Kernel message that originates from thehierarchical storage management (HSM) client

    *

    Message variables in the message text appear in italics. The server and clientmessages fall into the following categories:v Common messages that pertain to all Storage Manager server platforms

    4 IBM Tivoli Storage Manager: Messages

  • v Platform specific messages that pertain to each operating environment for theserver and the client

    v Messages that pertain to application clients

    How to Read a Return Code MessageMany different commands can generate the same return code. The followingexamples are illustrations of two different commands issued that result in the samereturn code; therefore, you must read the descriptive message for the command.

    Example One for QUERY EVENT Command:

    Example Two for DEFINE VOLUME Command:

    Chapter 1. Introduction 5

  • 6 IBM Tivoli Storage Manager: Messages

  • Chapter 2. Obtaining Help for IBM Tivoli Storage Manager

    This section describes the following:v How to obtain help with processing errors by using Internet and

    IBMLink/ServiceLinkv How to describe errors with keywordsv How to obtain online message helpv What information to have available when you contact your service

    representative

    Internet and IBMLink AssistanceStorage Manager message help explanations may suggest that you contact yourservice representative for additional help with processing errors.

    Online help is available through Internet and IBMLink/ServiceLink.

    InternetYou can get additional information through an anonymous FTP server,ftp.software.ibm.com. Tivoli Storage Manager information is in the/storage/tivoli-storage-management directory.

    A newsgroup, [email protected], is implemented by a third party. IBM supportsthis newsgroup on a best-effort basis only.

    IBMLink/ServiceLinkIf your installation has access to IBMLink/ServiceLink, an interactive onlinedatabase program, you can:v Search for an existing authorized program analysis report (APAR) that is similar

    to your problem.v Search for an available program temporary fix (PTF) for the existing APAR.v Order the PTF if it is available.v Create an Electronic Technical Response (ETR) problem report to get assistance

    from an Storage Manager service representative.

    Describing the Error with KeywordsWhen you use IBMLink/Servicelink or call your service representative, accuratelydescribe the problem so that the service representative may quickly help you solvethe problem. Identify the processing error with a full set of keywords wheneverpossible. A keyword is a word or an abbreviation used to describe a single aspectof a program failure. Each keyword describes an aspect of a processing error.

    The following example displays the necessary set of keywords:

    56480200n R312 type command function

    Where Represents56480200n Component identification keyword

    Copyright IBM Corp. 1993, 2002 7

  • Where RepresentsR312 Release level keywordtype Type-of-failure keywordcommand Command keywordfunction Function keyword

    Component Identification KeywordThe component identifiers for Storage Manager are 5698-ISM and 5698-ISX, withthe exceptions listed below:

    Component Component IDSpace Manager (HSMclients)

    5698-HSM

    Managed System forSAN

    5698-SAN

    High Speed DataAccess for LANfree toDisk

    5698-SAN

    Storage Manager forMail

    5698-APE

    Storage Manager forDatabases

    5698-APD

    Storage Manager forApplication Servers

    5698-APW

    Storage Manager forHardware

    5698-APH

    Storage Manager forEnterprise ResourcePlanning

    5698-APR

    Type-of-Failure KeywordThe following keywords identify the type of failure that may occur:

    Keyword DescriptionABENDxxx Use this keyword when the system ends abnormally.INCORROUT Use this keyword when incorrect output is received or expected

    output is missing.LOOP Use this keyword if a part of the program code runs endlessly;

    include situations in which a part of the output repeatscontinuously.

    MSGANRnnnnt (or)MSGANSnnnnt

    Use this keyword when a message:

    v Indicates an internal program errorv Is issued in a set of conditions that should not cause it to be

    issued

    v Contains invalid or missing dataSee Understanding Messages on page 3 for a description of themessage format.

    WAIT Use this keyword when you receive no response within areasonable time that can be perceived as poor response or poorperformance.

    8 IBM Tivoli Storage Manager: Messages

  • Keyword Descriptionxxxxxxxxxx(Documentation)

    Use this keyword when a programming problem appears to becaused by incorrect, missing, or ambiguous information in one ofthe Storage Manager publications. Enter the order number of thepublication in place of xxxxxxxxxx. Include the letter prefix andversion number, but omit all hyphens, for example, GC35040500.Refer to IBM Tivoli Storage Manager Publications on page v for alist of the Storage Manager publications.

    PERFM Use this keyword as a closing code for an APAR.

    Command KeywordBuild keywords based on Storage Manager commands. Refer to AdministratorsReference for a list of the commands.

    Function KeywordUse keywords that refer to basic Storage Manager functions such as backup,retrieve, archive, recover, migrate, and export-import.

    Obtaining Online HELP (Get Help on Error Messages)Use the HELP command on the server console or administrative command lineclient to display information about server and administrative command line clientmessages. Use the HELP command on the backup-archive client to displayinformation about backup-archive client messages.

    The Help error message number command displays the help text specific to the errormessage. You can get help information on server messages (prefixed by ANR), andadministrative command line and backup-archive client messages (prefixed byANS or ANE) except those specific to the administrative graphical user interfaceclient.

    Contacting Your Service RepresentativeWhen you contact your service representative after the proper diagnosticprocedures have been followed and user specifications have been checked foraccuracy, you should have on hand the information listed in Reporting aProblem on page ix.

    Running Trace CommandsYour service representative may request that you run trace commands to performdiagnostic functions. The output from the trace commands is classified asDiagnosis, Modification, and Tuning Information.

    Messages That Do Not Appear in This PublicationSee Messages Not Appearing in This Publication on page v for information aboutmessages that appear online but are not documented in this publication.

    Chapter 2. Obtaining Help for IBM Tivoli Storage Manager 9

  • 10 IBM Tivoli Storage Manager: Messages

  • Part 2. Server Messages

    Copyright IBM Corp. 1993, 2002 11

  • 12 IBM Tivoli Storage Manager: Messages

  • Chapter 3. Common and Platform Specific Messages(ANR0100ANR9999)

    This chapter contains the common and platform-specific server messages. Theorganization of the messages are grouped by the message prefix ANR anddocumented in ascending numeric order. If a message is platform specific and aduplicate, the appropriate platform name is added after the message number andit is also documented alphabetically by platform name.

    ANR0100E Source file(line number): Error error codecreating table table name.

    Explanation: An internal error has occurred in anattempt to create a server database table. This messagealways accompanies another error message andprovides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0101E Source file(line number): Error error codeopening table table name.

    Explanation: An internal error has occurred in anattempt to access a server database table. This messagealways accompanies another error message andprovides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0102E Source file(line number): Error error codeinserting row in table table name.

    Explanation: An internal error has occurred in anattempt to add data to a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0103E Source file(line number): Error error codeupdating row in table table name.

    Explanation: An internal error has occurred in anattempt to update data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0104E Source file(line number): Error error codedeleting row from table table name.

    Explanation: An internal error has occurred in anattempt to remove data from a server database table.This message always accompanies another errormessage and provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0105E Source file(line number): Error settingsearch bounds for table table name.

    Explanation: An internal error has occurred in anattempt to access data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0106E Source file(line number): Unexpected errorerror code fetching row in table tablename.

    Explanation: An internal error has occurred in anattempt to access data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.

    System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0107W Source file(line number): Transactiontransaction ID was not committed due toan internal error.

    Explanation: An internal error was detected duringtransaction commit. This message should be precededby another error message which provides more detailabout that error.

    Copyright IBM Corp. 1993, 2002 13

  • System Action: The activity that generated this errorfails.

    User Response: Contact your service representative.

    ANR0108E Source file(line number): could not start anew transaction.

    Explanation: An error occurred while attempting tostart a new transaction. Possibly there is not enoughmemory.

    System Action: The activity that generated this errorfails.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory.

    ANR0110E An unexpected system date has beendetected; the server is disabled. Use theACCEPT DATE command to establishthe current date as valid.

    Explanation: The server has noted that the currentsystem date is suspect. It is earlier than the serverinstall date or has suddenly moved into the future by30 days or more.

    System Action: The server is disable for client access.Server expiration will not execute.

    User Response: If the current system date is not valid,reset the date. Use the ACCEPT DATE command toestablish the current date as valid on the server. Afterexecuting this command, you can use the ENABLESESSIONS command to enable the server for clientsessions.

    ANR0130E DiagnosticID: Server LOG spaceexhausted.

    Explanation: There is no space to write data to theserver recovery log.

    System Action: The activity that generated this errorfails.

    User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes by using the DEFINE LOGVOLUMEcommand, and extend the size of the log by using theEXTEND LOG command.

    ANR0131E DiagnosticID: Server DB space exhausted.

    Explanation: There is no space to write data to theserver database.

    System Action: The activity that generated this errorfails.

    User Response: To increase the amount of databasespace available to the server, an authorized

    administrator can add database volumes by using theDEFINE DBVOLUME command, and extend the size ofthe database by using the EXTEND DB command.

    ANR0132E DiagnosticID: Memory allocation failed:object object name, size size.

    Explanation: The server cannot obtain enoughmemory to create the object named.

    System Action: The activity that generated this errorfails.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory.

    ANR0133E Error loading module modname: errorstring

    Explanation: The error specified by error stringoccurred when the server attempted to load modulemodname

    System Action: Server operation continues, but thefunction provided by the module is not available.

    User Response: Refer to the error string and correctthe condition causing the load to fail.

    ANR0195W Attempting to remove extraneousdatabase entries for volume volume name.

    Explanation: The server is attempting to removeextraneous database entries for the specified volume.

    System Action: TSM will attempt to remove theextraneous database entries for this volume.

    User Response: Review the completion messages forthis volume to determine if the removal of theextraneous database entries was successful or if anerror was encountered.

    ANR0196I Removal of extraneous database entriesfor volume volume name was successful.

    Explanation: The server successfully removedextraneous database entries for the specified volume.

    System Action: System operation continues and futureoperations on the specified volume should worknormally.

    User Response: The server successfully repaired thespecified volume.

    ANR0108E ANR0196I

    14 IBM Tivoli Storage Manager: Messages

  • ANR0197E Removal of extraneous database entriesfor volume volume name failed due tocontention with other server processesor activities.

    Explanation: The server was not able to removeextraneous database entries for the specified volume.This was due to contention with another server processor activity.

    System Action: System operation continues and thisvolume still has extraneous database entries.

    User Response: It is possible that future serveractivities or processes will select this volume andattempt to repair it. If this occurs and the futureattempt is successful, no further action is needed. Theserver administrator should review the activity log forthe time that the repair was attempted and try todetermine what caused the contention. If you areunable to determine the cause of the contention of theproblem persists, please contact your servicerepresentative for additional assistance.

    ANR0198E Removal of extraneous database entriesfor volume volume name failed.

    Explanation: The server was not able to removeextraneous database entries for the specified volume.

    System Action: System operation continues and thisvolume still has extraneous database entries.

    User Response: The server administrator shouldreview the activity log for the time that the repair wasattempted and try to determine the cause of the failure.If you are unable to determine the cause of thecontention of the problem persists, please contact yourservice representative for additional assistance.

    ANR0199W Not possible to repair volume volumename due to other database references tothis volume.

    Explanation: The server was not able to removeextraneous database entries for the specified volumebecause other database references to this volume exist.

    System Action: System operation continues.

    User Response: The volume repair operation for thisvolume is not able to take any action because otherunexpected database references to this volume exists.For additional assistance contact your IBM servicerepresentative.

    ANR0200I Recovery log assigned capacity is sizemegabytes.

    Explanation: The amount of space allocated to therecovery log is shown.

    System Action: None.

    User Response: None.

    ANR0201I Database assigned capacity is sizemegabytes.

    Explanation: The amount of space allocated to thedatabase is shown.

    System Action: None.

    User Response: None.

    ANR0202W Database volume volume name variedoffline due to excessive read errors.

    Explanation: The database volume shown has beenvaried offline because too many read errors have beenencountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the read errors.

    ANR0203W Database volume volume name variedoffline due to excessive write errors.

    Explanation: The database volume shown has beenvaried offline because too many write errors have beenencountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the write errors.

    ANR0204W Recovery log volume volume name variedoffline due to excessive read errors.

    Explanation: The recovery log volume shown hasbeen varied offline because too many read errors havebeen encountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the read errors.

    ANR0205W Recovery log volume volume name variedoffline due to excessive write errors.

    Explanation: The recovery log volume shown hasbeen varied offline because too many write errors havebeen encountered.

    System Action: If available, a mirrored copy of thevolume is used.

    User Response: Correct the cause of the write errors.

    ANR0197E ANR0205W

    Chapter 3. Common and Platform Specfic Messages 15

  • ANR0206W Partial write detected on databasevolume volume name, logical page logicalpage number (physical page physical pagenumber).

    Explanation: During a write of a database page, anerror occurred so that the page was not completelywritten to disk.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0207E Page address mismatch detected ondatabase volume volume name, logicalpage logical page number (physical pagephysical page number); actual: logical pagenumber.

    Explanation: During a read of a database page, thepage does not contain the expected page address.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0208W Partial write detected on recovery logvolume volume name, logical page logicalpage number (physical page physical pagenumber).

    Explanation: During a write of a recovery log page,an error occurs so that the page is not completelywritten to disk.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0209E Page address mismatch detected onrecovery log volume volume name, logicalpage logical page number (physical pagephysical page number); actual: logical pagenumber.

    Explanation: During a read of a recovery log page, thepage does not contain the expected page address.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0210S Inconsistency found in LVM data pagepage number - partial write detected.

    Explanation: During a write of an LVM internal page,an error occurs so that the page is not completelywritten to disk.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0211S Inconsistency found in LVM data pagepage number - page address mismatch(actual page number).

    Explanation: During a read of an LVM internal page,the page does not contain the expected page address.

    System Action: The failed I/O operation is retried ona mirrored volume.

    User Response: See accompanying messages forinformation about the volume in error.

    ANR0212E Unable to read disk definition file filespecification.

    Explanation: At startup, the server cannot read theindicated file in order to obtain a list of disk volumesto mount.

    System Action: Server initialization fails.

    User Response: Use a text editor to recreate the file; itshould contain one line with the name of a single logor database volume. Then restart the server.

    ANR0213W Unable to rewrite disk definition file.

    Explanation: An error occurs trying to update the diskdefinition file.

    System Action: None.

    User Response: Attempt to determine the cause of thewrite error and correct it.

    ANR0214W Database volume volume name is in theoffline state - VARY ON required.

    Explanation: At system startup, the server finds thatthe specified database volume is in the offline state.

    System Action: The volume is not accessed.

    User Response: Determine the reason for the volumebeing offline; if possible, vary it online.

    ANR0206W ANR0214W

    16 IBM Tivoli Storage Manager: Messages

  • ANR0215W Recovery log volume volume name is inthe offline state - VARY ON required.

    Explanation: At system startup, the server finds thatthe recovery log volume shown is in the offline state.

    System Action: The volume is not accessed.

    User Response: Determine the reason for the volumebeing offline; if possible, vary it online.

    ANR0216I Database volume volume name is in thestale state - synchronization processstarted.

    Explanation: At system startup, the server finds thatthe database volume shown is not synchronized.

    System Action: A process is started to synchronize thevolume.

    User Response: None.

    ANR0217I Recovery log volume volume name is inthe stale state - synchronizationprocess started.

    Explanation: At system startup, the server finds thatthe recovery log volume shown is not synchronized.

    System Action: A process is started to synchronize thevolume.

    User Response: None.

    ANR0218I Unable to install database volumevolume name - capacity must be at least 5megabytes.

    Explanation: An attempt has been made to add adatabase volume that is smaller than the serverminimum.

    System Action: The volume is not added.

    User Response: Increase the size of the volume orsupply another larger volume.

    ANR0219I Unable to install recovery log volumevolume name - capacity must be at least 5megabytes.

    Explanation: An attempt has been made to add arecovery log volume that is smaller than the serverminimum.

    System Action: The volume is not added.

    User Response: Increase the size of the volume orsupply another larger volume.

    ANR0220I Synchronization of database volumevolume name started as process process ID.

    Explanation: A background process was started tosynchronize the contents of the database volume shownwith its copy volume. The background process wasassigned the process ID shown.

    System Action: The background process starts tosynchronize the volume and server operation continues.

    User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process by using theCANCEL PROCESS command.

    ANR0221I Synchronization of recovery log volumevolume name started as process process ID.

    Explanation: A background process was started tosynchronize the contents of the recovery log volumeshown with its copy volume(s). The backgroundprocess was assigned the process ID shown.

    System Action: The background process starts tosynchronize the volume and server operation continues.

    User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process by using theCANCEL PROCESS command.

    ANR0222E Error action disk definition file filespecification.

    Explanation: An error occurred creating or changingthe disk definition file.

    System Action: None.

    User Response: Attempt to determine the cause of thewrite error and correct it.

    ANR0223E Error writing list of disks to diskdefinition file.

    Explanation: The disk definition file cannot bewritten.

    System Action: Installation ends.

    User Response: Determine the cause of the write errorand correct it.

    ANR0224E Volume volume name is specified morethan once - server installation failed.

    Explanation: The specified volume name wasspecified more than once in the server installationexecution.

    System Action: Installation ends.

    User Response: Reinitialize the server install

    ANR0215W ANR0224E

    Chapter 3. Common and Platform Specfic Messages 17

  • specifying a unique name for each database andrecovery log volume.

    ANR0230E Synchronization process failed fordatabase volume volume name.

    Explanation: The process that was attempting tosynchronize the database volume shown has failed.

    System Action: The volume is in the stale state.

    User Response: See accompanying messages for moreinformation.

    ANR0231E Synchronization process failed forrecovery log volume volume name.

    Explanation: The process that was attempting tosynchronize the recovery log volume shown has failed.

    System Action: The volume is in the stale state.

    User Response: See accompanying messages for moreinformation.

    ANR0232I Synchronization process canceled fordatabase volume volume name.

    Explanation: The process that was attempting tosynchronize the database volume shown has beencanceled.

    System Action: The volume is in the stale state.

    User Response: If desired, issue a VARY ONLINEcommand to start another synchronize process.

    ANR0233I Synchronization process canceled forrecovery log volume volume name.

    Explanation: The process that was attempting tosynchronize the database volume shown has beencanceled.

    System Action: The volume is in the stale state.

    User Response: If desired, issue a VARY ONLINEcommand to start another synchronize process.

    ANR0234I Synchronization complete for databasevolume volume name.

    Explanation: The synchronization process for thedatabase volume named has finished successfully.

    System Action: The volume is varied online.

    User Response: None.

    ANR0235I Synchronization complete for recoverylog volume volume name.

    Explanation: The synchronization process for therecovery log volume named has finished successfully.

    System Action: The volume is varied online.

    User Response: None.

    ANR0240E Deletion process failed for databasevolume volume name.

    Explanation: The process that was attempting todelete the database volume shown has failed.

    System Action: The volume is not deleted.

    User Response: See accompanying messages for moreinformation.

    ANR0241E Deletion process failed for recovery logvolume volume name.

    Explanation: The process that was attempting todelete the recovery log volume shown has failed.

    System Action: The volume is not deleted.

    User Response: See accompanying messages for moreinformation.

    ANR0242I Deletion process canceled for databasevolume volume name.

    Explanation: The process that was attempting todelete the database volume shown has been canceled.

    System Action: The volume is not deleted.

    User Response: None.

    ANR0243I Deletion process canceled for recoverylog volume volume name.

    Explanation: The process that was attempting todelete the recovery log volume shown has beencanceled.

    System Action: The volume is not deleted.

    User Response: None.

    ANR0244I Deletion complete for database volumevolume name.

    Explanation: The delete process for the databasevolume named has finished successfully.

    System Action: The volume is deleted.

    User Response: None.

    ANR0245I Deletion complete for recovery logvolume volume name.

    Explanation: The delete process for the recovery logvolume named has finished successfully.

    System Action: The volume is deleted.

    User Response: None.

    ANR0230E ANR0245I

    18 IBM Tivoli Storage Manager: Messages

  • ANR0246E Error reading logical page logical pagenumber (physical page physical pagenumber) from database volume volumename.

    Explanation: An error has been encountered whenattempting to read a page from the specified databasevolume.

    System Action: The failed I/O operation is retried ona mirrored volume, if available.

    User Response: See accompanying messages forinformation about the volume in error. If the errorpersists and another mirrored copy of the volume isavailable, the failing volume should be taken offline byusing the VARY OFF command, and repaired.Otherwise, halt the server and repair the volume. Thenrestart the server.

    ANR0247I Database page logical page numbersuccessfully read from an alternate copyon volume volume name.

    Explanation: After a read error, the server is able toread the desired page from another synchronizedmirrored volume.

    System Action: Processing continues.

    User Response: None.

    ANR0248E Unable to read database page logical pagenumber from any alternate copy.

    Explanation: After a read error, the server is unable toread the desired page from another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

    ANR0249E Error reading logical page logical pagenumber (physical page physical pagenumber) from recovery log volumevolume name.

    Explanation: An error has been encountered whenattempting to read a page from the specified recoverylog volume.

    System Action: The failed I/O operation is retried ona mirrored volume, if available.

    User Response: See accompanying messages forinformation about the volume in error. If the errorpersists and another mirrored copy of the volume isavailable, the failing volume should be taken offline, byusing the VARY OFF command, and repaired.

    ANR0250I Recovery log page logical page numbersuccessfully read from an alternate copyon volume volume name.

    Explanation: After a read error, the server is able toread the desired page from another synchronizedmirrored volume.

    System Action: Processing continues.

    User Response: None.

    ANR0251E Unable to read recovery log page logicalpage number from any alternate copy.

    Explanation: After a read error, the server is unable toread the desired page from another mirrored volumebecause no other mirrored volume was in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

    ANR0252E Error writing logical page logical pagenumber (physical page physical pagenumber) to database volume volume name.

    Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

    System Action: If a mirrored volume is available thenthe failing volume is forced into the offline state.

    User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0253E Unable to write database page logicalpage number to any alternate copy.

    Explanation: After a write error, the server is unableto write the desired page to another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: Repair the failed volume.

    ANR0254E Error writing logical page logical pagenumber (physical page physical pagenumber) to recovery log volume volumename.

    Explanation: An error has been encountered whenattempting to write a page to the specified recovery logvolume.

    System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.

    ANR0246E ANR0254E

    Chapter 3. Common and Platform Specfic Messages 19

  • User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0255E Unable to write recovery log page logicalpage number to any alternate copy.

    Explanation: After a write error, the server is unableto write the desired page to another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

    System Action: Processing is ended.

    User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

    ANR0256E Error writing physical page physical pagenumber to restart/checkpoint area ondatabase volume volume name.

    Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

    System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.

    User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0257E Error writing physical page physical pagenumber to restart/checkpoint area onrecovery log volume volume name.

    Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

    System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.

    User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

    ANR0258E Unable to write completerestart/checkpoint information to disk.

    Explanation: While writing restart/checkpointinformation to disk, the server encounters an errorwriting to a database or recovery log volume for whichno synchronized mirrored copy is available. Thismessage is normally preceded by a message indicatingwhich volume failed.

    System Action: Processing is ended.

    User Response: Repair the failing volume.

    ANR0259E Unable to read completerestart/checkpoint information from anydatabase or recovery log volume.

    Explanation: During server restart, the server isunable to read a complete set of restart/checkpointinformation from any of the defined database orrecovery log volumes.

    System Action: Server restart is ended.

    User Response: Ensure that all defined database andrecovery log volumes are available for use by theserver.

    ANR0260I Database page logical page numbersuccessfully resynchronized.

    Explanation: After detecting a partially-writtendatabase page, the server is able to rewrite the page byusing a synchronized mirror copy.

    System Action: Processing continues.

    User Response: None.

    ANR0261I Recovery log page logical page numbersuccessfully resynchronized.

    Explanation: After detecting a partially-writtenrecovery log page, the server is able to rewrite the pageby using a synchronized mirror copy.

    System Action: Processing continues.

    User Response: None.

    ANR0265E Log disk processing failed: sufficientmemory is not available.

    Explanation: At server installation, the server isunable to process the server log disks due toinsufficient memory.

    System Action: Server installation stops.

    User Response: Restart the server installation processwith more memory available.

    ANR0266E Database disk processing failed:sufficient memory is not available.

    Explanation: At server installation, the server isunable to process the server database disks due toinsufficient memory.

    System Action: Server installation stops.

    User Response: Restart the server installation processwith more memory available.

    ANR0255E ANR0266E

    20 IBM Tivoli Storage Manager: Messages

  • ANR0267E Log volume volume name is not available.

    Explanation: The specified volume cannot be foundduring installation.

    System Action: Server installation stops.

    User Response: Determine the reason the disk isunavailable, and correct the problem. Restart the serverinstallation process.

    ANR0268E Database volume volume name is notavailable.

    Explanation: The specified volume cannot be foundduring installation.

    System Action: Server installation stops.

    User Response: Determine the reason the disk isunavailable, andcorrect the problem. Restart the server.

    ANR0269E Process for Log volume volume nameterminated - thread resource notavailable.

    Explanation: During installation for the indicatedvolume, the server cannot start a thread to service I/Orequests.

    System Action: Server installation stops.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory. Restart the serverinstallation process.

    ANR0270E Process for Database volume volumename terminated - thread resource notavailable.

    Explanation: During installation for the indicatedvolume, the server cannot start a thread to service I/Orequests.

    System Action: Server installation stops.

    User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see Appendix A. AllocatingAdditional Server Memory. Restart the serverinstallation process.

    ANR0271E Maximum number of recovery logvolumes exceeded.

    Explanation: More recovery log volumes have beenspecified than the server can manage.

    System Action: Server installation stops.

    User Response: Reduce the number of recovery logvolumes specified. Restart the server installationprocess.

    ANR0272E Maximum number of database volumesexceeded.

    Explanation: More database volumes have beenspecified than the server can manage.

    System Action: Server installation stops.

    User Response: Reduce the number of databasevolumes specified. Restart the server installationprocess.

    ANR0285I Database page shadowing started usingfile file name.

    Explanation: The database page shadowing functionwas started. The file specified is used to store theshadowed database pages.

    System Action: None.

    User Response: None.

    ANR0286W Database page shadowing using file filename failed to start.

    Explanation: The database page shadowing functioncould not start. An error has been encounteredaccessing the page shadow file specified.

    System Action: None.

    User Response: Verify that there is enough space forthe page shadow file. That page shadow file requiresapproximately 65 kilobytes of space, if this space is notavailable a new location for the file should be specified.

    ANR0287W Contents of the page shadow file filename are not valid.

    Explanation: The database page shadowing functioncould not use the contents of the existing file. Restartrecovery using this file is not possible.

    System Action: The server attempts to start withouthaving the database page shadow file available.

    User Response: The database page shadow filecontents are not valid. This can be caused by: a partialwrite to the page shadow file itself, the file beingmanipulated by a process outside of the server, the filebeing overlayed by a different file, or the file couldhave been erased.

    ANR0288W One or more database pages in the lastbatch written is corrupt - contents ofdatabase page shadow file will be usedto fix the page or pages.

    Explanation: One or more pages from the last batch ofpages written to the server database has been detectedto be corrupt. The server will attempt to use thecontents of database page shadow file and replace thecorrupted database page.

    ANR0267E ANR0288W

    Chapter 3. Common and Platform Specfic Messages 21

  • System Action: Server startup continues.

    User Response: A corruption of a database pagewithin the server database, is typically caused by apartial write. A partial write may occur when theserver is brought down external to normal serverprocessing. If the server terminated without a haltcommand being issued or if the machine the server isrunning on crashed unexpectedly, this may account forthe partial write. Other possible causes of a partialwrite are a disk drive failure, improperly terminatedscsi bus, or a failure in a device controller. Please try toidentify the cause of the partial write and take theappropriate action to prevent this from occurring in thefuture.

    ANR0289W Damaged database pages weresuccessfully replaced using contents ofpage shadow file.

    Explanation: The damaged database pages werereplaced using the corresponding pages from the pageshadow file. The pages were successfully replaced.

    System Action: The server continues to restart.

    User Response: None.

    ANR0290W Failure occurred attempting to replaceone or more damaged database pagesusing the contents of the page shadowfile.

    Explanation: The damaged database pages could notbe replaced using the corresponding pages from thepage shadow file.

    System Action: The server continues to restart.

    User Response: None.

    ANR0291E Error writing to db page shadow file -restart will be attempted.

    Explanation: The server encountered an error writingto the database page shadow file. The page shadowingfor the server is currently disabled.

    System Action: The server will attempt to restart thedatabase page shadowing for the server once a minuteuntil it is restarted or until the server is halted.

    User Response: Check the file specified as thedatabase page shadow file. It may be that there is notenough space for the file. If enough space is available,check the filesystem, drive, or disk that it resides on foran indication of the error. Once the error preventing theserver from writing to the page shadow file has beenresolved, the server will recovery and begin writing tothe page shadow file again.

    ANR0292W Database page shadow file file name doesnot exist.

    Explanation: The server attempted to use the pageshadow file referenced but was unable to open the file.The file does not exist.

    System Action: The server will continue to operateand will attempt to create this as a new database pageshadow file.

    User Response: None.

    ANR0300I Recovery log format started; assignedcapacity count megabytes.

    Explanation: Initial formatting of the server recoverylog has started.

    System Action: The log is formatted for use by theserver.

    User Response: None.

    ANR0301I Recovery log format in progress; countmegabytes of count.

    Explanation: The amount of the server recovery logshown has been successfully formatted.

    System Action: Formatting continues.

    User Response: None.

    ANR0302I Recovery log formatting took msecondsmilliseconds.

    Explanation: Formatting of the recovery log hascompleted and took the number of milliseconds shown.

    System Action: None.

    User Response: None.

    ANR0303I Format rate: rate pages/second.

    Explanation: During formatting, the formatterprocessed the number of pages indicated each second.

    System Action: None.

    User Response: None.

    ANR0304I Page service time: rate ms.

    Explanation: During formatting, the formatterrequired the number of milliseconds indicated toprocess each page.

    System Action: None.

    User Response: None.

    ANR0289W ANR0304I

    22 IBM Tivoli Storage Manager: Messages

  • ANR0305I Recovery log format complete.

    Explanation: Formatting of the server recovery logcompleted successfully.

    System Action: None.

    User Response: None.

    ANR0306I Recovery log volume mount in progress.

    Explanation: During restart, the server is mountingrequired recovery log volumes.

    System Action: None.

    User Response: None.

    ANR0307I Recovery log extend in progress; countmegabytes of count formatted.

    Explanation: As a result of an EXTEND LOGcommand, the additional recovery log pages are beingformatted.

    System Action: Formatting continues.

    User Response: None.

    ANR0309I Recovery log extend terminated -process canceled.

    Explanation: The process started as a result of anEXTEND LOG command and has been canceled.

    System Action: The EXTEND command is ended.

    User Response: None.

    ANR0311I Recovery log reduce in progress; countmegabytes of count moved.

    Explanation: As a result of a REDUCE LOGcommand, the amount of data from the recovery logshown has been moved.

    System Action: The REDUCE LOG commandcontinues.

    User Response: None.

    ANR0313I Recovery log reduce terminated -process canceled.

    Explanation: The process started as a result of aREDUCE LOG command and has been canceled.

    System Action: The REDUCE command is ended.

    User Response: None.

    ANR0314W Recovery log usage exceeds utilizationpercentage % of its assigned capacity.

    Explanation: This message is issued to notify theadministrator that the server recovery log utilizationexceeds 90% or more of its assigned capacity.

    System Action: Server operation continues.

    User Response:v If the server is operating in NORMAL log mode,

    depending upon the size of your recovery log, addrecovery log volumes, or extend the recovery log, orboth, before it fills completely. Refer to the DEFINELOGVOL, and EXTEND LOG commands for moreinformation on these operations.

    v If the server is operating in ROLLFORWARD logmode: backup the database, or define a database backup trigger if one is not

    already defined, or lower the database backup trigger if one is

    defined

    Refer to the DEFINE DBBACKUPTRIGGER orUPDATE DBBACKUPTRIGGER commands.

    ANR0350I Recovery checkpoint started.

    Explanation: During server initialization, the processof bringing the server database back to a state ofconsistency has begun.

    System Action: None.

    User Response: None.

    ANR0351I Recovery checkpoint complete.

    Explanation: During server initialization, the processof bringing the server database back to a state ofconsistency has completed successfully.

    System Action: None.

    User Response: None.

    ANR0352I Transaction recovery complete.

    Explanation: During server initialization, the processof recovering any incomplete transactions hascompleted successfully.

    System Action: None.

    User Response: None.

    ANR0353I Recovery log analysis pass in progress.

    Explanation: During server initialization, the processof analyzing the server recovery log has begun.

    System Action: None.

    User Response: None.

    ANR0305I ANR0353I

    Chapter 3. Common and Platform Specfic Messages 23

  • ANR0354I Recovery log redo pass in progress.

    Explanation: During server initialization, the processof committing incomplete transactions has begun.

    System Action: None.

    User Response: None.

    ANR0355I Recovery log undo pass in progress.

    Explanation: During server initialization, the processof rolling back incomplete transactions has begun.

    System Action: None.

    User Response: None.

    ANR0356I Recovery log compression started.

    Explanation: The process of removing unneeded datafrom the server recovery log has begun.

    System Action: None.

    User Response: None.

    ANR0357I Recovery log compression ended.

    Explanation: The process of removing unneeded datafrom the server recovery log has completed.

    System Action: None.

    User Response: None.

    ANR0358E Database initialization failed: sufficientmemory is not available.

    Explanation: During server initialization, the serverdatabase fails initialization because sufficient servermemory is not available.

    System Action: Initialization fails.

    User Response: Make more memory available to theserver.

    ANR0359E Database initialization failed: unable toread database restart record.

    Explanation: During server initialization, the serverdatabase initialization fails because the required restartrecord cannot be read.

    System Action: Initialization fails.

    User Response: Contact your service representative.

    ANR0360E Database initialization failed: databasesize mismatch; LVM size = size, expectedsize = size.

    Explanation: During server initialization, the serverdatabase initialization fails because the size of thedatabase does not match its prior size.

    System Action: Initialization fails.

    User Response: Contact your service representative.

    ANR0361E Database initialization failed: errorinitializing database page allocator.

    Explanation: During server initialization, the serverdatabase initialization fails because the page allocatorcannot be started.

    System Action: Initialization fails.

    User Response: Contact your service representative.

    ANR0362W Database usage exceeds utilizationpercentage % of its assigned capacity.

    Explanation: This message is issued to notify theadministrator that the server database utilizationexceeds 80% or more of its assigned capacity.

    System Action: Server operation continues.

    User Response: Depending upon the size of yourdatabase, add database volumes, or extend thedatabase, or both, before it fills completely. The serverexpiration process may also free up database spacemaking it available to other server processes. Refer tothe EXPIRE INVENTORY, DEFINE DBVOL, andEXTEND DB commands for more information on theseoperations.

    ANR0363I Database was automatically upgraded tothe server program level.

    Explanation: This message is issued to notify theadministrator that the server database wasautomatically upgraded to the current server programlevel. The upgrade is performed when theUPGRADEDB parameter is specified at server start-upand the server is started over a database that waswritten by a down-level version of the server program.

    System Action: Server operation continues.

    User Response: None. The UPGRADEDB parameterdoes not need to be specified during future serverstart-ups.

    ANR0364W Server has detected a zero bit mismatcherror.

    Explanation: This message is issued to notify theadministrator that the server has detected a zero bitmismatch error during a RESTORE DB process. Therecovery process is the database must be restored witha process that includes a DSMSERV FORMAT. Eitherthe data base volumes must be formatted then aDSMSERV RESTORE DB performed from a data basebackup that does not have this problem, or aDSMSERV UNLOADDB followed by the formatting,then a DSMSERV LOADDB. Do not use DSMSERVDUMPDB on the data base for this recovery.

    ANR0354I ANR0364W

    24 IBM Tivoli Storage Manager: Messages

  • System Action: Server RESTORE DB continues.

    User Response: Perform one of the data base recoveryactions after the RESTORE DB completes.

    ANR0380W The database buffer pool recoveredfrom an overcommit of number of pagespages. Consider increasing your bufferpool size by kilobytes needed kilobytesunder current server load.

    Explanation: During normal processing, additionalbuffer pool space is required beyond that specified inthe BUFPOOLSIZE in the server options file. Theadditional kilobytes of buffer pool space that arerequired are indicated in the message.

    System Action: Server operation continues; theadditional buffer pool space is obtained from availableserver memory.

    User Response: If the current server load is typical,consider increasing the size specified for yourBUFPOOLSIZE option by the number of kilobytesspecified in the message. To do this, you must halt theserver, change the options file, and then restart theserver.

    ANR0381I Bufferpool statistics were successfullyreset.

    Explanation: Bufferpool statistics, such as the CacheHit Ratio, have been reset by the RESET BUFPOOLcommand.

    System Action: Server operation continues.

    User Response: The QUERY DB command(FORMAT=DETAILED) can be used to to display thecurrent values for the buffer pool statistics.

    ANR0382I The database maximum utilizationstatistic was successfully reset.

    Explanation: The database maximum utilizationstatistic has been reset by the RESETDBMAXUTILIZATION command to the currentutilization.

    System Action: Server operation continues.

    User Response: The QUERY DB command(FORMAT=DETAILED) can be used to display thecurrent value for the maximum utilization.

    ANR0383I The recovery log maximum utilizationstatistic was successfully reset.

    Explanation: The recovery log maximum utilizationstatistic has been reset by the RESETLOGMAXUTILIZATION command to the currentutilization.

    System Action: Server operation continues.

    User Response: The QUERY LOG command(FORMAT=DETAILED) can be used to display thecurrent value for the maximum utilization.

    ANR0384I The recovery log consumption statisticwas successfully reset.

    Explanation: The recovery log consumption statistichas been reset by the RESET LOGCONSUMPTIONcommand.

    System Action: Server operation continues.

    User Response: The QUERY LOG command(FORMAT=DETAILED) can be used to display thecurrent value for recovery log consumption.

    ANR0385I Could not free sufficient buffers toreach reduced BUFPoolsize.

    Explanation: A reduction in the database buffer poolsize was requested. However, too many buffers were inuse to reach the lower buffer pool size.

    System Action: Server operation continues. Whateverbuffer pool size reduction that could be achieved is ineffect. The new bufpoolsize is written to the options filefor use on the next server startup.

    User Response: None.

    ANR0386I The BUFPoolsize has been changed tobuffer pool size.

    Explanation: The BUFPoolsize option has beenchanged to the indicated value.

    System Action: Server operation continues.

    User Response: None.

    ANR0390W A server database deadlock situation hasbeen encountered: lock request fortransaction transaction ID will be deniedto resolve the deadlock.

    Explanation: The server detected a deadlock situationbetween a number of processes attempting to accessdatabase information. A lock request for one of theprocesses will be denied to resolve the databasedeadlock. When server processes encounter a databasedeadlock, they usually reattempt the function that wasin progress when the deadlock was encountered. Notall process can explicitly re-try an operation. Forexample, migration and reclamation will eventuallyretry. However, something like a delete volume run in amacro will only retry if the delete command is reissuedeither in the macro or the command line.

    System Action: A lock request fails for one of thedeadlocked processes. Server operation continues.

    User Response: If a process can retry (like migration),then monitor the re-try attempt to see if it succeeds or

    ANR0380W ANR0390W

    Chapter 3. Common and Platform Specfic Messages 25

  • not. If it fails, contact a service representative. If theprocess or command is not able to retry on its own,then reissue the command or macro that caused theaction to occur. If it fails again, contact a servicerepresentative for further assistance to better isolate thedeadlock condition.

    ANR0400I Session session number started for nodenode name (client platform) (communicationmethod).

    Explanation: A new client session has been initiatedby the specified node. The session number, clientplatform type and communication method used by thissession are included in the message.

    System Action: The server begins a communicationssession to service the client node.

    User Response: None.

    ANR0401I Session session number started for nodenode name (client platform) (communicationmethod) (WDSF client).

    Explanation: A new WDSF client session has beeninitiated by the specified node. The session number,client platform type and communication method usedby this session are included in the message.

    System Action: The server begins a communicationssession to service the client node.

    User Response: None.

    ANR0402I Session session number started foradministrator administrator ID(administrators platform) (communicationmethod).

    Explanation: A new administrator client session hasbeen initiated by the specified administrator. Thesession number, administrators platform type andcommunication method used by this session areincluded in the message.

    System Action: The server begins a communicationssession to service the administrator client.

    User Response: None.

    ANR0403I Session session number ended for nodenode name (client platform).

    Explanation: A client session has completed normally.

    System Action: Server operation continues.

    User Response: None.

    ANR0404I Session session number ended for nodenode name (client platform) (WDSF client).

    Explanation: A WDSF client session has completednormally.

    System Action: Server operation continues.

    User Response: None.

    ANR0405I Session session number ended foradministrator administrator ID (clientplatform).

    Explanation: An administrative client session hascompleted normally.

    System Action: Server operation continues.

    User Response: None.

    ANR0406I Session session number started for nodenode name (client platform) (communicationmethod communication address).

    Explanation: A new client session has been initiatedby the specified node. The session number, clientplatform type, communication method and addressused by this session are included in the message.

    System Action: The server begins a communicationssession to service the client node.

    User Response: None.

    ANR0407I Session session number started foradministrator administrator ID(administrators platform) (communicationmethod communication address).

    Explanation: A new administrator client session hasbeen initiated by the specified administrator. Thesession number, administrators platform type,communication method and address used by thissession are included in the message.

    System Action: The server begins a communicationssession to service the administrator client.

    User Response: None.

    ANR0408I Session session number started for serverserver name (servers platform)(communication method) for purpose.

    Explanation: A new server session has been initiatedby the specified server for the specified purpose. Thesession number, servers platform type andcommunication method used by this session areincluded in the message.

    System Action: The server begins a communicationssession to service the administrator client.

    User Response: None.

    ANR0400I ANR0408I

    26 IBM Tivoli Storage Manager: Messages

  • ANR0409I Session session number ended for serverserver name (client platform).

    Explanation: A server has completed normally.

    System Action: Server operation continues.

    User Response: None.

    ANR0410E EXPORT operation to server server namerejected - administrator administrator isnot authorized to perform the importoperation on the target server.

    Explanation: An export operation to the named serverwas rejected, because the administrator issuing theexport command is not defined on the target server ordoes not have sufficient authority to perform theimport operation on the target server.

    System Action: Server operation continues.

    User Response: None.

    ANR0411I Session session number for administratoradministrator name logged in as node nodename restored or retrieved object typeobject: node node name, filespace filespacename, object object name.

    Explanation: This message logs information about anobject that was restored or retrieved by anadministrator logged in for a node.

    System Action: Server operation continues.

    User Response: None.

    ANR0412I Session session number for node nodename restored or retrieved object typeobject: node node name, filespace filespacename, object object name.

    Explanation: This message logs information about anobject that was restored or retrieved by anadministrator logged in for a node.

    System Action: Server operation continues.

    User Response: None.

    ANR0413I Session session number for administratoradministrator name logged in as node nodename is restoring backup set: node nodename, set filespace name.

    Explanation: This message logs information about abackup set restored by an administrator logged in for anode.

    System Action: Server operation continues.

    User Response: None.

    ANR0414I Session session number for node nodename is restoring backup set: node nodename, set filespace name.

    Explanation: This message logs information about abackup set restored by a node.

    System Action: Server operation continues.

    User Response: None.

    ANR0418W Session session number for administratoradministrator name (client platform) refused- invalid password submitted.

    Explanation: The server refuses a request to start aclient session because an invalid password has beensubmitted by the client during sign-on processing. Theserver will continue to deny access attempts by thisclient until a valid password is submitted.

    System Action: Server operation continues.

    User Response: Enter the proper password. If thepassword has been forgotten by the user, an authorizedadministrator can assign a new password by using theUPDATE ADMIN command.

    ANR0419W Administrative client useridadministrative ID cannot be used whenauthentication is on.

    Explanation: The server refuses a request for a client(administrative) session because the user ID specifiedcannot be used when authentication of IDs is in effect.SERVER_CONSOLE is an administrative ID that hasthis restriction.

    System Action: Server operation continues.

    User Response: Use an administrative ID that wasregistered for this server and that has a password.

    ANR0420W Session session number for node nodename (client platform) refused - serverdisabled for user access.

    Explanation: The server refuses a request for a client(backup-archive) session because the server is currentlydisabled for client access.

    System Action: Server operation continues.Administrative clients are permitted access to theserver.

    User Response: An authorized administrator mustissue the ENABLE command before client nodes arepermitted access to the server.

    ANR0409I ANR0420W

    Chapter 3. Common and Platform Specfic Messages 27

  • ANR0421W Session session number for node nodename (client platform) refused - sign-onprotocol violation.

    Explanation: The server refuses a request for a clientsession because sign-on protocol has been violated.

    System Action: Server operation continues.

    User Response: This error is usually the result of aclient programming error in which the sign-on verb hasbeen incorrectly formatted and delivered to the server.This error can also result when the server is contactedby an application that is not a part of this product.

    ANR0422W Session session number for node nodename (client platform) refused - nodename not registered.

    Explanation: The server refuses a request to start aclient session because the client node name is notregistered in the server database.

    System Action: Server operation continues.

    User Response: Register the node name with theserver before establishing a session. If the server isrunning with OPEN registration, no action is required;the client prompts the user for a password andregisters the client with the server. If CLOSEDregistration is in effect on the server, an authorizedadministrator must use the REGISTER NODEcommand to register the client node name with theserver.

    ANR0423W Session session number for administratoradministrator ID (client platform) refused -administrator name not registered.

    Explanation: The server refuses a request to start anadministrative session because the administrator nameis not registered in the server database.

    System Action: Server operation continues.

    User Response: Register the administrator name withthe server before establishing a session. An authorizedadministrator must use the REGISTER ADMINcommand to register the administrator with the server.

    ANR0424W Session session number for node nodename (client platform) refused - invalidpassword submitted.

    Explanation: The server refuses a request to start aclient session because an i