Connecting to Catalog & Target Database

I am trying to register a target database with a recovery catalog. RMAN database and the catalog table space were created. When trying to connect to target with the SID set to the instance name and simply connecting as username/password, I am getting connected to the target. If I try to connect using the connect string, I get the following error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database: ORA-12154: TNS:could not resolve service name
But the TNS names have been properly configured and I am able to connect from sql*plus using the connect string.
Similarly I set the SID to RMAN database and try to connect catalog with username/password I am able to connect to Catalog and if I use connect string for the target, I am getting the same error as mentioned above.
I really do not know, How to resolve this and to connect to Target and RMAN databases simultaneously.

I suggest you do the following to see if the connect strings are really working, either:
1) Change ORACLE_SID to be of the catalog database, now do:
% sqlplus "<user>/<pwd>@<target string> as sysdba"
Does that work? If as I suspect it does not work or connects you to the catalog database (not the target), then it is a missconfiguration of the network files.
2) Do the same for connection to the catalog, set ORACLE_SID to be the one of the target database and do:
% sqlplus "<user>/<pwd>"
Does that connects you to the catalog?

Similar Messages

From RMAN - Not able to connect to the target database as sysdba

I wanted to configuring the backup server (rman catalog database server) to take RMAN
backups of the varius target databases. while connecting to the target database
from backup server, i am getting ORA-01031: insufficient privileges error.
I created password file and modified the init.ora file in the target server, but
still having connection issue.
I can over come this issue by keep trying many times while using sqlplus.
pbackup1$ sqlplus "sys/oracle @HCPRD as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Apr 25 17:02:56 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
pbackup1$ sqlplus "sys/oracle @HCPRD as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Apr 25 17:03:05 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
SQL>
-- finally, after few attempts, i can connect to the target database server as
sysdba ---
While connectiong thru RMAN, get the following error:
RMAN> connect target sys/oracle@HCPRD
RMAN-00571: ===========================================================
RMAN-00569: ========= ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
RMAN> connect target "sys/oracle @HCPRD as sysdba"
RMAN-00571: ===========================================================
RMAN-00569: ======== ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ===========================================================
ORA-12154: TNS:could not resolve the connect identifier specified
Text continued in next action...

Hey,
Please take a look at URL below to see it can help you -
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcnctg002.htm#i1008102
or
http://www.lc.leidenuniv.nl/awcourse/oracle/server.920/a96566/rcmcnctg.htm#443912
regards,
Marcello.

Recovery catalog, target database.

Hello all,
I have a question concerning recovery catalog.
Can i use the same database as recovery catalog and target database?
Let us say that i have a database orcl, can this database be the target and the recovery catalog at the same time ? is there any disadvantages?
Regards,

NB wrote:
Hello all,
I have a question concerning recovery catalog.
Can i use the same database as recovery catalog and target database?
Let us say that i have a database orcl, can this database be the target and the recovery catalog at the same time ? is there any disadvantages?Yes you can use the same database as the recovery catalog but that's going to be a wrong decision. Think about this, you have lost your target database and since you had your recovery catalog also stored in it, now that's also gone! So a good thing or bad thing it would be ?
Edit:
Please read the same from the docs,
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcatdb.htm#CHDECBEH
Do not use the target database to be backed up as the database for the recovery catalog. The recovery catalog must be protected in the event of the loss of the target database.Aman....
Edited by: Aman.... on Aug 7, 2011 4:26 PM

Views to check the catalog database name from target database.

Hi,
Please help me to find view to check the catalog database name which is connected to my target database because I am new to the current environment where I am working now and the previous DBA have done the set up having 2 catalog database. I want view to check from target database, which can show the catalog database name to which it is connected to.
We can check the catalog database name from the following ways but I want views to check it from target database.
1.TNSnames.ora
2.Any backup script connecting to catalog database.
3.From catalog database we can use rc_database view to check the databases registered with the catalog database.

Please help me to find view to check the catalog database name which is connected to my target databaseYou can check for any RMAN backup jobs that been scheduled on the server.
In the scheduled script check rman command.
You can then identify the database alias (of the catalog db) that is used in the rman backup script.
Once you have found the database alias, check for the database alias entry in tnsnames.ora file present in your target database server.
Once the entry is found, you can find the IP address and catalog db name from the tns entry.
Edited by: st. osh on Nov 22, 2012 11:38 PM

Trying to connect to target database...ORA-01994: GRANT failed: password

