RE: after adding DBSERVERALIASES into onconfig file
Posted in 2000
First off, it may prove helpful to provide us with a snapshot of your DBSERVERNAME and DBSERVERALIASES lines from your $ONCONFIG file (before and after your changes were made) as well as snapshots of your sqlhosts file. Off the top of my head, though, you may want to check the following: - Confirm that the spelling of dataPower is spelt exactly the same (including case) in your $ONCONFIG and sqlhosts files. - Confirm that your DBSERVERALIASES values are separated by commas, all on one line. - You didn't change the value of DBSERVERNAME from <something> to dataPower, did you? I once did this over a year ago. Due to a bug in the tools I couldn't use shared memory when accessing the instance, so I used the onsoctcp INFORMIXSERVER as my DBSERVERNAME value. When I got the upgraded tools I tried modifying the $ONCONFIG to change the DBSERVERNAME to my onshmipc INFORMIXSERVER, moving my onsoctcp INFORMIXSERVER to DBSERVERALIASES; it failed giving me this same error message. I suspected, but didn't confirm, that the DBSERVERNAME is stored somewhere in the rootdbs (in the reserved pages?) and if you subsequently mess with this $ONCONFIG parameter initialization would fail. This is why I'm requesting the before and after snapshots above. Hope this helps. If it doesn't, then the more experienced gurus here will ask you more pointed questions. Best regards, Edmund Nigel Gall Senior Information Systems Specialist Process Plant Services Limited Atlantic Avenue, Point Lisas Industrial Estate Point Lisas, Couva, Trinidad & Tobago, W.I. Tel: (868) 636 2906 x 274 Fax: (868) 679 3770 -----Original Message----- From: Kathy Huo [mailto:kathy.huo@ssi1.com] Sent: 2000 March 08 2:04 PM To: informix-list@iiug.org Subject: after adding DBSERVERALIASES into onconfig file I can't bring the server ON-LINE after manually adding server aliases into onconfig file. The error message was: "shared memory not initialized for INFORMIXSERVER 'dataPower'. Does it mean I have to reinitialize the root database or reboot the server?