hi,

I have the following setup, and during a (too) massive delete process,
things died and now i can't seem get things going again...

RDB Version: Oracle Rdb V7.0-14
VMS Version: VMS Version V7.1


An update process died, with a bugcheck dump, as follows:

%RDMS-I-BUGCHKDMP, generating bugcheck dump file
PATH$DB_JNL_DEV:[DB.BOB]RDSBUGCHK.DMP;

The .DMP file had the following error msgs:

***** Exception at 00642E87 : PIOABW$SYNCH_PAGE + 00000298
%RDMS-F-CANTWRITEDBS, error writing pages 198:8587-8587
-SYSTEM-F-EXQUOTA, process quota exceeded

and..

***** Exception at 00642AD9 : PIOABW$WRITE_PAGES + 00000182
%RDMS-F-CANTWRITEDBS, error writing pages 198:8587-8587
-SYSTEM-F-EXQUOTA, process quota exceeded


now when I try to access the database, I get:

$ sql
SQL> set verify;
SQL> declare transaction read only;
%SQL-F-ERRATTDEF, Could not use database file specified by SQL$DATABASE
-RDB-F-SYS_REQUEST, error from system services request
-RDMS-F-DBNOTOPEN, database is not open for access

so I try to open it:

$ rmu/open sql$database /access=restricted
%RDMS-F-TERMINATE, database recovery failed -- access to database denied by
monitor

so I try to close it:

$ rmu/close/abort=delprc/wait sql$database
%RDMS-F-TERMINATE, database recovery failed -- access to database denied by
monitor

check users:
$ rmu/dump/users sql$database
Active user with process ID 0000105A (recovery in progress)
Stream ID is 2
Monitor ID is 1
Transaction ID is 582
Recovery journal filename is
"PATH$DB_JNL_DEV:[DB.BOB]MS$00014C47455C.RUJ;1"
Read/write transaction in progress
Last Process quiet-point was AIJ sequence 4628
Transaction sequence number is 0:4585043

Does the process exist?:
$ show process/id=105a
%SYSTEM-W-NONEXPR, nonexistent process


Does the journal file exist?
$ dir PATH$DB_JNL_DEV:[DB.BOB]MS$00014C47455C.RUJ
Directory PATH$DB_JNL_DEV:[DB.BOB]

MS$00014C47455C.RUJ;1

Total of 1 file.


I've tried stopping/restarting the rdb monitor process, and rebooting the
machine, and still the problem persists. Any help would be greatly
appreciated.


thanks,

John

I think looks like the DBR processes are failing. Enable
DBR logging and also look to see if you get a DBR dump
file (the monitor log should at least give a hint here).
Get in touch directly with Oracle Rdb support for more
assistance.

John Thomas wrote: