![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We have an RDB V6.1 database running on VMS V5.5-2h4 (for hardware reasons) that we suddenly cannot connect to. When attempting to connect using our application or interactively using $sql$, the invoking process is aborted. If I connect from another system, I get an SQL-F-ERRATTDEF (Could not use database file) followed by an RDB-F-IO_ERROR (input or output error) followed by a LINKABORT message. The process also gets aborted if I do an RMU/VERIFY, RMU/VERIFY/ROOT, ro RMU/VERIFY/ALL. I *CAN* do an RMU/DUMP/HEADER and everything in the header looks okay. Does anyone have any ideas to try before I restore to my last backup (3 months old)? |
#3
| |||
| |||
|
|
We have an RDB V6.1 database running on VMS V5.5-2h4 (for hardware reasons) that we suddenly cannot connect to. When attempting to connect using our application or interactively using $sql$, the invoking process is aborted. If I connect from another system, I get an SQL-F-ERRATTDEF (Could not use database file) followed by an RDB-F-IO_ERROR (input or output error) followed by a LINKABORT message. The process also gets aborted if I do an RMU/VERIFY, RMU/VERIFY/ROOT, ro RMU/VERIFY/ALL. I *CAN* do an RMU/DUMP/HEADER and everything in the header looks okay. Does anyone have any ideas to try before I restore to my last backup (3 months old)? |
![]() |
| Thread Tools | |
| Display Modes | |
| |