Failed to increment sequence of ENABLED_EXTENSIONS_VERSION and reload data
Question ID: 107702

We are getting the following exception when trying to restore projects in our ALM 11 instance.

Failed to Restore Project;
Failed to restore project;
Failed to increment sequence of ENABLED_EXTENSIONS_VERSION and reload data;
[Mercury][Oracle JDBC Driver]Object has been closed.;

Stack Trace:
java.sql.SQLException: [Mercury][Oracle JDBC Driver]Object has been closed.
at com.mercury.jdbc.oraclebase.dda4.b(Unknown Source)
at com.mercury.jdbc.oraclebase.dda4.a(Unknown Source)
at com.mercury.jdbc.oraclebase.dda3.b(Unknown Source)
at com.mercury.jdbc.oraclebase.dda3.a(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseConnection.prepareStatement(Unknown Source)
at com.mercury.jdbc.oraclebase.BaseConnection.prepareStatement(Unknown Source)
at com.mercury.optane.core.db.CTdPreparedStatement.createPreparedStatement(
at com.mercury.optane.core.db.CTdPreparedStatement.(
at com.mercury.optane.core.db.CTdPreparedStatement.(
at com.mercury.optane.core.db.CTdPreparedStatement.(

Originally we realized that we were unable to perform activities like creating new projects etc. when we started to prepare to upgrade to ALM ver. 12

We mistakenly thought that the issue was that the project/schema user password was incorrect so we followed the procedure outlined in HPE KB article KM00463817.

When we were unable to restore the projects we realized that the actual issue was that our DBA had changed the "system" password in our Oracle instance. We then changed the DB Admin User password, under the DB Servers tab in Site Admin, to the correct password.

After this when we try to restore the project we get the above exception. Can someone please assist me???

Marked as spam
Posted by (Questions: 113, Answers: 8)
Asked on July 13, 2017 4:34 pm
Answers (1)
Private answer

Doing a quick search on Google I found the following article...

''Object has been closed'' error when lots of data is inserted with Oracle JDBC driver


The exact cause is not known at this time.


This issue is not caused by the driver.
The connection pool configuration or whatever mechanism is in use to get the connection should be monitored.

After you updated the password for the DB Admin User did you restart the ALM Service? This might close some of the connections to the DB server and allow the operation to complete.

Marked as spam
Posted by (Questions: 0, Answers: 309)
Answered on July 13, 2017 4:39 pm
Restarting the ALM service worked. I'll hope fully I will not have the issue in the future but if I do I'll reboot.
( at July 13, 2017 4:40 pm)

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

Scroll to Top