Database - RAC/Scalability (MOSC)

MOSC Banner

Unable to track source of 'WARNING: ASM communication error: op 0 state 0x0 (15055)'

edited Jun 14, 2016 5:09AM in Database - RAC/Scalability (MOSC) 2 commentsAnswered

Hello,

The statements 'WARNING: ASM communication error: op 0 state 0x0 (15055)' followed by 'ERROR: direct connection failure with ASM' has recently started appearing in a production database alert log.  DB version is 11.2.0.4 running on Oracle Linux.  The database is a single instance running under CRS and supports a Peoplesoft installation.

There are no trace files, no additional errors, no user complaints.  Nor is there anything reported in the ASM alert log, /var/log/oracleasm, etc. I've checked local listener in both the DB and ASM instance and they're correct.  I've attempted to correlate this with an event from the listener, such as an auto-registration and cannot find anything.  I've looked for file permission issues and other problems as suggested by various Google searches.  I've not found anything that seems to apply.

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