My Oracle Support Banner

TNS Listener Up And Running But Jobs In State CHAIN_STALLED And Hitting ORA-12537: TNS:connection Closed / ORA-12541: no listener (Doc ID 2099496.1)

Last updated on FEBRUARY 20, 2023

Applies to:

Oracle Life Sciences Data Hub - Version 2.2.2 and later
Information in this document applies to any platform.


LSH 2.2.2.

Cannot submit any job although the database and TNS listener are up and running. There is not firewall between any of the layers involved that may have new rules implemented.

1. ORA-12537: TNS:connection closed.

2. select * from all_scheduler_job_run_details where owner=<your_jobs_owner> order by actual_start_date desc;

It displays: ORA-12541: TNS: no listener ORA-06512 at <OWNER>.DIAL_PROCESS_MGMT_PKG, line 1457 ORA-06512 at line 1.

3. There are not changes at OS/DB/LSH level, but could see below error in Alert log:

Error 1012 trapped in 2PC on transaction 47.22.169409. Cleaning up.
Error stack returned to user:
ORA-01012: not logged on
ORA-02063: preceding line from USER_DB_NAME.PH.CHBS
ORA-00028: your session has been killed
ORA-02063: preceding line from USER_DB_NAME.PH.CHBS
ORA-06512: at "D<jobs_owner>.DIAL_PROCESS_MGMT_PKG", line 1078
ORA-06512: at line 1
Errors in file /<path>/DB_ALIAS_j004_21213.trc (incident=360973):
ORA-00603: ORACLE server session terminated by fatal error
ORA-01012: not logged on



To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.