Highlighted
Contributor.. Contributor..
Contributor..
1015 views

Error while connecting Data Flow Probe with uCMDB 10.22

Jump to solution

Dear Experts,

I have installed uCMDB 10.22 in Linux environment with Oracle Database, and installed a DFP in Windows environment.

Data Flow Probe is not able to register itself with uCMDB Server, I am finding many errors below from error.log.

 

Can anyone please help me with the issue,

uCMDB 10.22(2 server) - Linux Environment

Caused by: com.mercury.topaz.cmdb.shared.base.CmdbException: [ErrorCode [-2147483648] undefined error code]
com.mercury.topaz.cmdb.server.manage.dal.CmdbDalBatchException: [ErrorCode [-2147483648] undefined error code]
Can't execute BATCH prepared statement [INSERT INTO HDM_160110NT_1 (ID, CMDB_ID, A_LIC_TYPE_UDI,A_NT_WORKGROUP,A_NET_BIOS_NAME,A_SNMP_SYS_NAME,A_PRIMARY_MAC_ADDRESS,A_CITY,A_NODE_OS_DESCRIPTION,A_UD_UNIQUE_ID,A_PROCESSOR_FAMILY,A_NT_KERNEL,A_DISCOVERED_OS_VENDOR,A_CREATE_TIME,A_BIOS_ASSET_TAG,A_TENANTOWNER,A_HOST_ISVIRTUAL,A_HOST_OSACCURACY,A_ROOT_CONTAINER,A_DATA_EXTERNALID,A_NT_SERVICEPACK,A_DATA_ORIGIN,A_DESCRIPTION,A_DEFAULT_GATEWAY_IP_ADDRESS,A_PRIMARY_IP_ADDRESS,A_DISCOVERED_VENDOR,A_ACK_CLEARED_TIME,A_SERIAL_NUMBER,A_LANGUAGE,A_HOST_OSINSTALLTYPE,A_DIGEST,A_NT_MAINPROCESSORTYPE,A_CODEPAGE,A_SYS_OBJECT_ID,A_DOMAIN_NAME,A_NT_PHYSICALMEMORY,A_TRACK_CHANGES,A_DISPLAY_LABEL,A_NAME,A_BIOS_DATE,A_BIOS_UUID,A_DISCOVERED_LOCATION,A_DATA_ALLOW_AUTO_DISCOVERY,A_NODE_FAMILY,A_NT_IEVERSION,A_USER_LABEL,A_DISCOVERED_OS_NAME,A_NT_REGISTEREDOWNER,A_MEMORY_SIZE,A_CHASSIS_TYPE,A_PAE_ENABLED,A_PRIMARY_DNS_NAME,A_DISCOVERED_CONTACT,A_ROOT_ENABLEAGEING,A_BIOS_SERIAL_NUMBER,A_INTERNAL_NAME,A_CALCULATED_ID,A_HOST_NNM_UID,A_NT_PROCESSORSNUMBER,A_GLOBAL_ID,A_OS_ARCHITECTURE,A_DISCOVERED_OS_VERSION,A_ACK_ID,A_ROOT_ICONPROPERTIES,A_OS_VENDOR,A_HOST_LAST_BOOT_TIME,A_HOST_OSRELEASE,A_DATA_SOURCE,A_COUNTRY,A_EXTENDED_OS_FAMILY,A_OS_FAMILY,A_HOST_ISROUTE,A_DATA_NOTE,A_SWAP_MEMORY_SIZE,A_VENDOR,A_CREDENTIALS_ID,A_IS_SAVE_PERSISTENCY,A_BIOS_VERSION,A_STATE,A_CALCULATED_LOCATION,A_HOST_ISDESKTOP,A_ROOT_SYSTEM,A_BIOS_SOURCE,A_NT_MAINPROCESSORSPEED,A_OS_DESCRIPTION,A_EXTENDED_NODE_FAMILY,A_DISCOVERED_MODEL,A_HOST_NNM_INTERNAL_KEY,A_DISCOVERED_DESCRIPTION,A_DEFAULT_GATEWAY_437101766,A_DOCUMENT_LIST,A_LIC_TYPE_UDF,A_NT_REGISTRATIONORG,A_HOST_SERVERTYPE,A_NODE_MODEL,START_TIME, CHANGER_DATASTORE,CHANGER_INFO, CHANGE_TYPE,TENANTS_BITMASK) VALUES (?, ?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)], failed prior to DB execution due to exception: com.mercury.jdbc.oraclebase.ddc: [mercury][Oracle JDBC Driver][Oracle]ORA-00904: "A_HOST_NNM_INTERNAL_KEY": 無効な識別子です。

