-
Title
Data are not being displayed after installing the FMS with an external Oracle repository -
Description
We just installed the FMS (Foglight Management Server) with an external Oracle repository. We are not seeing all of the data we expect to see in the VMWare dashboards. Error messages like the following are being reported in the management server log:
2011-08-01 15:41:54.114 WARN [Data-3-thread-290] com.quest.nitro.service.agent.AgentManager - Canonical data transform failed. Some agent data may be lost: java.lang.IllegalStateException: Error processing incoming data for root node: XML-HTTP::Virtual-VMware-5_5_8/cdt-5_5_8/topology-adapter.xml: java.lang.RuntimeException: Unable to resolve object: VMWVirtualMachineNetworkInterface: {virtualMachine=0d9263db-..., name=hostname}
java.lang.IllegalStateException: Error processing incoming data for root node: XML-HTTP::Virtual-VMware-5_5_8/cdt-5_5_8/topology-adapter.xml: java.lang.RuntimeException: Unable to resolve object: VMWVirtualMachineNetworkInterface: {virtualMachine=0d9263db-..., name=hostname}
at com.quest.nitro.service.agent.TopologyAdapter.rethrowAsRuntimeException(TopologyAdapter.java:335)
...
Caused by: java.lang.RuntimeException: Unable to resolve object: VMWVirtualMachineNetworkInterface: {virtualMachine=0d9263db-..., name=hostname}
...
Caused by: com.quest.nitro.service.sl.interfaces.topology.OptimisticLockException: ORA-00001:...(FOGLIGHT.SYS_C0016418)
-
Cause
The character set used by the Oracle repository was not a Unicode character set. The Foglight Oracle repository must be configured to support Unicode characters.
-
Resolution
RESOLUTION:
Issue the following command from the Oracle repository and check the value of the NLS_CHARACTERSET parameter to determine the character set. After determining the character set check to see if it is a Unicode character set.
SELECT * FROM nls_database_parameters;
If the character set used by the Oracle repository does not support Unicode characters change the character set to one that does support Unicode characters. You can use UTF-8 or UTF-16, for example, to support Unicode.
-
Additional Information
The NLS_CHARACTERSET parameter is the value you should check in the output of the "SELECT * FROM nls_database_parameters" command. Don't check the value of the NLS_NCHAR_CHARACTERSET parameter because not all of the Foglight tables use NCHAR column types.
Following is an example of the output from the "SELECT * FROM nls_database_parameters" command. In the output below the NLS_CHARACTERSET parameter is set to a value of WE8MSWIN1252, which is not a character set that supports unicode.
SQL> SELECT * FROM nls_database_parameters;
PARAMETER VALUE
------------------------------ ----------------------------------------
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8MSWIN1252 <---- Check this one
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
PARAMETER VALUE
------------------------------ ----------------------------------------
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET UTF8
NLS_RDBMS_VERSION 11.2.0.2.0