Highlighted
Contributor.
Contributor.
840 views

Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

 

Dear Experts,

Issue has been occured with HP UCMDB rollback from version 10.20 to 10.11. Below is the error message I am getting :-

2017-04-28 12:58:38,141 [Starter for "model_topology" (during Writer server startup). (customer 1, id name: Default Client)] ERROR Failed to execute command [CmdbDalLoadModelGraphComplexCommand] time [124 ms] customer ID [1, id name: Default Client] operation stack [N/A]
com.mercury.topaz.cmdb.server.manage.dal.CmdbDalException: [ErrorCode [-2147483648] undefined error code] Error loading model graph due to exception: com.mercury.topaz.cmdb.server.manage.dal.CmdbDalException: [ErrorCode [-2147483648] undefined error code] Can't execute statement [ select INLINE_COMPOSITION_CMDB_ID is not null ], due to exception: java.sql.SQLSyntaxErrorException: [mercury][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalAbstractLoadModelGraphComplexCommand.getModelGraph(CmdbDalAbstractLoadModelGraphComplexCommand.java:168)
at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalAbstractLoadModelGraphComplexCommand.perform(CmdbDalAbstractLoadModelGraphComplexCommand.java:122)
at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalAbstractLoadModelGraphComplexCommand.perform(CmdbDalAbstractLoadModelGraphComplexCommand.java:42)
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.executeQuery(CmdbDalJdbcDAO.java:61)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalJdbcDAO.executeQuery(CmdbDalJdbcDAO.java:53)
at com.mercury.topaz.cmdb.server.dal.dao.impl.CmdbDalJdbcDataModelDAO.executeQuery(CmdbDalJdbcDataModelDAO.java:96)
at com.mercury.topaz.cmdb.server.dal.dao.impl.CmdbDalJdbcDataModelDAO.loadModel(CmdbDalJdbcDataModelDAO.java:219)
at com.mercury.topaz.cmdb.server.dal.dao.impl.CmdbDalJdbcDataModelDAO.loadModelTopology(CmdbDalJdbcDataModelDAO.java:195)
at com.mercury.topaz.cmdb.server.model.manager.impl.ModelTopologyManagerImpl.loadModelTopology(ModelTopologyManagerImpl.java:142)
at com.mercury.topaz.cmdb.server.model.manager.impl.ModelTopologyManagerImpl.startUp(ModelTopologyManagerImpl.java:90)
at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startup(ServiceComponentImpl.java:118)
at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startupSubsystemManagers(ServiceComponentImpl.java:108)
at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startUp(ServiceComponentImpl.java:70)
at com.mercury.topaz.cmdb.server.manage.instance.CustomerInstanceImpl.startComponentLocally(CustomerInstanceImpl.java:104)
at com.mercury.topaz.cmdb.server.manage.instance.CustomerInstanceImpl.startComponentLocally(CustomerInstanceImpl.java:94)
at com.mercury.topaz.cmdb.server.manage.instance.Controller$ComponentLifecycleImpl.startComponent(Controller.java:291)
at com.mercury.topaz.cmdb.server.manage.instance.CustomerController.startComponent(CustomerController.java:482)
at com.mercury.topaz.cmdb.server.manage.instance.CustomerController.access$200(CustomerController.java:29)
at com.mercury.topaz.cmdb.server.manage.instance.CustomerController$RunnerWrapper.run(CustomerController.java:444)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
at java.lang.Thread.run(Thread.java:722)
Caused by: com.mercury.topaz.cmdb.server.manage.dal.CmdbDalException: [ErrorCode [-2147483648] undefined error code] Can't execute statement [ select INLINE_COMPOSITION_CMDB_ID as CMDB_ID, 'composition' as -------------

-----

[Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl.executeQuery(CmdbDalStatementImpl.java:284)
at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalAbstractLoadModelGraphComplexCommand.queryLinks(CmdbDalAbstractLoadModelGraphComplexCommand.java:327)
at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalAbstractLoadModelGraphComplexCommand.queryLinks(CmdbDalAbstractLoadModelGraphComplexCommand.java:268)
at com.mercury.topaz.cmdb.server.dal.command.datamodel.impl.CmdbDalAbstractLoadModelGraphComplexCommand.getModelGraph(CmdbDalAbstractLoadModelGraphComplexCommand.java:149)
... 29 more
Caused by: java.sql.SQLSyntaxErrorException: [mercury][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

at com.mercury.jdbc.oraclebase.ddcr.b(Unknown Source)
at com.mercury.jdbc.oraclebase.ddcr.a(Unknown Source)
at com.mercury.jdbc.oraclebase.ddcq.b(Unknown Source)
at com.mercury.jdbc.oraclebase.ddcq.a(Unknown Source)
at com.mercury.jdbc.oracle.ddal.a(Unknown Source)
at com.mercury.jdbc.oracle.ddal.a(Unknown Source)
at com.mercury.jdbc.oracle.ddam.t(Unknown Source)
at com.mercury.jdbc.oraclebase.dde3.w(Unknown Source)
at com.mercury.jdbc.oraclebase.dde3.v(Unknown Source)
at com.mercury.jdbc.oraclebase.dde3.executeQuery(Unknown Source)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl$FlowControlQueryExecuter.execute(CmdbDalStatementImpl.java:327)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl$FlowControlQueryExecuter.execute(CmdbDalStatementImpl.java:317)
at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:227)
at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalStatementImpl.executeQuery(CmdbDalStatementImpl.java:274)
... 32 more

 

Also thethe error was occured during upgrade from 10.11 to 10.20 and as per it the application was upgraded at application end but not upgraded at DB end.

Kindly share the steps to fix them.

 

Kind Regards,

Nitin

0 Likes
1 Solution

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

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

We didn't run the newdbtool as confirmed with mf expert also we don't use CM in our environment.

MF engg ask to run rebuild model on jmx ..this is done attaching for your reference

View solution in original post

0 Likes
7 Replies
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

I have the same problem, did you find any solution for this?

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

Seems like the class model or datamodel got stuck on the higher version.

Did you try to run the newDBtool on preview?

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

We didn't run the newdbtool as confirmed with mf expert also we don't use CM in our environment.

MF engg ask to run rebuild model on jmx ..this is done attaching for your reference

View solution in original post

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

Ah, Finally I understood where the composition relationships are retained, when they are not visible in the CDM_COMPOSITION_1 table! They are an attribute of the CIs! In this case you have to check if FCPORT has the INLINE_COMPOSITION attributes in the Oracle/MSSQL tables set properly, after you rebuild the Views/Models through JMX. They are required in order the contained CI to find it's container (the Node). I have some suspicion than during upgrade the model changed from the old one - using separate composition table to using the inlinecomposition column, part of the FCPORT table. 

 

Regards,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

Likes are appreciated!
Tags (1)
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

Yes @popadiyski , this was a new feature for UCMDB 10.10 with Inline composition links.
RnD noticed that most of the relationships are composition and this will use too much space on the DB. Also, the links themselves don't have much data on them but they still have their own tables and column in the DB. By storing the composition links on one of their ends we managed to improve the DB performance and usage.

I think this was advertised in the 10.10 release notes.

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

In your particular case, running the JMX method  rebuildModelDBSchemaAndViews revealed  that you had 2 missing columns on CIT FCport.

 

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Issue occurred after up-gradation rolback from UCMDB 10.20 to 10.11

Jump to solution

You should vote for this one https://community.microfocus.com/t5/CMS-Idea-Exchange/After-each-CP-upgrade-check-for-inconsistencies-with/idi-p/1794256

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
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.