I am trying to connect to a target database which on linux from a catalog database which is on Windows. I was initially having problems with our DEV database but eventually got it working. Now I have to register the QA database and I'm running into the same problems. Below is a list og things that I have tried:
C:\>rman
Recovery Manager: Release 10.2.0.3.0 - Production on Thu May 10 17:01:51 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target sys/password@fprcqa
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
2. So I went to the target database (FPRCQA) and I checked the following:
SYS@FPRCQA> select * from v$pwfile_users;
no rows selected
SYS@FPRCQA> grant sysdba to sys;
grant sysdba to sys
ERROR at line 1:
ORA-01994: GRANT failed: password file missing or disabled
3. Then I checked the passwordfile
SYS@FPRCQA> show parameter pass
NAME TYPE VALUE
remote_login_passwordfile string[b] EXCLUSIVE
4. Then I created a passwordfile in $ORACLE_HOME/dbs because it did not exist.
[oracle@rh-staging dbs]$ orapwd file=orapwdFPRCQA password=password entries=300
-rw-r----- 1 oracle oinstall 8385 Sep 11 1998 init.ora
-rw-r--r-- 1 oracle oinstall 12920 May 3 2001 initdw.ora
-rw-rw---- 1 oracle oinstall 1552 May 8 14:09 hc_FPRCQA.dat
-rw-rw---- 1 oracle oinstall 24 May 8 14:09 lkFPRCQA
drwxr-xr-x 63 oracle dba 4096 May 8 15:12 ..
drwxr-x--- 2 oracle oinstall 4096 May 10 16:10 .
-rw-r----- 1 oracle oinstall 5632 May 10 16:10 spfileFPRCQA.ora
-rwSr----- 1 oracle oinstall 39424 May 10 16:14 orapwdFPRCQA
5. Then I tried again to grant sysdba to sys and it gave me the same error as before.
ALSO, I cannot connect to the the target database from the catalog database through sqlplus...as I get the same error of insufficient privs:
C:\>set ORACLE_SID=fprcqa
C:\>sqlplus /nolog
SQL*Plus: Release 10.1.0.3.0 - Production on Thu May 10 17:11:41 2007
Copyright (c) 1982, 2004, Oracle. All rights reserved.
SQL> connect sys/password@fprcqa as sysdba
ERROR:
ORA-01031: insufficient privileges
Can anyone help please?

Hello all;
I created the files with following command in $ORACLE_HOME/dbs/
orapwd file=orapwRCVDB password=sys entries=20
remote_login_passwordfile=EXCLUSIVE
$ ls -ltr orapw*
-rwxrwxrwx 1 oracle dba 3584 Dec 22 15:29 orapwRCVDB
but still I am facing similar error ..
SQL> grant sysdba to system;
ORA-01994: GRANT failed: password file missing or disabled
so i checked ...
SQL> select * from v$pwfile_users;no rows selected
can anyone tell me where I am doing mistakes ? It's urgent !!
atul.

Duplicate target database for standby failed

Hi,
Im trying to uplicate target database for standby and get error message bellow :
RMAN> DUPLICATE TARGET DATABASE
2>   FOR STANDBY
3>   FROM ACTIVE DATABASE
4>   DORECOVER
5>   SPFILE
6>     SET db_unique_name='dgtst' COMMENT 'Is standby'
7>     SET LOG_ARCHIVE_DEST_2='SERVICE=dgtst ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dgtst'
8>     SET FAL_SERVER='dgtst' COMMENT 'Is primary'
9>   NOFILENAMECHECK;
Starting Duplicate Db at 24-FEB-12
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/24/2012 22:51:21
RMAN-05501: aborting duplication of target database
RMAN-03009: failure of allocate command on ORA_AUX_SBT_TAPE_1 channel at 02/24/2012 22:51:21
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2Please advice
Thanks

