My Oracle Support Banner

SHIA:: After upgrade to 12c listener was recycling (Doc ID 2133292.1)

Last updated on FEBRUARY 13, 2019

Applies to:

Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After upgrading to 12C listener was recycling regularly for sometime.

 

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Fist occurrence of service died@

03-FEB-2016 19:17:53 * service_died * LsnrAgt * 12537 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<03-FEB-2016 19:17:53 * pid * 0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++




2016-02-03 19:17:53.260014 :CLSDYNAM:1252869888: [ora.<listener>.lsnr]{0:0:22836} [clean] lsnrctl clean: Going to kill 7197)
The command completed successfully

2016-02-03 19:17:53.260043 :CLSDYNAM:1252869888: [ora.<listener>.lsnr]{0:0:22836} [clean] Trying to stop PID = 7197)
The command completed successfully

 

File_name :: ohasd_oraagent_oracle_3646.trc

2016-02-12 16:06:11.308544 : GPNP:1829824256: clsgpnp_Init: [at clsgpnp0.c:1004] Result: (66) CLSGPNP_WALLET_NONE. (:GPNP00211:)Error getting certkeys.

2016-02-12 16:06:11.308568 : GPNP:1829824256: clsgpnp_Init init failed. Error: CLSGPNP_ERR (1) .
2016-02-12 16:06:11.310405 : default:1829824256: (:CLSUG0001:)Failed to initialize clsgpnp context grv CLSGPNP_ERR (1). Return GPNP [12]
2016-02-12 16:06:11.310411 : default:1829824256: clsugam:3: Failed to get gpnp profile. Return GPNP [12].
2016-02-12 16:06:11.310463 :CLSDYNAM:1829824256: [ora.RAID5.dg]{0:0:2} [check] Error getting ASM Mode returningASM mode info = -1 <<-----------
2016-02-12 16:06:11.310584 :CLSDYNAM:1829824256: [ora.RAID5.dg]{0:0:2} [check] DgpAgent::runCheck: asm stat asmRet 0
2016-02-12 16:06:25.728427 : AGFW:1857140480: {0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:2574
2016-02-12 16:06:26.871119 : CLSDMC:1829824256: command 0 failed with status 1
2016-02-12 16:06:26.871146 :CLSDYNAM:1829824256: [ora.evmd]{0:0:2} [check] ClsdmClient::sendMessage clsdmc_respget return: status=0, ecode=1
2016-02-12 16:06:26.871163 :CLSDYNAM:1829824256: [ora.evmd]{0:0:2} [check] DaemonAgent::check returned 0
2016-02-12 16:06:26.871176 :CLSDYNAM:1829824256: [ora.evmd]{0:0:2} [check] Deep check returned 1
2016-02-12 16:06:55.113534 : AGENT:1855039232: {0:0:759} {0:0:759} Created alert : (:CRSAGF00113:) : Aborting the command: check for resource: ora.L_EMREP2.lsnr ausoutemid01 1
2016-02-12 16:06:55.113577 :CLSDYNAM:1855039232: [ora.L_EMREP2.lsnr]{0:0:759} [check] (:CLSN00110:) clsn_agent::abort {
2016-02-12 16:06:55.113625 :CLSDYNAM:1855039232: [ora.L_EMREP2.lsnr]{0:0:759} [check] abort {
2016-02-12 16:06:55.113640 :CLSDYNAM:1855039232: [ora.L_EMREP2.lsnr]{0:0:759} [check] Agent::abort last call info:
2016-02-12 16:06:55.113656 :CLSDYNAM:1855039232: [ora.L_EMREP2.lsnr]{0:0:759} [check] :Time:02/12/2016 15:43:05.740 Tint:{0:0:2} action:104

File_name :: ohasd_oraagent_oracle.trc.20160212

 

Cause

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
Symptoms
Cause
Solution
References


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