Tracefiles Being Generated After Upgrade to 126.96.36.199 : Segment does not exist
Last updated on DECEMBER 25, 2016
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 25-Dec-2016***
After migration to 220.127.116.11, 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 .
Upgrade to 18.104.22.168
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms