Purging Large Data Fails with "java.sql.SQLException: java.sql.SQLException: Already closed" (Doc ID 2083607.1)

Last updated on JANUARY 06, 2017

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Symptoms

While trying to purge the OAG audit database using the script per document Purging the Reports Database :


the bellow error is encountered:

Connecting to configuration at : federated:file:////tess2/oracle/webtier/oag/apigateway/conf/fed/configs.xml

Purging data older than: Thu Oct 23 17:00:00 PDT 2014
Purging table: audit_log_sign... deleted 0 rows
Purging table: transaction_data... deleted 0 rows
Purging table: audit_message_payload...Traceback (most recent call last):
File "/tess2/oracle/webtier/oag/apigateway/system/lib/jython/dbpurger.py", line 139, in main()
File "/tess2/oracle/webtier/oag/apigateway/system/lib/jython/dbpurger.py", line 139, in main()
File "/tess2/oracle/webtier/oag/apigateway/system/lib/jython/dbpurger.py", line 135, in main
Purger.purge(connection, int(options.retain[0]), options.retain[1]);
at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:114)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:191)
at com.vordel.reporting.maintenance.Purger.purge(Purger.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

java.sql.SQLException: java.sql.SQLException: Already closed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms