FRD6022A UNABLE TO RECOVER: dbname, reason

Explanation

A RECOVER START command was issued, but the database data set or area cannot be recovered. This message is sent to the issuer of the command.

In the message text:
dbname
Identifies the database data set or area that could not be recovered.
reason
Indicates the cause of the error and is one of the following:
AUTHORIZATION FAILED, RSN = XX
Authorization processing failed to properly authorize one or more of the database data sets or areas in the recovery list. XX identifies the DBRC reason code. The DBRC reason codes are documented in the IMS Messages and Codes manual, under message DFS047A.
IMAGE COPY ALREADY TAKEN
The OUTPUT(ICR) option was specified, and the IMS Database Recovery Facility tried to create an incremental image copy as a concurrent image copy. However, the last incremental image copy was the concurrent image copy and there were no log data sets (SLDS) to apply thereafter. Therefore, no new incremental image copy was created.
IMAGE COPY NOT AVAILABLE
DBRC was unable to locate a usable image copy for the database data set.
INCOMPLETE CA NOT ALLOWED
An incomplete change accumulation was detected during an attempt to generate a batch Incremental Image Copy using the ICRCA option. A complete change accumulation is required.
INVALID RCVTIME
DBRC determined that the RCVTIME specified falls in the middle of an ALLOC for this entry, and the PITR option was not specified.
LOG NOT ARCHIVED
Logs that are selected for recovery are not archived. Verify that the logs are in the RECON, then run an archive job for the unarchived OLDS.
LOGS MARKED IN ERROR
DBRC determined that none of the log data sets are usable. They might be marked in error. Or DBRC was unable to locate log data sets for recovery from only secondary sources.
NEEDS HIGHER RELEASE LOG
The IMS Database Recovery Facility detected logs generated by a higher release IMS. The database cannot be selected if it was updated by an IMS operating at a higher release.
NO BATCH ICR POINT FOUND
IMS Database Recovery Facility attempted to generate a batch Incremental Image Copy and was unable to. A usable batch window does not exist.
NO IC FOUND FOR LASTIC
RCVTYPE(LASTIC) was specified, however no IC exists where the DSDS/Area has been stopped.
NO CA FOUND FOR PITCA or LASTPITCA
A recovery was attempted using a PITCA, but no PIT CA was found. A PITCA must have a RUN time which matches the RCVTIME timestamp for a PITCA recovery. A PITCA must be marked ERR, and the CA data set name must have the suffix .HPCAP.
NO IC TAKEN AFTER A PITR
The IMS Database Recovery Facility requires input for recovery (in the form of an image copy, logs, and change accumulation). The input that was received is not allowed. Because the later PITR recovery might have removed Backout information from the RECON, the integrity of the database might be compromised by this recovery. After a PITR recovery, an image copy must be taken.

Recovery of the identified DBDS failed.

NO PRILOG FOUND
DBRC was unable to locate a PRILOG record. This condition should not occur. Call IBM® Software Support for assistance.
NO RECOV RECORD FOUND
The USEDBDS option was specified on the RECOVER ADD command, but the latest recovery recorded in RECON was not for a time stamp recovery, or the DBDS or AREA is marked in RECON as needing recovery.
NOT FOUND
One or more of the database data sets or areas in the recovery list is not listed in the RECON data set.
NOT OFFLINE
One or more of the database data sets or areas in the recovery list was not taken offline with an IMS DBR command. When the database is in this state, proper operation of the IMS Database Recovery Facility cannot be guaranteed.
RECOV RECORD UNUSABLE
The USEDBDS option was specified on the RECOVER ADD command, but the DBDS or AREA has been updated or reorganized since the latest recovery recorded in the RECON.
REORG LATER THAN IMAGE COPY
A recovery to a time that includes an ALLOC range after a REORG, cannot be allowed unless an image copy was taken after the REORG job. If this situation is allowed, recovery applies data produced under one version of the database (before REORG) and the data from the reorganized version of the database; this will undoubtedly produce a broken database. Take an image copy after your REORG job.

