ASM STARTUP TAKES 3 MINUTES IN ORACLE RESTART (Solaris)
(Doc ID 2650868.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
Applied 12.1 July 2019 PSU and thereafter ASM STARTUP TAKES 3 MINUTES IN ORACLE RESTART(in solaris Operating system).
bash-3.2$ srvctl stop asm -f
-bash-3.2$ date
Sat Nov 9 08:09:54 GMT 2019<<<<<<<<<<<<<<<<<<<<<<
-bash-3.2$ ps -ef |grep pmon
21670 21642 0 08:09:57 pts/2 0:00 grep pmon
-bash-3.2$ srvctl start asm
-bash-3.2$ date
Sat Nov 9 08:13:19 GMT 2019<<<<<<<<<<<<<<<<<<<<<<<ASM startup with 3 minutes latency
//From ASM alert log:
==============
Instance shutdown complete
Thu Nov 09 08:13:19 2019==================>3 mins latency to trigger startup in ASM alert logs.
ERROR: -9(Error 27041, OS Error (SVR4 Error: 13: Permission denied
Additional information: 3)
)
ERROR: -9(Error 27041, OS Error (SVR4 Error: 13: Permission denied
Additional information: 3)
)
ERROR: -9(Error 27041, OS Error (SVR4 Error: 13: Permission denied
Additional information: 3)
)
ERROR: -9(Error 27041, OS Error (SVR4 Error: 13: Permission denied
Additional information: 3)
)
ERROR: -9(Error 27041, OS Error (SVR4 Error: 13: Permission denied
Additional information: 3)
)
ERROR: -9(Error 27041, OS Error (SVR4 Error: 13: Permission denied
Additional information: 3)
)
* instance_number obtained from CSS = 1, checking for the existence of node
0...
* node 0 does not exist. instance_number = 1
Starting ORACLE instance (normal) (OS id: 9749)
Thu Nov 09 08:13:19 2019<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<3 mins latency to trigger startup in ASM alert logs.
CLI notifier numLatches:3 maxDescs:618
Thu Nov 09 08:13:19 2019
Further drill down to starting the ASM instance with out mounting ASM diskgroups and it doesn't seems much difference.
3:00 mins latency > starting with initial configuration
2:50 mins latency >starting with empty asm_diskgroups
2:50 mins latency >starting with specific devices in asm_diskstring
//From asmtrace(asm_ora_<pid>.trc)
clsgpnpkwf.c:452] Result: (7) CLSGPNP_IO. (:GPNP01004:)Fatal: Cannot open
neither PEER nor PRDR GPnP wallet. No more wallets to verify GPnP
configuration (profile). Check GPnP configuration: wallet(s) either missing
or do not have access privileges. statres: -5, Wallet home :
/var/opt/oracle/grid_121012r1/gpnp/etrandb2/wallets/.
sult: (66) CLSGPNP_WALLET_NONE. (:GPNP00254:)Error initializing gpnp security
key provider: file wallet (LSKP-FSW).
2019-11-09 08:13:02.376: [ GPNP]clsgpnp_getCK: [at clsgpnp0.c:2541]
(:GPNP00233:)Fatal error: failed to get local gpnp security keys (wallet).
Gpnp profiles cannot be verified. ***LOCAL GPNP SETUP INVALID***.>
2019-11-09 08:13:02.377: [ GPNP]clsgpnp_InitIdSetCtxCK: [at
clsgpnp0.c:5230] Result: (66) CLSGPNP_WALLET_NONE. (:GPNP00267:)Cannot get
stored certkey for id=1
2019-11-09 08:13:02.377: [ GPNP]clsgpnp_Init: [at clsgpnp0.c:1026] Result:
(66) CLSGPNP_WALLET_NONE. (:GPNP00211:)Error getting certkeys.
2019-11-09 08:13:02.377: [ GPNP]clsgpnp_Init init failed. Error:
CLSGPNP_ERR (1) .
2019-11-09 08:13:02.389: [ default](:CLSUG0001:)Failed to initialize clsgpnp
context grv CLSGPNP_ERR (1). Return GPNP [12]
2019-11-09 08:13:02.389: [ default]clsugam:3: Failed to get gpnp profile.
Return GPNP [12].
2019-04-10 09:31:45.389984 : clsu_get_asm_mode failed with [12]
kgfmIsAppliance=0 (due to init)
KJHA:2phase calling kjha_ASMAction2 flag:8c0 statflag:0 clsrflag:
+++++++++++++++
Changes
Applied 12.1.0.2 July 2019 PSU in Solaris environment.
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 |
| Changes |
| Cause |
| Solution |
| References |