Projects are not opening after installing patch1 to QC12.55
« Back
Tags:
Question ID: 108778
▲
0
▼
♥ 0

After installing patch1 in QC dev environment, we are unable to open few projects.

We see 2 repeating Messages in the QC log:
===============================================

Can’t create a new database connection for url ‘jdbc:mercury:oracle://myORA.alm.myServer.com:3101;servicename=hpqcpdev.alm.myServer.com’ on getting connection to database server (jdbc:mercury:oracle://myORA.alm.myServer.com:3101;servicename=hpqcpdev.alm.myServer.com)
com.hp.alm.platform.exception.CTdException

[Mercury][Oracle JDBC Driver][Oracle]ORA-28001: the password has expired ;

Stack Trace:
java.sql.SQLException: [Mercury][Oracle JDBC Driver][Oracle]ORA-28001: the password has expired
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.OracleImplConnection.b(Unknown Source)
at com.mercury.jdbc.oracle.OracleImplConnection._(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseConnection.b(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseConnection.k(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseConnection.b(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseConnection.a(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at com.hp.alm.platform.db.CTdDriverManager.getConnection(CTdDriverManager.java:88)
wrapped in com.hp.alm.platform.exception.CTdException:
at com.hp.alm.platform.db.CTdDriverManager.getConnection(CTdDriverManager.java:95)
at com.hp.alm.platform.db.CConnectionPool.newConnection(CConnectionPool.java:821)
at com.hp.alm.platform.db.CConnectionPool.tryToGetConnection(CConnectionPool.java:610)
at com.hp.alm.platform.db.CConnectionPool.getConnection(CConnectionPool.java:377)
at com.hp.alm.platform.db.CConnectionManager.getNotTransactedConnection(CConnectionManager.java:243)
at com.hp.alm.platform.db.CConnectionManager.getConnection(CConnectionManager.java:217)
at com.hp.alm.platform.db.CAbsStatement.(CAbsStatement.java:87)
at com.hp.alm.platform.db.CTdPreparedStatement.(CTdPreparedStatement.java:97)
at com.hp.alm.platform.db.CTdPreparedStatement.(CTdPreparedStatement.java:89)
at com.hp.alm.platform.db.jdbc.JDBCTemplate$AbstractPreparedStatementCreator.create(JDBCTemplate.java:1252)
at com.hp.alm.platform.db.jdbc.JDBCTemplate.executeQuery(JDBCTemplate.java:1051)
at com.hp.alm.platform.db.jdbc.JDBCTemplateWithRetry.access$101(JDBCTemplateWithRetry.java:19)
at com.hp.alm.platform.db.jdbc.JDBCTemplateWithRetry$2.exec(JDBCTemplateWithRetry.java:56)
at com.hp.alm.platform.db.jdbc.JDBCTemplateWithRetry.executeWithRetry(JDBCTemplateWithRetry.java:98)
at com.hp.alm.platform.db.jdbc.JDBCTemplateWithRetry.executeQuery(JDBCTemplateWithRetry.java:52)
at com.hp.alm.platform.db.jdbc.JDBCTemplate.queryForObject(JDBCTemplate.java:775)
at com.hp.alm.platform.db.jdbc.JDBCTemplate.queryForObject(JDBCTemplate.java:750)
at com.hp.alm.platform.db.jdbc.JDBCTemplate.queryForInteger(JDBCTemplate.java:676)
at com.hp.alm.platform.repository.smartrepository.SmartRepositoryFile.exists(SmartRepositoryFile.java:815)
at com.hp.alm.platform.repository.smartrepository.SmartRepositoryFile.exists(SmartRepositoryFile.java:796)
at com.hp.alm.platform.repository.CRepositoryUtils.createDir(CRepositoryUtils.java:82)
at com.hp.alm.platform.siteadmin.directory.CProject.loadRepositoryRootFolders(CProject.java:3844)
at com.hp.alm.platform.siteadmin.directory.CProject.loadProjectProperties(CProject.java:3560)
at com.hp.alm.platform.siteadmin.directory.CProject.loadAllProjectProperties(CProject.java:3536)
at com.hp.alm.platform.directory.CProjectsDirectory.getItem(CProjectsDirectory.java:76)
at com.hp.alm.platform.connection.request.ConnectProject.execute(ConnectProject.java:51)
at com.hp.alm.platform.web.RequestsDispatcher.execute(Req

Marked as spam
Posted by (Questions: 193, Answers: 14)
Asked on December 18, 2018 8:58 pm
102 views
Answers (1)
▲
1
▼
✔
Private answer

This issue has NOTHING to do with patching the QC/ALM-Server.

The log says your ORACLE password has expired for some of your project schemas.

Normally, ALL QC-related Oracle ''QC-admin'' and Schema-users have STATIC / never expiring passwords or this type of issue will occur.
My guess is that you created these 2 projects about 90 or 180 days ago -- the default password expiration setting in Oracle.
When you create a new project in QC, IMMEDIATELY have the DBA set the schema-user's password to NEVER Expire.

The other rule of thumb is to have ALL schema passwords in Oracle be the same password string for convenience.
When you create new projects (QC creates new corresponding schemas in Oracle), it will assign the same ''default'' password to them as it creates them.

By default, this is ''tdtdtd'', but likely has been changed to something different.

The easiest thing to do would be to have the DBA re-enable the expired schema-user passwords and set back to their original password. This way, your stored password strings in QC will still be honored and the project(s) will start working again.

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on December 18, 2018 9:06 pm
▲
0
▼
Yeah, it was the Oracle passwords expiring.
( at December 18, 2018 9:07 pm)
« Back
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Got it!
X
Scroll to Top