The Timeslicing Job Fails With Exception: [CA Clarity][Oracle JDBC Driver]Object has been closed.

Document ID : KB000004960
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The Time Slicing job does not complete and other jobs may fail as well with the exception: 
[CA Clarity][Oracle JDBC Driver]Object has been closed. 

An error similar to the following may show up in the the background server (bg-ca.log) file:

ERROR 2016-09-13 02:27:13,550 [Dispatch Time Slicing 13sep : 
bg2@ABC123 (tenant=clarity)] niku.blobcrack 
(clarity:<string>:22038092__140A3BF5-28F5-4071-A0F4-6700CD0EBE81: 
Time Slicing 13sep) Exception during blobcrack process 
com.niku.union.persistence.PersistenceException: 
SQL error code: 0 
Error message: [CA Clarity][Oracle JDBC Driver]Object has been closed. 

Environment:
Supported Windows and Linux environments for 14.2 and 14.3
Cause:

First, verify that the SQLNET.ora file on your Oracle DBMS has the following parameters set.

If not, please set them as per the requirements for PPM:

SQLNET.INBOUND_CONNECT_TIMEOUT = 0 
SQLNET.SEND_TIMEOUT = 600

The second reason for seeing this exception is that this may be caused by the Data Direct Oracle driver version used by PPM.

 

Resolution:

From a 15.1 environment, copy the c-oracle.jar file from <CLARITY_HOME>/lib/ to the <CLARITY_HOME/lib> folder in your 14.2 or 14.3 environment.

If you have trouble locating the file, please open a support case to contact CA Technical Support.

Restart the bg service(s):

<CLARITY_HOME>/bin/service stop start bg

Re-run the Time Slicing job.

Note: This problem was not reported in 14.4 or 15.1.