Any help on this would be great !

Could some one figure this out ? Here is the scenario, on my restore everything works fine. Only thing is that I do not see the usual message in the bar_act.log for each logical log restore stating that it completed all the logical logs, it only shows the last logicat log been restored in this case 4503. There are about 15 other logical logs that shows on the ixbar.o file prior to logical log number 4503 and after the very last dbspace. 2003-12-22 08:54:03 3393 3391 /opt/informix/IDS_9.30.UC3/bin/onbar_d -r 2003-12-22 08:54:04 3393 3391 Successfully connected to Storage Manager. 2003-12-22 08:54:05 3393 3391 Begin salvage for log 4503. 2003-12-22 08:54:06 3393 3391 Completed salvage of logical log 4503. 2003-12-22 08:54:08 3393 3391 Successfully connected to Storage Manager. 2003-12-22 08:54:50 3393 3391 Begin cold level 0 restore rootdbs (Storage Manager copy ID: 1072100595 1072100596). 2003-12-22 08:55:05 3393 3391 Completed cold level 0 restore rootdbs. 2003-12-22 08:55:23 3393 3391 Begin cold level 0 restore dbspace1 (Storage Manager copy ID: 1072100732 1072100734). 2003-12-22 08:59:16 3393 3391 Completed cold level 0 restore dbspace1. 2003-12-22 08:59:17 3393 3391 Successfully connected to Storage Manager. 2003-12-22 08:59:21 3393 3391 Begin restore logical log 4503 (Storage Manager copy ID: 1072101244 1072101245). 2003-12-22 08:59:29 3393 3391 Completed restore logical log 4503. 2003-12-22 08:59:36 3393 3391 Completed logical restore. 2003-12-22 08:59:36 3393 3391 ON-Bar is waiting for the database server to exit fast recovery mode. 2003-12-22 08:59:42 3393 3391 ON-Bar is waiting for the database server to exit fast recovery mode. 2003-12-22 08:59:47 3393 3391 ON-Bar is waiting for the database server to exit fast recovery mode. 2003-12-22 08:59:59 3393 3391 /opt/informix/IDS_9.30.UC3/bin/onbar_d complete, r --------------------------------- Do you Yahoo!? Yahoo! Photos - Get your photo on the big screen in Times Square

Hi, have you checked, how long your server actually is in the recovery ? This effect seems to be caused by the server doing quite some work during the log rollback phase. When the logical logs have all be restored and the log records have been applied, then the server checks for (still) open transactions. If any such transactions are found they will now be rolled back to get the system to a consistent state. Depending on how many open transactions there were at the time and how long these have been, this rollback will take some time (it can take even hours, though that has been seen seldomly). In the meantime ON-Bar is waiting for the server to finish up and get into quiescent mode. However, ON-Bar does not know how much rollback work the server has to do. Therefore it waits for a certain time (seems to be 5 seconds which are not changable) and then retries the server check 3 times. This number of retries can be configured in $ONCONFIG by setting parameter BAR_RETRY (default is 3). [ However, this value is most probably used by ON-Bar for other "retry-occasions" as well. So adjusting the value may cause unexpected side-effects. ] [ Contrary to ON-Bar, ontape does not wait for the server to finish the log rollback phase. It will exit rather immediately and return the command prompt to you. Sometimes you can then see (onstat -) that the server is still in recovery ... ] Important in the end is, that eventually the server will become "quiescent" which means that everything worked fine. You can also check the message log file (see MSGPATH parameter in your $ONCONFIG for file location). TIA, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "Mike Smith " <idsquiz@yahoo.com> Sent by: forum.subscriber@iiug.org 23.12.2003 01:21 To: ids@iiug.org cc: Subject: Any help on this would be great ! [2387] Could some one figure this out ? Here is the scenario, on my restore everything works fine. Only thing is that I do not see the usual message in the bar_act.log for each logical log restore stating that it completed all the logical logs, it only shows the last logicat log been restored in this case 4503. There are about 15 other logical logs that shows on the ixbar.o file prior to logical log number 4503 and after the very last dbspace. 2003-12-22 08:54:03 3393 3391 /opt/informix/IDS_9.30.UC3/bin/onbar_d -r 2003-12-22 08:54:04 3393 3391 Successfully connected to Storage Manager. 2003-12-22 08:54:05 3393 3391 Begin salvage for log 4503. 2003-12-22 08:54:06 3393 3391 Completed salvage of logical log 4503. 2003-12-22 08:54:08 3393 3391 Successfully connected to Storage Manager. 2003-12-22 08:54:50 3393 3391 Begin cold level 0 restore rootdbs (Storage Manager copy ID: 1072100595 1072100596). 2003-12-22 08:55:05 3393 3391 Completed cold level 0 restore rootdbs. 2003-12-22 08:55:23 3393 3391 Begin cold level 0 restore dbspace1 (Storage Manager copy ID: 1072100732 1072100734). 2003-12-22 08:59:16 3393 3391 Completed cold level 0 restore dbspace1. 2003-12-22 08:59:17 3393 3391 Successfully connected to Storage Manager. 2003-12-22 08:59:21 3393 3391 Begin restore logical log 4503 (Storage Manager copy ID: 1072101244 1072101245). 2003-12-22 08:59:29 3393 3391 Completed restore logical log 4503. 2003-12-22 08:59:36 3393 3391 Completed logical restore. 2003-12-22 08:59:36 3393 3391 ON-Bar is waiting for the database server to exit fast recovery mode. 2003-12-22 08:59:42 3393 3391 ON-Bar is waiting for the database server to exit fast recovery mode. 2003-12-22 08:59:47 3393 3391 ON-Bar is waiting for the database server to exit fast recovery mode. 2003-12-22 08:59:59 3393 3391 /opt/informix/IDS_9.30.UC3/bin/onbar_d complete, r ---------------------------------