DFS4266I UNABLE TO RECOVER: dbname, reason

Explanation

A database recovery service /RECOVER START command was issued, but the database data set or area cannot be recovered. The message destination is the z/OS® system console and the IMS master terminal (if this is a DB/DC IMS). This message is also 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, RC = 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 return code.
HALDB MASTER IS STOPPED
The master database for a HALDB partition has been stopped. Although the database recovery service requires that the partitions being recovered be stopped, the master database must be started. Start the master database, and then reissue the /RECOVER START command.
IMAGE COPY NOT AVAILABLE
DBRC was unable to locate a usable image copy for the database data set.
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.
LOGS MARKED IN ERROR
DBRC determined that none of the log data sets are usable. They may be marked in error.
NEEDS HIGHER RELEASE LOG
DBRC detected logs created by a higher release IMS. The database cannot be selected if it was updated by an IMS operating at a higher release.
NO IC TAKEN AFTER A PITR
Recovery for the database data set or area failed because a point-in-time (PITR) recovery was performed earlier and no image copy was taken afterward. Because backout information may have been deleted from the RECON due to the prior PITR recovery, a new recovery may result in a corrupted database.
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.

If the database data set or area has been removed from the system in Online Change and no longer needs to be recovered, use the /RECOVER REMOVE command to remove the data set or area from the recovery list. If the database data set or area has been removed from the system in Online Change and now must be recovered, use Online Change to add it back to the system; then re-issue the /RECOVER START command.

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 database recovery service 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
The REORG utility ran against the database data set but there is no subsequent image copy data set registered in the RECON.

System action

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

System programmer response

Take the appropriate action based on the specified reason:
AUTHORIZATION FAILED
Determine which IMS did not stop the appropriate database or area, then stop the database or area with the IMS /DBR command.
HALDB MASTER IS STOPPED
The master database for a HALDB partition must be started for recovery. Start the master database and reissue the /RECOVER START command.
IMAGE COPY NOT AVAILABLE
Verify that an image copy is available for the database data set and not migrated to another site.
INVALID RCVTIME
Non-PITR time stamp recoveries cannot fall in the middle of an ALLOC boundary. Adjust the time used for the time stamp recovery or reissue the /RECOVER START command specifying PITR.
LOGS MARKED IN ERROR
Verify that the log data sets are available and not migrated to another site.
NEEDS HIGHER RELEASE LOGS
Logs created 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 PRILOG FOUND
Contact IBM Software Support for assistance.
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 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 database recovery service can be used to recover the DBDS or AREA with the USEDBDS parameter.
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 IMS /DBR command.
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. Then the database recovery service can be used to recover the DBDS or AREA with the USEDBDS parameter.
REORG LATER THAN IMAGE COPY
A DBDS or AREA cannot be recovered using an image copy taken prior to a reorganization.

Module

DFSRWCS0