System action

If ERRORCONT was specified for the database data set or area, processing continues for the remaining members in the IMS Database Recovery Facility recovery list. If ERRORCONT was not specified, recovery stops.

User response

Take the appropriate action based on the specified reason:
AUTHORIZATION FAILED
The DBRC reason codes are documented in the IMS Messages and Codes manual under message DFS047A. If the reason indicates that a database or area is in use, determine which IMS did not stop the appropriate database or area, then stop the database or area with the IMS DBR command. Otherwise, take the action indicated in the DFS047A message.
IMAGE COPY ALREADY TAKEN
In order to create a new incremental image copy, archive the log data set containing the update log records. Otherwise, no action is required.
IMAGE COPY NOT AVAILABLE
If this failure occurred while recovering from only secondary sources (SOURCE(SEC) was specified), verify that secondary image copies were created prior to running recovery.
INCOMPLETE CA NOT ALLOWED
In order to be able to successfully run with the ICRCA option, modify your process to ensure that complete change accumulations are generated. Ensure that the complete change accumulations are generated to a time where no transactions occur against the database.
INVALID RCVTIME
Ensure that the RCVTIME specified falls in the middle of an ALLOC for this entry or specify the PITR option is a point-in-time recovery is desired.
LOGS MARKED IN ERROR
If this failure occurred while recovering from only secondary sources (SOURCE(SEC) was specified), verify that SECLOGs and/or SECSLDs were generated for this database data set prior to running recovery.
NEEDS HIGHER RELEASE LOGS
Logs generated on a higher release IMS cannot be used for recovery on a lower release IMS. This situation can occur when running multiple IMS systems in coexistence mode. Rerun the recovery on the level of IMS in which the logs were created.
NO BATCH ICR POINT FOUND
A batch image copy cannot be generated. Ensure that a batch window exists.
NO IC FOUND FOR LASTIC
A RCVTYPE(LASTIC) recovery is not possible.
NO CA FOUND FOR PITCA or LASTPITCA
For a PITCA recovery, verify that the RCVTIME timestamp matches the RUN time listed for the CA record in the RECON created by the HPCA PIT. Also, the CA must be marked ERR and the CA data set name must have the suffix .HPCAP.
NO IC TAKEN AFTER A PITR
After a point-in-time recovery, take an image copy so that subsequent recoveries have a valid starting point. If you know the integrity of the database will not be compromised, delete the RECOV record by using the DBRC DELETE.RECOV command, then rerun the recovery.
NO PRILOG FOUND
Call IBM Software Support for assistance.
NOT FOUND
The database data set or area was deleted from the RECON data set after the RECOVER ADD command was issued. If the database data set or area is legitimate and needs to be recovered, define it in RECON.
NOT OFFLINE
The database data set or area was not stopped on the IMS performing recovery. Stop the database or area with the IMSDBR command.
NO RECOV RECORD FOUND
Recover the DBDS or AREA using a nonstandard image copy. Then inform DBRC of the recovery with a NOTIFY.RECOV command specifying the time that the recovery was run (current), and the time to which the DBDS or AREA was recovered. Then the IMS Database Recovery Facility can be used to recover the DBDS or AREA with the USEDBDS parameter.
RECOV RECORD UNUSABLE
Changes have been made to the DBDS or AREA since the last recovery; as a result, you must run the recovery again. Recover the DBDS or AREA using a nonstandard image copy. Then, inform DBRC of the recovery with a NOTIFY.RECOV command specifying the time that the recovery was run (current) and the time to which the DBDS or AREA was recovered. The IMS Database Recovery Facility can then be used to recover the DBDS or AREA with the USEDBDS parameter.
REORG LATER THAN IMAGE COPY
Inspect the database and ensure that it is in the same workable state as it was before the REORG ran. To issue an IMS Database Recovery Facility time stamp recovery to before the REORG runtime you must first delete the REORG by issuing the DELETE.REORG command.

Module

FRXVSTA0