RE: Trouble restoring database on test/recovery system

> So I tried oninit -r and I get a different problem, my log files fill > up and then the process stops. We are using the alarm script > to backup > the logs to disk. This doesn't seem to work and I can't seem to do > anything to get the log file cleared and remove the Blocked: CKPT. > There has been no change in the alarm script in like 2-3 years. > > How can I get the database up and working again? Why did the ontape > -r not work this time, what might have cause this? Should I try a > new ontape -r? or something else. Any help or suggestions are > welcomed. I had exactly the same problem several months ago. I discovered LTAPEDEV was set to a non-existing device. When I changed LTAPEDEV to /dev/null - or the device of your choice - and restarted the engine, all was well. Check the value of LTAPEDEV in the onconfig file and make sure it is set to a valid device. Mike Badar ESRI Professional Services 1 International Ct. Broomfield, CO 80021 mbadar@esri.com 303-449-7779 www.esri.com > > Norma Jean Sebastian > ERP Support Administration > GIS- Enterprise Technical Services > > > -----Original Message----- > From: informix-list-bounces@iiug.org > [mailto:informix-list-bounces@iiug.org] On Behalf Of jda > Sent: Tuesday, November 28, 2006 11:02 AM > To: informix-list@iiug.org > Subject: Trouble restoring database on test/recovery system > > Trouble restoring database on test system (IDS 9.40.HC3 on HP-UX 11i > (11v1) > > Yesterday when I was restoring the production database on the > test/recovery server I got some errors I never gotten before. I have > done this processes 20-30 times in the last 2 years and never had any > problems. > > I used an ontape -r to restore the database and that process finished > and ended at the command prompt. > > When I tried to bring the database up in multi-user mode I get the > following errors in the log file: > > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp0' > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp1' > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp2' > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp3' > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp4' > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp5' > 14:59:58 Warning: Invalid (non-existent/blobspace/disabled) dbspace> listed in DBSPACETEMP: 'temp6' > > Which tells me the engine has lost its mind and doesn't know about > temp0-temp6. We have had these 7 temp spaces for years and I know of > no changes to the onconf file. I have tried onmode onmode -yuk and > then a new oninit. I even rebooted the server, I still get > these error > when I do a onint. > > So I tried oninit -r and I get a different problem, my log files fill > up and then the process stops. We are using the alarm script > to backup > the logs to disk. This doesn't seem to work and I can't seem to do > anything to get the log file cleared and remove the Blocked: CKPT. > There has been no change in the alarm script in like 2-3 years. > > How can I get the database up and working again? Why did the ontape > -r not work this time, what might have cause this? Should I try a > new ontape -r? or something else. Any help or suggestions are > welcomed. > > > adamski cars: onstat -l > > IBM Informix Dynamic Server Version 9.40.HC3 -- Fast > Recovery (CKPT > REQ) -- Up 14:47:41 -- 1027988 Kbytes > Blocked:CKPT > > Physical Logging > Buffer bufused bufsize numpages numwrits pages/io > P-1 0 16 0 0 0.00 > phybegin physize phypos phyused %used > 13:53 67569 53105 0 0.00 > > Logical Logging > Buffer bufused bufsize numrecs numpages numwrits > recs/pages pages/io > L-1 0 16 0 0 0 0.0 0.0 > Subsystem numrecs Log Space used > > address number flags uniqid begin size used > %used > 9e23cfc8 51 F------ 0 12:53 4096 0 > 0.00 > 9f26a128 52 F------ 0 12:4149 4096 0 > 0.00 > 9f26a168 53 F------ 0 12:8245 4096 0 > 0.00 > 9f26a1a8 54 F------ 0 12:12341 4096 0 > 0.00 > 9f26a1e8 55 F------ 0 12:16437 4096 0 > 0.00 > 9f26a228 56 F------ 0 12:20533 4096 0 > 0.00 > 9f26a268 57 F------ 0 12:24629 4096 0 > 0.00 > 9f26a2a8 58 F------ 0 12:28725 4096 0 > 0.00 > 9f26a2e8 59 F------ 0 12:32821 4096 0 > 0.00 > 9f26a328 60 F------ 0 12:36917 4096 0 > 0.00 > 9f26a368 61 F------ 0 12:41013 4096 0 > 0.00 > 9f26a3a8 62 F------ 0 12:45109 4096 0 > 0.00 > 9f26a3e8 63 F------ 0 12:49205 4096 0 > 0.00 > 9f26a428 64 F------ 0 12:53301 4096 0 > 0.00 > 9f26a468 65 F------ 0 12:57397 4096 0 > 0.00 > 9f26a4a8 66 F------ 0 12:61493 4096 0 > 0.00 > 9f26a4e8 67 F------ 0 12:65589 4096 0 > 0.00 > 9f26a528 68 F------ 0 12:69685 4096 0 > 0.00 > 9f26a568 69 F------ 0 12:73781 4096 0 > 0.00 > 9f26a5a8 70 F------ 0 12:77877 4096 0 > 0.00 > 9f26a5e8 71 F------ 0 12:81973 4096 0 > 0.00 > 9f26a628 72 F------ 0 12:86069 4096 0 > 0.00 > 9f26a668 73 F------ 0 12:90165 4096 0 > 0.00 > 9f26a6a8 74 F------ 0 12:94261 4096 0 > 0.00 > 9f26a6e8 75 F------ 0 12:98357 4096 0 > 0.00 > 9f26a728 76 F------ 0 12:102453 4096 0 > 0.00 > 9f26a768 77 F------ 0 12:106549 4096 0 > 0.00 > 9f26a7a8 78 F------ 0 12:110645 4096 0 > 0.00 > 9f26a7e8 79 F------ 0 12:114741 4096 0 > 0.00 > 9f26a828 80 F------ 0 12:118837 4096 0 > 0.00 > 9f26a868 81 F------ 0 12:122933 4096 0 > 0.00 > 9f26a8a8 82 F------ 0 12:127029 4096 0 > 0.00 > 9f26a8e8 83 F------ 0 12:131125 4096 0 > 0.00 > 9f26a928 84 F------ 0 12:135221 4096 0

Mike Badar wrote: > I had exactly the same problem several months ago. I discovered > LTAPEDEV was set to a non-existing device. When I changed LTAPEDEV to > /dev/null - or the device of your choice - and restarted the engine, all > was well. Check the value of LTAPEDEV in the onconfig file and make > sure it is set to a valid device. > Thanks that was the problem, somehow the location we write the logs to got messed up. For now I'm got LTAPEDEV set to /dev/null and the engine came up. After I get the table data that got corrupted by one of our developers testing on the live database, I will have to figure out what wrong with the path we had on LTAPEDEV. Thanks again for your help and solution. John