Recovery Process Error Messages [ Silhouette Reference Manual ] MPE/iX 5.0 Documentation
Silhouette Reference Manual
Recovery Process Error Messages
The following error messages are concerned with the Silhouette Recovery
Process (RP).
0001 MESSAGE Error writing to SAVE file. (RPERR 1)
CAUSE An MPE file system error occurred in the FWRITE to the SAVE
file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0002 MESSAGE Couldn't open the input pipe file. (RPERR 2)
CAUSE An MPE file system error occurred in the FOPEN of the input
pipe file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0003 MESSAGE Error setting the extended wait. (RPERR 3)
CAUSE Internal file system error.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0004 MESSAGE Couldn't open the command pipe file. (RPERR 4)
CAUSE An MPE file system error occurred in the FOPEN of the
command pipe file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0005 MESSAGE Error setting command wait. (RPERR 5)
CAUSE Internal file system error.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0006 MESSAGE Error setting command timeout. (RPERR 6)
CAUSE Internal file system error.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0007 MESSAGE Couldn't open output pipe file. (RPERR 7)
CAUSE An MPE file system error occurred in the FOPEN of the output
pipe file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0008 MESSAGE Couldn't open the SAVE file. (RPERR 8)
CAUSE An MPE file system error occurred in the FOPEN of the SAVE
file on the secondary system. Cannot restart the Silhouette
subsystem.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0009 MESSAGE Couldn't close the SAVE file. (RPERR 9)
CAUSE An MPE file system error occurred in the FCLOSE of the SAVE
file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0010 MESSAGE Error writing to the SAVE file. (RPERR 10)
CAUSE An MPE file system error occurred in an FWRITE to the SAVE
file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0011 MESSAGE Error reading the SAVE file. (RPERR 11)
CAUSE An MPE file system error occurred in an FREAD of the SAVE
file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0012 MESSAGE Checkpoint (SAVE) file indicated potentially bad database.
(RPERR 12)
CAUSE The first two records in the SAVE file are different,
indicating a DB call failure or critical system failure
during a DB update.
ACTION Use recovery procedure for major failure on secondary
system.
--------------------------------------------------------------------------------------
0013 MESSAGE Restore Silhouette databases, checkpoint (SAVE) file and
logfiles. (RPERR 13)
CAUSE A failure occurred on the secondary system and Silhouette
requires files to be restored. Database is potentially
corrupt.
ACTION Restore the databases, checkpoint (SAVE) file, and logfiles.
--------------------------------------------------------------------------------------
0014 MESSAGE Error opening the logfile. (RPERR 14)
CAUSE The RP could not open the logfile on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0015 MESSAGE Error closing the logfile. (RPERR 15)
CAUSE An MPE file system error occurred in the FCLOSE of the
logfile on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0016 MESSAGE Error writing to the logfile. (RPERR 16)
CAUSE An MPE file system error occurred in an FWRITE to the
logfile on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0017 MESSAGE Error reading the logfile. (RPERR 17)
CAUSE An MPE file system error occurred in an FREAD of the logfile
on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0018 MESSAGE Error issuing backup tape equate. (RPERR 18)
CAUSE An MPE COMMAND intrinsic error occurred in issuing an equate
for the backup tape on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0022 MESSAGE These transactions have been removed from the Silhouette
database. This system must now be used as the MAIN system.
The databases are no longer identical. You must ensure that
the databases are identical before starting the Silhouette
system again. (RPWARN 22)
CAUSE This message appears after a successful >SWITCH on the
secondary system.
ACTION No action is required.
--------------------------------------------------------------------------------------
0023 MESSAGE There were no incomplete Silhouette transactions. (RPMSG
23)
CAUSE An MPE file system error occurred in an FREAD of the logfile
on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0024 MESSAGE The DBUPDATE data doesn't compare. (RPERR 24)
CAUSE When processing a DBUPDATE request from the primary system,
the "before change" data was not the same.
ACTION Check for secondary database modify occurrence. Restore
databases(s), SAVE file, and logfile.
--------------------------------------------------------------------------------------
0025 MESSAGE DBPUT record number error. (RPERR 25) Old = nnnNew = nnn.
CAUSE Detail data set record numbers do not match. Databases are
not the same.
ACTION Check for secondary database modify occurrence. Restore
databases(s), SAVE file, and logfile.
--------------------------------------------------------------------------------------
0027 MESSAGE DBDELETE data compare error. (RPERR 27)
CAUSE Detail data set record numbers do not match. Databases are
not the same.
ACTION Check for secondary database modify occurrence. Restore
databases(s), SAVE file, and logfile.
--------------------------------------------------------------------------------------
0028 MESSAGE Error writing to secondary system. (RPERR 28)
CAUSE The RP failed in writing back to the CP via the message pipe
on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0029 MESSAGE RESTART requested at logfile record nnn. (RPMSG 29)
CAUSE This message appears at the Console in response to a >START
or >USE command when RP already existed.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0030 MESSAGE *** Silhouette Requested shutdown. *** (RPMSG 30)
CAUSE This message appears after a >KILL or >STOP command when
there is no outstanding BEGIN.
ACTION No action is required.
--------------------------------------------------------------------------------------
0031 MESSAGE Silhouette recovery process shutdown. (RPMSG 31)
CAUSE This message appears after a >KILL or >STOP command when
there is no outstanding BEGIN.
ACTION No action is required.
--------------------------------------------------------------------------------------
0032 MESSAGE Database opened filename. (RPMSG 32)
CAUSE Issued for a successful DB open requested by an MP >START or
>RESUME command.
ACTION No action is required.
--------------------------------------------------------------------------------------
0033 MESSAGE Unable to re-open SAVE file or logfile. (RPERR 33)
CAUSE >RESUME or >START command not able to open SAVE or logfile
via RP.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0034 MESSAGE RESUME request executed. (RPMSG 34)
CAUSE This message appears after a >RESUME command is entered.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0035 MESSAGE Starting stand-alone recover. (RPMSG 35)
CAUSE This message appears after a >RECOVER command.
ACTION No action is required.
--------------------------------------------------------------------------------------
0036 MESSAGE (No rollout of incomplete transactions.) (RPMSG 36)
CAUSE This message appears after a successful >RECOVER command
with the NOROLLOUT or REPORT options.
ACTION No action is required.
--------------------------------------------------------------------------------------
0037 MESSAGE (No new transactions added.) (RPMSG 37)
CAUSE This message appears after a successful >RECOVER command
with the NOROLLFWD or REPORT options.
ACTION No action is required.
--------------------------------------------------------------------------------------
0038 MESSAGE Starting recover. (RPMSG 38)
CAUSE This message appears after a >RECOVER command from the MP.
ACTION No action is required.
--------------------------------------------------------------------------------------
0039 MESSAGE Unable to open SWITCHed log nnn. (RPERR 39)
CAUSE An MPE file system error occurred in the FOPEN of the
logfile on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
(cont.)
0040 MESSAGE Unable to open SWITCHed SAVE file filename. (RPERR 40)
CAUSE An MPE file system error occurred in the FOPEN of the SAVE
file on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0041 MESSAGE Unable to read SAVE file label. (RPERR 41)
CAUSE An MPE file system error occurred in the FREADLABEL of the
SAVE file.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0042 MESSAGE SAVE file does not correspond to a backup quiet point.
(RPERR 42)
CAUSE This message appears after the FREADLABEL indicates a backup
though there are still outstanding transactions.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0043 MESSAGE Recovering log record number nnn. (RPMSG 43)
CAUSE This message gives the logfile record number in which an
error was encountered.
ACTION No action is required.
--------------------------------------------------------------------------------------
0044 MESSAGE Finished recover. (RPMSG 44)
CAUSE This message appears after a successful >RECOVER.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0045 MESSAGE FREADDIR error on logfile. (RPERR 45)
CAUSE An MPE file system error occurred in an FREADDIR of the
logfile on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0046 MESSAGE Tape operation failed. FSERR nnn. (RPERR 46)
CAUSE An MPE file system error occurred in reading the transaction
tape during a >SWITCH or >RECOVER.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0047 MESSAGE Record out of sequence. Expected nnnGot nnn. (RPERR 47)
CAUSE This message appears if a log record is received out of
sequence.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0048 MESSAGE Tape is Silhouette nnn. (RPMSG 48)
CAUSE This message give a tape sequence number.
ACTION No action is required.
--------------------------------------------------------------------------------------
0049 MESSAGE Wrong tape set / Missing records. (RPERR 49)
CAUSE This message appears if an incorrect tape is mounted during
a >SWITCH or >RECOVER.
ACTION Mount the correct tape and try again.
--------------------------------------------------------------------------------------
(cont.)
0050 MESSAGE End of Silhouette tape records. No trailer. (RPWARN 50)
CAUSE There was no trailer on the Silhouette tape. This is a
normal occurrence when the primary system has failed.
ACTION No action is required.
--------------------------------------------------------------------------------------
0051 MESSAGE Silhouette tapes processed OK. (RPMSG 51)
CAUSE This message appears after a >SWITCH or >RECOVER is
finished.
ACTION No action is required.
--------------------------------------------------------------------------------------
0052 MESSAGE Cannot purge filename, rename did not take place. (RPERR
52)
CAUSE An MPE COMMAND intrinsic error occurred in renaming the log
and SAVE files after a >SWITCH or >RECOVER.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0053 MESSAGE *** Manager requested a SWITCH. *** (RPMSG 53)
CAUSE This message appears after a >SWITCH request on the
secondary system.
ACTION No action is required.
--------------------------------------------------------------------------------------
0054 MESSAGE End of stand-alone recovery. (RPMSG 54)
CAUSE This message appears after a successful stand-alone
>RECOVER.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0055 MESSAGE Command file FSERR nnn. (RPERR 55)
CAUSE An MPE file system error occurred in reading a command from
the CP on the secondary system.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0056 MESSAGE Missed a heartbeat. (RPERR 56)
CAUSE This message appears after a missed heartbeat from the
primary system.
ACTION Check primary system status.
--------------------------------------------------------------------------------------
0057 MESSAGE Recovery process no longer communicating to main system.
(RPERR 57)
CAUSE Two heartbeats in a row were missed from the primary system.
ACTION Check primary system status.
--------------------------------------------------------------------------------------
0059 MESSAGE End of stand-alone recovery. (No rollout of incomplete
transactions) (RPMSG 59)
CAUSE This message appears after a >RECOVER with the NOROLLBACK or
REPORT options.
ACTION No action is required.
--------------------------------------------------------------------------------------
0060 MESSAGE End of stand-alone recovery. (No new transactions added.)
(RPMSG 60)
CAUSE This message appears after a >RECOVER with the NOROLLFWD or
REPORT options.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0061 MESSAGE Is Silhouette tape reel #nnnavailable? (Y/N) (RPMSG 61)
CAUSE During SWITCH or stand-alone recovery, the RP requires the
next tape reel.
ACTION Mount the appropriate tape.
--------------------------------------------------------------------------------------
0069 MESSAGE Not a Silhouette log tape. Mount another? (Y/N) (RPMSG 69)
CAUSE This is not recognized as a Silhouette log tape.
ACTION Determine whether this is the correct tape.
--------------------------------------------------------------------------------------
0070 MESSAGE Database not opened filename. (RPERR 70)
CAUSE RP couldn't open database.
ACTION Check $STDLIST to determine the IMAGE error.
--------------------------------------------------------------------------------------
0071 MESSAGE The SAVE file on the secondary is out-dated. (RPERR 71)
CAUSE Silhouette is using an old SAVE file with a newer version of
Silhouette.
ACTION Start Silhouette with new log cycle.
--------------------------------------------------------------------------------------
0072 MESSAGE START request at logfile record nnn. (RPMSG 72)
CAUSE This message appears at the Console in response to a >START
or >USE command. Similar to RPERR 29 except that this is a
>START with no RP on the secondary.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0073 MESSAGE Bad logfile sequence number encountered: nnn(RPERR 73)
CAUSE The user started a new log cycle incorrectly or changed the
logfile name, causing the RP logfile name to be out of
sequence.
ACTION Synchronize primary and secondary logfile sequence numbers.
--------------------------------------------------------------------------------------
0074 MESSAGE Logfile change from logidto logid. (RPMSG 74)
CAUSE This message is sent to the Console to indicate a change in
logfiles (U-MIT CHANGELOG).
ACTION No action is required.
--------------------------------------------------------------------------------------
0075 MESSAGE Logfile logidopened. (RPMSG 75)
CAUSE The specified logfile has been opened. This is usually the
result of the CHANGELOG Console message.
ACTION No action is required.
--------------------------------------------------------------------------------------
0076 MESSAGE Failed to open logfile logid. (RPMSG 76)
CAUSE The specified logfile could not be opened. (Console
message.)
ACTION No action is required.
--------------------------------------------------------------------------------------
0077 MESSAGE SWITCH logfile logidnot present. Available? (RPMSG 77)
CAUSE This is an Operator message to supply a logfile for a
>SWITCH request. Occurs when a previous logfile is required
for rollback.
ACTION No action is required.
--------------------------------------------------------------------------------------
(cont.)
0078 MESSAGE SWITCH operator request for new logfile failed. (RPERR 78)
CAUSE Found on $STDLIST of recovery job if Operator request
failed.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0079 MESSAGE SWITCH command aborted due to errors. (RPERR 79)
CAUSE Found on $STDLIST of recovery job if Operator request
failed.
ACTION Call your System Manager.
--------------------------------------------------------------------------------------
0080 MESSAGE Logfile "logfilename" is not available. (RPERR 80)
CAUSE During Rollback, a previous logfile was required but not
found.
ACTION Restore backup copy of required logfile. Respond to the
associated console request.
--------------------------------------------------------------------------------------
0081 MESSAGE Rename logfile to "logfilename". RP couldn't. (RPWARN 81)
CAUSE Rollback was completed successfully. However, the renaming
of the logfile to zogfile was not possible.
ACTION Rename logfile to zogfile, manually under MPE.
--------------------------------------------------------------------------------------
(cont.)
0082 MESSAGE Recover SAVE file tables from log record nnnto nnn. (RPMSG
82)
CAUSE Previous run of RP terminated abnormally so that the SAVE
file tables are out of date. RP will update the SAVE file.
ACTION No action is required.
--------------------------------------------------------------------------------------
0083 MESSAGE Actively check last log record nnn. (RPMSG 83)
CAUSE RP restart code checks last log record to see if the
database I/O is completed.
ACTION No action is required.
--------------------------------------------------------------------------------------
MPE/iX 5.0 Documentation