Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

PPM 9.14 DB refreshed by PPM 8.01 DB in error - Services not starting

SOLVED
Go to solution
Highlighted
Arjun_K
Member

PPM 9.14 DB refreshed by PPM 8.01 DB in error - Services not starting

Hi There,

 

We upgraded HP PPM 8.01 to 9.14. Since Oracle Apps was also installed, the extension was upgraded to 9.12 too.

In error, DBA refreshed the 9.14 Databse with that of 8.01 (PRD instance of PPM still on 8.01)  and we are now unable to start the HP PPM services (on 9.14)

How do we correct this error? Any suggestions on this would be of great help.

 

Attaching the ServerLog.

 

 

Warm Regards,
Mallikarjun.S
4 REPLIES
Arjun_K
Member

Re: PPM 9.14 DB refreshed by PPM 8.01 DB in error - Services not starting

UNABLE TO ATTACH - HERE IS THE LOG

============

 

 

STATUS server:main:SystemOut:2013/08/07-17:53:24.011 GMT-08:00: Logging reconfiguration complete
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2013/08/07-17:53:24.012 GMT-08:00: Running pre-startup checks for node kintana_n2 in clustered mode
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2013/08/07-17:53:24.125 GMT-08:00: Checking: /u01/ITG/server.conf
STATUS server:main:com.kintana.core.server.ServerStartupSanity:2013/08/07-17:53:24.209 GMT-08:00: All pre-startup checks completed for node kintana_n2
STATUS server:main:SystemOut:2013/08/07-18:53:25.775 PDT: Logging reconfiguration complete
STATUS server:main:SystemOut:2013/08/07-18:53:30.432 PDT:
---------------------------------------------------------
GMS: address is 102.21.206.16:48863 (cluster=HPPPMDEV)
---------------------------------------------------------
STATUS server:main:com.mercury.itg.core.jms.service:2013/08/07-18:53:32.465 PDT: Started PPMClusterPartition
STATUS server:main:com.mercury.itg.core.jms.service:2013/08/07-18:53:32.576 PDT: Starting HASingleton...
STATUS server:main:com.mercury.itg.core.jms.service:2013/08/07-18:53:32.576 PDT: Deploying JMS producer...
STATUS server:main:com.mercury.itg.core.jms.service:2013/08/07-18:53:33.024 PDT: Deployed JMS producer
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:33.724 PDT: Starting web context: ROOT
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:34.158 PDT: Completed start of web context: ROOT
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:34.191 PDT: Starting web context: jbossmq-httpil
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:34.258 PDT: Completed start of web context: jbossmq-httpil
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:41.351 PDT: Starting web context: admin-jmx
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:41.417 PDT: Completed start of web context: admin-jmx
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:41.446 PDT: Starting web context: dashboard
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:41.918 PDT: Completed start of web context: dashboard
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMJbossMonitor:2013/08/07-18:53:41.980 PDT: Starting web context: itg
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2013/08/07-18:53:42.395 PDT: Starting listener: com.mercury.itg.servlet.ServletContextListenerImpl
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2013/08/07-18:53:42.397 PDT: Completed Start of listener: com.mercury.itg.servlet.ServletContextListenerImpl
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2013/08/07-18:53:42.397 PDT: Starting listener: com.kintana.core.web.listener.ServerStartListener
STATUS server:main:com.kintana.core.server:2013/08/07-18:53:42.400 PDT: Servlet container: Apache Tomcat/5.5.31
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:42.941 PDT: Cannot load gloabl parameters
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:42.952 PDT: ORA-00904: "IS_CLUSTER_ONLY": invalid identifier

ERROR server:main:com.kintana.core.server:2013/08/07-18:53:43.457 PDT: Cannot load gloabl parameters
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:43.457 PDT: ORA-00904: "IS_CLUSTER_ONLY": invalid identifier

