DB2 Server for VSE & VM: Data Restore Guide


Part 1. System Errors

For all messages issued by a system refer to the documentation for that system.

The messages are issued on SYSLOG or the system console and can be complimented with a storage DUMP.

Most of the time, during the Data Restore Feature processing, system errors will occur because hardware devices are not properly LINKed or Ready with an appropriate file mounted.

This partial list of potential problems and suggested actions will help you to solve problems before contacting your technical support.

VM Environment - Possible Problems:

  1. Feature not linked to the directory and dbextents minidisks:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXIN571I CREATING NEW FILE:
    DMSXSU559W WARNING: FILE IS EMPTY
    DMSXSU585E NO LINE(S) CHANGED
    DMSXSU559W WARNING: FILE IS EMPTY
    DMSXCT559E EMPTY FILE SQLDB2 XTS9FEDF A1 NOT WRITTEN
    

    User response: Parameter DBNAME specified in SYSIN refers to the database to process. Data Restore needs to LINK the directory and dbextent minidisks to access the specified database. File dbname SQLFDEF defined on the production minidisk of the database server must be accessed to process the required LINK commands. Execute the required LINK and ACCESS commands to the database server production minidisk and retry the process.

  2. The Server is active and access required needs Read/Write access:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    HCPLNM105E SQLDB2 0200 NOT LINKED; R/W BY SQLDB2
    ARIO644E ERROR OCCURRED DURING LINK COMMAND FOR CUU 200
             THE RETURN CODE = 105.
    XTS9-146 Error at EXEC XTS9FDEF DEF
    

    User response: The function executed requires access in READ/WRITE mode, but the server is still active and the disk cannot be linked. The user should terminate the database server before restarting the procedure OR modify the MODE= parameter with value ONLINE to specify that the server is still active.

  3. Tape device for output is not properly attached:



    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    DMSTLM110S ERROR READING TAP1(181)
    XTS9-132 LMBRC031 file BASE2-ARCHIV OPEN ERROR R15=00
    

    User response: Verify that the tape device is attach at address 181 and is ready.

  4. Tape is probably write protected:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    DMSTLM111S ERROR WRITING TAP1(181)
    XTS9-132 LMBRC031 file BASE2-ARCHIV OPEN ERROR R15=00
    

    User response: Verify that the tape mounted is not write protected and is ready.

  5. Disk access is not properly defined :



    DMSFLD069I FILEMODE H NOT ACCESSED
    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    

    User response: Access all disks, where the FILEDEFs are defined.

  6. Tape mounted is not a standard label tape:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    DMSTLM431E TAP1(181) VOL1 LABEL MISSING
    DMSTLM446R ENTER 1(VOLID) (WRITE(VOLID)), 2(REJECT) OR 3(NEWTAPE)
    1(111111)
    

    User response The FILEDEF specifies a standard label tape is being used, but the tape mounted has no label. Specify the valid LABEL as requested within parenthesis.

  7. Error in archiving to two tapes concurrently



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    DMSSOP036E OPEN ERROR CODE 4 ON ARCHIV2
    XTS9-132 LMBRC031 file BASE2-ARCHIV2 OPEN error R15=00
    

    User response The parameter ARCHIV2 is specified to process a DUAL BACKUP but the associated FILEDEF ARCHIV2 was not defined.

    Add the required FILEDEF and rerun the EXEC.

  8. Error in attempting to archive to disk :



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    XTS9-141 External labeling of this archive is
    XTS9-142 Base BASE2    Date 26/09/95 Time 10:04:15
    XTS9-001 Processing directory
    DMSEERD107S DISK A(191) IS FULL
    DMSSCT120S OUTPUT ERROR CODE 013 ON ARCHIV2
    DMSABE148T SYSTEM ABEND 001 CALLED FROM 00E3A3FC REASON CODE 000000
    DMSABE141T PROGRAM INTERRUPT X'00CC' OCCURRED AT E3A3FC IN ROUTINE
    CMS
    

    User response: The parameter ARCHIV2 is specified to process a DUAL BACKUP, the associated FILEDEF ARCHIV2 is defined on DISK but the DISK is full. Define a larger disk or change device to tape.

  9. Insufficient storage available to satisfy storage request:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    XTS9-141 External labeling of this archive is
    XTS9-142 Base BASE2    Date 26/09/95 Time 10:09:28
    XTS9-001 Processing directory
    XTS9-002      9571 directory blocks saved
    DMSFR0159E INSUFFICIENT STORAGE AVAILABLE TO SATISFY FREE STORAGE REQUEST FROM 
    000363B8 XTS9-117 GETMAIN unsuccessful (R15=01)
    READY(00016); T=1.51/3.07 10:09:48
    

    User response: The CMS machine processing the function does not have enough storage to operate successfully. Define an 8 Meg virtual storage machine to process the function.

  10. Error in executing the main Data Restore program:



    backup
         7 *-* 'XTS91001'
           +++ RC(-3) +++
    READY(-0003);; T=0.02/.02 10:33:45
    

    User response: The CMS machine where Data Restore was installed is not linked or the XTS9GMOD procedure has not been properly processed. Link the disk, and retry the operation. If it still fails, repeat the installation process and ensure that the Data Restore Feature is properly installed.

  11. Feature not properly linked:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    XTS9-132 LMBRC033 file BASE2-BDISK READ error R15=08
    

    User response: The disk where Data Restore was installed is likely linked with the virtual address that was used for the database directory disk.

    We recommend to link the minidisk where Data Restore is installed, with an address which is not currently used by any of the application server's minidisks.

  12. Feature not properly linked:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 200 REPLACES B (200)
    DMSACC724I 201 REPLACES C (201)
    DMSACC724I 201 REPLACES C (201)
    XTS9-172 DB2 was ended with logmode L
    XTS9-141 External labeling of this archive is
    XTS9-142 Base BASE2    Date 26/09/95 Time 10:09:28
    XTS9-001 Processing directory
    XTS9-002      9571 directory blocks saved
    READY(00016); T=1.51/3.07 10:09:48
    

    User response: The disk where The Data Restore Feature was installed is likely linked with the virtual address that was used for a dbextent.

    We recommend to link the minidisk where The Data Restore Feature is installed, with an address which is not currently used by any of the application server's minidisks.

  13. Failure on Restore function:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 6 OCCURRENCE(S) CHANGED ON 6 LINE(S)
    XTS9-034 Restore from user archive invoked
    XTS9-305 Current database will be destroyed
    XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
    1
    DMSACC724I 200 REPLACES B (203)
    XTS9-008 Restoring directory
    DMSDK1307T FILE SYSTEM ERROR DETECTED BY DMSRCM AT ADDRESS 00E2AFBE (OFFSET 
    000023B6):
    DMSDKD1307T WRTK REQUEST FAILED WITH CODE 8 WHILE PROCESSING FILE BASE2 BDISK B6
    DMSABE2047I AUTODUMP DUMP STARTED; PLEASE WAIT
    DMSABE1297I DUMP HAS BEEN TAKEN
    HCPGIR450W CP ENTERED; DISABLED WAIT PSW 00020000 00F11316
    

    User response: The directory size of the current database is different from the saved database (smaller). Define an appropriate size minidisk and execute a FORMAT and RESERVE for this minidisk before restarting the RESTORE procedure.

  14. Incorrect password specified for minidisk access:



    XTS9-100 Data Restore Feature Version 7.1.0
    DMSXCG517I 4 OCCURRENCE(S) CHANGED ON 4 LINE(S)
    ENTER WRITE PASSWORD:
     
    HCPLNM114E SQL350 1200 NOT LINKED; MODE OR PASSWORD INCORRECT
    ARI0644E An error occurred during LINK command for
             CUU 1200 .
             Return Code = 114
    XTS9-146 Error at EXEC XTS9FDEF DEF
    READY; T=0.20/0.36 11:45:25
    

    User response: You were restoring a database but the minidisks are password protected and you entered a wrong password. You can specify this password on the CONTROL statement in SYSIN.

  15. Invalid access to the server:



    Do you want to continue the UNLOAD     process ?
    XTS9-146 Enter 0(CANCEL) or 1(CONTINUE)
    1
    XTS9-100 Data Restore Feature Version 7.1.0
    HCPLNM105E SQLDB2 0200 NOT LINKED; R/W BY SQLDB2
    ARI0644E ERROR OCCURRED DURING LINK COMMAND FOR CUU 200
             THE RETURN CODE = 105.
    XTS9-146 Error at EXEC XTS9FDEF DEF
    READY; T=0.53/0.90 11:57:27
    

    User response: The UNLOAD function was executed with OFFLINE parameter, but the server is still active. Specify ONLINE in SYSIN or terminate the server.

  16. Wrong format found on tape mounted:



    Do you want to continue the TRANSLATE process ?
    XTS9-146 Enter 0(CANCEL) or 1(CONTINUE)
    1
    XTS9-100 Data Restore Feature Version 7.1.0
    DMSSCT120S INPUT ERROR CODE 008 ON ARIARCH
    DMSABE148T SYSTEM ABEND 001 CALLED FROM 00E3A3FC REASON CODE 00000000
    DMSABE141T PROGRAM INTERRUPT X'00CC' OCCURRED AT E3A3FC IN ROUTINE
    

    User response: The tape mounted for ARIARCH is not in the DB2 Server for VSE & VM archive format. Mount a tape produced by DB2 Server for VSE & VM standard ARCHIVE Version 7 Release 1 .

  17. Incorrect National Language specification selected:



    DMSLIO201W THE FOLLOWING NAMES ARE UNDEFINED:
     LMBRS003
    READY; T=0.22/0.37 17:01:46
    

    User response: The user has chosen a national language by specifying LANG= parameter. The associated TEXT was not found.

    Example: LANG=S003 is specified but LMBRS003 TEXT is not found. Correct the LANG= parameter or contact IBM Support Center for assistance.