Hello mseberg,
Actually you find the problem .....
Adding the following softlink helped :
ln -s /opt/omni/lib/libob2oracle8_64bit.so /u01/app/oracle/product/11.2.0/DG11gR2TST/lib/libobk.so
I run the duplicate command and its look much better:
$ rman TARGET sys/mysyspass@dgtst AUXILIARY sys/mysyspass@drtst
Recovery Manager: Release 11.2.0.2.0 - Production on Sat Feb 25 07:43:15 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DGTST (DBID=244743902)    <<<=== connected
connected to auxiliary database: DGTST (not mounted)    <<<=== connected
RMAN> DUPLICATE TARGET DATABASE
2> FOR STANDBY
3> FROM ACTIVE DATABASE
4> DORECOVER
5> SPFILE
6> SET db_unique_name='dgtst' COMMENT 'Is standby'
SET LOG_ARCHIVE_DEST_2='SERVICE=dgtst ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=dgtst'
7> 8> SET FAL_SERVER='dgtst' COMMENT 'Is primary'
9> NOFILENAMECHECK;
Starting Duplicate Db at 25-FEB-12
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_SBT_TAPE_1
channel ORA_AUX_SBT_TAPE_1: SID=156 device type=SBT_TAPE
channel ORA_AUX_SBT_TAPE_1: Data Protector A.06.11/PHSS_40470/PHSS_40471/DPSOL_00391/DPLNX_
allocated channel: ORA_AUX_SBT_TAPE_2
channel ORA_AUX_SBT_TAPE_2: SID=189 device type=SBT_TAPE
channel ORA_AUX_SBT_TAPE_2: Data Protector A.06.11/PHSS_40470/PHSS_40471/DPSOL_00391/DPLNX_
allocated channel: ORA_AUX_SBT_TAPE_16
channel ORA_AUX_SBT_TAPE_16: SID=129 device type=SBT_TAPE
channel ORA_AUX_SBT_TAPE_16: Data Protector A.06.11/PHSS_40470/PHSS_40471/DPSOL_00391/DPLNX_
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=160 device type=DISK
contents of Memory Script:
   backup as copy reuse
   targetfile '/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/orapwdgtst' auxiliary format
'/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/orapwdgtst'   targetfile
'/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/spfiledgtst.ora' auxiliary format
'/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/spfiledgtst.ora'   ;
   sql clone "alter system set spfile= ''/u01/app/oracle/product/11.2.0/DG11gR2TST/dbs/spfiledgtst.ora''";
executing Memory Script
Starting backup at 25-FEB-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/25/2012 07:44:02
ORA-17629: Cannot connect to the remote database server <<<<<<====
ORA-17627: ORA-12541: TNS:no listener                    <<<<<<====
ORA-17629: Cannot connect to the remote database server
continuing other job steps, job failed will not be re-run
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/25/2012 07:44:03
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/25/2012 07:44:03
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12541: TNS:no listener
ORA-17629: Cannot connect to the remote database serverAs you can see above rman successfully connected to the local and remote database.
It also successfully allocated the DISK channel , but than it failed on :
ORA-17627: ORA-12541: TNS:no listenerI cant understand why it happen:
$ tnsping dgtst
TNS Ping Utility for HPUX: Version 11.2.0.2.0 - Production on 25-FEB-2012 08:54:48
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = hercules)(PORT = 1528))) (CONNECT_DATA = (SERVICE_NAME = dgtst)))
OK (0 msec)
$ tnsping drtst
TNS Ping Utility for HPUX: Version 11.2.0.2.0 - Production on 25-FEB-2012 08:54:54
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = pulse)(PORT = 1528))) (CONNECT_DATA = (SERVICE_NAME = dgtst)))
OK (10 msec)And as you i show the rman successfully connect to both rempte and local as SYS user.

RMAN incompatible with TARGET database

I have two databases:
The database with the catalog, version 8.1.7.
The database to be backed up (target), version 8.0.6.
When I try to connect to the target, I get an error stating: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
I've tried changing the "compatible" parameter to 8.0.4, but then I get an error when I restart the database (regarding locally managed tablespaces, which I am not using).
Any idea what I need to do to connect to the target database?
thanks....

Hi !
I guess you have confused the compatible init.ora parameter with RMAN compatible parameter ,
They are entirely different. The excerpts here, which i have taken from the Oracle online docs should
clear your problem.
The compatible parameter specifies the minimum acceptable release of the RMAN executable that can function with the catalog. For example, if the recovery catalog compatibility is set to 8.1.4, then only an RMAN executable of release 8.1.4 or later can connect to the catalog.
You cannot set the compatible parameter to a version that is not supported by the currently-installed DBMS_RCVMAN or DBMS_RCVCAT packages. If you try to set compatibility to a version that is not supported by one of the packages, then you receive an error message that indicates the lowest and highest value you can set, as in the following example:
RMAN> configure compatible = 8.0.1;
RMAN-03022: compiling command: configure
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06455: illegal compatible value 8.0.1: must be between 08.00.04 and 08.01.06
To view the compatibility level of the recovery catalog:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Start a SQL*Plus session and connect to the recovery catalog database as the recovery catalog owner. For example, enter:
SQL> connect rman/rman@rcat
Issue the following query:
SQL> SELECT value FROM config WHERE name='compatible';
VALUE
080106
To create an 8.1.6 recovery catalog that is usable with a pre-8.1.6 RMAN executable:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This procedure assumes that you have the use of both an 8.1.6 and pre-8.1.6 RMAN executable. The method employed it to use a pre-8.1.6 RMAN executable to create the recovery catalog, and a release 8.1.6 RMAN executable to upgrade it. The compatibility level is automatically set to 8.0.4, which has the implications described in Table 3-1.
Use a pre-8.1.6 RMAN executable to connect to the catalog database. For example, enter:
% rman catalog rman/rman@rcat
Recovery Manager: Release 8.1.5.0.0
RMAN-06008: connected to recovery catalog database
Create the recovery catalog and then exit. For example, enter:
RMAN> create catalog;
RMAN> exit
Note:
If you use a release 8.0 RMAN executable to create the catalog, you must use the catrman.sql script to create the recovery catalog.
Use the 8.1.6 RMAN executable to connect to the newly created recovery catalog:
% rman catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0
RMAN-06008: connected to recovery catalog database
Upgrade the recovery catalog to release 8.1.6:
RMAN> upgrade catalog;
RMAN> exit
The compatibility level of the recovery catalog is now automatically set to 8.0.4.
Regards,
Mohamed Iqbal.
[email protected]

