EM 13.5C: Exadata/ZDLRA Cell Storage Target Stuck In Pending Status Post RU19/RU20 On Agent Side
(Doc ID 3030588.1)
Last updated on JUNE 25, 2024
Applies to:
Enterprise Manager for Exadata - Version 13.5.0.0.0 and laterEnterprise Manager Base Platform - Version 13.5.0.0.0 and later
Information in this document applies to any platform.
Symptoms
Exadata/ZDLRA Cell storage target stuck in pending status after RU19 or RU20 Patch on Agent side.
Agent logs showing below error when collecting Response : <AGENT_INST>/sysman/log/gcagent.log
2024-03-11 08:45:48,767 [532:99112BA7] DEBUG - Executing cleanup action End session [3580] for task oracle_exadata:<CELL_STORAGE>:Response
2024-03-11 08:45:48,767 [532:99112BA7] DEBUG - Target Manager session 3580 ended
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Cleaning old sessions (maxAgeInMs=259200000 , #sessions to scan=1)
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Released coll and host quotas oracle_exadata:<CELL_STORAGE>:Response
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - update for FIVEMIN, expDur = 5000, duration is 1
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Scheduling next oracle_exadata:<CELL_STORAGE>:Response after delay 299999 including periodShift of 0 milliseconds
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Skipped task oracle_exadata:<CELL_STORAGE>:Response due to non-existent, broken, or not fully loaded target
2024-03-11 08:45:48,767 [532:99112BA7] DEBUG - Target Manager session 3580 ended
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Cleaning old sessions (maxAgeInMs=259200000 , #sessions to scan=1)
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Released coll and host quotas oracle_exadata:<CELL_STORAGE>:Response
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - update for FIVEMIN, expDur = 5000, duration is 1
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Scheduling next oracle_exadata:<CELL_STORAGE>:Response after delay 299999 including periodShift of 0 milliseconds
2024-03-11 08:45:48,768 [532:99112BA7] DEBUG - Skipped task oracle_exadata:<CELL_STORAGE>:Response due to non-existent, broken, or not fully loaded target
getmetric command gives below error :
<AGENT_HOME>/bin/emctl getmetric agent <CELL_STORAGE>,oracle_exadata,Response
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 1996, 2021 Oracle Corporation. All rights reserved.
EMD getmetric error: the Response metric does not exist for oracle_exadata target <CELL_STORAGE>
Oracle Enterprise Manager Cloud Control 13c Release 5
Copyright (c) 1996, 2021 Oracle Corporation. All rights reserved.
EMD getmetric error: the Response metric does not exist for oracle_exadata target <CELL_STORAGE>
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 |