Repeated User <USER> not found in OCR Messages in ASM Trace Log
(Doc ID 2732600.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 20.3.0.0.0 Preview [Release 12.2 to 20.0]Information in this document applies to any platform.
Symptoms
Following error report in the ASM trace when execute dbms_diskgroup.open() in 18c from ASM instance by a user 'testasm' and the connection is not bequeath. This can report by any other manually created user having privilege to run for example: create user in ASM followed by asmcmd orapwusr --grant.
Impact is that ASM generate huge trace files with above messages and not able to execute dbms_diskgroup.open command by the user
Changes
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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |