onbar restore problem

Hi, I use onbar to do the redirect restore. and I see below message twice, why? thanks for your time . Clearing the physical and logical logs has started Cleared 263968 MB of the physical and logical logs in 392 seconds 1) run "onbar -r -rename -f ./list.txt -t "2016-10-09 23:56:50" 11/02/16 22:10:45 Checkpoint Completed: duration was 0 seconds. 11/02/16 22:10:45 Wed Nov 2 - loguniq 518235, logpos 0x1f84560, timestamp: 0x4645602f Interval: 1270144 11/02/16 22:10:45 Maximum server connections 0 11/02/16 22:10:45 Start Logical Recovery - Start Log 518235, End Log ? 11/02/16 22:10:45 Starting Log Position - 518235 0x1f84560 11/02/16 22:10:45 Clearing the physical and logical logs has started 11/02/16 22:17:17 Cleared 263968 MB of the physical and logical logs in 392 seconds 11/02/16 22:17:17 Suspending Logical Restore 11/02/16 22:17:22 Resuming Logical Restore 11/02/16 22:17:24 Suspending Logical Restore 11/02/16 22:17:29 Resuming Logical Restore 11/02/16 22:17:30 Suspending Logical Restore 11/02/16 22:17:35 Resuming Logical Restore 11/02/16 22:17:36 Suspending Logical Restore 11/02/16 22:17:41 Resuming Logical Restore 11/02/16 22:17:42 Suspending Logical Restore 11/02/16 22:17:47 Resuming Logical Restore 11/02/16 22:17:48 Suspending Logical Restore 11/02/16 22:17:53 Resuming Logical Restore 11/02/16 22:17:55 Suspending Logical Restore 11/02/16 22:18:00 Resuming Logical Restore 11/02/16 22:18:01 Suspending Logical Restore 11/02/16 22:18:06 Resuming Logical Restore 11/02/16 22:18:07 Suspending Logical Restore 11/02/16 22:18:12 Resuming Logical Restore 11/02/16 22:18:13 Suspending Logical Restore 11/02/16 22:18:18 Resuming Logical Restore 11/02/16 22:18:19 Suspending Logical Restore 11/02/16 22:18:24 Resuming Logical Restore 11/02/16 22:18:26 Suspending Logical Restore 11/02/16 22:18:31 Resuming Logical Restore 11/02/16 22:18:32 Suspending Logical Restore 11/02/16 22:18:37 Resuming Logical Restore 11/02/16 22:18:38 Suspending Logical Restore 11/02/16 22:18:43 Resuming Logical Restore 11/02/16 22:18:44 Suspending Logical Restore 11/02/16 22:18:49 Resuming Logical Restore 11/02/16 22:18:50 Suspending Logical Restore 11/02/16 22:18:55 Resuming Logical Restore 11/02/16 22:18:57 Suspending Logical Restore 11/02/16 22:19:02 Resuming Logical Restore 11/02/16 22:19:03 Suspending Logical Restore 11/02/16 22:19:08 Resuming Logical Restore 11/02/16 22:19:09 Suspending Logical Restore 11/02/16 22:19:14 Resuming Logical Restore 11/02/16 22:19:15 Suspending Logical Restore 2, onbar -r -l -X # stop the logical restore Thu Nov 3 08:02:20 2016 11/03/16 08:02:20 Resuming Logical Restore 11/03/16 08:02:20 rsrecvr.c 5028 set EOF 11/03/16 08:02:21 No logical log restore will be performed. 11/03/16 08:02:21 Clearing the physical and logical logs has started 11/03/16 08:08:27 Cleared 263968 MB of the physical and logical logs in 365 seconds 11/03/16 08:08:30 Physical Recovery Started at Page (3:5042117). 11/03/16 08:08:30 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored. 11/03/16 08:08:30 Logical Recovery Started. 11/03/16 08:08:30 200 recovery worker threads will be started. 11/03/16 08:08:31 Logical Recovery has reached the transaction cleanup phase. 11/03/16 08:08:56 Logical Recovery Complete. 0 Committed, 1 Rolled Back, 0 Open, 0 Bad Locks 11/03/16 08:08:57 Bringing system to Quiescent Mode with no Logical Restore. 11/03/16 08:08:58 Quiescent Mode

