Shared Memory on NT

Hello out there, we have the following strange behaviour on an Windows NT 4.0 SP 3 with IDS 7.22 TC1. Each night we are using a cmd-script to shutdown the db-server using onmode -ky.After doing a complete backup of the hard-drive, another script tries to start the db-server again. Most of the time everything works fine. But sometimes we get errors like the following, when trying to bring IDS online. 11:39:22 shmget: [EEXIST][17]: key 52564801: Shared Memory bereitsvorhanden 11:39:27 mt_shm_init: Segment resident kann nicht angelegt werden In each case the online log states, that online terminated correctly without any errors. Any ideas ? Wolfgang

Try to reboot the machine. It seems that NT is not releasing the shared memory allocation that Informix had. I am not sure if this is a bug with the sp3 or informix. This happens ever so often with my NT box as well. You might want to check to see if there are other running processes that is eating up your memory. This will cause informix (if there is not enough memory needed to be allocated) not to initialize properly as well. Lloyd AJ Wilson. Wolfgang Zager wrote in message <37DE430F.31DCA091@compuserve.com>... >Hello out there, > >we have the following strange behaviour on an Windows NT 4.0 SP 3 with >IDS 7.22 TC1. > >Each night we are using a cmd-script to shutdown the db-server using >onmode -ky.>After doing a complete backup of the hard-drive, another script tries to >start >the db-server again. Most of the time everything works fine. But >sometimes we get >errors like the following, when trying to bring IDS online. > >11:39:22 shmget: [EEXIST][17]: key 52564801: Shared Memory bereits>vorhanden >11:39:27 mt_shm_init: Segment resident kann nicht angelegt werden> >In each case the online log states, that online terminated correctly >without any errors. > >Any ideas ? > >Wolfgang > >

>we have the following strange behaviour on an Windows NT 4.0 SP 3 with >IDS 7.22 TC1. > >Each night we are using a cmd-script to shutdown the db-server using >onmode -ky. You would be better off the stop the Database server service by: net stop "Informix Dynamic Server - <Server Name>" >After doing a complete backup of the hard-drive, another script tries to start the db-server again. restart the database engine by using: net start "Informix Dynamic Server - <Server Name>" This should not give you the shared memory errors, as this is the procedure used by a couple of my clients. Cheers Hans