The Data Restore Feature messages are preceded by XTS9. This part is ordered by message number.
Possible solution: You have specified a national language with the LANG parameter on the OPTIONS statement (refer to OPTIONS and CONTROL Statements for more information). For example, when you specify a language SSSS : program LMBRSSSS must be found. Correct the LANG parameter.
Possible solutions:
If the program specified in the message is LMBRP008 : The tape was not created on a DB2 Version 7 Release 1 database. The TRANSLATE function cannot proceed. Mount the correct tape.
If the program specified in the message is LMBRP043 : To save your database, virtual storage is required and the work size specified is too small for your database. Increase the value of the WRKSIZE parameter and retry the process.
If the program specified in the message is LMBRP061 : You are reloading a table with full environment recreation, and the table is contains many views. Increase the NBVIEWS parameter to specify the maximum number of views to recreate and retry the process.
Possible solution: You are trying to RELOAD an unknown table. Verify the input file content using the DESCRIBE function or check the table name and creator in SYSIN.
Possible solution: An open error occurred. Verify the specified file is accessible and the tape drive ready and that a FILEDEF or DLBL/TLBL is defined. Also analyze the system message on the operator console.
Possible solution: You are trying to execute the FORMAT function in a VM system but this function is only available for in VSE. To format a DBEXTENT in VM, you can use CMS FORMAT and RESERVE commands.
Possible solution: You are trying to restore a database but the input file defined with ddname ARCHIV has not been generated by a BACKUP function. If the tape was generated by a standard DB2 archive, use the TRANSLATE function to convert the archive file into a Data Restore format.
Possible solution: Tables containing LONGVARCHAR columns cannot be processed by the SELECT function.
Possible solution: You have selected a table using the SELECT function. The number of resulting rows is not the same as the one expected. The SELECT function processes pages on disk and if a checkpoint has not been issued, pages on the disk may contain old information. You can ACQUIRE and DROP a dbspace to force a checkpoint and retry your request.
Possible solution: An SQLDBA userid must be defined in the database with a password and have DBA authority. Verify that such a user is defined. To define an SQLDBA userid process the following command while connected with DBA authority: 'GRANT DBA TO SQLDBA IDENTIFIED BY xxxxxxxx' and retry your request.
Possible solution: The TRANSLATE function is processed to convert a DB2 archive file that was not created in Version 7 Release 1. Data Restore can only process DB2 Version 7 Release 1 archive files.
Possible solution: You are processing a dbspace with UNLOAD function but the dbspace specified does not exist. Verify the DBNAME parameter is correct. Verify the syntax for the DBSPACE parameter.
Possible solution: You are processing a RESTORE function, but the mounted tape was not produced by a BACKUP or TRANSLATE function. Mount the correct tape before restarting the RESTORE process.
Possible solution: You are reloading a table and using the RESTARTCOUNT parameter to skip a certain number of rows, but the table contains LONG columns. RESTARTCOUNT cannot be used with tables containing LONG columns. You must restart the RELOAD function without specifying RESTARTCOUNT parameter.
Possible solution: You are processing a BACKUP function for a database. The database server must be terminated using the SQLEND UARCHIVE operator command. The server was not stopped using this command. Restart the server to specify that command and retry the BACKUP process.
Possible solution: You are processing a RELOAD function with forward log recovery. The database archive has been found in the log history area, but an action is found that cannot guarantee security for the recovery process (such as COLDLOG or ARCHIVE when running in LOGMODE A). Re-execute the process without RECOVERY=YES parameter.
| Note: | You will not be able to recover using updates in the log in this situation. |
Possible solution: The DB2 version displayed is not correct during installation of Data Restore Feature:
Possible solution: You are restoring from a file that was produced on a different database. Confirm to continue the process or verify that the mounted tape is the correct one.
Possible solution: If no other messages are displayed, verify that the files defined in the process (such as ARIARCH or ARCHIV) are assigned to the correct file. Retry the process after verifying the FILEDEFs (VM) or DLBLs/TLBLs (VSE).
When you specify REPLACE for the FUNCT parameter during the RELOAD function, all SQL commands necessary to recreate the environment are executed. If a DB2 Server for VM error occurs during this process, the commands for environment recreation are inserted into a DB2 Server for VM table named DATARFTR.CMD and information about the SQLCODE and the program in error are displayed on SYSPRINT for VM or on the PRINTER for VSE.
When all the rows are not reloaded:
| Note: | If the RESTARTCOUNT parameter is specified, log recovery cannot be done. |
When all the rows are reloaded:
The following is an example of JCL to run the program XTS91002 in VSE:
Figure 235. Example JCL to Recover From an Environment Recreation Error
// JCL RECOVER
// LIBDEF *, SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC XTS91002,SIZE=AUTO,PARM='DBAPW=XXXXXXXX,DBNAME(dbname)'
/ *
The following is an example of an EXEC to run the program XTS91002 in VM:
Figure 236. Example EXEC to Recover From an Environment Recreation Error
/**/
'FILEDEF SYSPRINT DISK XTS91002 SYSPRINT A'
'XTS91002 DBAPW=XXXXXXXX'
The DATARFTR.CMD table has the following columns:
To select rows from the table in the proper order, you must specify ORDER BY SEQ,SUBSEQ on the SELECT statement.
The following is an example of rows that may be found in the DATARFTR.CMD table.
Figure 237. Example of Rows in DATARFTR.CMD
*
SELECT * FROM DATARFTR.CMD ORDER BY SEQ,SUBSEQ
*
SEQ SUBSEQ CMD
--- ------- -------------------------------------------------------------
5 5 CREATE INDEX "SQLDBA"."ISYSTEXT1" ON "SQLDBA"."SYSTEXT1" ("T
5 10 OPIC" ASC ) PCTFREE=10;
10 5 COMMIT WORK ;
15 5 CREATE UNIQUE INDEX "SQLDBA"."DEUXIEME" ON "SQLDBA"."SYSTEXT
15 10 1" ("TOPIC" ASC ,"ITEM" ASC ) PCTFREE=10;
20 5 COMMIT WORK ;
25 5 CREATE INDEX "SQLDBA"."I1SYSTEXT1" ON "SQLDBA"."SYSTEXT1" ("
25 10 TOPIC" ASC ) PCTFREE=10;
30 5 COMMIT WORK ;
35 5 CONNECT SQLDBA ;
40 5 GRANT SELECT ON "SQLDBA"."SYSTEXT1" TO "PUBLIC";
45 5 COMMIT WORK ;
50 5 GRANT SELECT ON "SQLDBA"."SYSTEXT1" TO "GEORGE" WITH GRANT O
50 10 PTION;
55 5 COMMIT WORK ;
60 5 CONNECT SQLDBA ;
65 5 LABEL ON COLUMN "SQLDBA"."SYSTEXT1"."ITEM" IS '""';
70 5 COMMIT WORK ;
75 5 LABEL ON COLUMN "SQLDBA"."SYSTEXT1"."TOPIC" IS '""';
80 5 COMMIT WORK ;
When you reload a table from a BACKUP or a DB2 Server for VSE & VM archive file, the reloaded table does not contain any of the changes made on that table after the backup was taken. Those changes are recorded in any log archives taken since the backup and in the current log.
If you want to reload a table and apply the changes, specify RECOVERY=YES on the OPTIONS statement (refer to OPTIONS and CONTROL Statements) during the RELOAD process. Refer to the next sections for information on listing and applying the changes in the log.
Notes:
Figure 238. Possible Input Sources for RELOADing Tables with Forward Recovery
|
If an error occurs during full environment recreation, refer to Recover from a DB2 Server for VM Error during Full Environment Recreation.
Problems may occur on an extended dynamic command; see Figure 239 for an example of this.
Figure 239. DB2 Server for VSE Error on an Extended Dynamic Statement During the Reload Process
Problems may also occur on a dynamic statement; see Figure 240 for an example of this.
Figure 240. DB2 Server for VSE Error on a Dynamic Statement During the Reload Process
XTS9-143 RELOAD TNAME=SYSCATALOG
XTS9-143 CREATOR=DATARFTR
XTS9-143 FUNCT=NEW NEWCREATOR=GEORGE
XTS9-143 CONTROL DBNAME=dbname
XTS9-143 OPTIONS DEVICE=DASD,COMMITCOUNT=5000
XTS9-143 /*
XTS9-100 Data Restore Feature Version 7.1.0
XTS9-136 Processing SQL/VSE archived on (14/10/94-15:38:54)
XTS9-129 SQL error (sqlcode= -601,errd1= 0,errd2= 0)
XTS9-153 SQL msg()
XTS9-162 SQL stmt:SQLDBA .LMBRP017.006
Figure 241. Example of a Dump Produced for a DB2 Server for VSE Error on a Dynamic Statement During the Reload Process
LMBRP099-0209
0000 0208C3D9 C5C1E3C5 40E3C1C2 D3C5407F D4C9D3D3 D6D57F40 4B7FE2E8 E2C3C1E3
0020 C1D3D6C7 7F4D7FE3 D5C1D4C5 7F40E5C1 D9C3C8C1 D94D40F1 F85D6B7F C3D9C5C1
0040 E3D6D97F 40C3C8C1 D94D40F8 5D6B7FE3 C1C2D3C5 E3E8D7C5 7F40C3C8 C1D94D40
0060 F15D3B7F D5C3D6D3 E27F40E2 D4C1D3D3 C9D5E36B 7FD9C5D4 C1D9D2E2 7F40E5C1
0080 D9C3C8C1 D94D40F2 F5F45D6B 7FC4C2E2 D7C1C3C5 D5D67F40 E2D4C1D3 D3C9D5E3
00A0 6B7FC4C2 E2D7C1C3 C5D5C1D4 C57F40E5 C1D9C3C8 C1D94D40 F1F85D6B 7FE3C1C2
00C0 C9C47F40 E2D4C1D3 6B7FC3D3 E4E2E3C5 D9E3E8D7 C57F40C3 C8C1D94D D3C9D5E3
00E0 40F15D6B 7FC3D3E4 E2E3C5D9 D9D6E67F 40C9D5E3 C5C7C5D9 406B7FC1 E5C7D9D6
0100 E6D3C5D5 7F40E2D4 C1D3D3C9 D5E36B7F D6E4D5E3 7F40C9D5 E3C5C7C5 D9D6E6C3
0120 D9406B7F D5D7C1C7 C5E27F40 C9D5E3C5 C7C5D940 6B7FD7C3 E3D7C1C7 C5E27F40
0140 E2D4C1D3 D3C9D5E3 6B7FD5D6 E5C5D9C6 D3D6E67F 40C9D5E3 C5C7C5D9 406B7FD3
0160 C6C4E3C1 C2C9C47F 40E2D4C1 D3D3C9D5 E36B7FD3 C6C4D3C9 D5D27F40 E2D4C1D3
0180 D3C9D5E3 6B7FD3C6 C4C4C2E2 D7C1C3C5 7F40E2D4 C1D3D3C9 D5E36B7F E3D3C1C2
01A0 C5D37F40 E5C1D9C3 C8C1D94D 40F3F05D 6B7FD7C1 D9C5D5E3 E27F40E2 D4C1D3D3
01C0 C9D5E36B 7FC4C5D7 C5D5C4C5 D5E3E27F 40E2D4C1 D3D3C9D5 E36B7FC9 D5C1C3E3
01E0 C9E5C57F 40E2D4C1 D3D3C9D5 E35D40C9 D5407D7 E4C2D3C9 C37F404B 7FC2C1C3
0200 D2E2E3D6 D9C57F40 40400000
Figure 242. Example of Table Content for a DB2 Server for VSE & VM Error on a Dynamic Statement During the Reload Process
*..CREATE TABLE "GEORGE" . "SYSCAT * 0D2008
*ALOG" ("TNAME" VARCHAR( 18) , "CREA * 0D2028
*TOR" CHAR( 8) , "TABLETYPE" CHAR ( * 0D2048
*1),"NCOLS" SMALLINT , "REMARKS" VA * 0D2068
*RCHAR( 254) , "DBSPACENO" SMALLINT * 0D2088
*,"DBSPACENAME" VARCHAR( 18) , "TAB * 0D20A8
*ID" SMALLINT , "CLUSTERTYPE" CHAR( * 0D20C8
* 1) , "CLUSTERROW" INTEGER , "AVGRO * 0D20E8
*WLEN" SMALLINT,"ROWCOUNT" INTEG * 0D2108
*ER , "NPAGES" INTEGER , "PCTPAGES" * 0D2128
*SMALLINT,"NOVERFLOW" INTEGER , "L * 0D2148
*FDTABID" SMALLINT,
LFDLINK" SMAL * 0D2168
*LINT, "LFDDBSPACE" SMALLINT ,"TLAB * 0D2188
*EL" VARCHAR ( 30) , "PARENTS" SMALL* 0D21A8
*INT,"DEPENDENTS" SMALLINT,"INACT * 0D21C8
*IVE" SMALLINT ) IN "PUBLIC"."BAC * 0D21E8
*KSTORE" 0D2208
*
In any case, refer to the DB2 Server for VM Messages and Codes manual to check the meaning of the SQLCODE, or contact your database administrator or system administrator for assistance.
| Note: | The dump that is produced will help IBM technical support investigate the problem, if you are not able to solve it yourself. |