SG Question

[JIJ_1]

Hi Gents,

I am in the process of configuring a 2 nodes cluster. I have two servers named ETL and EDW. When i am running cmquerycl to create the ascii template file i am speciying the ETL node first and then EDW ,but template file is getting generated with EDW server information first. After the cluster creation cmviewcl output shows EDW node first and then the ETL node as given below,

etl:/tmp#cmviewcl

CLUSTER STATUS
etl-edw up

NODE STATUS STATE
--> edw up running
--> etl up running

I was under the impression that node order in the cmviewcl output is based on the order in which nodes details are specified in the ascii template file. I have tried changing the node detials order in the ascii file and reconfigured the cluster but still getting the same cmviewcl o/p.

Is there anyway to change the order in teh cmviewcl o/p ? or is it based on alphabatic order ?

[Luk Vandenbussche]

Hi,

It is based on alphabetic order.

[Geoff Wild]

Not really - you could script something - but why?

cmviewcl |sort -rn

Rgds...Geoff

[Pavol Halcin]

Hi,

it doesn't matter whick node is being listed first. what matters is which node is configured as primary/alternate for each of the packages that will run in the cluster.

[JIJ_1]

Yes . It is is not a problem , ultimatlely the primary node and secondary node of a package is defined in the package config file. But i am wondering the behaviour of cmquerycl command , while executing cmqurycl i am specifying etl server first and then the edw server .But still the ascii file is getting created with edw server information first.

[JIJ_1]

Please note that i am running the cmquerycl command from ETL server.

[Geoff Wild]

Manually edit your ascii file, and re-arrange the nodes, then run your cmapplyconf.

cmquerycl just pull the data out of the binary config file - it should be based on the order from teh ascii file that was used to create it.

Rgds...Geoff

[JIJ_1]

As i mentioned in my first post , this manual modification in the ascii file was already tried.

[skt_skt]

did you try the cmapplyconf after the modification on the cluser ascii file?

you have not confirmed about the cmapplyconf?

[Naveej.K.A]

Hello,

I checked the clusters we have here and it definitely doesn't look like they are based on alphabetic order. As you have observed, by changing the order in the ASCII file doesn't make any difference either.

So I think - it may be - I am not sure here, that it is taking the node which has the lock VG activated at the time of cmapplyconf as its first node in the cmviewcl. I don't have a test enviro to check it out...

Please check and let us know if it makes any difference.

Regards,
Naveej

[skt_skt]

did you try the cmapplyconf after the modification on the cluser ascii file?

you have not confirmed about the cmapplyconf?verify the changes with cmgetconf or cmviewconf

[JIJ_1]

yes, i have already tried all these options. I have changed the node order in the ascii file and reconfigured the cluster but result is same. Even i have tried creating the cluster from the other node also. Here the cmviewconfig command o/p is showing that node 1 is ETL and node 2 is EDW , but when it comes to the o/p of cmviewcl command it is just giving the reverse way.

[JIJ_1]

Hi Naveej,

That was a good suggestion , but even that also didnt work here.

[Srinivas Thokala_1]

You are at cluster creation stage and I assume when you complete the package creation, export and import mapfiles on to the EDW server, the primay node ETL takes the fist position, until then it may be following alpha order.

-Srinivas