EM 13c: Repository Database Alert log Getting Filled With "ORA-01555 Caused By SQL Statement Below (SQL ID: 4atpmpqmu7dzu, SCN: 0x073a.48c7968c)"
(Doc ID 2730482.1)
Last updated on JANUARY 17, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
13c Enterprise Manager Cloud Control configured with 12.1.0.2 as a repository database.
Alert log of Repository database is getting filled with below error:
Tue Nov 17 09:16:36 2020
ORA-01555 caused by SQL statement below (SQL ID: 4atpmpqmu7dzu, SCN: 0x073a.48e28f7f):
Tue Nov 17 09:16:36 2020
BEGIN EM_NOTIF_PKG.DEQUEUE(:1 , :2 , :3 , :4 , :5 , :6 ); END;
Tue Nov 17 11:16:36 2020
ORA-01555 caused by SQL statement below (SQL ID: 4atpmpqmu7dzu, SCN: 0x073a.48e45f60):
Tue Nov 17 11:16:36 2020
BEGIN EM_NOTIF_PKG.DEQUEUE(:1 , :2 , :3 , :4 , :5 , :6 ); END;
ORA-01555 caused by SQL statement below (SQL ID: 4atpmpqmu7dzu, SCN: 0x073a.48e28f7f):
Tue Nov 17 09:16:36 2020
BEGIN EM_NOTIF_PKG.DEQUEUE(:1 , :2 , :3 , :4 , :5 , :6 ); END;
Tue Nov 17 11:16:36 2020
ORA-01555 caused by SQL statement below (SQL ID: 4atpmpqmu7dzu, SCN: 0x073a.48e45f60):
Tue Nov 17 11:16:36 2020
BEGIN EM_NOTIF_PKG.DEQUEUE(:1 , :2 , :3 , :4 , :5 , :6 ); END;
Current configuration of UNDO:
SQL> show parameter undo
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
temp_undo_enabled boolean FALSE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
temp_undo_enabled boolean FALSE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
Collected UNDO details with the help of below document:
Script - Check Current Undo Configuration and Advise Recommended Setup <Note ID 1579035.1>
Retention Recommendation Shows the below:
-----------------------------------------------------
The best possible retention with current configuration is : 1111035 Seconds
The longest running query ran for : 1909 Seconds
The undo retention required to avoid errors is : 1909 Seconds
PL/SQL procedure successfully completed.
-----------------------------------------------------
The best possible retention with current configuration is : 1111035 Seconds
The longest running query ran for : 1909 Seconds
The undo retention required to avoid errors is : 1909 Seconds
PL/SQL procedure successfully completed.
Changes
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 |