Hmmmm, three things to annotate: - onbar -r ... -t <point=5Fin=5Ftime> should go through physical and lo= g.=20 restore and bring you to quiescent mode anyway, no extra command should be = required - what are all those Suspending and Resuming Logical Restore messages?=20 What's going on there, why don't we see any sign of real logical restore=20 taking place, like checkpoint messages? - eventually you're reaching quiescent mode, with exactly that "onbar -r=20 -l -X" command - why now? I'd not pay too much attention on that clearing of phys. and log. logs,=20 that's just done to avoid confusion later and shouldn't harm your restore. From what's displayed here, I'd not be sure even a single logical log=20 really gets restored, maybe this is the reason for "Logical Log File not=20 found." ? But then again, you'd not even see this message any more ? Please consult your bar=5Fact.log (onconfig: BAR=5FACT=5FLOG param) for wh= at=20 the restore really did and restored, and maybe other interesting messages. HTH, Andreas From: "CHUAN LU" <luchuan@cn.ibm.com> To: ids@iiug.org Date: 22.11.2016 03:00 Subject: onbar restore problem [38193] Sent by: ids-bounces@iiug.org Hi,=20 I use onbar to do the redirect restore. and I see below message twice,=20 why?=20 thanks for your time .=20 Clearing the physical and logical logs has started=20 Cleared 263968 MB of the physical and logical logs in 392 seconds=20 1) run "onbar -r -rename -f ./list.txt -t "2016-10-09 23:56:50"=20 11/02/16 22:10:45 Checkpoint Completed: duration was 0 seconds.=20 11/02/16 22:10:45 Wed Nov 2 - loguniq 518235, logpos 0x1f84560, timestamp: = 0x4645602f Interval: 1270144=20 11/02/16 22:10:45 Maximum server connections 0=20 11/02/16 22:10:45 Start Logical Recovery - Start Log 518235, End Log ?=20 11/02/16 22:10:45 Starting Log Position - 518235 0x1f84560=20 11/02/16 22:10:45 Clearing the physical and logical logs has started=20 11/02/16 22:17:17 Cleared 263968 MB of the physical and logical logs in=20 392=20 seconds=20 11/02/16 22:17:17 Suspending Logical Restore=20 11/02/16 22:17:22 Resuming Logical Restore=20 11/02/16 22:17:24 Suspending Logical Restore=20 11/02/16 22:17:29 Resuming Logical Restore=20 11/02/16 22:17:30 Suspending Logical Restore=20 11/02/16 22:17:35 Resuming Logical Restore=20 11/02/16 22:17:36 Suspending Logical Restore=20 11/02/16 22:17:41 Resuming Logical Restore=20 11/02/16 22:17:42 Suspending Logical Restore=20 11/02/16 22:17:47 Resuming Logical Restore=20 11/02/16 22:17:48 Suspending Logical Restore=20 11/02/16 22:17:53 Resuming Logical Restore=20 11/02/16 22:17:55 Suspending Logical Restore=20 11/02/16 22:18:00 Resuming Logical Restore=20 11/02/16 22:18:01 Suspending Logical Restore=20 11/02/16 22:18:06 Resuming Logical Restore=20 11/02/16 22:18:07 Suspending Logical Restore=20 11/02/16 22:18:12 Resuming Logical Restore=20 11/02/16 22:18:13 Suspending Logical Restore=20 11/02/16 22:18:18 Resuming Logical Restore=20 11/02/16 22:18:19 Suspending Logical Restore=20 11/02/16 22:18:24 Resuming Logical Restore=20 11/02/16 22:18:26 Suspending Logical Restore=20 11/02/16 22:18:31 Resuming Logical Restore=20 11/02/16 22:18:32 Suspending Logical Restore=20 11/02/16 22:18:37 Resuming Logical Restore=20 11/02/16 22:18:38 Suspending Logical Restore=20 11/02/16 22:18:43 Resuming Logical Restore=20 11/02/16 22:18:44 Suspending Logical Restore=20 11/02/16 22:18:49 Resuming Logical Restore=20 11/02/16 22:18:50 Suspending Logical Restore=20 11/02/16 22:18:55 Resuming Logical Restore=20 11/02/16 22:18:57 Suspending Logical Restore=20 11/02/16 22:19:02 Resuming Logical Restore=20 11/02/16 22:19:03 Suspending Logical Restore=20 11/02/16 22:19:08 Resuming Logical Restore=20 11/02/16 22:19:09 Suspending Logical Restore=20 11/02/16 22:19:14 Resuming Logical Restore=20 11/02/16 22:19:15 Suspending Logical Restore=20 2, onbar -r -l -X # stop the logical restore=20 Thu Nov 3 08:02:20 2016=20 11/03/16 08:02:20 Resuming Logical Restore=20 11/03/16 08:02:20 rsrecvr.c 5028 set EOF=20 11/03/16 08:02:21 No logical log restore will be performed.=20 11/03/16 08:02:21 Clearing the physical and logical logs has started=20 11/03/16 08:08:27 Cleared 263968 MB of the physical and logical logs in=20 365=20 seconds=20 11/03/16 08:08:30 Physical Recovery Started at Page (3:5042117).=20 11/03/16 08:08:30 Physical Recovery Complete: 0 Pages Examined, 0 Pages=20 Restored.=20 11/03/16 08:08:30 Logical Recovery Started.=20 11/03/16 08:08:30 200 recovery worker threads will be started.=20 11/03/16 08:08:31 Logical Recovery has reached the transaction cleanup=20 phase.=20 11/03/16 08:08:56 Logical Recovery Complete.=20 0 Committed, 1 Rolled Back, 0 Open, 0 Bad Locks=20 11/03/16 08:08:57 Bringing system to Quiescent Mode with no Logical=20 Restore.=20 11/03/16 08:08:58 Quiescent Mode=20 ***************************************************************************= ****=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20