Ingres vnode

From PTAGISWiki

Question

This command on reedi works:

report -upittag blueback::ptagis3 -iistatus.rw

<span class="page_description">Last Upload: 09/18/2007 07:20:38</span><br>
<span class="page_description">Next Upload: 09/18/2007 10:20:38</span><br>

But the same command on bay gives the wrong times.

report -upittag blueback::ptagis3 -iistatus.rw

<span class="page_description">Last Upload: 07/10/2007 07:22:12</span><br>
<span class="page_description">Next Upload: 07/10/2007 10:22:12</span><br>

As far as I can tell, the ingres environment is configured identically on bay and reedi:

TERM_INGRES=vt100fx
INST_CODE=C1
II_SYSTEM=/usr/ingres/ing26
ING_REGISTRY=/tmp/ing_installs.16008.261103120
ING_SET=$'set lockmode session where readlock=nolock'

Where is the magic cookie that determines which ingres instance is used?

Answer

In the command "report -upittag blueback::ptagis3 -iistatus.rw", "blueback" is the name of a vnode which can be defined to point to any ingres instance. The netutil command is used to change the definition of a vnode.

To fix this problem, I had to change the Listen Address for vnode blueback on bay from TH to UI. I also had to update the Login/password data for that vnode.