Can't complete recovery following successful onbar restore
Posted in 2004
Topics: Backup & Restore, Server Administration, Logging & Checkpoints, Platform-Specific Issues
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 SerialNumber 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 = : Noconnections 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 = : Noconnections are allowed in Dynamic Server quiescent mode.
21:09:48 IBM Informix Dynamic Server Initialized -- Shared MemoryInitialized.
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
Neil Truby wrote:
> 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
>
>
What have you got in the bar_act.log??
"TheBiggestPotatoeYouHaveEverSeen" <TBP@Nospam.Nothere.Co.Uk> wrote in message news:3ZgSb.13468$JL4.110465@newsfep4-glfd.server.ntli.net... > > > 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%)
"Neil Truby" <neil.truby@ardenta.com> wrote in message news:<bvc6mh$qntoa$1@ID-162943.news.uni-berlin.de>... > "TheBiggestPotatoeYouHaveEverSeen" <TBP@Nospam.Nothere.Co.Uk> wrote in > message news:3ZgSb.13468$JL4.110465@newsfep4-glfd.server.ntli.net... > > > > > 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 <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
"Neil Truby" <neil.truby@ardenta.com> wrote in message
news:bvbv2i$pcl92$1@ID-162943.news.uni-berlin.de...
> 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 ?
Thanks to everyone who replied.
The answer in the end was ... RTFM :-(
The correct syntax was onbar -r -w -p # physical restore only.