VSE Environment

  1. Missing TLBL definition:



    XTS9-100 Data Restore Feature Version 7.1.0
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    XTS9-172 DB2 was ended with logmode Y
    4183I INVALID LOGICAL UNIT  ARCHIV   SYS006
    0V15I JOB LMBRBACK CANCELED. REQUEST FROM SYSTEM SERVICE ROUTINE
    1S78I  JOB TERMINATED DUE TO  PROGRAM ABEND
    

    User response: The TLBL for ARCHIV file is missing. Specify a TLBL/DLBL with ddname ARCHIV.

  2. A user archive is requested, but server is on-line:



    XTS9-100 Data Restore Feature Version 7.1.0
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    4228I FILE LOGDSK1    OPEN  ERROR X'A8'(168)
    1S78I  JOB TERMINATED DUE TO  RETURN CODE
    EOJ LMBRBACK  MAX.RETURN CODE=0016
    

    User response: Stop the server to process the BACKUP function.

  3. Tape device not properly attached:



    // JOB LMBRBACK
    0P31A    DVC NOT OP SYSCTL=4A1
    CCSW=   NOT AVAILABLE   CCB=047360
    

    User response: Verify that the tape device specified is attached properly.

  4. Missing TLBL definition:



    XTS9-100 Data Restore Feature Version 7.1.0
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    XTS9-172 DB2 was ended with logmode Y
    4881I NO LABEL INFORMATION  ARCHIV
    0V15I JOB LMBRBACK CANCELED. REQUEST FROM SYSTEM SERVICE ROUTINE
    

    User response: TLBL for ARCHIV is missing. Add the required TLBL specification to the JCL.

  5. LIBDEF statement points to an incorrect library :



    // EXEC XTS91001,SIZE=XTS91001,PARM='DBNAME=dbname'
    1U58I  PROGRAM NOT FOUND.
    1I70I  JOB LMBRBACK CANCELED DUE TO CONTROL STATEMENT
    

    User response: The LIBDEF statement is omitted or the Data Restore library is not specified. Correct the LIBDEF statement. If the problem persists, verify that Data Restore was installed correctly, and if necessary repeat the installation.

  6. Incorrect specification on the Unload function:



    XTS9-100 Data Restore Feature Version 7.1.0
    XTS9-309 Processing DB2 Server for VSE & VM version 7
    ARI0415D Database server &1 is not ready. Enter WAIT or CANCEL.
    

    User response: An UNLOAD function is executed with MODE=ONLINE parameter, but the server is not active. Restart the server and reply WAIT on console.

  7. Incorrect specification on the Unload function:



    XTS9-100 Data Restore Feature Version 7.1.0
    4228I FILE BDISK      OPEN  ERROR X'A8'(168)
    1S78I  JOB TERMINATED DUE TO  RETURN CODE
    EOJ LMBRBACK  MAX.RETURN CODE=0016
    

    User response: An UNLOAD function is executed with MODE=OFFLINE parameter, but the server is active. Shut down the server and restart the process or specify MODE=ONLINE parameter.

  8. Incorrect National Language support specification selected:



    PROG=LMBRS003 NOT FOUND
    1S55I  LAST RETURN CODE WAS 0016
    

    User response: LANG=S003 parameter is specified but the associated program is not found. Correct the LANG parameter or contact your technical support.

  9. Incorrect specification for the DB2 archive tape:



    // JOB LMBRBACK
    XTS9-100 Data Restore Feature Version 7.1.0
    4183I INVALID LOGICAL UNIT  ARIARCH  SYS007
    0V15I JOB LMBRBACK CANCELED. REQUEST FROM SYSTEM SERVICE ROUTINE
    1S78I  JOB TERMINATED DUE TO  PROGRAM ABEND
    EOJ LMBRBACK
    

    User response: The TRANSLATE function is executing but the DB2 Server for VSE & VM archive tape was not defined with ddname ARIARCH and was not assigned to the SYS0007 address unit. Correct the JCL and retry the procedure.

  10. Incorrect JCL specification for the TRANSLATE function :



    // JOB LMBRBACK
    XTS9-100 Data Restore Feature Version 7.1.0
    4228I FILE DIRWORK    OPEN  ERROR X'80'(128)
    1S78I  JOB TERMINATED DUE TO  RETURN CODE
    EOJ LMBRBACK  MAX.RETURN CODE=0016
    

    User response: The TRANSLATE function requires a DLBL for the DIRWORK, SYS0001, and HEADER work files. Correct the JCL and restart the process.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]