Re: help: Shared memory init error

In article <32BBFB3F.4109@netcomuk.co.uk>, Neil Truby <ntruby@netcomuk.co.uk> writes >My experience is that Online ALWAYS hangs in fast recovery mode after a >cold restore. You must use onmode -m to start it. If you don't, and >you stop the instance with onmode -ky, you can't subsequently re-start >the instance as you'll get a Shared Memory Initialisation error. The >only remedy is to re-do the restore. ??? I'll try this when I get back into the Office next year :->. > >I've pondered why this should be so, and have come to the conclusion >that the server is waiting to see whether you have any logical logs to >supply. If not, and you issue the onmode -m, the engine flushes the It will do. Are you using ontape or onarchive to restore. If ontape it will ask "Do you have another logical log tape?" (or something like that. If you say no then the system will come up. (I can't remmebr if it goes to Online or Quesicent Mode). >pyhsical logs and off you go. I would imagine it would do fast recovery to reach a consistent state. > >That's my theory anyway. I look forward to having it demolished! > >Neil Truby >Chase Bank >Bournemouth, UK -- David Williams