ETL Error : Caused By: java.sql.SQLException: Listener refused the connection (Doc ID 2052781.1)

Last updated on FEBRUARY 10, 2017

Applies to:

Oracle Application Access Controls Governor - Version 8.6.3 and later
Information in this document applies to any platform.

Symptoms

On :  8.6.3 version, Application Access Contr. Gov.

When user run access synchronization, it failed with below error in grc.log and catalina.out.


ERROR
------------

grc.log
---------
2015-08-26 15:00:53,190 DEBUG [pool-10-thread-1] EtlJob:255 END OF AACG ETL
2015-08-26 15:00:53,191 ERROR [pool-10-thread-1] EtlJob:346 Error occured in EtlJob
oracle.apps.grc.dataaccessfacade.exception.UpdateException: Access etl failed.
at oracle.apps.grc.appservices.EtlJob.runJob(SourceFile:335)
at oracle.apps.grc.scheduler.job.AbstractJob.run(AbstractJob.java:355)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
2015-08-26 15:00:53,191 ERROR [pool-10-thread-1] AbstractJob:383 Error occurred in concrete job implementation
oracle.apps.grc.common.job.JobExecutionException: Error occured during Sync Job


catalina.out
----------------
SEVERE: Session LOADACCESSDATA (22044) fails with return code 12505.
ODI-1226: Step WF_LOCAL_ROLES_table_exists fails after 1 attempt(s).
ODI-1228: Task WF_LOCAL_ROLES_table_exists (Variable) fails on the target  connection physical_schema_src.
Caused By: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Navigate to Administration Management > Manage Application Data.
2. Select a required datasource.
3. Go to Action > Run Access synchronization.
4. Check the job status.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot able to run access synchronization.

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