<<Back to Oracle Main Page
Database Alertlog is Flooded with Trace File After DB Restart
After restart of the database I noticed today that the database alertlog is being flooded with trace files
Extract of Database Alert Log
===========================================================
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:Thu Aug 09 10:37:42 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:37:54 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:38:07 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:38:57 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:39:15 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:39:31 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:39:48 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:39:48 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:39:51 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:40:06 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:40:19 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc:
Thu Aug 09 10:41:10 2018
===========================================================
Extract of the Trace File
psdgbt: bind csid (1) does not match session csid (871)
psdgbt: session charset is UTF8
*** 2018-08-09 10:24:51.108
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=1, mask=0x0)
----- Error Stack Dump -----
----- Current SQL Statement for this session (sql_id=a0qc12302fzfk) -----
begin dbms_application_info.set_module(:1 , :2 ); end;
Cause
This is most probably caused by the listener and database not being started yet when the EM agent is started which picks up a wrong character set.
You can check that the issue is happening from the EM agent from trace files, e.g. emagent.trc showing:
PLS-00553: character set name is not recognized
Solution
Restart the EM agent to fix the issue
$emctl stop agent
$emctl start agent
Comments
Post a Comment