Now I get the following error trying to recover log backup. The log files are present, they are called BURVIS_LOG.001 and BURVIS_LOG.002, owner sdb user. I have a suspicion that this is because there is no log volume file itself in the directory (LOG_001). However I don't know why that is. There is also no log volume file (physically) on my master database, although I've created it in Database Manager and it shows there in the GUI. ------ medium_put burvlog BURVIS_LOG FILE LOG
[EMAIL PROTECTED]:~/maxdb> dbmcli -d STANDBY -u dbm,dbm -uUTL dbmcli on STANDBY>recover_start burvlog LOG 001 ERR -24988,ERR_SQL: SQL error -902,I/O error 3,Database state: OFFLINE 6,Internal errorcode, Errorcode 9050 "disk_not_accessible" 20017,RestartFilesystem failed with 'I/O error' --- dbmcli on STANDBY> knldiag.err: ------------------------ 2007-01-17 12:21:18 --- Starting GMT 2007-01-17 10:21:18 7.6.00 Build 027-123-124-939 2007-01-17 12:22:26 31672 ERR 11987 IO/READ read error: rc=0, wanted=8192, 'NO ERROR(0)', try again 2007-01-17 12:22:27 31672 ERR 11987 IO/READ read error: rc=0, wanted=8192, 'NO ERROR(0)', try again 2007-01-17 12:22:28 31664 ERR 11000 vattach dev0_vattach returned FALSE 2007-01-17 12:22:28 31664 ERR 20027 IOMan Attach error on log volume 1: Could not open volume 2007-01-17 12:22:28 31664 ERR 3 Admin Database state: OFFLINE 2007-01-17 12:22:28 31664 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible" 2007-01-17 12:22:28 31664 ERR 20017 Admin + RestartFilesystem failed with 'I/O error' 2007-01-17 12:22:34 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL) 2007-01-17 12:22:34 ___ Stopping GMT 2007-01-17 10:22:34 7.6.00 Build 027-123-124-939
