Exadata General (MOSC)

MOSC Banner

gipcdOUT.trc is growing by ibwarn errors in virtual nodes in exadata

in Exadata General (MOSC) 7 commentsAnswered ✓

Hi all,

I have two exadatas with the same error in the virtual nodes with ibwarn in file gipcdOUT.trc.

ibwarn: [18685] sa_rpc_call: attr 0x11 mod 0x0 route Lid 1

ibwarn: [18685] mad_rpc_rmpp: rmpp (nil) data 0x7f87502ecd20

ibwarn: [18685] umad_set_addr: umad 0x7f87502ec330 dlid 1 dqp 1 sl 1, qkey 80010000

ibwarn: [18685] umad_send: fd 73 agentid 2 umad 0x7f87502ec330 timeout 100

ibwarn: [18685] umad_recv: fd 73 umad 0x7f87502ec730 timeout 100

ibwarn: [18685] umad_recv: mad received by agent 2 length 320

skgzib_check_guid_reachability: GUID 0xb8599f0300a3b471 is found online, return REACHABLE. query_time: 10


These errors are showing all time in the trace file /u01/app/grid/crsdata/hostname/output/gipcdOUT.trc in all virtual nodes and it is growing too much.

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