 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / Informix Topics / January 2004Can't complete recovery following successful onbar restore
9.40 FC2 on HP-UX 11.11: I've done a 12-hour whole database restore (onbar -r -w). At the end I got these messages: 20:39:15 Maximum server connections 0 20:39:15 Start Logical Recovery - Start Log 113124, End Log ? 20:39:15 Starting Log Position - 113124 0x3abf018 20:39:15 Clearing the physical and logical logs has started 20:41:06 Cleared 2548 MB of the physical and logical logs in 111 seconds 20:43:12 Suspending Logical Restore Nothing until I tried onmode -m, when I got 21:05:15 No logical log restore will be performed. 21:05:15 A Logical Restore is active. 21:05:15 Cannot change to On-Line Mode. 21:08:59 No logical log restore will be performed. 21:08:59 A Logical Restore is active. 21:08:59 Cannot change to On-Line Mode. Eventually I stopped then re-started the engine, but I get a shared-memory failure, though nothing discernibly useful from the logs: 21:09:09 IBM Informix Dynamic Server Stopped. 21:09:31 IBM Informix Dynamic Server Started. 21:09:38 Segment locked: addr=0xc000000000478000, size=1080684544 Thu Jan 29 21:09:40 2004 21:09:40 Event alarms enabled. ALARMPROG = '/opt/informix/9.21/etc/log_full.sh' 21:09:40 Booting Language <c> from module <> 21:09:40 Loading Module <CNULL> 21:09:40 Booting Language <builtin> from module <> 21:09:40 Loading Module <BUILTINNULL> 21:09:44 IBM Informix Dynamic Server Version 9.40.FC2 Software Serial Number AAA#B000000 21:09:44 HPUX Version B.11.11 -> Using flag/select style KAIO 21:09:44 HP KAIO concurrent requests changed from 1000 to 2300 21:09:46 (6) connection rejected - no calls allowed for sqlexec 21:09:46 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 21:09:47 (12) connection rejected - no calls allowed for sqlexec 21:09:47 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 21:09:48 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized. 21:09:48 Physical Recovery Started at Page (2:35801). 21:09:48 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 21:09:48 Logical Recovery Started. 21:09:48 10 recovery worker threads will be started. 21:09:51 Logical Recovery has reached the transaction cleanup phase. 21:09:51 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks Any ideas how I can get the engine on line? Probably Tech Support can intervene, but it really shouldn't be this difficult ... thanks Neil > 9.40 FC2 on HP-UX 11.11: > [quoted text clipped - 63 lines] > thanks > Neil What have you got in the bar_act.log?? > What have you got in the bar_act.log?? Hmm, Good question. Reproduced below, which suggests to me that I interrupted some vital task that Data Protector was going to get around to eventually, but had more important calls on its time than restoring my databases ...! 2004-01-29 21:09:23 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:09:23 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:09:35 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:09:35 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:09:47 29814 29812 SQL 4294940294 No connections are allowed in Dynamic Server quiescent mode. 2004-01-29 21:09:48 29814 29812 SQL 4294940294 No connections are allowed in Dynamic Server quiescent mode. 2004-01-29 21:09:49 29814 29812 SQL 4294940294 No connections are allowed in Dynamic Server quiescent mode. 2004-01-29 21:10:08 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:10:08 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:10:20 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:10:20 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:10:32 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:10:32 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:10:44 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:10:44 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:10:49 29814 29812 SQL 4294940294 No connections are allowed in Dynamic Server quiescent mode. 2004-01-29 21:10:50 29814 29812 SQL 4294940294 No connections are allowed in Dynamic Server quiescent mode. 2004-01-29 21:11:08 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:11:08 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:11:20 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:11:20 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:11:32 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:11:32 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:11:44 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:11:44 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:11:57 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:11:57 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:12:09 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:12:09 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:12:21 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:12:21 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:12:33 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:12:33 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:12:45 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:12:45 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:12:57 29814 29812 SQL 4294941708 The appl process cannot connect to Dynamic Server lawson_live_shm. 2004-01-29 21:12:57 29814 29812 ISAM 2 No such file or directory 2004-01-29 21:12:57 29814 29812 /opt/informix/9.40/bin/onbar_d complete, returning 0 (0x00) 2004-01-29 22:08:08 2701 2699 /opt/informix/9.40/bin/onbar_d -b -L 0 -w 2004-01-29 22:08:08 2701 2699 Logical Logs will not be backed up / salvaged because LTAPEDEV value is /dev/null 2004-01-29 22:08:08 2701 2699 Working with omni as generic storage manager. 2004-01-29 22:08:09 2701 2699 Begin level 0 backup rootdbs. 2004-01-29 22:08:09 2701 2699 Successfully connected to Storage Manager. 2004-01-29 22:08:18 2701 2699 Completed level 0 backup rootdbs (Storage Manager copy ID: 39 2004001029). 2004-01-29 22:08:18 2701 2699 Begin level 0 backup llogdbs. 2004-01-29 22:08:21 2701 2699 Completed level 0 backup llogdbs (Storage Manager copy ID: 39 2004001029). 2004-01-29 22:08:21 2701 2699 Begin level 0 backup physdbs. 2004-01-29 22:08:23 2701 2699 Completed level 0 backup physdbs (Storage Manager copy ID: 39 2004001029). crap (21%) > > What have you got in the bar_act.log?? > [quoted text clipped - 9 lines] > cannot connect to Dynamic Server lawson_live_shm. > 2004-01-29 21:09:35 29814 29812 ISAM 2 No such file or directory <SNIP> Last time I saw errors like one of our customers was trying to restore a 9.21.FC5 backup to a 9.20.FC3 instance. I've seen successful version migrations when the difference was very small (i.e. 9.21.FC5 --> 9.21.FC4), but I would avoid it if possible. Hope this information helps. Brice Avila Minneapolis, Minnesota Current temperature: -24 degrees Fahrenheit Have you run the following command "ipcs |grep informix". If after you run "oninit -yuk" to verify that the database is down and you see a file that looks similar to the following: s 137625608 00000000 --ra-ra---- root informix, have the system admin remove any and all the shared memory segments. This problem usually occurs when the database crashes. I believe the command that the system admin must run to remove the shared memory segments that are still allocated is: ipcsrm -s number value after the s. Rerun the command "ipcs |grep informix", the command should return no shared memory segments. Next step is to try and bring the engine on-line. Good luck. Barbara A. McCabe-Reed breed@sikorsky.com (203) 386-6431 -----Original Message----- From: Neil Truby [mailto:neil.truby@ardenta.com] Sent: Thursday, January 29, 2004 4:48 PM To: informix-list@iiug.org Subject: Can't complete recovery following successful onbar restore 9.40 FC2 on HP-UX 11.11: I've done a 12-hour whole database restore (onbar -r -w). At the end I got these messages: 20:39:15 Maximum server connections 0 20:39:15 Start Logical Recovery - Start Log 113124, End Log ? 20:39:15 Starting Log Position - 113124 0x3abf018 20:39:15 Clearing the physical and logical logs has started 20:41:06 Cleared 2548 MB of the physical and logical logs in 111 seconds 20:43:12 Suspending Logical Restore Nothing until I tried onmode -m, when I got 21:05:15 No logical log restore will be performed. 21:05:15 A Logical Restore is active. 21:05:15 Cannot change to On-Line Mode. 21:08:59 No logical log restore will be performed. 21:08:59 A Logical Restore is active. 21:08:59 Cannot change to On-Line Mode. Eventually I stopped then re-started the engine, but I get a shared-memory failure, though nothing discernibly useful from the logs: 21:09:09 IBM Informix Dynamic Server Stopped. 21:09:31 IBM Informix Dynamic Server Started. 21:09:38 Segment locked: addr=0xc000000000478000, size=1080684544 Thu Jan 29 21:09:40 2004 21:09:40 Event alarms enabled. ALARMPROG = '/opt/informix/9.21/etc/log_full.sh' 21:09:40 Booting Language <c> from module <> 21:09:40 Loading Module <CNULL> 21:09:40 Booting Language <builtin> from module <> 21:09:40 Loading Module <BUILTINNULL> 21:09:44 IBM Informix Dynamic Server Version 9.40.FC2 Software Serial Number AAA#B000000 21:09:44 HPUX Version B.11.11 -> Using flag/select style KAIO 21:09:44 HP KAIO concurrent requests changed from 1000 to 2300 21:09:46 (6) connection rejected - no calls allowed for sqlexec 21:09:46 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 21:09:47 (12) connection rejected - no calls allowed for sqlexec 21:09:47 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 21:09:48 IBM Informix Dynamic Server Initialized -- Shared Memory Initialized. 21:09:48 Physical Recovery Started at Page (2:35801). 21:09:48 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 21:09:48 Logical Recovery Started. 21:09:48 10 recovery worker threads will be started. 21:09:51 Logical Recovery has reached the transaction cleanup phase. 21:09:51 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks Any ideas how I can get the engine on line? Probably Tech Support can intervene, but it really shouldn't be this difficult ... thanks Neil sending to informix-list I have seen this a few times when I am doing multiple restores of live databases to a backup server. My solution has been to reboot the server and start again. The scripts I use delete all devices and volumes before it starts, so is always starting from a clean position. Easy to do on a test server. I have the luxury of being the only one to know when I screw Up :-) Colin Bull c.bull@videonetworks.com > -----Original Message----- > From: owner-informix-list@iiug.org [quoted text clipped - 74 lines] > thanks > Neil sending to informix-list > 9.40 FC2 on HP-UX 11.11: > [quoted text clipped - 4 lines] > 20:39:15 Maximum server connections 0 > 20:39:15 Start Logical Recovery - Start Log 113124, End Log ? Thanks to everyone who replied. The answer in the end was ... RTFM :-( The correct syntax was onbar -r -w -p # physical restore only. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.