memory, rootdbs problems
Posted in 1998
I had an informix DB up and runing on a HPUX 10.20 system running
through Livewire and Netscape Enterprise Server 2.01 to publish data to
the web. I had to rename the system (new ip and hostname) and remove
the external Jaz drive and now my informix db engine wont work anymore.
It made my rootdbs file = 0 length and when I try to run the start.sh
file I get the message that it couldnt initialize memory for INFORMIXDIR
I then tried reinstalling informix and then tried to start it and I got
the same message but I did get a clean online.log file form it this time
and it may shed some light on the situation
online.log
>Sun Mar 1 11:32:59 1998
>
>11:32:59 DR: DRAUTO is 0 (Off)
>11:33:11 INFORMIX-OnLine Initialized -- Complete Disk Initialized.
>11:33:12 Checkpoint Completed: duration was 0 seconds.
>11:33:12 Dataskip is now OFF for all dbspaces
>11:33:12 On-Line Mode
>11:33:12 Building 'sysmaster' database ...
>11:33:26 Logical Log 1 Complete.
>11:33:35 Logical Log 2 Complete.
>11:33:37 Checkpoint Completed: duration was 1 seconds.
>11:33:45 Logical Log 3 Complete.
>11:33:55 Logical Log 4 Complete.
>11:33:57 'sysmaster' database built successfully.
>11:38:47 Checkpoint Completed: duration was 1 seconds.
>11:40:46 shmget: [EEXIST][17]: key 52644801: shared memory alreadyexists
>11:40:46 mt_shm_init: can't create resident segment
I then told it to run the start.sh script rfom my profile login script
and it gave me the following log file
>Sun Mar 1 11:47:33 1998
>
>11:47:33 DR: DRAUTO is 0 (Off)
>11:47:33 INFORMIX-OnLine Initialized -- Shared Memory Initialized.
>11:47:34 Physical Recovery Started.
>11:47:34 Physical Recovery Complete: 0 Pages Restored.
>11:47:34 Logical Recovery Started.
>11:47:37 Logical Recovery Complete.> 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
>
>11:47:37 Dataskip is now OFF for all dbspaces
>11:47:37 On-Line Mode
>11:47:38 Checkpoint Completed: duration was 1 seconds.
this looks like the engine is working but then when I go and run onstat
- it tells me again that the memory is not initialized and that it can't
find messgae 19511.
If you have any clue as to how to solve this or know who I can contact
please let me know... I have to have this fixed by tomorrow (monday)
morning.
Will Johnson