Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Oracle Database Appliance (ODA) (MOSC)

Loopback MTU Size and ORA 603 From +ASM1_xxx

Nov 15, 2019 6:18AM edited Nov 15, 2019 6:20AM in Oracle Database Appliance (ODA) (MOSC)

We had some OEM alerts regarding the following issue on one of our ODA X6-2L's.

A session termination detected in /u01/app/grid/diag/asm/+asm/+ASM1/alert/log.xml at time/line number: Fri Oct 25 09:33:06 2019/139

Looking at the alert log showed the following :

2019-10-25T09:33:06.369125+01:00

skgxpvfynet: mtype: 61 process 86278 failed because of a resource problem in the OS. The OS has most likely run out of buffers (rval: 4)

Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_m000_86278.trc (incident=144965):

ORA-00603: ORACLE server session terminated by fatal error

ORA-27504: IPC error creating OSD context

Tagged:

legacy_documents

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month