How to get RMAN catalog information from Target database?

Hi,
How to get RMAN catalog information from Target database because i don't know about catalog database? is it possible?
Thanks

If you run RMAN backups of a target database using a Catalog schema in another database, the target is not aware of the catalog.
The RMAN backup script would have the connection identifier for the Catalog.
Hemant K Chitale

RMAN catalog fails to show target database information when in nomount mode

Hello everyone, I am trying to restore a dev. database from its own backup taken a week back. The DB is in noarchivelog mode and recently 2 of the datafiles were removed from the files system and thus the need to restore the DB from its backup. However rest of the files and control files are intact.
Now, when I put the database in mount mode and connect to the catalog then I can see the DB's incarnation;
:->rman catalog cde01_rman4/xxxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:54:40 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: EGVBFI2 (DBID=4238332493, not open)
connected to recovery catalog database
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
84789 84883 EGVBFI2 4238332493 PARENT 2478183021921 17-JAN-04
84789 84790 EGVBFI2 4238332493 CURRENT 2498633332010 10-OCT-07
RMAN>
However I am not able to see DB incarnation in the RMAN catalog if I put the DB in nomount mode (which is required to recover DB);
:->rman catalog cde01_rman4/xxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:58:29 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: egvbfi2 (not mounted)
connected to recovery catalog database
RMAN> list incarnation;
RMAN>
Please advice?
Thanks,
Jairaj

Hi,
You won't be able to see incarnation information when the DB is in "nomount" since the incarnation is written in the control file. I don't think the catalog has this information.
Anyway, in order to restore datafiles, the instance must be mounted, so you should be OK.
Mount the instance and just restore the datafiles.
Liron Amitzi
Senior DBA consultant
link: [www.dbsnaps.com]
link: [www.obriumsoftware.com]

Getting ORA-01031 while connecting to target database

I have created RMAN catalog. While connecting to target database i am getting ORA-01031: insufficient privileges. What could be the reason. I have added entry of both the databases in listner.ora as well as tnsnames.ora, but still facing the same problem. Please help
[oracle@dbapool ~]$ rman catalog=rman/pass@sdn target=sys/pass@sdn1
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Apr 30 23:49:46 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges

Issue got resolved. The problem was with password file.

10204 catalog database 112 target database and OEM

