Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
323 views

AM Generic Adapter Database Error

Hi Experts,

We just underwent an database migration project where we copied our production database from one server to another and upgraded to a later (compatible) version of  Oracle.  The migration went smoothly except for one of our existing integrations.  The integration that was working previously is now failing with the following error.  The interesting thing is that the AM Push is working, but the UI reports that the integration job failed.  Any ideas?

2019-01-14 10:07:23,179  ERROR  [RequestProcessorAsyncPool-2515] (AbstractSynchronizerCommandRunSyncUnit.java:283) - Replication [AMGenericRecon_AM Push] error!!!

com.mercury.topaz.cmdb.server.manage.dal.CmdbDalException: [ErrorCode [-2147483648] undefined error code]

Can't execute prepared statement [MERGE INTO SYNC_ID_MAP M USING (SELECT  /*+ cardinality(TEMP_SYNC_ID_MAP 500) */ SOURCE_ID, TARGET_ID, SOURCE_EXT_ID, TARGET_EXT_ID, IS_REL FROM TEMP_SYNC_ID_MAP) S ON ((M.SOURCE_ID=S.SOURCE_ID OR M.TARGET_ID=S.SOURCE_ID) AND M.DS_ID=?) WHEN MATCHED THEN UPDATE SET M.TARGET_ID=S.TARGET_ID, M.TARGET_EXT_ID=S.TARGET_EXT_ID WHEN NOT MATCHED THEN INSERT (DS_ID, IS_REL, SOURCE_ID, TARGET_ID, SOURCE_EXT_ID, TARGET_EXT_ID) VALUES (?, S.IS_REL, S.SOURCE_ID, S.TARGET_ID, S.SOURCE_EXT_ID, S.TARGET_EXT_ID); Values: 15,15], due to exception: java.sql.SQLTimeoutException: [mercury][Oracle JDBC Driver]Execution timeout expired.

0 Likes
4 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: AM Generic Adapter Database Error

Hi RRose,

Is this error appearing on the Probe or on the UCMDB server?

it's best to find where to control the database jdbc driver timeouts. I think by default it is 10 or 15 minutes. 

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

Likes are appreciated!
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: AM Generic Adapter Database Error

Thanks Petko, 

I changed the integration probe log level to DEBUG and all appears to be clean in the probe logs.  That being the case the issue appears to be on the UCMDB server side as the progress of the push doesn't get updated in the UI and eventually times out.  Do you know what log file I should be looking at?  I've looked at the error.log but is there somewhere else that might provide some additional detail?

Bob

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: AM Generic Adapter Database Error

Hi RRose, 

 

you have to be looking at the dal logs : cmdb.dal.log, cmdb.dal.error.log and cmdb.dal.slow.log. Also consider increasing the timeout from conf/cmdb.conf, where you can set the db queries to last more than 15 minutes.

 

Petko

Likes are appreciated!
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: AM Generic Adapter Database Error

All,

In case interested.  Worked with our Oracle DBA and found that the issue is related to upgrading the Oracle database version.  Per the Oracle admin, "The execution plan for the SQL statement has changed on the newer version of Oracle. I have forced the optimizer to use the execution plan that it used on the older version of Oracle."

Our first tests were successful with a single AM Push job (hardware only).  When we expanded the push to include other TQL's the issue reappeared.  Still determining if the "fix" has to be done for each SQL statement or whether there is a global setting that can be incepted.

 

Bob

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.