informix with Service Cluster

[Thomas Kopp]

Moin,
we have two HP-Server's(L9000), which are connected two one informix-database(VA 7100).
The both server are running with MC Service Guard.)
The problem:
If you are running one HP server with informix, the database starts
correct (and vice versa).
But, if both server running in cluster mode, informix does not come up.
The database ends up in quiescent mode.

The online.log from Informix:
02:49:58 Informix Dynamic Server 2000 Version 9.21.HC4
02:49:58 (7) connection rejected - no calls allowed for sqlexec
02:49:58 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server 2000 quiescent mode.

02:49:58 (8) connection rejected - no calls allowed for sqlexec
02:49:58 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server 2000 quiescent mode.

02:49:58 (9) connection rejected - no calls allowed for sqlexec
02:49:58 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server 2000 quiescent mode.

02:49:59 Informix Dynamic Server 2000 Initialized -- Shared Memory Initialized.

02:49:59 Physical Recovery Started at Page(112:37510).
02:49:59 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored.

02:49:59 Logical Recovery Started.
02:49:59 10 recovery worker threads will be started.
03:20:38 Informix Dynamic Server 2000 Started.

Any idea's are welcome.
Thanks Thomas

[Massimo Bianchi]

Hi,
just a couple of check:

- onconfig files are referring to the correct virtual instance ?

- are you running the Online Dynamic Server on one server at time ? may be you have left some automatic start process in /sbin/init.d and this is preventing the correct start of the instance

- is the VG activated in EXCULSIVE mode ?

HTH,
Massimo

[Karthik S S]

If you are running Informix as a Package, Is the Informix server been given the Package's hostname??.

Karthik

[Steve Lewis]

It could be lots of things.

Firstly make sure you are starting up informix using command 'oninit' NOT 'oninit -s'.

I suspect it could be a synchronisation issue, where you application software is attempting to connect to the database before the database is fully up in multi-user mode. The connection fails and the application software refuses to start (maybe halting the package in the process). Put a 15 second delay in the package startup after the informix startup and before any other software tries to connect.

Test your package without the informix and applications, to make sure that the volume groups are properly activated (exclusively), filesystems are mounted and the required IPs are there. Then add the informix and other software to the end of the package startup script (preferably in a subscript that returns a success/fail value).

[Rainer von Bongartz]

What I see from the log files is that INFORMIX start up correctly. If it ends in quiescent mode inspect your SG scripts (oninit -s ???)
INFORMIX will NOT end in quiescent mode unless explicitly requested.

Can you take the quiescent server online afterwards (oninit -m )

Regards
rainer

[Thomas Kopp]

Log is o.k???
But, why I cant see, that the Logical Recovery
is finished.
In syslog.log I can see the following:
cmcld: WARNING: Cluster lock on disk /dev/dsk/c8t0d1 is missing!
cmcld: Until it is fixed, a single failure could
cmcld: cause all nodes in the cluster to crash

What does this mean??

Thomas

[Massimo Bianchi]

Hi,
your last message means that you are missing some piece of your mcsg config !

Fot the precision, the lock disk may be not well configured, you may have to re-apply che config.

Check if your vg have the same number of disks on both the nodes and if you included the lock disk correctly (correct different name of the disk) on both nodes.

HTH,
Massimo

[Rainer von Bongartz]

Please post an onstat -l output

Rainer