Highlighted
Established Member..
Established Member..
897 views

Upgrade from uCMDB v10.00 to 10.01 CUP6 renders system unavailable

We have attempted upgrade of our uCMDB 10.00 system to 10.01 with CUP6, and each time the upgrade goes through successfully but the status page does not load, nor can we get to the application login page.

 

there is the following error in the error.log file:-

 

2013-09-25 12:01:41,472 [Starter for "state_management" (during Writer server startup). (customer 1, id name: Default Client)] (Transaction.java:82) ERROR - Transaction with ID: 2822 Failed and started to rollback. (ref:com.mercury.topaz.cmdb.server.transaction.Transaction@b37468c,threadId:85) 2013-09-25 12:01:41,473 [Starter for "state_management" (during Writer server startup). (customer 1, id name: Default Client)] (LogUtil.java:30) ERROR - Error rolling back connection [3d733a78] java.sql.SQLException: Connection com.mercury.jdbc.sqlserverbase.ddai@3d733a78 is closed.  at org.apache.commons.dbcp.DelegatingConnection.checkOpen(DelegatingConnection.java:398)  at org.apache.commons.dbcp.DelegatingConnection.rollback(DelegatingConnection.java:368)  at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalConnection.rollback(CmdbDalConnection.java:143)  at com.mercury.topaz.cmdb.server.manage.dal.CmdbDalTransaction.rollback(CmdbDalTransaction.java:37)  at com.mercury.topaz.cmdb.server.transaction.Transaction.rollback(Transaction.java:107)  at com.mercury.topaz.cmdb.server.transaction.Transaction.commit(Transaction.java:83)  at com.mercury.topaz.cmdb.server.transaction.TransactionManager.commit(TransactionManager.java:88)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerImpl.commitTransaction(UnifiedResourceManagerImpl.java:405)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerImpl.commitTransaction(UnifiedResourceManagerImpl.java:388)  at com.mercury.topaz.cmdb.server.urm.transactions.URMTransactionWrapper.execute(URMTransactionWrapper.java:25)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerImpl.put(UnifiedResourceManagerImpl.java:96)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerStatisticsDecorator$5.callDecoratedMethod(UnifiedResourceManagerStatisticsDecorator.java:213)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerStatisticsDecorator$StatisticsMethodWrapper.<init>(UnifiedResourceManagerStatisticsDecorator.java:60)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerStatisticsDecorator$5.<init>(UnifiedResourceManagerStatisticsDecorator.java:211)  at com.mercury.topaz.cmdb.server.urm.impl.UnifiedResourceManagerStatisticsDecorator.put(UnifiedResourceManagerStatisticsDecorator.java:211)  at com.mercury.topaz.cmdb.server.util.URMOfflineTool.put(URMOfflineTool.java:111)  at com.mercury.topaz.cmdb.server.manage.settings.InternalSettings.setSystemParameter(InternalSettings.java:148)  at com.mercury.topaz.cmdb.server.base.cfg.impl.InternalSettingsProvider.setValue(InternalSettingsProvider.java:52)  at com.mercury.topaz.cmdb.server.base.cfg.impl.SettingsReaderImpl.setProperty(SettingsReaderImpl.java:137)  at com.mercury.topaz.cmdb.server.upgrade.impl.SubsystemManagersUpgrader.updateUpgraderVersion(SubsystemManagersUpgrader.java:266)  at com.mercury.topaz.cmdb.server.upgrade.impl.SubsystemManagersUpgrader.performPostStartupUpgrade(SubsystemManagersUpgrader.java:152)  at com.mercury.topaz.cmdb.server.upgrade.impl.SubsystemManagersUpgrader.postStartup(SubsystemManagersUpgrader.java:140)  at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startup(ServiceComponentImpl.java:123)  at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startupSubsystemManagers(ServiceComponentImpl.java:110)  at com.mercury.topaz.cmdb.server.manage.service.impl.ServiceComponentImpl.startUp(ServiceComponentImpl.java:72)  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:442)  at com.mercury.topaz.cmdb.server.manage.instance.CustomerController.access$200(CustomerController.java:27)  at com.mercury.topaz.cmdb.server.manage.instance.CustomerController$RunnerWrapper.run(CustomerController.java:404)  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)

 

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

Re: Upgrade from uCMDB v10.00 to 10.01 CUP6 renders system unavailable

Looks like from 10.01 onwards you can't use SQL Server 2005, as the MERGE statement is used (found in error.log) which was a new feature from SQL Server 2008. v10.00 didn't use this as we had it running fine under SQL Server 2005.

Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Upgrade from uCMDB v10.00 to 10.01 CUP6 renders system unavailable

Good catch, Ben.

Please find attached support matrix for UCMDB 10.01. It's showing MSSQL 2005 out of scope.

The doc itself could be found along with other prfs at C:\hp\UCMDB\UCMDBServer\deploy\ucmdb-docs\docs\eng\pdfs\ folder.

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
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.