Hi, >> Ended up restoring from the day before's database backup. >> Gonna be some upset people in the A.M. for future you might want to either change logmode to rollforward or simply perform incremental database backups between full ones. Limitation: much largere logvolumes necessary. I have scheduled incremental database backups each 2 hours, with disk files as target device. This will not help in case of disaster, but suits perfectly for software problems like yours. This backups tend to be very small and quick - look at Q DB F=D; Changed Since Last Backup; to see how small this sort of backups vere at your site. Limitation: only 32 incremental backups are allowed, so you will not be able to schedule it very often. best regards juraj salak -----Ursprüngliche Nachricht----- Von: William Boyer [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 16. April 2001 04:30 An: [EMAIL PROTECTED] Betreff: More LOADDB woes!!! After running for almost 23-hours, the LOADDB process terminated with: ANR9999D PVRNTP(2536): RC 0x0 Reading cartridge block 00026776 to ddname SYS00040. ANR0664E LOADDB: Media not accessible in accessing data storage. ANR1364I Input volume M00750 closed. ANR5209I Dismounting volume M00750 (read-only access). ANR9999D DLLOAD(1249): Premature End of Dump - Missing Volumes ? VCS0201E **** DATA LOST - VCSS NOT OPERATIVE **** ANR4032I LOADDB: Copied 2236928 database records. ANR4033I LOADDB: Copied 351 bit vectors. ANR4035I LOADDB: Encountered 0 bad database records. ANR4036I LOADDB: Copied 78859100 database entries. ANR4037I LOADDB: 4919 Megabytes copied. ANR4005E LOADDB: Database load process terminated due to error (-1). ANR2106I : Quiescing database update activity. ANR2107I : Database update activity is now quiesced. Ended up restoring from the day before's database backup. Gonna be some upset people in the A.M. Bill Boyer "Some days you are the bug, some days you are the windshield." - ??