catalog database is 10.2.0.4 on server CSERV
OEM server is 10.2.0.4 OSERV
target database is 11.2 on server TSERV
I ran the RMAN command from RSERV (v10204) and registered target database (v112) without error
I went into OEM->TARGET page ->Maintenance->Recovery Catalog Settings->
     selected Use recovery catalog
     (the correct catalog was listed in the drop down (CSERV:1521:RMANUSER-rman_schema1
     added the OS username/password for TSERV
     pressed 'OK'
The error that was returned was:
"Recovery catalog scheme version 10.02 is not compatible with this version of RMAN."
I'm sure i'm doing something stupid, but would really appreciate any help.....
Regards,
Susan

Hi Susan,
Probably you used a 10g rman client on the command line to connect to both the target (11.2) and the catalog (10.2.0.4) during registration.
(according to the compatibilty matrix this works).
Be aware:
When using an older version of the RMAN client with a newer version of the database, you do not get the features of the newer version.According to your own information Grid uses the 11gr2 software.
added the OS username/password for TSERVWhich is incompatible with the 10.2 catalog.
Unfortunately, we can't upgrade the catalog at this time.You can upgrade the catalog schema without upgrading the catalog rdbms (but probably you do not want to execute any change during xmas and new year).
Please check:
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsynta052.htm
Regards,
Tycho

Query to identify the recovery catalog database name from target database

Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi P

You can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM

Unable to connect to catalog database

Dear All,
I tried to take offline DB backup using recovery catalog.But it is failing with below error.
RMAN> backup database;
Starting backup at 28-FEB-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 02/28/2012 14:40:20
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE
I'm running RMAN on target db host.
This is the cmd I used to connect to RMAN. env.
rman target / catalog=username/password .
Kindly help me.
Best Regards,
Gopal.

Hello mseberg
Thanks for your suggestion.I removed the entry in tnsnames.ora file ans restarted the listener.
This how exactly I'm wroking with RMAN now.
C:\Documents and Settings\TEST>rman target / catalog=xxxxl/xxxxxxx
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 28 15:50:43 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: GOP (DBID=11843514)
connected to recovery catalog database
RMAN> shutdown immediate;
database closed
database dismounted
Oracle instance shut down
RMAN> startup mount;
connected to target database (not started)
Oracle instance started
database mounted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 02/28/2012 15:52:03
RMAN-06004: ORACLE error from recovery catalog database: ORA-03113: end-of-file
on communication channel
Thanks for your help.
With Regards,
Gopal.
Edited by: user8829891 on Feb 28, 2012 6:54 AM

Rman backup to be stored on other machine than catalog and Target database

I have target database on machine A, catalog on machine B. I am executing RMAN from machine B but want to store RMAN backup on machine C. is it possible.

Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: NEFT (DBID=3608824086)
connected to recovery catalog database
RMAN> run{
2> allocate channel c1 device type disk format '\\bobfs\f\RMAN\data\neft\Rman_NEFT_%U';
3> backup full database;
4> backup current controlfile;
5> }
6>
allocated channel: c1
channel c1: sid=16 devtype=DISK
Starting backup at 15-OCT-08
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00011 name=F:\DATABASE\NEFT\DATABASENEFT_DATA1.DBF
input datafile fno=00015 name=F:\DATABASE\NEFT\UNDOTBS.DBF
input datafile fno=00013 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_DATA1.DBF
input datafile fno=00002 name=F:\DATABASE\NEFT\UNDOTBS01.DBF
input datafile fno=00001 name=F:\DATABASE\NEFT\SYSTEM01.DBF
input datafile fno=00014 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_NDX1.DBF
input datafile fno=00005 name=F:\DATABASE\NEFT\EXAMPLE01.DBF
input datafile fno=00012 name=F:\DATABASE\NEFT\DATABASENEFT_NDX1.DBF
input datafile fno=00010 name=F:\DATABASE\NEFT\XDB01.DBF
input datafile fno=00006 name=F:\DATABASE\NEFT\INDX01.DBF
input datafile fno=00009 name=F:\DATABASE\NEFT\USERS01.DBF
input datafile fno=00003 name=F:\DATABASE\NEFT\CWMLITE01.DBF
input datafile fno=00004 name=F:\DATABASE\NEFT\DRSYS01.DBF
input datafile fno=00007 name=F:\DATABASE\NEFT\ODM01.DBF
input datafile fno=00008 name=F:\DATABASE\NEFT\TOOLS01.DBF
channel c1: starting piece 1 at 15-OCT-08
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 10/15/2008 10:45:38
ORA-19504: failed to create file "\\bobfs\f\RMAN\data\neft\Rman_NEFT_7qjt6tat_1_1"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
Recovery Manager complete.
I am executing rman from catalog machine,
WHen i give path \\bobfs\f\RMAN\data\neft\ in start-> run it is accessible from there.
I cant understand why rman is not abl to create file there.
full rights are given to user. and user on rman catalog and network machine is same having same password

How to un-register target database in Catalog DB?

I am using 8.0.5. I create a Catalog database and register a target database with it for online backup. How do I un-register a target database from the Catalog DB if I do not want to continue taking backup? Is there any 'unregister' command?
Thanks in advance
- Sanchayan RoyChoudhury
Bangalore, India
null

Let me try...
If u know your dbid (which can be found out by just logging into rman with the target databasse)
login ot the catalog database throught sqlpplus as the catalog schema owner...
run the following query..
SELECT db_key, db_id FROM db WHERE db_id ="dbid just found";
then run
execute dbms_rcvcat.unregisterdatabase(db_key, db_id);
This will unregister your database from the catalog. however keep in mind that you will lose all records of your old backups..
HTH
null

Connecting to Catalog & Target Database

Similar Messages

Maybe you are looking for