RE: CKPT REQ stops ontape -r recovery

Please post your onstat -d output .... so we can see what has successfully restored and what has not. Are there any other files in your $INFORMIXDIR or $INFORMIXDIR/etc with relatively recent timestamps that might have output to help understand the problem? if so, please post that info. Thanks, Norma Jean -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Beau Nanaz Sent: Saturday, September 16, 2006 10:09 PM To: informix-list@iiug.org Subject: CKPT REQ stops ontape -r recovery Greetings, Family. I am trying to "clone" a server from the ontape backup set of another. It was going great for about 11 hours and then seems to have stopped all actvity. From the online.log: 01:20:38 Maximum server connections 0 01:32:39 Checkpoint Completed: duration was 0 seconds. 01:32:39 Checkpoint loguniq 494406, logpos 0xe0d018, timestamp:-2141117962 01:32:39 Maximum server connections 0 01:44:52 Checkpoint Completed: duration was 0 seconds. 01:44:52 Checkpoint loguniq 494406, logpos 0xe0d018, timestamp:-2141117565 01:44:52 Maximum server connections 0 ---------------That's the last activity at 1:44 AM - it stops checkpointing after that. I have a script to monitor the total output by dbspace by filtering the output of onstat -g iof. It shows me that there is no chunk I/O taking place. For the first few hours of the recovery process I was runnning this script every few minutes and watching the I/O count rise at a nice clip. Here's the last couple of lines of my output: ---- DBSpace totalops dskread dskwrite io/s ... DBSP thddb_tscon041dbs 589820 0 589820 4.80 DBSP thddb_tscon034dbs 589820 0 589820 4.80 Total IO-Stats: 33318739 122 33318617 275.30 That total I/O count, 33,318,739 has not changed since I noticed the CKPT REQ about an hour ago. I found a old thread from 2003 that sounded similar to this but that one ended when the poster realized there was I/O activity on the chunks. No such luck here. I have tried "onmode -c unblock", to no avail. I did look into the undocumentd "onmode -O" but it gave a dire warning about marking chunks/dbspaces down and requiring a recovery. That would be a useless exercise for me so I answered N and exited. Any other ideas? You have my rapt attention! ;-( Thanks much. -- J.S. PS. Here's my script. I will see about posting it to the IIUG library when I get a round tuitt. #!/usr/bin/ksh # monitorDBspaceIO.sh # onstat -g iof|tail +6 |gawk ' BEGIN { total_io = 0 iopersec = 0.0 } $3 != 0 { #print total_io += $3 dskread += $4 dskwrite += $5 iopersec += $6 split($2, q_chunk, ".") cur_dbspace = q_chunk[2] dbspace_total_io[cur_dbspace] += $3 dbspace_dskread[cur_dbspace] += $4 dbspace_dskwrite[cur_dbspace] += $5 dbspace_iopersec[cur_dbspace] += $6 } END { printf("---- DBSpace totalops dskread dskwrite io/s\\n") for (dbsname in dbspace_total_io) { if (length(dbsname) == 0) continue #printf ("dbsname is <%s>\\n", dbsname) printf("DBSP %s %d %d %d %7.2f\\n", dbsname, dbspace_total_io[dbsname], dbspace_dskread[dbsname], dbspace_dskwrite[dbsname], dbspace_iopersec[dbsname]) } printf ("\\nTotal IO-Stats: %d %d %d %7.2f\\n", total_io, dskread, dskwrite, iopersec) } ' BTW, the above output had been piped through "beautify-unl.sh -db", which is available at IIUG. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================