Vnode invalid installation password

From PTAGISWiki

Summary

After upgrading Ingres on sockeye and blueback, some of the client installations had trouble connecting to the servers. The problem would manifest on the client when a database connect was attempted and the error would result that the installation password was invalid.

This was solved for some clients by entering in the same installation password on their vnode. But for some clients, it didn't help to reset the installation password.

Resolution

The server has a vnode installation password as well, and the solution was to refresh the password on the server and then wait for GCC connections to time out and use the new password.

Testing through netutil within a minute of the change would not necessarily be a valid test. It takes some amount of time, between one and five minutes, for the password change to take effect. This delay could probably be eliminated by bouncing ingres after making the change.