Tracefiles Being Generated After Upgrade to 11.2.0.2 : Segment does not exist...

郑全

In this Document
[size=-1]   Symptoms
   Changes
   Cause
   Solution
   References

---

[size=-1]This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to: Oracle Server - Enterprise Edition - Version: 11.2.0.2 to 11.2.0.2 - Release: 11.2 to 11.2
Information in this document applies to any platform.

Symptoms After migration to 11.2.0.2, trace files are generated with content like:

  *** 2011-01-06 22:05:18.924
  *** SESSION ID:(10.2947) 2011-01-06 22:05:18.924
  *** CLIENT ID:() 2011-01-06 22:05:18.924
  *** SERVICE NAME:(SYS$BACKGROUND) 2011-01-06 22:05:18.924
  *** MODULE NAME:(KTSJ) 2011-01-06 22:05:18.924
  *** ACTION NAME:(KTSJ Slave) 2011-01-06 22:05:18.924

  Segment does not exist


The frequency seems to be related to activity in the database.
The alert log contains no entry. This happens for all  instances running on this ORACLE_HOME .
Changes Upgrade to 11.2.0.2
Cause The issue has been discussed in Bug 11671938 - TRC FILE AFTER 11.2.0.2 PATCH: SEGMENT DOES NOT EXIST closed as duplicate of

Bug 10420891 - W00 PROCESS GETS TRACE FILES WITH

Both bugs are unpublished.

Solution There is no impact on the database behavior as those are messages wrongly printed by some internal processes, and they can be safely ignored.

If these traces raise space issues, you can also apply the patch 10420891 if available.

For Windows platform, patch 10420891 is planed to be included in 11.2.0.2 patch 8.