Extending the Domain in the Local Instance
The following SQL update extends the domain from the MIB server to all servers in the local instance of Ingres. This makes visible, for example, other DBMS servers, logging and locking objects, RCP and ACP:
UPDATE ima_mib_objects
SET value = DBMSINFO('IMA_VNODE')
WHERE classid = 'exp.gwf.gwm.session.control.add_vnode'
AND instance = '0'
AND server = DBMSINFO('IMA_SERVER');
It is not necessary to use DBMSINFO('IMA_SERVER') to define the name of the MIB server to which the session is connected; DBMSINFO('IMA_SERVER') could be replaced by a program variable or a hard coded value, but DBMSINFO('IMA_SERVER') is used for ease and to make the SQL generic across operating systems.
As the above SQL is extending the local MIB server domain, it is necessary to set the value of the "value" column to the local VNODE, which can be retrieved through the use of a program variable with the value in, a hard coded value, or through DBMSINFO('IMA_VNODE').
Note: Updating the "value" column will not actually change what is in the column; it is an instruction to the MIB server to expose the other servers in that VNODE.
The following is an example of the count of the number of classid and instances done before and after the local domain is extended:
The actual values will change depending on the number of servers running, the number of sessions, and so on.