Highlighted
Absent Member.. GTrejos7 Absent Member..
Absent Member..
98 views

[ST OMU] Problem setting nodes to CONTROLLED after export/import from OMW to OML

PROBLEM:

After importing nodes from OMW, one cannot change the node type of several nodes to Controlled using the command
#opcnode -chg_nodetype node=<server name> node_type=CONTROLLED”


The "opcnode –chg_nodetype node" command completes without error, but the nodetype is not changed.     
On the other hand making changes to the nodetype via the AdminUI completes successfully.


CAUSE:

Previously a configuration export/import from OMW to OML had occurred using the following commands.

Exporting nodes using:
#ovowconfigexchange

Importing Nodes using:
#/opt/OV/bin/OpC/opccfgupld -replace

The problem is due to an incompatible character set, when nodes are imported into OML from OMW.

There was a problem with the OMW code during the configuration export process,
which generated the node_char_set to be set to 65 on normal nodes, which means
Japanese EUC in OMU/L (not accepted/supported by Windows nodes)

On OMU/L, Windows nodes (machine_type = 45 or 91) are only allowed to have value 69 (UTF8) set for node_char_set.

To verify the node_char_set for windows nodes you can run the following query to the databse:
#echo "select node_char_set from opc_nodes where machine_type='45' or machine_type='91' and node_char_set !='69';" | opcdbpwd -exe sqlplus -s


The AdminUI is capable of changing the node type successfully since it automatically changes
the node_char_set to the supported value when saving the changes.

RESOLUTION :


Instead of modifying the node with the opcnode CLI, modify the node in the OML AdminUI.
That will automatically set the node character set to an allowed value.

After that it is also possible to use opcnode.

The issue was reported to the OMW support team and they created a fix for it:
http://support.openview.hp.com/selfsolve/document/LID/QCCR1A150547

The fix was released onto the following OMW patches:
OMW_00169 - OVO Server 08.19.100 Windows
OMW_00170 - OVO Server 09.00.100 Windows
Once installed, new configuration export/import should not present the same issue.

 

This is documented in the following KCS article:

http://support.openview.hp.com/selfsolve/document/KM00712615

 

 

 

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you liked it I would appreciate KUDOs.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.