at com.mercury.topaz.cmdb.shared.model.operation.update.impl.HistoryModelChangeListenerFineGrained.onFinishDeployment(HistoryModelChangeListenerFineGrained.java:340)
at com.mercury.topaz.cmdb.shared.notification.service.util.ChangesPublisher.publish(ChangesPublisher.java:49)
at com.mercury.topaz.cmdb.shared.model.operation.update.impl.AbstractExternalModelUpdate.auditChanges(AbstractExternalModelUpdate.java:324)
at com.mercury.topaz.cmdb.shared.model.operation.update.impl.AbstractExternalModelUpdate.modelUpdateExecute(AbstractExternalModelUpdate.java:286)
at com.mercury.topaz.cmdb.shared.model.operation.update.impl.bulk.AbstractModelUpdateBulks.bulkExecute(AbstractModelUpdateBulks.java:91)
at com.mercury.topaz.cmdb.shared.model.operation.update.impl.bulk.AbstractModelUpdateBulks.modelUpdateExecute(AbstractModelUpdateBulks.java:77)
at com.mercury.topaz.cmdb.shared.model.operation.update.impl.AbstractExternalModelUpdate.doExecute(AbstractExternalModelUpdate.java:163)
at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractFrameworkOperation.commonExecute(AbstractFrameworkOperation.java:17)
at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractCommonOperation$OperationExecuteFlowTrackingCommand.execute(AbstractCommonOperation.java:87)
... 70 more
Caused by: com.mercury.topaz.cmdb.server.manage.dal.CmdbDalBatchException: [ErrorCode [-2147483648] undefined error code]
Can't execute BATCH prepared statement [INSERT INTO HDM_160110NT_1 (ID, CMDB_ID, A_LIC_TYPE_UDI,A_NT_WORKGROUP,A_NET_BIOS_NAME,A_SNMP_SYS_NAME,A_PRIMARY_MAC_ADDRESS,A_CITY,A_NODE_OS_DESCRIPTION,A_UD_UNIQUE_ID,A_PROCESSOR_FAMILY,A_NT_KERNEL,A_DISCOVERED_OS_VENDOR,A_CREATE_TIME,A_BIOS_ASSET_TAG,A_TENANTOWNER,A_HOST_ISVIRTUAL,A_HOST_OSACCURACY,A_ROOT_CONTAINER,A_DATA_EXTERNALID,A_NT_SERVICEPACK,A_DATA_ORIGIN,A_DESCRIPTION,A_DEFAULT_GATEWAY_IP_ADDRESS,A_PRIMARY_IP_ADDRESS,A_DISCOVERED_VENDOR,A_ACK_CLEARED_TIME,A_SERIAL_NUMBER,A_LANGUAGE,A_HOST_OSINSTALLTYPE,A_DIGEST,A_NT_MAINPROCESSORTYPE,A_CODEPAGE,A_SYS_OBJECT_ID,A_DOMAIN_NAME,A_NT_PHYSICALMEMORY,A_TRACK_CHANGES,A_DISPLAY_LABEL,A_NAME,A_BIOS_DATE,A_BIOS_UUID,A_DISCOVERED_LOCATION,A_DATA_ALLOW_AUTO_DISCOVERY,A_NODE_FAMILY,A_NT_IEVERSION,A_USER_LABEL,A_DISCOVERED_OS_NAME,A_NT_REGISTEREDOWNER,A_MEMORY_SIZE,A_CHASSIS_TYPE,A_PAE_ENABLED,A_PRIMARY_DNS_NAME,A_DISCOVERED_CONTACT,A_ROOT_ENABLEAGEING,A_BIOS_SERIAL_NUMBER,A_INTERNAL_NAME,A_CALCULATED_ID,A_HOST_NNM_UID,A_NT_PROCESSORSNUMBER,A_GLOBAL_ID,A_OS_ARCHITECTURE,A_DISCOVERED_OS_VERSION,A_ACK_ID,A_ROOT_ICONPROPERTIES,A_OS_VENDOR,A_HOST_LAST_BOOT_TIME,A_HOST_OSRELEASE,A_DATA_SOURCE,A_COUNTRY,A_EXTENDED_OS_FAMILY,A_OS_FAMILY,A_HOST_ISROUTE,A_DATA_NOTE,A_SWAP_MEMORY_SIZE,A_VENDOR,A_CREDENTIALS_ID,A_IS_SAVE_PERSISTENCY,A_BIOS_VERSION,A_STATE,A_CALCULATED_LOCATION,A_HOST_ISDESKTOP,A_ROOT_SYSTEM,A_BIOS_SOURCE,A_NT_MAINPROCESSORSPEED,A_OS_DESCRIPTION,A_EXTENDED_NODE_FAMILY,A_DISCOVERED_MODEL,A_HOST_NNM_INTERNAL_KEY,A_DISCOVERED_DESCRIPTION,A_DEFAULT_GATEWAY_437101766,A_DOCUMENT_LIST,A_LIC_TYPE_UDF,A_NT_REGISTRATIONORG,A_HOST_SERVERTYPE,A_NODE_MODEL,START_TIME, CHANGER_DATASTORE,CHANGER_INFO, CHANGE_TYPE,TENANTS_BITMASK) VALUES (?, ?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)], failed prior to DB execution due to exception: com.mercury.jdbc.oraclebase.ddc: [mercury][Oracle JDBC Driver][Oracle]ORA-00904: "A_HOST_NNM_INTERNAL_KEY": 無効な識別子です。

