Hi All,

Peeve Mode On...
I've just spent an hour or so trying to create an installation password ona host...trivial, done it a million times...so why is just one host allowing me to define the password, yet when I test it it comes up with:

E_GC0141_GCN_INPW_NOSUPP An installation password has been defined for the remote vnode, but that installation is not allowing use of installation passwords.

I have:

* confirmed that II_GCNII_LCL_VNODE is set correctly.

* Destroyed the vnode, recreated it.

* Restarted the installation.

* Confirmed the IILTICKET, IIRTICKET look as expected.

* Confirmed that iipmhost returns the data I would expect.

* Confirmed SELINUX is disabled.

* I started the name server with II_GCN_TRACE 5 and examined the log file.

The installation is: II 9.2.1 (a64.lnx/103)NPTL + p14026.

I have another installation running the same version and patch. Its having no problems with an Installation password.

Eventually a thought occurred...wasn't there a new variable in the name server used to replace II_GCNII_LCL_VNODE?

Yep sure was...and it was gcn.local_vnode and it was set to 'vault_ctsu_ox_ac_uk' not 'vault.ctsu.ox.ac.uk'.

It seems that when we did the install, we installed 9.2.1 whereas the otherhosts were upgraded to 9.2.1 from earlier versions. The difference is thatthe 9.2.1 install must not set the LCL_VNODE but prefer to simply set the new cbf entry gcn.local_vnode and it defaults it to the underscore version not the period version. The upgrades probably just copied the existing values of LCL_VNODE.

Once I changed the gcn.local_vnode to use periods and restarted the gcn then all is now fine.

Martin Bowes

Marty,

Thanks for the heads-up on this particular 'gotcha'. I'll be keeping
an eye out for it.

Quite different, but no less annoying, is a 'gotcha' in Ingres 10
where having II_HOSTNAME in CAPTIALS stops 'ingbuild -express' from
configuring Ingres/STAR correctly during an upgrade! (See KB Doc.
420526).

Regards,