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

Error while restarting the PPM development server after cloning from production

Highlighted
happa
Collector

Error while restarting the PPM development server after cloning from production

Hello,

 

We have upgraded PPM -dev from 7.5 sp3 to 8.0.While applying service pack after upgrade we were facing errors.

 

So HP recommended to rollback it to 7.5 and then again upgrade to 8.0.

 

But we didnt have the backup for PPM 7.5- DEV.So we cloned it from PPM-PROD.

 

After both the database cloning and filesystem cloning were completed we have changed the server.conf file accordingly.

 

Then we are unable to start the PPM-DEV server.It showing the error as follows :

 

"Failed to extract DB connection string from JDBC URL jdbc:oracle:thin::@nlvdhq41.sn-eu.asml.com:1521:PPMDEV"

 

Could you please tell how to proceed from here or what we need to do.

 

Thanks in Advance.

 

Best Regards,

Harika.
 

11 REPLIES
Utkarsh_Mishra
Honored Contributor

Re: Error while restarting the PPM development server after cloning from production

Hi Harika,

 

The problem is in the below Server.conf parameter. It sould be like

 

com.kintana.core.server.JDBC_URL=jdbc:oracle:thin:@<machine-name>:<PORT>:<SID>

 

I hope in you parameter the Machine Name is creating problem. Try to put you machine name as just

 

nlvdhq41

 

Then run kUpdateHtml.sh and then try to start the server. If still the issue persists then put the IP address in place of machine name, then again kUpdateHtml and start the server.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
happa
Collector

Re: Error while restarting the PPM development server after cloning from production

Hi Utkarsh,

 

I have changed it  and tried to run sh kUpdateHtml.sh

 

It is showing below error:

 

 

[sa_ppm@nlvdhq47 bin]$ sh kUpdateHtml.sh
JAVA_HOME = /opt/mercury/jdk1.5.0_11
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
Updating JBoss configuration files
Generating configuration files for all deployed ITG servers
Generating configuration files for kintana
java.sql.SQLException: No suitable driver
        at java.sql.DriverManager.getConnection(DriverManager.java:545)
        at java.sql.DriverManager.getConnection(DriverManager.java:171)
        at com.kintana.core.util.DBUtils.createJdbcConnection(DBUtils.java:796)
        at com.kintana.core.util.DBUtils.createJdbcConnection(DBUtils.java:758)
        at com.kintana.core.server.ServerConfigAgent.getDefaultClusterName(ServerConfigAgent.java:2384)
        at com.kintana.core.server.ServerConfigAgent.configure(ServerConfigAgent.java:559)
        at com.kintana.core.server.tools.GenConfFiles.getServerProperties(GenConfFiles.java:240)
        at com.kintana.core.server.tools.GenConfFiles.createServerConfigDocument(GenConfFiles.java:188)
        at com.kintana.core.server.tools.GenConfFiles.generateConfigFiles(GenConfFiles.java:102)
        at com.kintana.core.server.tools.GenConfFiles.main(GenConfFiles.java:90)
Exception in thread "main" java.lang.NullPointerException
        at java.util.StringTokenizer.<init>(StringTokenizer.java:182)
        at java.util.StringTokenizer.<init>(StringTokenizer.java:204)
        at com.kintana.ex.util.ExPresentationUtils.init(ExPresentationUtils.java:50)
        at com.kintana.core.server.ServerConfigAgent.configure(ServerConfigAgent.java:893)
        at com.kintana.core.server.tools.GenConfFiles.getServerProperties(GenConfFiles.java:240)
        at com.kintana.core.server.tools.GenConfFiles.createServerConfigDocument(GenConfFiles.java:188)
        at com.kintana.core.server.tools.GenConfFiles.generateConfigFiles(GenConfFiles.java:102)
        at com.kintana.core.server.tools.GenConfFiles.main(GenConfFiles.java:90)
Updating kStart.sh
Updating right-to-left style sheets
Generating right-to-left style sheets for all deployed ITG servers
Generating right-to-left style sheets for kintana
71 files created.
Generating dms.conf
dms.conf existed.  Not replaced.

 

Again I tried to restart server, but again it is showing same error as in attached file.

 

Best Regards,

Harika.

 

 

Utkarsh_Mishra
Honored Contributor

Re: Error while restarting the PPM development server after cloning from production

In the error log.. the JDBC URL is showing one extra colon (highlighted in red below)

 

jdbc:oracle:thin::@nlvdhq41:1521:PPMDEV

 

Correct format is jdbc:oracle:thin:@nlvdhq41:1521:PPMDEV

 

Correct this and then try again. Also if it fails then try to put IP address in place of machine name.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
happa
Collector

Re: Error while restarting the PPM development server after cloning from production

Hi Utkarsh,

 

After removing the colon the jdbc_url error is not there.

 

\But its showing some java errors.

 

I am attaching the java error.

 

Best Regards,

Harika.

Utkarsh_Mishra
Honored Contributor

Re: Error while restarting the PPM development server after cloning from production

Can you share the complete error log file.

 

Also try this

 

  1. Make sure the none of the Java process is running, if so then kill that Java process
  2. Then try to start the server again.
  3. If error is still coming then please share the complete error logs
Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
happa
Collector

Re: Error while restarting the PPM development server after cloning from production

Hi Utkarsh,

 

I have checked that there are no java processes running.

 

I am attaching the error log file.

 

Best regards,

Harika.

Utkarsh_Mishra
Honored Contributor

Re: Error while restarting the PPM development server after cloning from production

I think you have not configured the server.conf properly after the migration. Also you Oracle process is either in initialization or shutdown pahse, verfiry this as well.

 

Errors:

 

  1. error while generating MULTICAST_CLUSTER_NAME, using PRIMARY_BASE_URL instead.

    change the parameters accordingly in server.conf
  2. server:main:com.kintana.core.server:2011/07/21-13:23:49.391 CEST: java.sql.SQLException: ORA-01033: ORACLE initialization or shutdown in progress

    verify that Oracle is running

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Surendra Poosar
Frequent Visitor

Re: Error while restarting the PPM development server after cloning from production

Harika,

 

Did you execute the kConfig.sh to make sure that the required parameters are changed to reflect your DEV instance?

 

Also please make sure that the DB is up and available.

 

Thanks

Suirendra.

happa
Collector

Re: Error while restarting the PPM development server after cloning from production

Hi Utkarsh and Surendra,

 

There was some issue on database cloning, our database team have rectified it.
 
Now am able to start server, but after starting it is throwing error as account locked.
 
And front end wise it is showing instance ,
 
 
but if I try to login it is showing as cannot open connection.
 
I have asked my database team to unlock the acccount.
 
But he have noticed that it is locking Production account not DEV.
 
I have verified in server.conf file is pointing to correct connection.
 
Could you please advice me what to change inorder to access correct connection.
 
 
Best Regards,
Harika.
Utkarsh_Mishra
Honored Contributor

Re: Error while restarting the PPM development server after cloning from production

Run kConfig.sh and modify/correct the Database parameters.

 

Also make sure that the Oracle SID is  correctly configured in TNS.ora file.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
happa
Collector

Re: Error while restarting the PPM development server after cloning from production

Hi Utkarsh,

 

There were some database issues which has now been rectified.

 

Now the issue is resolved completely and we are able to access PPM-DEV successfully.

 

Thanks for your suggestions.

 

Best Regards,

Harka.

//Add this to "OnDomLoad" event