at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalPreparedStatementImpl.internalExecuteBatch(CmdbDalPreparedStatementImpl.java:430)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalPreparedStatementImpl.executeBatch(CmdbDalPreparedStatementImpl.java:393)
at com.hp.ucmdb.history.dal.command.modify.HistoryDalAddEventCommand.insertNewEntries(HistoryDalAddEventCommand.java:259)
at com.hp.ucmdb.history.dal.command.modify.HistoryDalAddEventCommand.perform(HistoryDalAddEventCommand.java:91)
at com.hp.ucmdb.history.dal.command.modify.HistoryDalAddEventCommand.perform(HistoryDalAddEventCommand.java:38)
at com.mercury.topaz.cmdb.server.manage.dal.DalAbstractCommand$FlowControlDalCommandExecutor.execute(DalAbstractCommand.java:36)
at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:227)
at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:222)
at com.mercury.topaz.cmdb.server.manage.dal.DalAbstractCommand.execute(DalAbstractCommand.java:54)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalJdbcDAO$CmdbDalDeadlockRetriable.performAction(CmdbDalJdbcDAO.java:120)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalJdbcDAO$CmdbDalDeadlockRetriable.performAction(CmdbDalJdbcDAO.java:105)
at com.mercury.topaz.cmdb.shared.util.retry.impl.DefaultRetriableExecutorImpl.doExecute(DefaultRetriableExecutorImpl.java:37)
at com.mercury.topaz.cmdb.shared.util.retry.impl.AbstractRetriableExecutor.execute(AbstractRetriableExecutor.java:37)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalJdbcDAO.execute(CmdbDalJdbcDAO.java:81)
at com.mercury.topaz.cmdb.server.dal.dao.impl.CmdbDalJdbcDataModelDAO.executeBulk(CmdbDalJdbcDataModelDAO.java:395)
at com.mercury.topaz.cmdb.shared.model.operation.update.impl.HistoryModelChangeListenerFineGrained.onFinishDeployment(HistoryModelChangeListenerFineGrained.java:325)
... 78 more
Caused by: com.mercury.jdbc.oraclebase.ddc: [mercury][Oracle JDBC Driver][Oracle]ORA-00904: "A_HOST_NNM_INTERNAL_KEY": 無効な識別子です。

at com.mercury.jdbc.oraclebase.dddz.executeBatch(Unknown Source)
at com.mercury.jdbc.oraclebase.ddd2.executeBatch(Unknown Source)
at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalPreparedStatementImpl$FlowControlBatchExecuter.execute(CmdbDalPreparedStatementImpl.java:616)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalPreparedStatementImpl$FlowControlBatchExecuter.execute(CmdbDalPreparedStatementImpl.java:608)
at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:227)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalPreparedStatementImpl.internalExecuteBatch(CmdbDalPreparedStatementImpl.java:403)
... 93 more

0 Likes
1 Solution

Accepted Solutions
Highlighted
Contributor.. Contributor..
Contributor..

Re: Error while connecting Data Flow Probe with uCMDB 10.22

Jump to solution

I was able to resolve the issue, There was a problem with uCMDB Schema.

I have recreated the schema and its back to normal.

Regards

N V Rakesh

View solution in original post

0 Likes
2 Replies
Highlighted
Established Member..
Established Member..

Re: Error while connecting Data Flow Probe with uCMDB 10.22

Jump to solution

Hi Rakesh,

i have faced a similar kind of issue where the probe couldnot able to communicate with the server.

after a series of research and tests, i found out the problem is with the Key.bin file

the key.bin file got corrupted and as a result the communication between probe and server stopped working.

i have created a new key.bin file using JMX console and embedded with the probe and clear the cache and restart the services

voila! my probe started communicating with the server.

 

also please check the server.keystore file are in tact, there may be chances it may be corrupted too.

 

thanks,

Sada

(if you like my comment or found it useful, please use kudos 🙂

0 Likes
Highlighted
Contributor.. Contributor..
Contributor..

Re: Error while connecting Data Flow Probe with uCMDB 10.22

Jump to solution

I was able to resolve the issue, There was a problem with uCMDB Schema.

I have recreated the schema and its back to normal.

Regards

N V Rakesh

View solution in original post

0 Likes
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.