Strange trace files generated in RDBMS 19.6.
Date: Thu, 4 Jun 2020 11:07:03 +0200
Message-ID: <CAO8HWHbL+2xbZkucdEf8UZ22-LxKpmucZCWvdV+m-cy87WL_TA_at_mail.gmail.com>
Hello,
Jun 4 10:01 aisbip2_ora_8966_9012_lt.trc Jun 4 10:01 aisbip2_ora_8966_8982_lt.trc Jun 4 10:01 aisbip2_ora_8966_9011_lt.trc Jun 4 10:01 aisbip2_ora_8966_9009_lt.trc Jun 4 10:01 aisbip2_ora_8966_9008_lt.trc Jun 4 10:01 aisbip2_ora_8966_9010_lt.trcJun 4 10:01 aisbip2_ora_8966_9000_lt.trc Jun 4 10:01 aisbip2_ora_8966_9007_lt.trc
Jun 4 10:01 aisbip2_ora_8966_8997_lt.trc Jun 4 10:01 aisbip2_ora_8966_8991_lt.trc Jun 4 10:01 aisbip2_ora_8966_8992_lt.trc Jun 4 10:01 aisbip2_ora_8966_8990_lt.trc Jun 4 10:01 aisbip2_ora_8966_8989_lt.trc Jun 4 10:01 aisbip2_ora_8966_8988_lt.trcJun 4 10:01 aisbip2_ora_8966_8986_lt.trc Jun 4 10:01 aisbip2_ora_8966_8987_lt.trc Jun 4 10:01 aisbip2_ora_8966_8985_lt.trc
Jun 4 10:01 aisbip2_ora_8966_8984_lt.trc Jun 4 10:01 aisbip2_ora_8966_8981_lt.trc Jun 4 10:01 aisbip2_ora_8966_8983_lt.trc
In each file, we see something like
Dump file /ORA/dbs0a/AISBIP_AISBI_RAC52/diag/rdbms/aisbip_aisbi_rac52/AISBIP2/trace/aisbip2_ora_8966_8983_lt.trc Build label: RDBMS_19.3.0.0.0DBRU_LINUX.X64_190417Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.6.0.0.0
Build label: RDBMS_19.3.0.0.0DBRU_LINUX.X64_190417 ORACLE_HOME: xxxxxxxxxxx System name: Linux Node name: xxxxxxxxxx Release: 3.10.0-1062.1.2.el7.x86_64 Version: #1 SMP Mon Sep 16 14:19:51 EDT 2019 Machine: x86_64
Instance name: AISBIP2
Redo thread mounted by this instance: 2
Oracle process number: 0
Unix process pid: 8966, thread id: 8983, image: _LT
- 2020-06-04T10:01:28.718971+02:00 Process termination requested for pid 8966_8983_LT [source = rdbms], [info = 2] [request issued by pid: 8966, uid: 1286]
And that's all... There are many many files (one per process/thread) generated there, and DIAG filesystem becomes unusable.. these trace files are generated almost constantly... No idea if this correspond to a real problem (but no users are complaining about killed sessions). It could be another useless trace file generated by the DB. We have only seen this in this DB after the upgrade to 19.x . We are not using the threaded architecture (threaded_execution=false)
These trace files do not have an associated .trm file... only .trc. Besides, the filename convention is different... in the "normal" trace files, the instance name is in uppercase (AISBIP2), but here is lowercase (aisbip2).
Anybody seen a similar behavior ?
regards.
Nilo Segura
Database Support
CERN - Geneva
Switzerland
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Jun 04 2020 - 11:07:03 CEST