Hi All,
We have a horribly corrupt table in one of our clients databases. In order to fix this issue I need to restore the database onto another server, check the data integrity, create a new table in the production database and copy the records using SQL.
However, I have hit a brick wall with the restore on the 2nd server. Both servers are running IDS 9.30 (I know, not supported by IBM/Informix which is a major problem in itself).

We are using ONBAR with Tivoli Storage Manager.

The restore commences and then fails after about 45 minutes. Below is an extract from the onbar log file: -

006-06-23 23:16:15 2583 2581 /opt/informix/bin/onbar_d -r -p -w
006-06-23 23:16:16 2583 2581 Successfully connected to Storage Manager.
006-06-23 23:16:54 2583 2581 Begin cold level 0 restore rootdbs (Storage Manager copy ID: 0 197494047).
006-06-24 00:00:45 2583 2581 Unable to write storage space restore data to the database server: could not fork server connection.
006-06-24 00:00:45 2583 2581 Skipped backup/restore of space 'rootdbs'.
006-06-24 00:02:08 2583 2581 Begin cold level 0 restore db0 (Storage Manager copy ID: 0 197494048).
006-06-24 00:04:30 2583 2581 Completed cold level 0 restore db0.
006-06-24 00:04:30 2583 2581 Begin cold level 0 restore db1 (Storage Manager copy ID: 0 197494049).
006-06-24 00:08:23 2583 2581 Completed cold level 0 restore db1.
006-06-24 00:08:23 2583 2581 Begin cold level 0 restore db10 (Storage Manager copy ID: 0 197494050).
006-06-24 00:10:08 2583 2581 Unable to write storage space restore data to the database server: not enough memory.
006-06-24 00:10:08 2583 2581 Skipped backup/restore of space 'db10'.
006-06-24 00:16:57 2583 2581 Begin cold level 0 restore db11 (Storage Manager copy ID: 0 197494051).
006-06-24 00:16:58 2583 2581 ASSERT: file bar_unix.c line 1258 - contact product support
006-06-24 00:16:58 2583 2581 this process will hang waiting for a debugger to connect

The first concern is that it could not restore the rootdbs due to the error "Unable to write storage space restore data to the database server: could not fork server connection". The table in question resides in the rootdbs.

This is a cold restore. I then tried to completely re-initialize the engine (oninit -i) however this also fails with the following error in the online log: -

09:36:30 IBM Informix Dynamic Server Started.
09:36:30 Requested shared memory segment size rounded from 130048KB to 131072KB
09:36:30 Segment locked: addr=0x10000000, size=134217728


Any help with either of these 2 issues would be greatly appeciated.

Regards,

Paul Ridding
Sydney. Australia.