RDBPROD: RMU/RECOVER Fails With RMU-E-RECFAILED And FAIJBL Queue Is Not Empty
(Doc ID 331488.1)
Last updated on AUGUST 24, 2021
Applies to:Oracle Rdb Server on OpenVMS - Version 7.0 to 184.108.40.206 [Release 7.0 to 7.1]
HP OpenVMS Itanium
HP OpenVMS Alpha
HP OpenVMS VAX
HP VAX OpenVMSHP OpenVMS ItaniumHP OpenVMS Alpha
RMU/RECOVER bugchecks with the following footprint:
Alpha OpenVMS 7.3-2
Oracle Rdb Server 220.127.116.11
Got a RMUBUGCHK.DMP
COSI-F-BUGCHECK, internal consistency failure
Exception occurred at KUTREC$ABORT + 0000054C
Called from KUTREC$CLEANUP + 00000814
Called from RMUCLI$RECOVER + 000005E8
Called from RMU_DISPATCH + 00000BA4
No BLR for current query found
Failed AIJBL queue not empty
Running image RMU.EXE
This bugcheck was received on a copy of the production database which is kept up to date by applying the journals from the production database. Some records could not be recovered because there was no space on the database pages, thus they were placed in the failed AIJBL queue. Because Rdb wasn't able to recover those records at the end of the RMU/RECOVER, Rdb bugchecked which is normal behaviour.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document