My Oracle Support Banner

Getting RMAN Error "dbgc_init_all Failed With ORA-48141" While Connecting To Target (Doc ID 2589809.1)

Last updated on MAY 15, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Database Name: QA

Symptoms

RMAN connection to the target database failing with below error

rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Thu Sep 12 16:22:20 2019

Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.

dbgc_init_all failed with ORA-48141
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-12001: could not open channel default
RMAN-10008: could not create channel context
RMAN-10013: error initializing PL/SQL

During this time  following error in the alert log

Fri Sep 06 11:52:09 2019
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0xC531BC1, nstimexp()+113] [flags: 0x0, count: 1]
Errors in file /<path>/diag/rdbms/qa/QA/trace/QA_ora_5525.trc (incident=842865):
ORA-07445: exception encountered: core dump [nstimexp()+113] [SIGSEGV] [ADDR:0x9] [PC:0xC531BC1] [Address not mapped to object] []
Incident details in: /<path>/diag/rdbms/qa/QA/incident/incdir_842865/QA_ora_5525_i842865.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.


Changes

SQLNET tracing was enabled at the sqlnet.ora file

TRACE_LEVEL_SERVER = 16
TRACE_FILE_SERVER = sqlnet.trc
TRACE_DIRECTORY_SERVER =/<path>/network/trace
TRACE_TIMESTAMP_SERVER = ON
TRACE_FILELEN_SERVER=1000000
TRACE_FILENO_SERVER=1
DIAG_ADR_ENABLED= OFF

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


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