|
|
190
Data Restore Guide
Appendix A. Messages and Codes
XTS9-001
Processing directory
XTS9-012
12 days before password expiration
Explanation: The Data Restore feature is processing
Explanation: Your password will expire in 12 days.
the archive for the DB2 Server for VSE & VM directory.
All directory blocks are saved.
XTS9-013
Table xxx.xxx may be reloaded
Explanation: When processing BACKUP or UNLOAD
XTS9-002
xxx directory blocks saved
function, the list of reloadable tables will be displayed
Explanation: After the Data Restore feature has
on the PRINTER.
finished the directory archive, this message gives the
User Response: Check to make sure all tables are
user information about the number of blocks saved.
listed. If they are not all listed, Contact IBM Support
Center.
XTS9-005
xxx blocks saved
Explanation: All DBEXTENTS must be saved.
XTS9-014 to XTS9-027
Indicates how many blocks have been saved during
Explanation: Reports are created with these messages.
BACKUP or UNLOAD.
XTS9-100
The Data Restore feature Version xxx
XTS9-006
Processing xxx
Explanation: Data Restore FEATURE version is
Explanation: Indicates which DBEXTENT is being
displayed on PRINTER and CONSOLE.
saved.
XTS9-101
xxx tables successfully processed
XTS9-007
Processing successfully completed
Explanation: With the Data Restore feature, it is
Explanation: Indicates that the command or exec
possible to reload up to 90 tables in one step. At the
executed successfully.
end of the process, the number of reloaded tables is
displayed.
XTS9-008
Restoring directory
Explanation: The RESTORE function has been
XTS9-102
xxx rows loaded procedure completed
invoked, DATA RESTORE FEATURE restores the
Explanation: When reloading tables the Data Restore
directory.
feature the number of rows reloaded. If
RESTARTCOUNT parameter has been specified, the
XTS9-009
xxx directory blocks restored
number displayed includes SKIPPED rows.
Explanation: This message displays the number of
directory blocks restored.
XTS9-103
Filename (xxx) unknown for program
(xxx)
User Response: Check to make sure the number of
directory blocks is correct. If it is not correct, Contact
Explanation: Internal error.
IBM Support Center.
System Action: Processing ends.
User Response: Contact IBM Support Center.
XTS9-010
xxx blocks restored
Explanation: Shows the number of DBEXTENT blocks
XTS9-104
File function(yyy) unknown for
restored.
program(xxx)
Explanation: Internal error. Contact IBM Support
XTS9-011
Restoring xxx
Center.
Explanation: The RESTORE function has been
System Action: Processing ends.
invoked, the Data Restore feature is restoring
DBEXTENT xxx.
User Response: Contact IBM Support Center.
191
XTS9-105
Invalid parameter (yyy) for function
XTS9-111
Length error for xxx
(xxx)
Explanation: The value for NEWCREATOR,
Explanation: The syntax of SYSIN statement is invalid
NEWTNAME, CREATOR, TNAME, DBSPACE,
or the parameter has been specified twice (refer to
OWNER, PWD, BASE, DATE, TIME or DBAPW is too
“OPTIONS and CONTROL Statements” on page 167 for
long.
correct syntax).
System Action: Processing ends.
System Action: Processing ends.
User Response: Correct the SYSIN statement.
User Response: Verify the syntax for the specified
function and correct the SYSIN statement.
XTS9-113
Too many functions specified
Explanation: Only one function can be specified in
XTS9-106
Invalid command in SYSIN
SYSIN (BACKUP, RESTORE, SELECT, FORMAT,
Explanation: Valid commands in SYSIN are OPTIONS,
DESCRIBE, UNLOAD, SHOWDBS, APPLYLOG,
CONTROL, BACKUP, RESTORE, RELOAD, FORMAT,
LISTLOG or TRANSLATE).
SELECT, DESCRIBE, UNLOAD and SHOWDBS and
System Action: Processing ends.
SHOWPOOL. Correct the SYSIN statement.
User Response: Correct the SYSIN statement. Verify
System Action: Processing ends.
functions are specified in column one and continuation
User Response: Verify the syntax for the specified
statement after column one.
function and correct the SYSIN statement. Verify that
continuation lines start after column one.
XTS9-114
No function specified
Explanation: No function (BACKUP, RESTORE,
XTS9-107
Missing parameter (xxx)
RELOAD, SELECT, FORMAT, DESCRIBE, UNLOAD or
Explanation: A mandatory parameter is missing.
SHOWDBS) has been specified in SYSIN. Correct the
Correct the SYSIN statement.
SYSIN statements.
System Action: Processing ends.
Note: If the message, XTS9-107 Missing parameter (″(″
or ″)″ for DBSPACE=) is displayed, check that
User Response: Correct the SYSIN statement. Verify
the list of dbspaces is specified on a maximum of
functions are specified in column one and continuation
10 lines.
statement after column one.
System Action: Processing ends.
XTS9-115
Record not found (Program=xxx)
User Response: Verify the syntax for the specified
function and correct the SYSIN statement.
Explanation: Internal error. Contact IBM Support
Center.
XTS9-109
Invalid value for xxx
System Action: Processing ends.
Explanation: The value specified for xxx parameter is
User Response: Contact IBM Support Center.
invalid (refer to “OPTIONS and CONTROL
Statements” on page 167).
XTS9-116
More than xxx GETMAIN calls occurred
User Response: Verify the syntax for the specified
Explanation: Internal error. Contact IBM Support
function and correct the SYSIN statement.
Center.
System Action: Processing ends.
XTS9-110
More than xxx xxx command(s) in
SYSIN
XTS9-117
GETMAIN unsuccessful (R15=xxx)
Explanation: Only one of each command (OPTIONS,
CONTROL, BACKUP, RESTORE, FORMAT, SELECT,
Explanation: The WRKSIZE parameter specifies a
DESCRIBE, UNLOAD, SHOWDBS, APPLYLOG,
storage size that is larger than is available in the
LISTLOG, TRANSLATE or SHOWPOOL can be
partition (VSE) or the virtual machine (VM).
specified in the SYSIN. Correct SYSIN statements.
System Action: Processing ends.
System Action: Processing ends.
User Response: Correct the parameter WRKSIZE or
User Response: Verify the syntax for the specified
increase the amount of storage available for the Data
function and correct the SYSIN statement.
Restore feature (either by running in a different
partition (VSE) or increasing the size of the virtual
machine (VM).
192
Data Restore Guide
XTS9-118
FREEMAIN unsuccessful (R15=xxx)
XTS9-124
Debugger option in effect
Explanation: Internal error.
Explanation: Internal debugger started.
System Action: Processing ends.
XTS9-125
Debugger breakpoint xxx
User Response: Contact IBM Support Center.
Explanation: Specifies address of breakpoint for DATA
RESTORE FEATURE internal debugger.
XTS9-119
Invalid FREEMAIN address (xxx)
Explanation: Internal error.
XTS9-126
xxx.xxx table cannot be located
System Action: Processing ends.
Explanation: The table specified for RELOAD function
User Response: Contact IBM Support Center.
is not found in archive, or table has been specified
twice in SYSIN.
XTS9-120
EOF condition occurs in program xxx
System Action: Processing ends.
Explanation: This message can be displayed when you
User Response: Verify the TNAME and CREATOR
specify the DBSPACE= parameter for reloading a view.
parameters.
Internal error. In other cases, Contact IBM Support
Center.
XTS9-127
xxx rows loaded, procedure continuing
System Action: Processing ends.
Explanation: The number of loaded rows is displayed
on console when the COMMITCOUNT parameter has
XTS9-121
Program xxx cannot be located
been specified on the OPTIONS statement, and the
reload process is continuing.
Explanation: A program is missing.
System Action: Processing ends.
XTS9-128
xxx rows loaded into (xxx.xxx)
System Programmer Response: Check your
Explanation: The number of rows loaded is displayed
installation.
on console when the Processing ends.
XTS9-122
Processing capacity exhausted(xxx)
XTS9-129
SQL error (SQLCODE=xxx,
Explanation: If program specified in the message is
SQLERRD1=xxx, SQLERRD2=xxx)
LMBRP061 or LMBRP062 increase NBVIEWS parameter
Explanation: An SQLERROR occurred.
on the OPTIONS statement and retry process otherwise
the WRKSIZE parameter on the OPTIONS statement is
System Action: Processing ends.
too small for the Data Restore feature function.
User Response: Refer to the DB2 Server for VM
System Action: Processing ends.
Messages and Codes manuals for an explanation.
User Response: The minimum storage to specify for
WRKSIZE parameter is displayed on XTS9-158
XTS9-130
DBSPACE for xxx.xxx is unknown
message. Modify SYSIN to specify the right WRKSIZE
Explanation: The RELOAD function tried to create a
parameter.
non-existent table and the parameters DBSPACE=,
OWNER= are not specified on the reload SYSIN
XTS9-123
Invalid continuation syntax
statement, or the dbspace is not acquired.
Explanation: A continuation statement is a statement
System Action: Processing ends.
whose first word is not: CONTROL, RELOAD,
User Response: Acquire the specified dbspace or
BACKUP, RESTORE, FORMAT, SELECT, OPTIONS,
specify a different value for DBSPACE= and OWNER=
UNLOAD, SHOWDBS, APPLYLOG, LISTLOG or
parameters.
TRANSLATE and begins after column 1.
User Response: Modify SYSIN to specify continuation
XTS9-131
SQLDBA user not found or password is
properly.
blank
Explanation: The RELOAD, SELECT and UNLOAD
functions need an SQLDBA sign-on with DBA authority
and such a sign-on is not declared in DB2 Server for
VSE & VM database with a password.
System Action: Processing ends.
Appendix A. Messages and Codes
193
User Response: Execute command: GRANT DBA TO
XTS9-142
Base xxx Date xxx Time xxx
SQLDBA IDENTIFIED BY XXXXXXXX while
connected with DBA authority.
Explanation: This message gives the DBNAME, date
and time of the USER ARCHIVE.
XTS9-132
xxx file xxx-xxx xxx error R15=xxx
XTS9-143
xxx
Explanation: Internal error.
Explanation: SYSIN is displayed on PRINTER.
System Action: Processing ends.
User Response: Contact IBM Support Center.
XTS9-145
Table xxx.xxx cannot be processed
Explanation: Table containing longvarchar columns
XTS9-133
Invalid value for timestamp
cannot be processed by SELECT function.
Explanation: Forward log recovery requires a
System Action: Processing ends.
timestamp to process LUW up to a specific timestamp.
The format is invalid.
XTS9-146
Error at xxx xxx xxx
System Action: Processing ends.
Explanation: The storage address is displayed.
User Response: Correct the value. You can use
LISTLOG function to verify the timestamp to specify.
System Action: Processing ends.
User Response: Verify that DBNAME parameter is
XTS9-135
Function not supported VM/CMS)
correct and the server’s 195 disk is accessed.
Explanation: FORMAT function is only available for
VSE environment.
XTS9-147
File produced on xxx at xxx mounted
System Action: Processing ends.
Explanation: Date and time of the archive files do not
match the DATE= and TIME= parameters on the
CONTROL STATEMENT.
XTS9-136
Processing xxx archived on (xxx-xxx)
System Action: Processing ends.
Explanation: Date and time of the archive is
displayed.
User Response: Mount the correct file and re-execute
the process.
XTS9-137
No record ″0″ found on archive
XTS9-148
File produced on xxx at xxx required
Explanation: Internal error.
Explanation: Parameters DATE= and TIME= specified
System Action: Processing ends.
on CONTROL STATEMENT must correspond to
User Response: Verify the input file was produced by
archive file.
BACKUP or UNLOAD function or Contact IBM
User Response: Mount the correct file or change
Support Center.
DATE= and TIME= parameters. You can use DESCRIBE
function to determine the correct values.
XTS9-138
xxx archive mounted for xxx
Explanation: VERIFY=YES parameter is found and
XTS9-150
Table xxx.xxx not found
archive database name is different than the base in
Explanation: A SELECT function is executed for a
which the table is reloaded.
table (CREATOR=, TNAME=) which is not found in
System Action: Processing ends.
DB2 Server for VSE & VM catalogs. TNAME must
specify a table, not a view.
User Response: The database (DBNAME parameter)
processed is different from the one processed during
System Action: Processing ends.
BACKUP or UNLOAD function. Execute SQLINIT with
User Response: Choose an existing table or use
the correct DBNAME parameter. If the database is
DESCRIBE function to determine the tables that can be
different, then specify VERIFY=NO.
processed.
XTS9-141
External labeling of this archive is
:
194
Data Restore Guide
User Response: Modify your SYSIN to specify the
XTS9-151
Column xxx not found in xxx.xxx
required value for WRKSIZE= parameter.
Explanation: A SELECT function is executed for a
table, and only columns specified by COLUMNS=
XTS9-159
System Catalog tables cannot be
parameter will be displayed. One of the columns
reloaded
specified in COLUMNS= parameter is not found in
DB2 Server for VSE & VM catalogs for the table.
Explanation: The Reload function cannot process
System Catalog tables. The NEWCREATOR= parameter
System Action: Processing ends.
can be specified to RELOAD System Catalog tables into
User Response: Change the column name or verify
a user table.
the table name is correct.
System Action: Processing ends.
User Response: Correct the SYSIN.
XTS9-152
xxx rows selected
Explanation: After a SELECT function, the number of
XTS9-160
External labeling of this unload is
rows selected is displayed.
Explanation: The message following this message
displays date and time of the UNLOAD output file.
XTS9-153
Database server message (xxx)
Explanation: During the Data Restore feature
XTS9-161
DBSPACE xxx.xxx not found
functions, if an SQLERROR occurs, after SQLCODE
(message XTS9-129), a complementary message may be
Explanation: UNLOAD dbspace function cannot be
displayed.
executed for a non-existent dbspace, or the dbspace has
been specified twice.
XTS9-154
Wrong password for SQLDBA
System Action: Processing ends.
Explanation: The SQLDBA password must be
User Response: Correct the SYSIN.
specified on the CONTROL statement when the
SELECT function is used. The password specified is not
XTS9-162
SQL stmt: xxx . xxx . xxx
valid.
Explanation: During RELOAD process, if an SQL
System Action: Processing ends
ERROR occurs on a dynamic statement, this message
User Response: Specify the correct password for
will give the program name and statement number in
SQLDBA user.
error and the statement will be displayed on PRINTER.
System Action: Processing ends.
XTS9-155
Column xxx not found
User Response: Analyze SQLCODE and statement
Explanation: The column specified is not found in the
displayed or Contact IBM Support Center.
selected table.
System Action: Processing ends.
XTS9-163
Cursor name: xxx table: xxx.xxx
User Response: Correct SYSIN file.
Explanation: During RELOAD process, if an SQL
ERROR occurs, this message will give the name of the
table in error and the name of the associated cursor.
XTS9-157
Storage violation has occurred
System Action: Processing ends.
Explanation: A Data Restore feature function has not
been successful because a storage violation has
User Response: Analyze SQLCODE or Contact IBM
occurred. A dump is created.
Support Center.
System Action: Processing ends.
XTS9-164
xxx rows skipped, procedure continuing
User Response: Contact IBM Support Center.
Explanation: During RELOAD process, if
RESTARTCOUNT parameter is specified, this message
XTS9-158
WRKSIZE needed is xxx
will be displayed each time COMMITCOUNT
Explanation: Storage required for backup function
parameter value is reached.
should be at least equal to the value specified. Modify
your SYSIN on OPTIONS statement specify a
WRKSIZE parameter equal to or greater than this
value.
System Action: Processing ends.
Appendix A. Messages and Codes
195
User Response: Modify your procedure to specify the
XTS9-165
xxx rows loaded into (xxx.xxx) xxx
FILEDEF.
skipped
Explanation: During reload process, if
XTS9-172
Database server was ended with
RESTARTCOUNT parameter is specified, this message
logmode xxx
is displayed to specify how many rows were skipped
and how many were loaded.
Explanation: This message specifies the last logmode
for DB2 Server for VSE & VM server. If logmode was Y,
forward log recovery cannot be processed.
XTS9-166
File mounted was not produced by
BACKUP function
XTS9-173
Database server was not ended with
Explanation: The RESTORE function is executed for a
UARCHIVE
file that was not produced by BACKUP function.
Explanation: The user executes a BACKUP function
Note: A RESTORE cannot be executed from an
but the server was not ended with the UARCHIVE
UNLOAD file.
parameter.
System Action: Processing ends.
System Action: The process is stopped with RC=26.
User Response: Mount a BACKUP file.
User Response: Restart your database manager and
execute command SQLEND UARCHIVE.
XTS9-167
Record number xxx not found on
LMBRWRK
XTS9-174
Processing xxx unloaded on (xxx-xxx)
Explanation: During log recovery process a record
Explanation: The process is executed on a file
was not found in work file but is specified in
generated by UNLOAD function. The DBNAME, date
LMBRLGn files.
and time of UNLOAD function is displayed.
System Action: Processing ends.
XTS9-175
Recovery not allowed with file
User Response: Verify that all files were produced by
produced by UNLOAD function
the same RELOAD function.
Explanation: RECOVERY=YES parameter can only be
processed on a backup file.
XTS9-168
DBSPACE xxx and Pagexxx not found in
IXLNGVAR (step=xxx)
XTS9-176
Invalid ARCHIV file
Explanation: During log recovery for long columns,
an error occurred, no matching information was found
Explanation: The file was not produced by the
in IXLNGVAR table.
BACKUP function.
System Action: Processing ends.
System Action: Processing ends.
User Response: Contact IBM Support Center.
XTS9-177
Recovery not allowed with file
produced with logmode=xxx
XTS9-169
Processing tables containing long
columns
Explanation: Recovery is allowed only for databases
using LOGMODE = A or L.
Explanation: A specific process is executed for tables
including long columns.
System Action: Processing ends.
XTS9-170
RESTARTCOUNT cannot be used with
XTS9-178
Recovery not allowed with logmode=xxx
a table containing long columns
Explanation: Recovery can only be specified for
Explanation: RESTARTCOUNT parameter can’t be
databases using log archive or archive mode.
specified for tables having long columns.
System Action: Processing ends.
XTS9-171
Missing FILEDEF for xxx
|
XTS9-179
Current log
Explanation: A work file is used during log recovery
|
Explanation: The current log will be required to
process, the FILEDEF for this file is missing.
|
process RELOAD function with RECOVERY=YES
System Action: Processing ends.
|
parameter. This message may be followed by: XTS9-236
|
Inactive log
196
Data Restore Guide
XTS9-180
xxx at xxx
XTS9-187
Invalid action (xxx) found in LMBRLG1
Explanation: The list of archives and log archives
Explanation: The action specified in log is not
necessary for log recovery processing is displayed
INSERT, DELETE, UPDATE, DROP TABLE, DROP
before RELOAD function starts.
DBSPACE, ALTER DBSPACE.
System Action: Processing ends.
XTS9-181
Archive mounted not found in history
User Response: Call IBM Support Center.
area
Explanation: The history area contains all information
XTS9-188
Wrong file mounted
on date and time of archive, user archive and log
archive. The user is processing a tape that is not known
Explanation: The log file specified in message
for database manager in history area cannot be
XTS9-183 is not the one mounted.
processed.
System Action: Processing ends.
System Action: Processing ends.
User Response: Verify the external file label.
User Response: Verify the mounted archive.
XTS9-189
Timestamp xxx reached in log file
XTS9-182
Following files are needed for recovery
Explanation: During APPLYLOG, when END
Explanation: The list of archives and log archives
parameter is reached in log file, this message is
necessary for log recovery processing is displayed
displayed.
before RELOAD function starts.
System Action: Processing ends.
XTS9-183
Please mount log archive at xxx
XTS9-190
Action xxx found in history area
Explanation: The log archive with the specified
Explanation: Reload with log recovery cannot be
timestamp is required to process log recovery on
processed because COLDLOG, ARCHIVE, RESTORE,
reloaded tables.
STARTUP=R, SWITCH TO N, SWITCH TO Y has been
User Response: Mount the required file.
executed after the archive or UARCHIVE was taken.
System Action: Processing ends.
|
XTS9-184
Processing current log
|
Explanation: After all log archives are processed for
XTS9-191
Recovery not possible
|
log recovery, the current log is processed. This message
Explanation: Message XTS9-190 contains the reason
|
may be followed by: XTS9-235 Processing inactive log
why the recovery is not possible
System Action: Processing ends.
XTS9-185
Forward recovery stopped due to xxx
Explanation: During forward recovery process, if a
XTS9-192
Processing xxx archived by database
DROP TABLE, DROP DBSPACE or ALTER TABLE
server on (xxx-xxx)
command on a table being reloaded is found, the
process is stopped.
Explanation: When a process accesses an archive file,
the DBNAME, date and time at BACKUP or UNLOAD
DROP TBL: A DROP TABLE was found
time is displayed.
DROP DBS: A DROP DBSPACE was found
ALTER TB: An ALTER TABLE was found
XTS9-193
Mount first tape of database server
System Action: Processing ends.
archive
Explanation: When a database server archive is used
XTS9-186
Timestamp of statement is xxx
for recovery, the archive tapes must be read twice. This
message is displayed when the first tape of the archive
Explanation: The timestamp for the command
must be mounted for the second time.
specified in message XTS9-185 is displayed.
System Action: The process is waiting for operator
System Action: Processing ends.
intervention
Operator Response: Mount the first archive tape.
Appendix A. Messages and Codes
197
XTS9-194
SQLERRP(xxx)
XTS9-201
Medium is disk xxx xxx *
Explanation: SQLERRP is displayed with SQLCODE,
Explanation: The log archive to be processed was
SQLERRD1, SQLERRD2 and SQLERRM.
created on disk. The filename and filetype are
displayed.
User Response: Refer to the DB2 Server for VSE &
VM messages and Codes manual to analyze the error.
User Response: If the log archive file was moved onto
tape, the user can change the device support by
replying to message XTS9-408.
XTS9-195
xxx currently mounted
Explanation: When reload is executed with
XTS9-202
Processing database server archive
RECOVERY=YES parameter, the list of all necessary
(timestamp=xxx)
files is displayed. The BACKUP file is currently
mounted.
Explanation: The RELOAD process is executed from a
DB2 Server for VSE & VM archive. The timestamp of
the archive is displayed.
XTS9-196
Do you want to continue the xxx process
xxx
XTS9-203
pool=xxx First Extent=xxx Pool is xxx
Explanation: When CONFIRM=YES is specified, the
user is asked to confirm that the process should
Explanation: The SHOWPOOL function displays for
continue.
all defined storpool the list of attached dbextents. This
message displays the first attached dbextent. T his
storpool is recoverable or non recoverable.
XTS9-197
I/O error on LOG disk
Explanation: This message is displayed during the
XTS9-204
dbextent=xxx Pool =xxx Next
RELOAD process with RECOVERY=YES parameter,
Dbextent=xxx
when the current log is processed and an I/O error
occurs on disk.
Explanation: The SHOWPOOL function displays for
all defined storpool the list of attached dbextents. The
System Action: If DUAL logging exists, the reload
dbextents chaining can be analyzed with this message.
continues on the second LOG file. Otherwise, the
processing is terminated.
XTS9-205
dbextent=xxx extend deleted
XTS9-198
Switching to secondary log
Explanation: The SHOWPOOL function displays for
all defined storpool the list of attached dbextents. This
Explanation: This message is displayed during the
message displays deleted extents number.
RELOAD process with RECOVERY=YES parameter,
when the current log is processed and an I/O error
occurs on disk.
XTS9-207
Backup file used can not be restored
System Action: If DUAL logging exists, the reload
Explanation: Pool recovery can not process this file.
continues on the second LOG file.
The reason is describe in preceding message.
XTS9-199
Dual logging not in effect, cannot
XTS9-208
the current database is not R510 or later,
switch to secondary log
a pool recovery cannot be used
Explanation: This message is displayed during the
Explanation: The pool level recovery feature is only
RELOAD process with RECOVERY=YES parameter,
available for a database Version 5 Release 1 and later,
when the current log is processed and an I/O error
the function can’t be processed on the specified
occurs on disk.
database.
System Action: Dual logging is not in effect. RELOAD
User Response: Verify the dbname parameter in
processing is terminated.
SYSIN file and control the database level.
XTS9-200
Processing larchive at xxx
XTS9-209
Pool number xxx must be included in
pool list
Explanation: The log archive created at the displayed
timestamp is being processed.
Explanation: A pool level recovery has been executed
for a list of pool. The processing has been stopped due
to an error. After the problem has been solved, the list
you specified in SYSIN must contain at least the same
pool numbers, but you modified it and the specified
198
Data Restore Guide
number in message has been omitted.
XTS9-219
Mount dbname archived on (date - time )
User Response: The specified number in message
Explanation: You are processing a
must be included in the pool list.
RELOAD/RESTORE function from an INCREMENTAL
backup, and are being prompted to mount the
XTS9-210
Pool number xxx is not recoverable
associated full backup. You must use a FULLARC
FILEDEF or TLBL or DLBL to specify the file.
Explanation: The storpool number specified is not
recoverable. SPLR can not process it.
System Action: Mount the required file.
User Response: Remove this storpool from pool list.
XTS9-220
Storage pool level recovery not allowed
with INCREMENTAL BACKUP
XTS9-211
Beginning update of directory
Explanation: NEED WORDS HERE!!!
Explanation: SPLR has verified that all storpool of
pool list can be processed and start the update of
directory. Before this message is issued user can cancel
XTS9-225
Version DRF 6.1.0 required for
processing and restart SQL server with STARTUP=″W″.
INCREMENTAL BACKUP
After you must let SPLR completing the process and
Explanation: Incremental backup can only be run
restart SQL server with STARTUP=’u’
against Version 6 Release 1 of DB2 Server for VSE &
VM.
XTS9-213
Invalid value xxx for pool number xxx
System Action: The database must be migrated to
Explanation: The specified value is invalid as a pool
Version 6 Release 1 before incremental backup can be
number only defined pool numbers can be specified.
used.
User Response: Correct the pool list to process
XTS9-226
This file is a INCREM BACKUP
XTS9-214
Full restore is in progress
Explanation: The DESCRIBE function displays this
message to specify the type of the input file. In this
Explanation: If a Full restore was completed
case, the file is an INCREMENTAL backup file.
successfully, you must start DB2 Server for VSE & VM
with STARTUP=U before doing something else. If a
Full restore was not completed succesfully, you must
XTS9-228
The correlated full backup was archived
run Full restore completely.
on ( timestamp )
Explanation: For the DESCRIBE command, this
XTS9-215
Pool recovery is not allowed
message shows the timestamp of the associated full
backup for this incremental backup file.
Explanation: Pool recovery is not allowed after an
uncompleted Full restore. This message is preceded by
For the RELOAD and RESTORE commands, this
XTS9-214
message is a prompt to load the associated full backup
file. required.
XTS9-216
Feature not installed
XTS9-229
The file is a DB2
$1 archive
:
Explanation: The file being processed is a
REGULAR|FULL archive. When processing the
XTS9-217
Specify FULL or INCREMENTAL on
DESCRIBE or TRANSLATE function, this message
BACKUP card
specifies whether the input file is a REGULAR or FULL
Explanation: You need to specify either FULL or
archive.
INCREMENTAL as the type of input file.
XTS9-230
WRKSIZE= $1 has been used at backup
XTS9-218
A full backup has never been executed.
time
Explanation: You try to execute an Incremental
Explanation: To reload tables or restore a database
Backup, but you have never executed a FULL backup.
from an incremental backup, the WRKSIZE parameter
Incremental Backup is associated with a Full Backup.
may be required if the default capacity is exhausted.
System Action: You must take a full backup before
The WRKSIZE parameter to specify is equivalent to the
trying to take an incremental backup.
value used at backup time.
This message displays this value.
Appendix A. Messages and Codes
199
|
XTS9-233
Recovery will be stopped at this point.
XTS9-311
Base xxx specified but archive for base
xxx was found
|
Explanation: During RELOAD with RECOVERY=YES
|
a break occured in the log sequence in the history area.
Explanation: The DBNAME parameter does not match
|
The operator is asked to confirm if the table should be
the database name recorded on the archive or unload
|
reloaded and the log files applied until this point.
file.
|
This message is prompted before reload processing.
System Action: Processing ends.
|
User Response:
0 will cancel the process, 1 will
User Response: Modify the DBNAME parameter to
|
continue it.
match with the mounted tape or mount another tape.
|
XTS9-234
Further log records will not be
XTS9-313
DB2 for VSE and VM version xxx
|
processed
processed
|
Explanation: This message is displayed after reload
Explanation: This message displays DB2 version.
|
processing during log analysis.
XTS9-314
COMMIT WORK successful for reload
|
XTS9-235
Processing inactive log
of data, creating required objects
|
Explanation: In some cases, during reload processing
Explanation: After the table has been reloaded with
|
with RECOVERY=YES the INACTIVE log will be
FUNCT=REPLACE, a COMMIT WORK is issued and
|
processed before the ACTIVE log.
this message is displayed before the environment is
created.
|
XTS9-236
Inactive log
XTS9-315
ALL SQL statements loaded into table
|
Explanation: At the beginning of reload processing
DATARFTR.CMD
|
with RECOVERY=YES all log files required are
|
displayed. In some cases inactive logs will be needed.
Explanation: All commands required to recreate the
environment are loaded into the DATARFTR.CMD
table.
XTS9-304
Restore from user archive invoked
System Action: Processing ends.
:
User Response: If an SQLERROR occurs while
recreating the environment, refer to Chapter 11,
XTS9-305
Current database will be destroyed
“Restoring Logical Elements” on page 125 to continue.
Explanation: Before restoring an archive, the operator
is asked to confirm that the current database will be
XTS9-401
Enter 0(STOP) or 1(CONTINUE)
destroyed.
Explanation: During the RELOAD process with log
recovery, after each log archive is asked to be mounted
XTS9-307
Start the database manager with
this message is displayed.
parameter ″STARTUP=U″
System Action: Processing is waiting for operator
Explanation: After restoring from a database archive,
answer.
the database manager must be informed that an archive
was restored. This is accomplished by specifying the
User Response:
0 will stop the process, 1 will continue
STARTUP=U parameter.
it.
XTS9-308
Format DBEXTENT invoked (xxx)
XTS9-402
Enter 0 (NO) or 1 (YES)
Explanation: Format for DBEXTENT (xxx) invoked.
Explanation: This message is displayed to prompt for
a response to a previous message.
XTS9-309
Processing DB2 for VSE and VM
System Action: The system is waiting for a response.
version xxx
Operator Response: Reply 0 for NO or 1 for YES.
Explanation: This message displays DB2 Server for
VSE & VM version.
200
Data Restore Guide
XTS9-403
Reply is xxx
Explanation: This message displays the operator’s
response.
XTS9-405
Enter 0 (CANCEL) or 1(RETRY)
Explanation: A tape drive was not ready to allow
RELOAD to begin. Reply 1 to retry the RELOAD after
the tape drive is ready or reply 0 to cancel.
System Action: The system is waiting for a response.
Operator Response: Reply 0 to cancel or 1 to retry.
XTS9-406
Enter 0 (CANCEL) or 1 (CONTINUE)
Explanation: This message is displayed before the
RESTORE function to confirm the destruction of the
current database.
System Action: The system is waiting for a response.
Operator Response: Reply 0 to cancel or 1 to
continue.
XTS9-407
Enter 0 (CANCEL), 1 (CONTINUE) or
111(SKIPFILE)
Explanation: This message is displayed during the
RELOAD process, for each log archive tape, if
RECOVERY=YES parameter was specified.
System Action: The system is waiting for a response.
Operator Response: Reply 0 to cancel, reply 1 to
continue or reply 111 to stop.
XTS9-408
Enter 0(CANCEL), 1(CONTINUE),
11(CHANGE) or 111(SKIPFILE)
Explanation: The log archive to be processed was
created on disk. The filename and filetype are
displayed
System Action: The system is waiting for a response.
User Response: If the log archive file was moved to
tape, the user can change the device support by
replying 11. After replying 11, the operator will be
asked to mount the log archive tape.
XTS9-601
DATE: xxx TIME: xxx
Explanation: Date and time of process is displayed.
Appendix A. Messages and Codes
201
202
Data Restore Guide
Appendix B. Command Examples
This chapter shows some procedures that have been performed on our test system
to illustrate the usage of the Data Restore functions.
Using the BACKUP Function
In VSE
* $$ JOB JNM=DRFBACKP,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB DRFBCKUP
BACKUP DATABASE WITH
DRF
TO
TAPE
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC PROC=SQLVSE02
// TLBL
ARCHIV
// ASSGN
SYS006,180
// MTC
REW,SYS006
// EXEC XTS91001,SIZE=AUTO
OPTIONS DEVICE=TAPE
CONTROL DBNAME=SQLVSE02
BACKUP
/*
/&
* $$ EOJ
Figure 161. JCL File for Data Restore BACKUP to Tape
In VM
/*---------------------------------*/
/*-- filedef for output to tape --------*/
’FILEDEF ARCHIV TAP1 SL
(RECFM VB
BLOCK 32760’
/*-- filedef for dual output to disk ---*/
’FILEDEF ARCHIV2
DISK DRF
BACKUP A (RECFM VB
BLOCK 32760’
’FILEDEF SYSIN
DISK BACKUP SYSIN
A’
’FILEDEF SYSPRINT DISK BACKUP SYSPRINT A’
’XTS91001’
Exit rc
Figure 162. EXEC File for Data Restore BACKUP with Dual Backup to Tape and Disk
* backup1 to tape, 2 to disk
OPTIONS DEVICE=TAPE DEVICE2=DASD CONFIRM=NO
CONTROL BASE=S35VMDB1
BACKUP
Figure 163. SYSIN File for Data Restore BACKUP with Dual Backup to Tape and Disk
Using the DESCRIBE Function
The following are some examples using the DESCRIBE function.
203
CONTROL BASE=S35VMDB1
DESCRIBE
Figure 164. SYSIN File for Data Restore DESCRIBE (DESCRIBE SYSIN)
Figure 165 shows a sample EXEC for the DESCRIBE function. The FILEDEF
ARCHIV statement points to the file to be listed, and in this case it is an unloaded
dbspace on disk.
/**/
’FILEDEF ARCHIV DISK DRFSAMPL DATA A (RECFM VB BLOCK 32760’
’FILEDEF SYSIN
DISK DESCRIBE SYSIN A’
’FILEDEF SYSPRINT DISK DESCRIBE SYSPRINT A’
’XTS91001’
Exit rc
Figure 165. EXEC File for Data Restore DESCRIBE (DESCRIBE EXEC)
Figure 166 shows a SYSPRINT report from a DESCRIBE function of an unloaded
dbspace. Message XTS9-174 shows that the dbspace was unloaded by Data Restore
on June 10, 1996 at 16:49:26. The other information lists the tables in the dbspace
and indicates that the DESCRIBE function was successfully completed.
XTS9-143 CONTROL BASE=S35VMDB1
XTS9-143 DESCRIBE
XTS9-143 /*
XTS9-196 Do you want to continue the DESCRIBE process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-174 Processing S35VMDB1 unloaded on (10/06/96-16:49:26)
XTS9-013 Table SQLDBA
.ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.DEPARTMENT
may be reloaded
XTS9-013 Table SQLDBA
.DRF_ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.DRF_SQL_ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.EMP_ACT
may be reloaded
XTS9-013 Table SQLDBA
.EMPLOYEE
may be reloaded
XTS9-013 Table SQLDBA
.PROJ_ACT
may be reloaded
XTS9-013 Table SQLDBA
.PROJECT
may be reloaded
XTS9-007 Processing successfully completed
Figure 166. SYSPRINT File of Data Restore DESCRIBE (DESCRIBE SYSPRINT)
Figure 178 on page 214 shows the exec used for this function in VM, and Figure 167
on page 205 shows a VSE output sample of DESCRIBE.
204
Data Restore Guide
// JOB DRFDESCR
DESCRIBE ARCHIVE TAPE
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// TLBL
ARCHIV
** input file **
// ASSGN
SYS006,181
// MTC
REW,SYS006
// EXEC XTS91001,SIZE=AUTO
CONTROL DBNAME=SQLVSE02
DESCRIBE
XTS9-143 CONTROL DBNAME=SQLVSE02
XTS9-143 DESCRIBE
XTS9-143 /*
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-192 Processing SQL/VSE archived by database manager on (05/21/96-07-47-03)
XTS9-013 Table SQLDBA
.ACTIVITY
may be reloaded
XTS9-013 Table DATARFTR.CMD
may be reloaded
XTS9-013 Table SQLDBA
.CUSTOMER
may be reloaded
... more entries in between
XTS9-013 Table SQLDBA
.WAREHOUSE
may be reloaded
XTS9-007 Processing successfully completed
Figure 167. SYSPRINT File of Data Restore DESCRIBE
CONTROL DATE=05/21/96 TIME=07-47-03
BASE=S35VMDB1
RESTORE
Figure 168. CONTROL Statement Defining an Archive for Data Restore RESTORE
If the input file is a FULL BACKUP file, message XTS9-226 will indicate that it is a
FULL BACKUP file. For example:
XTS9-143 CONTROL BASE=SQLDBA
XTS9-143 DESCRIBE
XTS9-143 /*
XTS9-196 Do you want to continue the DESCRIBE process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 DATA RESTORE FEATURE VERSION 7.1.0
XTS9-136 Processing SQLDBA archived on (02/10/97-09:03:11)
---> XTS9-226 This file is a FULL BACKUP
XTS9-013 Table SQLDBA
.ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.DEPARTMENT
may be reloaded
XTS9-013 Table SQLDBA
.EMP_ACT
may be reloaded
XTS9-013 Table SQLDBA
.EMPLOYEE
may be reloaded
XTS9-013 Table SQLDBA
.PROJ_ACT
may be reloaded
XTS9-013 Table SQLDBA
.PROJECT
may be reloaded
XTS9-007 Processing successfully completed
If the input file is an INCREMENTAL backup file, message XTS9-226 indicates that
the file is an INCREMENTAL backup and backup file. For example:
Appendix B. Command Examples
205
XTS9-143 CONTROL BASE=SQLDBA
XTS9-143 DESCRIBE
XTS9-143 /*
XTS9-196 Do you want to continue the DESCRIBE process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 DATA RESTORE FEATURE VERSION 7.1.0
XTS9-136 Processing SQLDBA archived on (02/10/97-09:03:11)
---> XTS9-226 This file is an INCREMENTAL BACKUP
(01/10/97-08:50:02)
XTS9-013 Table SQLDBA
.ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.DEPARTMENT
may be reloaded
XTS9-013 Table SQLDBA
.EMP_ACT
may be reloaded
XTS9-013 Table SQLDBA
.EMPLOYEE
may be reloaded
XTS9-013 Table SQLDBA
.PROJ_ACT
may be reloaded
XTS9-013 Table SQLDBA
.PROJECT
may be reloaded
XTS9-007 Processing successfully completed
The following is an example of a function report for the DESCRIBE function on a
DB2 FULL archive.
XTS9-143 CONTROL BASE=SQLDBA
XTS9-143 DESCRIBE
XTS9-143 /*
XTS9-196 Do you want to continue the DESCRIBE process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 DATA RESTORE FEATURE VERSION 7.1.0
XTS9-136 Processing SQLDBA archived on (02/10/97-09:03:11)
---> XTS9-229 The file is a DB2 FULL archive
XTS9-013 Table SQLDBA
.ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.DEPARTMENT
may be reloaded
XTS9-007 Processing successfully completed
The following is an example of a function report for the DESCRIBE function on a
DB2 regular archive.
XTS9-143 CONTROL BASE=SQLDBA
XTS9-143 DESCRIBE
XTS9-143 /*
XTS9-196 Do you want to continue the DESCRIBE process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 DATA RESTORE FEATURE VERSION 7.1.0
XTS9-136 Processing SQLDBA archived on (02/10/97-09:43:25)
---> XTS9-229 The file is a DB2 regular archive
XTS9-013 Table SQLDBA
.ACTIVITY
may be reloaded
XTS9-013 Table SQLDBA
.DEPARTMENT
may be reloaded
XTS9-007 Processing successfully completed
Using the FORMAT Function
Figure 169 on page 207 shows a sample of the JCL to format the extent, known as
DDSK10 by DB2.
206
Data Restore Guide
* $$ JOB JNM=DRFORMAT,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB DRFORMAT
format data extent
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC PROC=SQLVSE02
// EXEC XTS91001,SIZE=AUTO
OPTIONS RECOVERY=NO,DEVICE=DASD
CONTROL DBNAME=SQLVSE02
FORMAT DDSK=10
/*
/&
* $$ EOJ
Figure 169. JCL File for Data Restore FORMAT Dbextent
Using the RELOAD Function
Archive
The file produced by the BACKUP function, or a DB2
Server for VSE & VM
database archive.
SYSIN
The file which specifies the tables to restore.
Log n
The log archive files and the current log.
Reload
The function to process.
LMBRWRK
The work file which contains pages for tables containing LONG columns.
LMBRLG1, LMBRLG2, and LMBRLG3
The files used to extract all of the changes referenced in the log files.
DB2 Server for VSE & VM database
The database directory and all dbextents.
Appendix B. Command Examples
207
XTS9-143 OPTIONS RECOVERY=YES
XTS9-143 CONTROL DBNAME=dbname
XTS9-143 RELOAD CREATOR=SQLDBA,TNAME=SUPPLIERS,FUNCT=NEW,NEWTNAME=SUPPLIERS2
XTS9-143
DBSPACE=SAMPLE
XTS9-143 /*
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-136 Processing BASE2
archived on (31/10/95-10:59:15)
XTS9-182 Following files are needed for recovery
XTS9-195 UARCHIVE
CURRENTLY MOUNTED
XTS9-180 LARCHIV
at 1995-243-11-01-05-015505
XTS9-179 CURRENT LOG
XTS9-406 Enter O(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-102
1000 rows loaded procedure completed
XTS9-128
1000 rows loaded into (SQLDBA.SUPPLIERS2)
XTX9-101
1 tables successfully processed
XTS9-314 Commit work successful for reload of data, creating required objects
CONNECT SQLDBA
;
COMMIT WORK
;
XTS9-183 Please mount LARCHIV at 1995-243-11-01-05-015504
XTS9-401 Enter 0(stop) OR 1(continue) OR 111(skipfile)
XTS9-403 Reply is 1
XTS9-184 Processing current log
XTS9-401 Enter 0(stop) OR 1(continue) OR 111(skipfile)
XTS9-403 Reply is 1
XTS9-007 Processing successfully completed
Figure 170. Example Console for a RELOAD with the RECOVERY=YES Parameter
Example of a Report from RELOAD
The number of reloaded rows is displayed at the end of each RELOAD function.
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-136 Processing BASE1
archived on (11/10/94-15:19:11)
XTS9-128
124 Rows loaded into (SQLDBA.SUPPLIERS)
XTS9-128
25 Rows loaded into (SQLDBA.EMPLOYEE)
XTS9-101
2 Tables successfully processed
XTS9-314 Commit work successful for reload of data, creating required objects
CONNECT SQLDBA;
COMMIT WORK;
Figure 171. Sample Report from the RELOAD Function
If the COMMITCOUNT parameter is specified on the OPTIONS statement, a
message is displayed each time a COMMIT WORK is performed. (For more
information, see “OPTIONS and CONTROL Statements” on page 167.)
208
Data Restore Guide
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-136 Processing BASE1
archived on (11/10/94-15:19:11)
XTS9-127
50 Rows loaded procedure continuing
XTS9-127
100 Rows loaded procedure continuing
XTS9-128
124 Rows loaded into (SQLDBA.SUPPLIERS)
XTX9-101
1 tables successfully processed
XTS9-314 Commit work successful for reload of data, creating required objects
CONNECT SQLDBA;
COMMIT WORK;
Figure 172. Example Report from the RELOAD Function with the COMMITCOUNT
Parameter
In VM, if a log archive taken on DASD is subsequently moved to tape, Data
Restore will still try to process the log archive from DASD. By replying 11 to
message XTS9-408, you can instruct Data Restore to process the log archive from
tape.
Appendix B. Command Examples
209
XTS9-143 OPTIONS RECOVERY=YES
XTS9-143 CONTROL VERIFY=NO DBNAME=dbname READPW=RR
XTS9-143 RELOAD CREATOR=SQLDBA,TNAME=CUSTOMERS,FUNCT=REPLACE
XTS9-143
DBSPACE=SAMPLE
XTS9-143 /*
XTS9-196 Do you want to continue the RELOAD process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-136 Processing BASE620 archived on (29/09/95-13:11:37)
XTS9-182 Following files are needed for recovery
XTS9-195 UARCHIVE
currently mounted
XTS9-180 LARCHIV
at 1995-272-13-13-24-714512
XTS9-180 LARCHIV
at 1995-272-13-39-57-753488
XTS9-179 Current log
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-128
100 rows loaded into (SQLDBA.CUSTOMERS)
XTS9-128
1481 rows loaded into (DATARFTR.SYSCOLUMNS)
XTS9-128
317 rows loaded into (DATARFTR.SYSCATALOG)
XTS9-128
661 rows loaded into (DATARFTR.SYSTABAUTH)
XTS9-128
113 rows loaded into (DATARFTR.SYSINDEXES)
XTS9-128
16 rows loaded into (DATARFTR.SYSVIEWS)
XTS9-128
22 rows loaded into (DATARFTR.SYSKEYCOLS)
XTS9-128
18 rows loaded into (DATARFTR.SYSKEYS)
XTS9-128
544 rows loaded into (DATARFTR.SYSUSAGE)
XTS9-128
28 rows loaded into (DATARFTR.SYSCOLAUTH)
XTS9-101
10 tables successfully processed
XTS9-314 COMMIT WORK successful for reload of data, creating required
objects.
CONNECT SQLDBA
;
COMMIT WORK ;
(1)
--->
XTS9-200 Processing LARCHIV at 1995-272-13-13-24-714512
(2)
--->
XTS9-201 Medium is disk BASE35
09299502 *
(3)
--->
XTS9-408 Enter 0(CANCEL),1(CONTINUE),11(CHANGE) or 111(SKIPFILE)
(4)
--->
XTS9-403 Reply is 11
(5)
--->
XTS9-183 Please mount LARCHIV at 1995-272-13-13-24-714512
XTS9-407 Enter 0(CANCEL),1(CONTINUE) or 111(SKIPFILE)
(6)
--->
XTS9-403 Reply is 1
(7)
--->
XTS9-183 Please mount LARCHIV at 1995-272-13-39-57-753488
XTS9-407 Enter 0(CANCEL),1(CONTINUE) or 111(SKIPFILE)
XTS9-403 Reply is 1
(8)
--->
XTS9-184 Processing current log
XTS9-407 Enter 0(CANCEL),1(CONTINUE) or 111(SKIPFILE)
(9)
--->
XTS9-403 Reply is 111
XTS9-007 Processing successfully completed
Figure 173. Example Reload with the RECOVERY=YES Parameter Changing Log Archive
Support
Statement 1
Displays the timestamp of the first log archive.
Statement 2
Displays the name and medium (in this case, disk) of the log archive.
Statement 3
Prompts the operator to change the medium or continue with the process.
Statement 4
Displays the operator’s response to the above prompt (in this case, since
the operator has chosen to change the medium, the new medium is
assumed to be tape).
210
Data Restore Guide
Statement 5
Requests that the log archive (on tape) be mounted.
Statement 6
Displays the operator’s response (continue).
Statement 7
Requests the next log archive.
Statement 8
Indicates that the current log is being processed.
Statement 9
Displays the operator’s response (not to process the current log).
RELOAD Examples using VM
SELECT * FROM SQLDBA.PROJECT
PROJNO PROJNAME
DEPTNO RESPEMP PRSTAFF
------ --------------------- ------ ------- -------
AD3100 ADMIN SERVICES
D01
000010
6.50
AD3110 GENERAL ADMIN SYSTEMS D21
000070
6.00
AD3111 PAYROLL PROGRAMMING D21
000230
2.00
AD3112 PERSONNEL PROGRAMMING D21
000250
1.00
AD3113 ACCOUNT PROGRAMMING D21
000270
2.00
IF1000 QUERY SERVICES
C01
000030
2.00
IF2000 USER EDUCATION
C01
000030
1.00
MA2100 WELD LINE AUTOMATION
D01
000010
12.00
MA2110 W L PROGRAMMING
D11
000060
9.00
MA2111 W L PROGRAM DESIGN
D11
000220
2.00
MA2112 W L ROBOT DESIGN
D11
000150
3.00
MA2113 W L PROD CONT PROGS
D11
000160
3.00
OP1000 OPERATION SUPPORT
E01
000050
6.00
OP1010 OPERATION
E11
000090
5.00
OP2000 GEN SYSTEMS SERVICES
E01
000050
5.00
OP2010 SYSTEMS SUPPORT
E21
000100
4.00
OP2011 SCP SYSTEMS SUPPORT
E21
000320
1.00
OP2012 APPLICATIONS SUPPORT
E21
000330
1.00
OP2013 DB/DC SUPPORT
E21
000340
1.00
PL2100 WELD LINE PLANNING
B01
000020
1.00
Figure 174. SQLDBA.PROJECT before Updates
In Figure 175 on page 212 and Figure 176 on page 213 the Data Restore archive is
read from tape, as well as the log archives.
Appendix B. Command Examples
211
/*------------------------------------------------------------------*/
/*- Reload procedure with forward Recovery -------------------------*/
/*- INPUT Data Restore Feature BACKUP - Log Archive - Current LOG---*/
/*------------------------------------------------------------------*/
Address Command
’FILEDEF ARCHIV TAP2 SL 1 (RECFM VB BLOCK 32760’
’FILEDEF LARCHIV TAP1 SL 1 (RECFM FB BLOCK 28672 LRECL 4096’
’FILEDEF LMBRWRK DISK LMBRWRK DATA A (RECFM FB BLOCK 28672 LRECL 4096’
’FILEDEF LMBRLG1 DISK LMBRLG1 DATA A (RECFM VB BLOCK 32760’
’FILEDEF LMBRLG2 DISK LMBRLG2 DATA A (RECFM VB BLOCK 32760’
’FILEDEF LMBRLG3 DISK LMBRLG3 DATA A (RECFM VB BLOCK 32760’
’FILEDEF SYSIN DISK RELOAD SYSIN A’
’FILEDEF SYSPRINT DISK RELOAD SYSPRINT A’
’XTS91001’
Exit rc
Figure 175. EXEC File for Data Restore RELOAD from Data Restore Archive with Forward
Recovery
212
Data Restore Guide
XTS9-143 OPTIONS RECOVERY=YES
XTS9-143 CONTROL BASE=S35VMDB1
XTS9-143 RELOAD CREATOR=SQLDBA,TNAME=PROJECT
XTS9-143
FUNCT=REPLACE
XTS9-143 /*
XTS9-196 Do you want to continue the RELOAD
process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-136 Processing S35VMDB1 archived on (05/30/96-15:18:48)
XTS9-182 Following files are needed for recovery
XTS9-195 UARCHIVE
currently mounted
XTS9-179 Current log
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-102
1351 rows loaded, procedure completed
XTS9-128
20 rows loaded into (SQLDBA.PROJECT)
.... more lines
XTS9-128
24 rows loaded into (DATARFTR.SYSCOLAUTH)
XTS9-101
10 tables successfully processed
XTS9-314 COMMIT WORK successful for reload of data,
creating required objects
ALTER TABLE "SQLDBA"."PROJECT" ADD PRIMARY KEY ("PROJNO" ASC
) PCTFREE=10;
COMMIT WORK ;
CREATE INDEX "SQLDBA"."DEPTNOI" ON "SQLDBA"."PROJECT"
("DEPTNO" ASC ) PCTFREE=10;
COMMIT WORK ;
CREATE INDEX "SQLDBA"."RESPEMPI" ON "SQLDBA"."PROJECT"
("RESPEMP" ASC ) PCTFREE=10;
COMMIT WORK ;
ALTER TABLE "SQLDBA"."PROJ_ACT" ADD FOREIGN KEY "R_PROJ2"
("PROJNO") REFERENCES "SQLDBA"."PROJECT" ON DELETE RESTRICT;
COMMIT WORK ;
ALTER TABLE "SQLDBA"."PROJECT" ADD FOREIGN KEY "R_DEPT2"
("DEPTNO") REFERENCES "SQLDBA"."DEPARTMENT" ON DELETE RESTRICT;
COMMIT WORK ;
ALTER TABLE "SQLDBA"."PROJECT" ADD FOREIGN KEY "R_EMPLY2"
("RESPEMP") REFERENCES "SQLDBA"."EMPLOYEE" ON DELETE SET NULL;
COMMIT WORK ;
CONNECT SQLDBA
;
GRANT SELECT ON "SQLDBA"."PROJECT" TO "PUBLIC";
COMMIT WORK ;
CONNECT SQLDBA
;
COMMIT WORK ;
XTS9-184 Processing current log
XTS9-407 Enter 0(CANCEL),1(CONTINUE) or 111(SKIPFILE)
XTS9-403 Reply is 1
XTS9-007 Processing successfully completed
Figure 176. SYSPRINT File of Data Restore RELOAD from Data Restore Archive with
Forward Recovery
In Figure 177 on page 214, ARCHIV is used as a work file while reading the DB2
archive (ARIARCH) from tape. The parameter ARCHTYPE=SQLDS is given in
Figure 180 on page 214.
Appendix B. Command Examples
213
/*------------------------------------------------------------------*/
/*- Reload procedure without forward recovery ----------------------*/
/*- Input=database manager archive----------------------------------*/
/*------------------------------------------------------------------*/
’FILEDEF ARCHIV DISK ARCHIV DATA A ( RECFM VB BLOCK 32760’
’FILEDEF ARIARCH TAP1 SL
(RECFM FB BLOCK 28672 LRECL 4096’
’FILEDEF LMBRLG1 DISK LMBRLG1 DATA A (RECFM VB BLOCK 32760’
’FILEDEF LMBRLG2 DISK LMBRLG2 DATA A (RECFM VB BLOCK 32760’
’FILEDEF LMBRLG3 DISK LMBRLG3 DATA A (RECFM VB BLOCK 32760’
’FILEDEF LMBRWRK DISK LMBRWRK DATA A (RECFM FB BLOCK 28672 LRECL 4096’
’FILEDEF SYS0001 DISK SYS0001 DATA A (RECFM F BLOCK 4096’
’FILEDEF HEADER DISK LMBRWRK DATA A (RECFM F BLOCK 4096’
’FILEDEF DIRWORK DISK LMBRWRK DATA A (RECFM F BLOCK 4096’
’FILEDEF SYSIN
DISK DRFRELA SYSIN A’
’FILEDEF SYSPRINT DISK DRFRELA SYSPRINT A’
’XTS91001’
Exit rc
Figure 177. EXEC File for Data Restore RELOAD from DB2 Archive without Forward
Recovery
/**/
’FILEDEF ARCHIV TAP1 SL 1 (RECFM VB BLOCK 32760’
’FILEDEF SYSIN DISK DESCRIBE SYSIN A’
’FILEDEF SYSPRINT DISK DESCRIBE SYSPRINT A’
’XTS91001’
Exit rc
Figure 178. EXEC File for Data Restore DESCRIBE
/output
/**/
’FILEDEF LMBRLG1 DISK LMBRLG1 DATA A (RECFM VB BLOCK
32760’
’FILEDEF LMBRLG2 DISK LMBRLG2 DATA A (RECFM VB BLOCK
32760’
’FILEDEF LMBRLG3 DISK LMBRLG3 DATA A (RECFM VB BLOCK
32760’
’FILEDEF LMBRWRK DISK LMBRWRK DATA T (RECFM FB BLOCK
28672 LRECL
4096’
’FILEDEF SYSIN DISK LISTLOG SYSIN A’
’FILEDEF SYSPRINT DISK LISTLOG SYSPRINT A’
’XTS91001’
Exit rc
Figure 179. EXEC File for Data Restore LISTLOG
OPTIONS RECOVERY=NO CONFIRM=NO ARCHTYPE=SQLDS
CONTROL BASE=S35VMDB1
RELOAD CREATOR=SQLDBA,TNAME=ACTIVITY,FUNCT=REPLACE
Figure 180. SYSIN for Data Restore RELOAD from DB2 Archive without Forward Recovery
214
Data Restore Guide
SELECT * FROM SQLDBA.PROJECT
PROJNO PROJNAME
DEPTNO RESPEMP PRSTAFF
------ --------------------- ------ ------- -------
IF2000 USER EDUCATION
C01
000030
1.00
MA2100 WELD LINE AUTOMATION D01
000010
12.00
OP1010 OPERATION UPD2
E11
000090
5.00
OP2010 SYSTEMS SUPPORT UPD1
E21
000100
4.00
Figure 181. Changed Data in Table SQLDBA.PROJECT after Data Restore APPLYLOG
To reload from an INCREMENTAL backup tape, see the following example. The
JCL or EXEC used for the RELOAD command must be a full backup file. The
ARCHIV label or filedef should be used for the incremental backup file.
The SYSIN file used for the RELOAD command must be modified to add the
WRKSIZE parameter on the OPTIONS statement. The value specified must be the
same as the one specified at incremental backup time.
/**/
’TAPE REW’
’FILEDEF ARCHIV TAP1 SL 1 (RECFM VB BLOCK 32760’
’FILEDEF LMBRWRK DISK WRK DATA A (RECFM FB BLOCK 28672
LRECL 4096’
’FILEDEF SYSPRINT DISK RESTORE SYSPRINT A’
---> ’FILEDEF FULLARC TAP1 SL 1 (RECFM VB BLOCK 32760’
’FILEDEF SYSIN DISK RELOAD SYSIN A’
’XTS91001’
The SYSIN file should contain:
OPTIONS DEVICE=TAPE DEVICE2=TAPE WRKSIZE=4096
CONTROL DBNAME=SQLDS
RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=PURGE
/*
The output from RELOAD will be:
XTS9-143 OPTIONS DEVICE=TAPE DEVICE2=TAPE WRKSIZE=4096
XTS9-143 CONTROL DBNAME=SQLDS
XTS9-143 RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=PURGE
XTS9-143 /*
XTS9-100 Data Restore feature VERSION 7.1.0
XTS9-136 Processing SQLDS archived on (11/25/97-15:16:53)
---> XTS9-219 Mount BASE2 archived on (09/25/97-14:52:59)
---> XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
---> XTS9-403 Reply is 1
XTS9-102
225 rows loaded, procedure completed
XTS9-128
225 rows loaded into (SQLDBA.CUSTOMER)
XTS9-101
1 tables successfully processed
Appendix B. Command Examples
215
RELOAD Examples using VSE
Figure 182 shows the JCL used in some of the following examples. It defines the
RELOAD work files for forward recovery.
* $$ JOB JNM=XTS9DLBL,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB XTS9DLBL CATALOG DLBL for data restore feature
// EXEC
LIBR,PARM=’MSHP’
ACCESS SUBLIB=PRD2.RCVvrm
CATALOG XTS9DLBL.PROC
EOD=&& DATA=YES REPLACE=YES
// PROC CAT=’VSESPUC’
// DLBL IJSYSUC,’VSESP.USER.CATALOG’,,VSAM
* **********************************************************
* XTS9DLBL: DATA RESTORE FEATURE WORKFILES
* **********************************************************
// DLBL LMBRWRK,,,VSAM,CAT=VSESPUC
// DLBL LMBRLG1,,,VSAM,CAT=VSESPUC
// DLBL LMBRLG2,,,VSAM,CAT=VSESPUC
// DLBL LMBRLG3,,,VSAM,CAT=VSESPUC
// DLBL SYS0001,,0,VSAM,RECSIZE=4096,RECORDS=(100,100),CAT=VSESPUC
// DLBL HEADER,,0,VSAM,RECSIZE=4096,RECORDS=(100,100),CAT=VSESPUC
// DLBL DIRWORK,,0,VSAM,CAT=VSESPUC
&&
/*
/&
* $$ EOJ
Figure 182. JCL File DLBL for Data Restore Work Files (XTS9DLBL.PROC)
In Figure 183, the DLBL JCL from Figure 182 is addressed. The Data Restore
archive is read from tape. Therefore, SYS006 is assigned and
OPTIONS DEVICE=TAPE.
* $$ JOB JNM=DRFRLOAD,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB DRFRLOAD
RELOAD TABLE WITH FORWARD RECOVERY
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC PROC=SQLVSE02
DLBL for database extents
// EXEC PROC=XTS9DLBL
DLBL for drf files
// TLBL
ARCHIV
// ASSGN
SYS006,180
input tape from BACKUP
// MTC
REW,SYS006
// EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(SQLVSE02)’
OPTIONS RECOVERY=YES DEVICE=TAPE
CONTROL DBNAME=SQLVSE02
RELOAD CREATOR=SQLDBA TNAME=PROJECT FUNCT=REPLACE
/*
/&
* $$ EOJ
Figure 183. JCL File for Data Restore RELOAD from Data Restore Archive with Forward
Recovery
Figure 184 on page 217 shows an example without using the DLBL from above.
SYS007 is assigned because a DB2 archive is read. ARCHIV is used as a work file
on disk as shown in the DLBL ARCHIV and the OPTIONS DEVICE=DASD
statements.
216
Data Restore Guide
* $$ JOB JNM=DRFRLOAD,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB DRFRLOAD
RELOAD TABLE WITH FORWARD RECOVERY
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC PROC=SQLVSE02
// TLBL
ARIARCH
// ASSGN
SYS007,181
INPUT SQL ARCHIVE
// MTC
REW,SYS007
// DLBL LMBRWRK,,,VSAM,CAT=VSESPUC
// DLBL LMBRLG1,,,VSAM,CAT=VSESPUC
// DLBL LMBRLG2,,,VSAM,CAT=VSESPUC
// DLBL LMBRLG3,,,VSAM,CAT=VSESPUC
// DLBL SYS0001,,,VSAM,RECSIZE=4096,RECORDS=(100,100),CAT=VSESPUC
// DLBL HEADER,,,VSAM,RECSIZE=4096,RECORDS=(100,100),CAT=VSESPUC
// DLBL DIRWORK,,,VSAM,CAT=VSESPUC
// DLBL ARCHIV,,,VSAM,RECORDS=(100,100),RECSIZE=4096,CAT=VSESPUC
// EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(SQLVSE02)’
OPTIONS RECOVERY=YES,ARCHTYPE=SQLDS,DEVICE=DASD
CONTROL DBNAME=SQLVSE02
RELOAD CREATOR=SQLDBA TNAME=PROJECT FUNCT=REPLACE
/*
/&
* $$ EOJ
Figure 184. JCL File for Data Restore RELOAD from DB2 Archive with Forward Recovery
In Figure 185 a DB2 archive is read using SYS007 as shown in Figure 184, but the
work file ARCHIV is defined on tape. Refer to the TLBL ARCHIV and
ASSGN SYS006 statements.
* $$ JOB JNM=SQLRLOAD,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB SQLRLOAD
RELOAD 2 TABLEs WITH FORWARD REC from sql archi
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC PROC=SQLVSE02
// EXEC PROC=XTS9DLBL
// TLBL
ARCHIV
// TLBL
ARIARCH
// TLBL
LARCHIV
// ASSGN
SYS006,180
// ASSGN
SYS007,181
// MTC
REW,SYS007
// EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(SQLVSE02)’
OPTIONS ARCHTYPE=SQLDS RECOVERY=YES
CONTROL DBNAME=SQLVSE02
RELOAD CREATOR=SQLDBA TNAME=PROJECT FUNCT=REPLACE
RELOAD CREATOR=SQLDBA TNAME=PROJ_ACT FUNCT=REPLACE
/*
/&
* $$ EOJ
Figure 185. JCL File for Data Restore RELOAD of 2 Tables from DB2 Archive with Forward
Recovery
The guest sharing example shows the general use of the PARM=’DBNAME()″
statement as opposed to CONTROL DBNAME=. PARM indicates the target
database, whereas the CONTROL statement defines the source of the archive, that
is, the database from which the archive was taken.
Appendix B. Command Examples
217
* $$ JOB JNM=DRFRLOAD,CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)
// JOB DRFRLOAD
RELOAD TABLE with guest sharing
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// TLBL
ARCHIV
* input tape *
// ASSGN
SYS006,181
// MTC
REW,SYS006
// SETPFIX
LIMIT=1M
// EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(S35VMDB1)’
OPTIONS RECOVERY=NO,DEVICE=TAPE
CONTROL DBNAME=SQLVSE02
RELOAD CREATOR=SQLDBA TNAME=ACTIVITY FUNCT=REPLACE
/*
/&
* $$ EOJ
Figure 186. JCL File for Data Restore RELOAD with Guest Sharing
To reload from an INCREMENTAL backup tape in, see the following example. The
JCL or EXEC used for the RELOAD command must be a full backup file. The
ARCHIV label or filedef should be used for the incremental backup file.
The SYSIN file used for the RELOAD command must be modified to add the
WRKSIZE parameter on the OPTIONS statement. The value specified must be the
same as the one specified at incremental backup time.
// JOB RELOAD
// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
// EXEC PROC=ARIS71DB
// DLBL LMBRWRK,,,VSAM
// TLBL ARCHIV,’ARCHIVE.SQL’,,,1
---> // TLBL FULLARC,’ARCHIVE.SQL’,,,,1
// ASSGN SYS006,180
// MTC REW,SYS006
// EXEC XTS91001,SIZE=AUTO
OPTIONS DEVICE=TAPE DEVICE2=TAPE WRKSIZE=4096
CONTROL DBNAME=SQLDS
RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=PURGE
/*
Using Control Center
RELOAD allows the user to reload and recreate tables from a Data Restore
BACKUP, translated database archive, or a Data Restore UNLOAD. Control Center
requires that a database archive first be translated before it is used as an input
source for RELOAD.
In our example the RECOVERY option is set to ’YES’. Then Data Restore will read
the active log to record all changes to this table executed since the BACKUP into
work files. This can later be examined with the LISTLOG function and re-executed
using the APPLYLOG function.
To run the Data Restore RELOAD the database must be active.
In this example we used a translated archive tape as input to the RELOAD
process.
218
Data Restore Guide
To start the RELOAD function, select R from the Date Restore Menu as shown in
Figure 187.
05.03.1997
Control Center Facility
13.55.16
*------------------------------- Data Restore Menu -------------------------*
| Option ===> R
CTRLID: ELDBMSRV |
|
Database ===> ELDB2B
NODE: BOEVMCT1 |
|
DRMACH: ELDB2DRF |
|
|
|
T TRANSLATE ARCHIVE
TRANSLATE archive into BACKUP format
|
|
U UNLOAD DBSPACES
UNLOAD one or more dbspaces
|
|
R RELOAD TABLES
RELOAD one or more tables
|
|
LL LISTLOG
LISTLOG selection panel
|
|
AL APPLYLOG
APPLYLOG selection panel
|
|
VJ VIEW JOB SCHEDULE
VIEW database job schedule
|
|
S VIEW DRMACH STATUS
VIEW Data Restore Machine status
|
|
SR RESET DRMACH STATUS
RESET Data Restore Machine status
|
|
D SHOWDBS
Generate report about all dbspaces
|
|
View Tapes Edit Tapes
View History
View Log
|
| BACKUP
BT
BM
BH
BL
|
| UNLOAD
UT
UM
UH
UL
|
| TRANSLATE
TT
TM
TH
TL
|
|
|
|
Enter OPTION, select DATABASE, press ENTER to process
|
|
|
*---------------------------------------------------------------SDRMAIN-----*
PF:
1 Help
3 End
Figure 187. Invoking Data Restore RELOAD Function
On the screen bellow, we specified Log Recovery=1 (Yes) and the input type is a
translated archive tape.
05.03.1997
Control Center Facility
14.02.19
*------------------ Data Restore Reload Table Utility
---------------------*
|
CTRLID: ELDBMSRV |
| Database ==> ELDB2B
NODE:
BOEVMCT1 |
|
DRMACH:
ELDB2DRF |
|
|
|
|
|
Log Recovery ==> 1
( 1 = ’YES’, 2 = ’NO’
|
|
Input Type
==> 2
( 1 = BACKUP, 2 = TRANSLATE, 3 = UNLOAD
|
|
Restart
==> 2
( 1 = ’YES’, 2 = ’NO’, Restart RELOAD
|
|
and use the same RELDCTL file
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*---------------------------------------------------------------DRRELD2------*
PF1 HELP
PF3 QUIT
PF4 EXIT
PF5 Main Menu
Enter Continue
To see all available restore sets, type all on the RELOAD SET field. A restore set
report will be presented. Write down the restore set number you wish to use. In
our case, the restore set number 1 will be used.
Appendix B. Command Examples
219
05.03.1997
Control Center Facility
14.06.06
*----------------------- Reload Restore Set Selection -----------------------*
| Command ==>
SQMID: ELDBMSRV
|
|
Database ===> ELDB2B
NODE: BOEVMCT1
|
|
|
|
|
|
RELOAD SET ===> all
Archive Restore Set to RELOAD
|
|
( Blank for LATEST or ALL for all available )
|
|
To execute RELOAD, you must select the archive restore set
|
|
to use. The restore set is a group of tapes or disks that were used
|
|
for a previous BACKUP or TRANSLATE. You may choose ALL to display ALL
|
|
available restore sets, or you may leave the restore set field BLANK
|
|
to retrieve the LATEST restore set.
|
|
|
|
The selected restore set will be displayed and you will be asked to
|
|
enter the restore set number to begin the RELOAD.
|
|
|
|
Enter Restore Set number and press ENTER to process, or press
|
|
PF3 to QUIT
|
|
|
*---------------------------------------------------------------SQMAR60------*
PF:
1 Help
3 End (Quit)
220
Data Restore Guide
RESTORE SET REPORT for Data Base ELDB2B
Date: 07.03.1997
Time: 18.49.05
DRF
1 2 3
RESTORE SET(s) generated using LOGMODE = L
NOTE: Examine the following restore set(s) and
remember the restore set that you wish to use.
Restore Set #1
From Data Base Archive Created 07.03.1997 15.03.11
Archive
Archive
Date
Time
Type (DB or Log) Sequence Archived Archived Series Volid
_________________
________
__________ ________ ______ ______
Data Base Archive
Tape #1
07.03.1997 15.03.11
100
VOL100
TDSK @1
07.03.1997 15.39.35
100
ELRES2
TRANSLAT * 192
BAC1 @2
07.03.1997 15.41.01
100
TRL200
ACTIVE Log
>>>>
Archived During The Recovery
<<<<
Restore Set #1 END
Restore Set #2
From Data Base Archive Created 07.03.1997 10.54.48
Archive
Archive
Date
Time
Type (DB or Log) Sequence Archived Archived Series Volid
_________________
________
__________ ________ ______ ______
DB USER ARCHIVE
Uarc #1
07.03.1997 10.54.48
200
USER BACKUP
DRFBACKUP 03/07/97 10:51:13
Log Archive(s):
Log
#2
07.03.1997 15.00.19
200
LOG201
ACTIVE Log
>>>>
Archived During The Recovery
<<<<
Restore Set #2 END
Restore Set #3
From Data Base Archive Created 07.03.1997 10.19.58
Archive
Archive
Date
Time
Type (DB or Log) Sequence Archived Archived Series Volid
_________________
________
__________ ________ ______ ______
DB USER ARCHIVE
Uarc #1
07.03.1997 10.19.58
200
USER BACKUP
DRFBACKUP 03/07/97 10:16:23
BAC1 @1
07.03.1997 10.19.56
200
VOL002
ACTIVE Log
>>>>
Archived During The Recovery
Restore Set #3 END
Figure 188. Restore Set Report
On the RELOAD Restore Set Selection screen, we type the restore set number
1
to
be used. In our case, the database is running in logmode=L and we do not have
any log tapes. Just the active log will be processed. If you have 1 or more log
tapes, you can limit the number of log tapes to be processed by especifing Y on the
Process Partial Logs field.
Appendix B. Command Examples
221
05.03.1997
Control Center Facility
14.08.12
*----------------------- RELOAD Restore Set Selection -----------------------*
| Command ==>
SQMID: ELDBMSRV
|
|
Database ===> ELDB2B
NODE: BOEVMCT1
|
|
|
| Logmode
===> L
Logmode for the RELOAD
|
| RELOAD Set
===> 1
Archive Restore Set Number to Use
|
|
(Select from the list below)
|
| Process Partial Logs
===> N
Limit Logs Processed (Y or N)
|
|
|
| BACKUP Type
===> BACKUP
BACKUP or BACKUP2
|
|
------------------ Valid Restore Sets -------------------
|
|
1
(04.03.1997), 2 (04.03.1997), 3 (04.03.1997)
|
|
|
|
|
| NOTE: If RECOVERY=’YES’, Data Restore will process the logs. To
|
|
limit the number of logs read, ENTER Y for Partial Log
|
|
processing.
|
|
|
|
Enter Restore Set and press ENTER to process, or press PF3 to QUIT
|
|
|
*---------------------------------------------------------------SQMAR70------*
PF:
1 Help
3 End (Quit)
Press enter to continue the RELOAD process.
05.03.1997
Control Center Facility
14.13.08
*--------------------------- Reload Verification ----------------------------*
| Command ==>
SQMID: ELDBMSRV
|
|
Database ===> ELDB2B
NODE: BOEVMCT1
|
|
|
|
This is your chance to review the RELOAD set. If you want to
|
|
continue with the RELOAD, press ENTER, if you want to CANCEL the
|
|
RELOAD now, press PF3.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Press ENTER to continue with the RELOAD request, or
|
|
press PF3 to QUIT
|
|
|
*---------------------------------------------------------------SQMAR80------*
PF:
1 Help
3 End (Quit)
The next panel is the RELOAD Table List screen. Here, you specify the table(s) to
be reloaded. Each table must include the function (Purge, New, Add, Replace) to
be applied. In this example, the sample sqldba.activity table will be reloaded. You
can specify up to 90 RELOAD table statements. After entering the RELOAD table
commands, press PF5 to continue the execution of the RELOAD process.
222
Data Restore Guide
05.03.1997
Control Center Facility
14.15.21
*---------------------------- Reload Table List -----------------------------*
| Database => ELDB2B
Selected Tables => 0
|
|
P,N,A,R Table
Dbspace
|
| Num Funct
Creator Table Name
Owner
Dbspace Name
|
| ---
-----
--------
------------------
--------
------------------
|
|
P
sqldba__
activity__________
public__
sample____________
|
|
NEW
________
__________________
|
|
|
|
_
________
__________________
________
__________________
|
|
NEW
________
__________________
|
|
|
|
_
________
__________________
________
__________________
|
|
NEW
________
__________________
|
|
|
|
_
________
__________________
________
__________________
|
|
NEW
________
__________________
|
|
|
|
|
|
Page 1
of 1
|
*---------------------------------------------------------------DRRELD3------*
PF:
1 Help
3 QUIT
5 Continue
6 Previous Menu
In the next step, Control Center will show the RELOAD control file that is created
to perform the RELOAD function. Here we can check if the right files (tape and
disk) are being used. Press PF3 to exit from the file and continue with the next
panel.
$$RELOAD $RELDCTL A1
V 74
1 Blks
3/07/97 Line
1 of 5
===>
:DBMACH=ELDB2B RELOAD RECOVERY=YES from TRANSLATEREC @ 07.03.1997 15.03.11
#1 DRF TRANSDSK 07.03.1997 15.39.35 100 N ELRES2 TRANSLAT * 192
#2 DRF BACKUP 07.03.1997 15.41.01 100 N TRL200
#3 LOG Archive ACTIVE LOG
END RESTORE SET
* * * End of file * * *
Figure 189. Reload Control File
Below we have the last panel of the RELOAD function. On this panel you specify
the type of execution. In our case we will execute the RELOAD immediately. Also,
In this example we are using RECOVERY=YES, therefore the RELOAD ID is name
of the database machine (ELDB2B) and you cannot change it. For RECOVERY=NO,
this field is empty and you can enter any unique file name.
Appendix B. Command Examples
223
07.03.1997
Control Center Facility
17.24.39
*---------------------------- RELOAD EXECUTION ------------------------------*
| DATABASE ==> ELDB2B
CTRLID: ELDBMSRV |
|
NODE: BOEVMCT1 |
|
|
| Execution
==> 2
( 1 = Schedule, 2 = Execute Immediately
|
|
|
| RELOAD ID
==> ELDB2B
(Unique file name for RELOAD event )
|
| The Reload Id (name) will be used as the file name for the RELDCTL control |
| file which will hold media and table list data required for the RELOAD.
|
| If you execute a RECOVERY=YES, the RELOAD ID is the database machine.
|
|
|
| NOTIFY ==> ________
(Userid)
________
(Node)
|
|
|
|
|
| Commitcount
==> ______
( Rows to reload before a commitcount
|
|
|
| Nbviews
==> ______
( Estimate number of views to recreate.
|
|
|
|
|
*----------------------------------------------------------------DRRELD5-----*
PF1 HELP PF3 QUIT
PF4 View RELDCTL file
PF7 PREVIOUS SCREEN
ENTER CONTINUE
After Control Center finishes the RELOAD operation, the LISTLOG function can be
used to produce a report of the changes to the tables that were specified at the
RELOAD operation. In our case, the sample sqldba.activity table was used. The
report produced with the LISTLOG function can be used to decide which LUWs
will be re-applied to the database using the APPLYLOG function.
Examples of Reloading Tables in a VSE Environment
The following is an example of JCL (VSE) to reload tables from a BACKUP.
Note: The Data Restore backup must be loaded on logical device SYS006. If
RECOVERY=YES is specified, any log archives will also be read from logical
device SYS006.
// JOB RELOAD
(1) ---> // LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
(2) ---> // DLBL LMBRWRK,,,VSAM
(3) ---> // TLBL ARCHIV,’ARCHIVE.DB2’,,,1
(4) ---> // ASSGN SYS006,180
(5) ---> // MTC REW,SYS006
(6) ---> // EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(dbname)’
(7) ---> CONTROL DBNAME=dbname
(7) ---> OPTIONS DEVICE=TAPE
(7) ---> RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=PURGE
(7) ---> RELOAD CREATOR=SQLDBA TNAME=SUPPLIERS
(7) --->
FUNCT=NEW
(7) --->
NEWTNAME=NEWSUPPLIERS
(7) --->
DBSPACE=SAMPLE
/*
Figure 190. Sample JCL to Reload Tables from a BACKUP File
Statement 1
Specifies the DB2 Server for VSE and Data Restore libraries for the
RELOAD function.
224
Data Restore Guide
Statement 2
Specifies the work file LMBRWRK which is used if the reloaded tables
contain LONG columns.
Statement 3
Specifies the ddname ARCHIV for the BACKUP file.
Statement 4
Assigns the tape containing the backup file.
Statement 5
Rewinds the tape.
Statement 6
Calls the program to execute the function. The dbname of the database to
process must be specified on the PARM option.
Statement 7
Specifies the SYSIN for the program.
The following is an example of JCL (VSE) to reload from an UNLOAD DBSPACE.
// JOB RELOAD
(1) ---> // LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
(2) ---> // DLBL LMBRWRK,,,VSAM
(3) ---> // TLBL ARCHIV,’UNLOAD.DB2’,,,1
(4) ---> // ASSGN SYS006,180
(5) ---> // MTC REW,SYS006
(6) ---> // EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(dbname)’
(7) --->
CONTROL DBNAME=dbname
OPTIONS DEVICE=TAPE
RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=REPLACE
/*
Figure 191. Example JCL to Reload a Table from an UNLOAD File
Statement 1
Specifies the DB2 Server for VSE and Data Restore libraries for the
RELOAD function.
Statement 2
Specifies the work file LMBRWRK which is used if the reloaded tables
contain LONG columns.
Statement 3
Specifies the ddname ARCHIV for the UNLOAD file.
Statement 4
Assigns the tape containing the UNLOAD file.
Statement 5
Rewinds the tape.
Statement 6
Calls the program to execute the function. The dbname of the database to
process must be specified on the PARM option.
Statement 7
Specifies the SYSIN for the program.
The following is an example of JCL (VSE) to reload and generate the log recovery
file from the last BACKUP.
Appendix B. Command Examples
225
// JOB RELOAD
(1) ---> // LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
(2) ---> // DLBL LMBRWRK,,,VSAM
(3) ---> // DLBL LMBRLG1,,,VSAM
(3) ---> // DLBL LMBRLG2,,,VSAM
(3) ---> // DLBL LMBRLG3,,,VSAM
(4) ---> // TLBL ARCHIV,’ARCHIVE.DB2’,,,1
(5) ---> // TLBL LARCHIV,,,,1
(6) ---> // ASSGN SYS006, 180
(7) ---> // MTC REW,SYS006
(8) ---> // EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(dbname)’
(9) --->
OPTIONS RECOVERY=YES DEVICE=TAPE
(9) --->
RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=REPLACE
/*
Figure 192. Example JCL to Reload a Table and Prepare Recovery from the Log
Statement 1
Specifies the DB2 Server for VSE & VM and Data Restore libraries for the
RELOAD function.
Statement 2
Specifies the work file LMBRWRK which is used if the reloaded tables
contain LONG columns.
Statement 3
Specifies the work files LMBRLG1, LMBRLG2, and LMBRLG3 which are
used to extract all changes referenced in the log for the reloaded tables
when the RECOVERY=YES parameter is specified. They will be used to
execute forward log recovery.
Statement 4
Specifies the ddname ARCHIV for the BACKUP file.
Statement 5
Specifies the ddname LARCHIV for the log archive files.
Statement 6
Assigns the tape containing the backup file.
Statement 7
Rewinds the tape.
Statement 8
Calls the program to execute the function. The dbname of the database to
process must be specified on the PARM option.
Statement 9
Specifies the SYSIN for the program. The OPTIONS statement specifies
that log recovery is requested.
The following is an example of JCL to reload from a DB2 Server for VSE archive.
Note: The DB2 Server for VSE archive must be loaded on logical device SYS007. If
a TLBL is specified for the ARCHIV file, it must be loaded on logical device
SYS006. If RECOVERY=YES is specified, any log archives will also be read
from logical device SYS006.
226
Data Restore Guide
// JOB RELOAD
(1) ---> // LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
(2) ---> // DLBL LMBRWRK,,,VSAM
(3) ---> // DLBL LMBRLG1,,,VSAM
(3) ---> // DLBL LMBRLG2,,,VSAM
(3) ---> // DLBL LMBRLG3,,,VSAM
(4) ---> // DLBL ARCHIV,,,VSAM,RECSIZE=4096,RECORDS=(100,100)
(5) ---> // TLBL LARCHIV,,,,1
(6) ---> // TLBL ARIARCH,’ARCHIVE.DB2’,,,1
(7) ---> // ASSGN SYS007, 180
(8) ---> // MTC REW,SYS007
(9) ---> // DLBL SYS0001,,,VSAM,RECSIZE=4096,RECORDS=(100,100)
(9) ---> // DLBL HEADER,,,VSAM,RECSIZE=4096,RECORDS=(100,100)
(9) ---> // DLBL DIRWORK,,,VSAM
(10)---> // EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(dbname)’
(11)--->
OPTIONS ARCHTYPE=DB2
(11)--->
CONTROL DBNAME=dbname
(11)--->
RELOAD CREATOR=SQLDBA,TNAME=CUSTOMERS FUNCT=NEW
(11)--->
DBSPACE=SAMPLE
/*
Figure 193. Sample JCL to Execute the RELOAD Function from a DB2 Server for VSE
Archiive.
Statement 1
Specifies the DB2 Server for VSE and Data Restore libraries for the
RELOAD function.
Statement 2
Specifies the work file LMBRWRK which is used if the reloaded tables
contain LONG columns.
Statement 3
Specifies the work files LMBRLG1, LMBRLG2, and LMBRLG3 which are
used to extract all changes referenced in the log files for the reloaded tables
when the RECOVERY=YES parameter is specified. They will be used to
execute forward log recovery.
Statement 4
Specifies the work file ARCHIV for this process.
Statement 5
Specifies the ddname LARCHIV for the log archive file.
Statement 6
Specifies the ddname ARIARCH for the DB2 Server for VSE database
archive file.
Statement 7
Assigns the tape containing the archive file.
Statement 8
Rewinds the tape.
Statement 9
Specifies the work files SYS0001, HEADER, DIRWORK for the function.
Statement 10
Calls the program to execute the function. The dbname of the database to
process must be specified on the PARM option.
Statement 11
Specifies the SYSIN for the program. The OPTIONS statement specifies
that the process is executed from a DB2 Server for VSE database archive.
Appendix B. Command Examples
227
The following is an example of a report generated by a RELOAD from a DB2
Server for VM archive.
(1) ---> XTS9-143 OPTIONS ARCHTYPE=DB2
XTS9-143 CONTROL DBNAME=dbname READPW=RR
XTS9-143 RELOAD CREATOR=SQLDBA,TNAME=CUSTOMERS FUNCT=NEW
XTS9-143
DBSPACE=SAMPLE
XTS9-143 /*
XTS9-196 Do you want to continue the RELOAD process ?
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
XTS9-100 Data Restore feature VERSION 7.1.0
(2) ---> XTS9-193 Mount first tape of database server archive
XTS9-406 Enter 0(CANCEL) or 1(CONTINUE)
XTS9-403 Reply is 1
(3) ---> XTS9-202 Processing database server archive (timestamp=1995-274-15-50-10)
XTS9-169 Processing tables containing long columns
XTS9-102
20 ROWS LOADED, PROCEDURE COMPLETED
XTS9-128
20 ROWS LOADED INTO (SQLDBA.CUSTOMERS)
XTS9-101
1 tables successfully processed
CONNECT SQLDBA
;
COMMIT WORK ;
XTS9-007 Processing successfully completed
Figure 194. Example Report from a RELOAD from a DB2 Server for VSE & VM Archive
Statement 1
Specifies that the input file is a DB2 Server for VM archive.
Statement 2
Prompts the operator to remount the first archive tape.
Statement 3
Displays the timestamp of the DB2 Server for VM archive.
// JOB RELOAD
(1) ---> // LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
(2) ---> // DLBL LMBRWRK,,,VSAM
(3) ---> // TLBL ARCHIV,’ARCHIVE.SQL’,,,1
(4) ---> // ASSGN SYS006,180
(5) ---> // MTC REW,SYS006
(5) ---> // EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(DBNAME)’
(7) ---> CONTROL DBNAME=DBNAME
(7) ---> OPTIONS DEVICE=TAPE
(7) ---> RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=PURGE
(7) ---> RELOAD CREATOR=SQLDBA TNAME=SUPPLIERS
(7) --->
FUNCT=NEW
(7) --->
NEWTNAME=NEWSUPPLIERS
(7) --->
DBSPACE=SAMPLE
/*
Figure 195. Example of JCL to Reload in a VSE Environment From a Full Backup
Statement 1
DB2 library must be specified for the RELOAD function.
Statement 2
LMBRWRK is used if the reloaded tables contain LONG columns.
Statement 3
ARCHIV is the ddname for the BACKUP file. It can be a BACKUP
file or a FULL BACKUP.
Statement 4
The tape containing the backup file is assigned.
Statement 5
The tape is rewound.
228
Data Restore Guide
Statement 6
Program to execute functions is called. The DBNAME of the
database to process must be specified on the PARM option.
Statement 7
SYSIN for the program is specified.
// JOB RELOAD
(1) ---> // LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)
(2) ---> // DLBL LMBRWRK,,,VSAM
(3) ---> // TLBL ARCHIV,’ARCHIVE.SQL’,,,1
(4) ---> // TLBL FULLARC,’ARCHIVE.SQL’,,,1
(5) ---> // ASSGN SYS006,180
(6) ---> // MTC REW,SYS006
(7) ---> // EXEC XTS91001,SIZE=AUTO,PARM=’DBNAME(dbname)’
(8) ---> CONTROL DBNAME=dbname WRKSIZE=4096
(8) ---> OPTIONS DEVICE=TAPE DEVICE2=TAPE
(8) ---> RELOAD CREATOR=SQLDBA TNAME=CUSTOMERS FUNCT=PURGE
(8) ---> RELOAD CREATOR=SQLDBA TNAME=SUPPLIERS
(8) --->
FUNCT=NEW
(8) --->
NEWTNAME=NEWSUPPLIERS
(8) --->
DBSPACE=SAMPLE
/*
Figure 196. Example of JCL to Reload in a VSE Environment From an Incremental Backup
Statement 1
DB2 library must be specified for the RELOAD function.
Statement 2
LMBRWRK is used if the reloaded tables contain LONG columns.
Statement 3
ARCHIV is the ddname for the last Incremental Backup.
Statement 4
FULLARC is the ddname for the last Full Backup.
Statement 5
The tape containing the backup file is assigned.
Statement 6
The tape is rewound.
Statement 7
Program to execute functions is called. The DBNAME of the
database to process must be specified on the PARM option.
Statement 7
SYSIN for the program is specified. WRKSIZE must be equivalent
to the parameter specified during the BACKUP function. DEVICE2
specifies if a TAPE or DASD (TLBL/DLBL) is used for Full Backup
(FULLARC).
Examples of Reloading Tables in a VM Environment
Note: Before executing a procedure to reload tables, you must run the SQLINIT
EXEC specifying DBNAME(database-name) PROTOCOL(SQLDS) to:
1. Establish database-name as the database into which the tables are to be
reloaded.
2. Ensure that an authorization ID can be specified on a CONNECT
statement.
You must also link and access the minidisk where Data Restore is installed.
The following is an example of an EXEC to RELOAD from a BACKUP or
UNLOAD file.
Appendix B. Command Examples
229
|
||
|
|
|