Thanks for the question, Joseph.
Asked: September 03, 2017 - 12:20 am UTC
Last updated: September 03, 2017 - 4:13 am UTC
Version: 12.1.0.2
Viewed 10K+ times! This question is
You Asked
Hi Tom,
We getting a weird error, while netbackup is trying to take backup using rman for an oracle instance PMTN5O1, below is the error:
dbgc_init_all failed with ORA-48141
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-12001: could not open channel default
RMAN-10008: could not create channel context
RMAN-10013: error initializing PL/SQL
Recovery Manager complete.
following Oracle Documentations: Doc ID 2202003.1, 2040126.1, issue not resolved.
cat /pmtn5o/oracle/product/12.1.0.2/install/orabasetab
#orabasetab file is used to track Oracke Home associated with Oracle Base
/pmtn5o/oracle/product/12.1.0.2:/pmtn5o/oracle:OraDb12102_pmtn5o:N:
echo $ORACLE_HOME
/pmtn5o/oracle/product/12.1.0.2
echo $ORACLE_BASE
/pmtn5o/oracle
echo $ORACLE_SID
PMTN5O1
I contacted oracle support, and engineer said issue is not related to rman. Because rman is able to connect to catalog.
Recovery Manager: Release 12.1.0.2.0 - Production on Sun Sep 3 02:18:11 2017
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
connected to target database: PMTN5O (DBID=**********)
connected to recovery catalog database
RMAN>
all seems correct not sure what am missing.
Please help.
Kind Regards,
Joseph
and Connor said...
"I contacted oracle support, and engineer said issue is not related to rman. Because rman is able to connect to catalog."
That *might* be true, but it might not be also.
As you've seen from the MOS notes, it is typically an OS permissions issue. So if netbackup is running as user "X", and your rman test is running as user "Y" (eg 'oracle') then its not really a valid test.
Whatever user netbackup is running as (and keep in mind, even if you launch it as user "A", it might simply be communicating to the background deamon runnings as user "B"), you need to see is *those* users can connect to rman successfully.
It might also be worthwhile doing some additional tracing, eg
rman debug trace my_trace.trc
Rating
(1 rating)
Is this answer out of date? If it is, please let us know via a Comment