Massive Increase Of Trace Files On the ODA After Upgrading to 12.2.x
(Doc ID 2469954.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database Appliance Software - Version 12.1.2.10 to 12.2.1.4.0 Bare Metal [Release 12.1 to 12.2]Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Information in this document applies to any platform.
Symptoms
Running out of storage after performing an upgrade to 12.2.x ODA
Trace files show
The Oracle 12.2 database
This writes a lot of logfiles (around 20 trace files per minute) into the Diagnostic-Dir under /u01/app/oracle/diag/rdbms/dbname/dbname/trace
The content is always similar and trace file is always created when log in to
the database as SYS AS SYSDBA. Attached trace files for your reference.
Details from trace file:
2018-02-15 ..: [GIPCXCPT][GIPCXCPT] gipcInternalSetAttribute:
failed during gipcInternalSetAttribute, ret gipcretInvalidAttribute (5)
2018-02-15 00:55:01.071 : [GIPCXCPT][GIPCXCPT] gipcSetAttributeNativeF [clscrsconGipcConnect : clscrscon.c : 655]:
EXCEPTION[ ret gipcretInvalidAttribute (5) ] failure for obj 0x160d3600 [000000000000002e]
{ gipcEndpoint : localAddr '', remoteAddr '', numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0,
pidPeer 0, readyRef (nil), ready 0, wobj (nil), sendp (nil) status 13flags 0x20000000, flags-2 0x0, usrFlags 0x0 },
name 'traceLevel', val 0x7ffcdbbb8114, len 4, flags 0x0
...
2018-02-15 ..: [GIPCXCPT][GIPCXCPT] gipcInternalSetAttribute: failed during gipcInternalSetAttribute, ret gipcretInvalidAttribute (5)
2018-02-15 ..: [GIPCXCPT][GIPCXCPT] gipcSetAttributeNativeF [clscrsconGipcConnect : clscrscon.c : 655]: EXCEPTION[ ret gipcretInvalidAttribute (5) ]
failure for obj 0x160d34e0 [000000000000006b]
{ gipcEndpoint : .......
..... name 'traceLevel', ......etc
Changes
upgrade to 12.2
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! |