Hi!
I have some problems getting SDS up and running.
I set up 2 machines with v11.10FC2, both connected to a SAN.
dbsroot is located on the SAN and can be seen and read and written
from both
machines.
Configuration of both machines is identical except to the points
mentioned
in documentation (e.g. DBSERVERNAME, SDS_ENABLE a.s.o.). Each machine
has
it's own temp-dbspace.
SDS-parameters are only set in onconfig on sec. machine. sqlhosts is
identical on both too.
To initialize SDS I do the following:
- set SDS-parameters on secondary in onconfig, don't start
- startup primary
- on primary: "onmode -d set SDS primary SERVERNAME" -> SDS-variable
is
added
- startup secondary
After startup both nodes can see each other (onstat -g sds). Both
nodes can
see dbroot.
After issuing a manual checkpoint or simply waiting about 5 minutes
secondary node is "shot in the head" by primary with the following
message
in online-log:
SDS: received shutdown request from PRIM-SERVERNAME, reason: onmode -d
clear
SDS primary, command was run at primary
DR: shutting down the server
And it does what it says- shutting down the secondary node. Exactly
as
described in IC54428 article from IBM. As far as I understand this
article
this issue should be fixed in my IDS release...
Could anyone give me a clue what to do?
Thanks,
Roland
Madison Pruet - 21 Feb 2008 19:05 GMT
> Hi!
> After startup both nodes can see each other (onstat -g sds). Both
> nodes can
[quoted text clipped - 17 lines]
>
> Could anyone give me a clue what to do?
There were some 'edge' conditions that were resolved in 11.10xC2w1
The bug entries were idsdb00153395 and idsdb00150125
> Thanks,
> Roland
Nilesh Ozarkar - 21 Feb 2008 19:09 GMT
IC54428 is a different issue than what you noticed. The behavior you
noticed is a known defect.
informix-list-bounces@iiug.org wrote on 02/21/2008 10:23:05 AM:
> Hi!
>
[quoted text clipped - 49 lines]
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list