STATUS server:main:com.kintana.core.server:2013/08/07-18:53:43.469 PDT: Starting RMI over SSL on port 1098
STATUS server:main:SystemOut:2013/08/07-18:53:43.481 PDT: SunX509
STATUS server:main:com.kintana.core.server:2013/08/07-18:53:43.542 PDT: HP Project and Portfolio Management v9.14.0007
STATUS server:main:com.kintana.core.server:2013/08/07-18:53:43.581 PDT: Local IP address = 102.21.206.16
STATUS server:main:com.kintana.core.server:2013/08/07-18:53:43.722 PDT: License accepted.
STATUS server:main:com.kintana.core.server:2013/08/07-18:53:43.723 PDT: Wed Aug 07 17:53:43 GMT-08:00 2013
STATUS server:main:com.kintana.core.cache:2013/08/07-18:53:43.749 PDT: cache: initializing multicast [clusterName - HPPPMDEV]
STATUS server:main:SystemOut:2013/08/07-18:53:43.901 PDT:
---------------------------------------------------------
GMS: address is 102.21.206.16:44270 (cluster=HPPPMDEV)
---------------------------------------------------------
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.375 PDT: OraApps DB Link OM_LINK is not valid:
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.375 PDT: ORA-12532: TNS:invalid argument

ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.375 PDT: WARNING: Cannot determine OraApps version due to problem in db link OM_LINK. This may lead to performance degradation submitting concurrent requests.
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.402 PDT: ERROR: Could not insert server property.
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.402 PDT:  key   = null
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.402 PDT:  value = null
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.410 PDT: java.sql.SQLSyntaxErrorException: ORA-00913: too many values

 at com.kintana.core.db.pool.PooledPreparedStatement.executeUpdate(PooledPreparedStatement.java:189)
 at com.kintana.core.server.ServerConfigAgent.loadAppServerPropertiesTable(ServerConfigAgent.java:1752)
 at com.kintana.core.server.ISIntegrityServerImpl.<init>(ISIntegrityServerImpl.java:360)
 at com.kintana.core.server.Server.main(Server.java:669)
 at com.kintana.core.server.ServerStartupInitializer.startServer(ServerStartupInitializer.java:100)
 at com.kintana.core.web.listener.ServerStartListener.contextInitialized(ServerStartListener.java:61)

 Filtered Out 143 Stack Trace Lines.
ERROR server:main:com.kintana.core.server:2013/08/07-18:53:49.410 PDT: *** ERROR: Unable to start HP Project and Portfolio Management Server (KNTA-10538)
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2013/08/07-18:53:49.410 PDT: Completed Start of listener: com.kintana.core.web.listener.ServerStartListener
STATUS server:main:com.mercury.itg.core.debug.monitor.PPMTomcatMonitor:2013/08/07-18:53:49.410 PDT: Starting listener: org.springframework.web.context.ContextLoaderListener
STATUS server:main:com.mercury.itg.core.scheduler:2013/08/07-18:54:00.394 PDT: Services scheduler and consumer node
STATUS server:main:com.mercury.itg.core.scheduler:2013/08/07-18:54:00.394 PDT: Clustered install - services scheduler will be started if failover occurs
STATUS server:main:com.mercury.itg.core.jms.service:2013/08/07-18:54:01.853 PDT: PPM Heavy Service Listener started
STATUS server:main:com.mercury.itg.core.jms.service:2013/08/07-18:54:01.906 PDT: PPM Light Service Listener started
ERROR :main:com.mercury.itg.integration.service.impl.QCIntegrationServiceImpl:2013/08/07-18:54:02.024 PDT: org.springframework.dao.InvalidDataAccessResourceUsageException: could not execute query; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query
ERROR :main:com.mercury.itg.integration.service.impl.QCIntegrationServiceImpl:2013/08/07-18:54:02.032 PDT: org.springframework.dao.InvalidDataAccessResourceUsageException: could not execute query; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query
ERROR :main:com.kintana.dms:2013/08/07-18:54:02.033 PDT: DMSLoader verify dms config
java.lang.RuntimeException: Couldn't retrieve Migration Controller Integration Service
 at com.kintana.dms.migration.controller.MigrationController.getConfig(MigrationController.java:85)

Warm Regards,
Mallikarjun.S
Utkarsh_Mishra
Honored Contributor
Solution

Re: PPM 9.14 DB refreshed by PPM 8.01 DB in error - Services not starting

What I get from your message is that on 9.14 (upgraded version); DBA refresh it with 8.x version DB.

 

In this case the safest approach is on 9.14 instance restore the File system with 8.x and then perform the upgrade agian. This should work.

 

Or restore the 9.14 DB from your backup.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
randull
HPE Expert

Re: PPM 9.14 DB refreshed by PPM 8.01 DB in error - Services not starting

Hi,

 

As Utkarsh is saying the best approach here will be to restore the backup of your 9.14 DB instance on the same instance, then upgrade your 8.1 instance to 9.14 and finally refresh the 9.14 DB with your dev database.

 

The problem is that between major releases usually the database structure change, and when you run the upgrade scripts these changes take place. But, if you do not upgrade the database or use a database from a previous major versions it do not have those changes and you will get lot of issues.

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Arjun_K
Member

Re: PPM 9.14 DB refreshed by PPM 8.01 DB in error - Services not starting

Hello Randul & Utkarsha,

 

We decided to go for a fresh upgrade instead of debugging the issue.

 

Here are the steps that we followed to have the issue resolved (technically a work around)

- Backup the PPM Home Directory

- Copy the PPM home directory from PROD (Which had the version 8.01)

- This way we have a clone of PPM 8.01 on our DEV machine.

- Configure and test the clone on 8.01

- Re Upgrade 8.01 to 9.10 - and so on.

 

Thank you for your suggestions.

 

 

Warm Regards,
Mallikarjun.S
//Add this to "OnDomLoad" event