Primary chunk sanity check error
Prashant Kompella could not start a restored Online 7.23 instance: primary chunk of a temp dbspace failed its sanity check, even with DBSPACETEMP commented out. Neil Truby suggested onspaces if the chunk is in place. Art S. Kagel said DBSPACETEMP is irrelevant at startup; the engine must find and verify all chunks, so check the link, size and dd read/write. No confirmation of a fix.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi, When we try to startup a restored Online 7.23 instance, we are getting the following error: "Fatal error initializing shared memory." In the log file: 'Primary chunk '/links/dbs04temp_01' sanity check failed -offline. ' We have checked that the raw device mapping etc are correct. This is actually the temp dbspace so I have tried to start the instance by commenting out the DBSPACETEMP variable. It should automatically start the instance with /tmp as temporary table space but it does not ? Thanks for your help in advance. Prashant
If the chunk is actually in place, with correct permissions and size
etc.etc. then you should be able to use onspaces to bring it back online.
Prashant Kompella wrote in message
<961407038.875784@news.hartingdale.com.au>...
>
>Hi,
>
>When we try to startup a restored Online 7.23 instance, we are getting the
>following error:
>"Fatal error initializing shared memory."
>In the log file:
>'Primary chunk '/links/dbs04temp_01' sanity check failed -offline. '
>
>We have checked that the raw device mapping etc are correct.
>
>This is actually the temp dbspace so I have tried to start the instance by
>commenting out the DBSPACETEMP variable. It should automatically start the
>instance with /tmp as temporary table space but it does not ?
>
>
>Thanks for your help in advance.
>Prashant
>
>
Check $INFORMIXDIR/etc/onconfig
DBSPACETEMP ....
<prashant@hartingdale.com.au> wrote:
>
>Hi,
>
>When we try to startup a restored Online 7.23 instance, we are getting the
>following error:
>"Fatal error initializing shared memory."
>In the log file:
>'Primary chunk '/links/dbs04temp_01' sanity check failed -offline. '
>
>We have checked that the raw device mapping etc are correct.
>
>This is actually the temp dbspace so I have tried to start the instance by
>commenting out the DBSPACETEMP variable. It should automatically start the
>instance with /tmp as temporary table space but it does not ?
>
>
>Thanks for your help in advance.
>Prashant
>
DBSPACETEMP is irrelevant during startup, it only affects which dbspace(s) are used for temp files. The engine STILL has to find, open, and verify all of the chunks recorded in the chunk table reserved page. Make sure that link is present and pointed to a hunk of disk at least as large as the one that was backed up. Verify that is it readable and writable using dd. Art S. Kagel Prashant Kompella wrote: > > Hi, > > When we try to startup a restored Online 7.23 instance, we are getting the > following error: > "Fatal error initializing shared memory." > In the log file: > 'Primary chunk '/links/dbs04temp_01' sanity check failed -offline. ' > > We have checked that the raw device mapping etc are correct. > > This is actually the temp dbspace so I have tried to start the instance by > commenting out the DBSPACETEMP variable. It should automatically start the > instance with /tmp as temporary table space but it does not ? > > Thanks for your help in advance. > Prashant