Exadata General (MOSC)

MOSC Banner

Exadata X8M-2 & 19c - why so many trace files?

edited Aug 15, 2021 1:18AM in Exadata General (MOSC) 6 commentsAnswered ✓

Presently we have one 19c (19.10) and several 11.2.0.4 RAC databases running on an X8M-2. The 19c database is generating an inordinate number of trace files. I am concerned that there will not be adequate space on /u01 to handle the diag directories of all databases once they have been migrated to 19c.

Looking for tips/patches for minimizing trace file generation. Many of the log file entries seem to be related to RDMA traffic such as:

OSSIPC:

IPCDAT DESTROY QP for qp 0x196a8758 ep 0x196a8530 drain start time 6987299977

OSSIPC:IPCDAT DESTROY QP for qp 0x196a8758 ep 0x196a8530 drain complete num reqs drained 0 drain end time 6987299977 drain time 0 msec time slept 0

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center