SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-21
Recovery Example
*** could not be accessed.
*** ERROR from File System [11]: file not in directory or row not
*** in file, or the specified tape file is not present on a
*** labeled tape.
>>
These error messages confirm that the table has been removed.
2. Identify the EMPLOYEE table's dependent objects that might also have been
dropped. To do this, check the output from the last DISPLAY USE OF command
issued for this table (see Recovery Example on page 11-20) to determine what
objects depend on the table. Now you can conclude that the EMPLIST protection
view, the MGRLIST and ORDREP shorthand views, and the XEMPDEPT and
XEMPNAME indexes have also been dropped.
3. Further confirm that these dependent objects were actually dropped by issuing a
TMFCOM INFO DUMPS, DETAIL command for each object. These commands list
the online dump entries in the TMF catalog for the objects. The dump entries for
three objects (EMPLOYEE, EMPLIST, and MGRLIST) appear next:
~INFO DUMPS $DATA.PERSNL.EMPLOYEE, DETAIL
Dump Dump
Date-Time Type Master Data Status
--------------------- ----- ------ ----- -------
12-Dec-1997 14:15:12 online 1 1 invalid. . .
.
.
.
~INFO DUMPS $DATA.PERSNL.EMPLIST, DETAIL
Dump
Date-Time Type Master Data Status
--------------------- ----- ------ ----- -------
12-Dec-1997 14:15:14 online 1 1 invalid. . .
.
.
.
~INFO DUMPS $DATA.PERSNL.MGRLIST, DETAIL
Dump
Date-Time Type Master Data Status
--------------------- ---- ------ ----- -------
12-Dec-1997 14:15:17 online 1 1 invalid. . .
.
.
.
The dump status “invalid” that appears for each object indicates that the object was
lost.
Similar INFO DUMPS DETAIL commands for XEMPNAME, XEMPDEPT, and
ORDREP reveal that they, too, were dropped.