My Oracle Support Banner

Database Fails to Start with Error ORA-56867 After Applying a BDS 3.1 or 3.2 Database Side Patch (Doc ID 2379002.1)

Last updated on JULY 25, 2021

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

 After applying a database side patch on top of Oracle Big Data SQL(BDS) 3.1/3.2 the database fails to start with an error like below in the alert.log:

ORA-56867: Cannot connect to Master Diskmon on pipe "/oracle/app/oracle/product/12.1.0/dbhome/<DIR>/.dskm_pipe"
ORA-27300: OS system dependent operation:connect failed with status: 111
ORA-27301: OS failure message: Connection refused
ORA-27302: failure occurred at: skgznpcon6

An example is applying patch 26170659: Patch 26170659: TRACKING BUG FOR BDSQL 3.2 RELEASE, on top of BDS 3.2.

Changes

Apply a database side patch on top of BDS 3.1/3.2.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.