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]

Similar Messages

Why doesn't a song I uploaded to the iTunes store show the Composer information when purchased?! Why is Apple deleting crucial info!?!

Why doesn't a song I uploaded to the iTunes store show the Composer information when purchased?! Why is Apple deleting crucial info!?! The information was embedded using iTunes and uploaded through TuneCore. But when the song is purchased and downloaded the Composer info has been deleted (and so has the copyright protection info that was in the comments window of the mp3's info in iTunes)???

Foundsound,
Since your direct commercial relationship is with TuneCore, not with Apple, you need to address your question to TuneCore.
Tune Core often places the song at multiple music retailers (iTunes, Amazon, etc.) so you should check if the same thing happened at the others.
The fact that the Comments field was blanked out doesn't surprise me, but deleting the composer does.
Pls let us know what you find out.

PSU level of RMAN Catalog DB version and Target DBs

Catalog DB Version: 11.2.0.2.3
Target DBs : 11.2.0.2.3
Currently our Catalog DB and Target DBs ( 15 of them) are of the same PSU level.
We are going to apply PSU 5 (11.2.0.2.3) on some of the target DBs . Should we apply PSU 5 (11.2.0.2.3) on the Catalog DB first before we apply this PSU on the target DBs?

Hi TeslaMan,
Probably you mean the rdbms version of the catalog is version 11.2.0.2.3.
If you upgrade target databases with a cpu you might need to upgrade the catalog schema to an equal or higher level.
Please check the current catalog schema version with the following sql.
select * from RCVER;Maybe you can create a dummy catalog schema with the patched up rdbms rman cli (maybe you tested the cpu already?) and check the new version with the same sql.
Regards,
Tycho

Set RMAN catalog default setting for all databases

Hi,
I am running a 11gR1 RMAN catalog.
I am wondering if is it possible to change a default configuration setting in the RMAN catalog so that all the new databases will inherit it.
For example, I would like all the new databases registered to the catalog to have:
BACKUP OPTIMIZATION ON
RETENTION POLICY TO REDUNDANCY 7
Thanks,
massi

No, the catalog cannot "dictate" configurations for databases. Each database retains configuration in the controlfile and this can be updated only by an rman connection (i.e. rman connecting to the database as a target). The CONFIGURE command in rman is used to set a "permanent" configuration parameter for a database but must be issued for each database individually.
Hemant K Chitale

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.

Unregistering of a database from RMAN Catalog

Hello,
We had set up RMAN backup though RMAN Catalog for one of our database.
We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
We know that the tapes don't have the backup of this database.
Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
Thanks!

Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
I have another question though -
We have compressed backup for one of the database/
If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
Question - How to check the compressed size of the backupset from the Catalog tables/views?
Thanks for your help on this!
Thanks!
,

Centralized RMAN Catalog Database

Hello,
I have two 10g R2 databases on two separate servers.
I am trying to centralize my RMAN backup by creating a RMAN_DATABASE in 11G.
- I create RMAN_DATABASE
- I created RMAN user and tablespaces
- I edited my TNSNAMES.ORA so that I could connect to my two 10G R2 databases
When I run the command:
rman catalog=rman/password@rman_database target=sys/password@10g_db1I get the following error:
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 req
uired
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
When I google the error it indicates to change the binary files, but that doesn't work either, unless I don't understand what that entails.
Any suggestions?

By saying that you have amended your tnsnames.ora to connect to the 10gR2 databases, I assume you are running the rman command on your 11gR1 server. This means that your RMAN client version is 11gR1, and your target database is 10gR2. This is not permitted, see the [compatibility matrix|http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/compat003.htm#i634479].
I suggest you try this on each of your 10gR2 servers:
1. Amend tnsnames.ora to include an entry for the 11gR1 rman_database
2. Ensure your oracle environment variables are set correctly, especially ORACLE_HOME and ORACLE_SID
3. rman target=sys/password catalog=rman/password@rman_database
This means you will be using the 10gR2 RMAN client on the 10gR2 target database which ensures no incompatibility problems. There is no issue with the fact your recovery catalog schema is at 11gR1, this is permitted to be greater than the RMAN client being used.

Duplicate target database for standby failing with below error

Hello All, Need your assistance
We are creating a physical standby database (standalone) from 2 node RAC database, OS =RHEL5 and DB =11gR2
What we did: We took RMAN backup of primary DB along with archives and copied to standby server in same location. We have modified necessory prameters on primary as well as standby too.
The command we used :
RMAN>connect target sys/pwd@primary auxiliary sys/pwd@stdby
RMAN> run {
allocate auxiliary channel ch1 type disk;
duplicate target database for standby dorecover nofilenamecheck;
release channel ch1;
Note we tried : duplicate target database for standby as well as duplicate target database for standby nofilenamecheck methods too....But no luck..we are getting following error.
channel ch1: reading from backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
channel ch1: ORA-19870: error while restoring backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
ORA-19501: read error on file "/u01/BDB/BWFCCPRD_5fmpdvce_1_1", block number 121856 (block size=8192)
ORA-27072: File I/O error
Additional information: 4
Additional information: 121856
Additional information: 1036288
failover to previous backup
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/20/2011 09:16:11
RMAN-05501: aborting duplication of target database
RMAN-05556: not all datafiles have backups that can be recovered to SCN 41855007833
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
could you pease help to resolve this ....?
Note : Creating standby using RMAN 11g new feature : duplicate target database for standby from active database is not possible in our environment since the network bandwith is tooooo low, We have tried and not able to succeed because of n/w issue, So we are doing this alternate method...!!!
Looking for your valuable advises...
Thanks in Advance....

Take the fresh backup and also check the space crunch. The below clink may help you
ORA-27072: File I/O error Additional information: 2
--neeraj
Edited by: Vishen on Oct 20, 2011 2:14 PM

RMAN DUPLICATE FOR STANDBY FROM ACTIVE DATABASE fails

Hello
I'm trying to use RMAN DUPLICATE to create a standby database using Oracle 11.2.0.3 with PSU 6 on HP-UX.
Primary is 2 node RAC. Standby is also 2 node RAC.
Standby database instance is started in nomount mode.
I use:
duplicate target database for standby from active database
spfile
<some spfile parameters>
with PFILE I get:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 12:41:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/01/2013 12:41:13
RMAN-11003: failure during parse/execution of SQL statement: alter system set spfile= '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-01565: error in identifying file '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
With SPFILE I get;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 13:06:34
RMAN-05501: aborting duplication of target database
RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause
But I do have RMAN connexion to target database.
Thanks for your help.

Here is the output beginning of the script which clearly shows that I'm always connected to target database:
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 1 13:05:47 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: CU (DBID=1143962925)
connected to auxiliary database: CU (not mounted)
RMAN> set echo on
2> run
3> {
4> configure device type disk parallelism 10;
5>   allocate channel pr1 type disk;
6>   allocate channel pr2 type disk;
7>   allocate channel pr3 type disk;
8>   allocate channel pr4 type disk;
9>   allocate channel pr5 type disk;
10>   allocate channel pr6 type disk;
11>   allocate channel pr7 type disk;
12>   allocate channel pr8 type disk;
13>   allocate channel pr9 type disk;
14>   allocate channel pr10 type disk;
15>   allocate auxiliary channel st1 type disk;
16>   allocate auxiliary channel st2 type disk;
17>   allocate auxiliary channel st3 type disk;
18>   allocate auxiliary channel st4 type disk;
19>   allocate auxiliary channel st5 type disk;
20>   allocate auxiliary channel st6 type disk;
21>   allocate auxiliary channel st7 type disk;
22>   allocate auxiliary channel st8 type disk;
23>   allocate auxiliary channel st9 type disk;
24>   allocate auxiliary channel st10 type disk;
25>   duplicate target database for standby from active database
26>   spfile

RMAN-05001 auxiliary .... conflicts with a file used by the target database

I can´t recreate my physical standby.
It worked in the past.
Now I reinstalled the 3 standbyclients.
Copied the spfile from the primary - modified the entries and did a rman backup.
But when issuing the duplicate database command - it comes up with the error above
SPFILE standyby db:
*.db_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
*.log_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
Starting restore at 15-APR-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/stage/33lb65n2_1_1
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/oracle/stage/33lb65n2_1_1 tag=TAG20100415T102434
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:11
output filename=+REDO1/stdy/controlfile/current.262.716293055
output filename=+REDO2/stdy/controlfile/backup.262.716293055
Finished restore at 15-APR-10
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2010 10:31:46
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename DATA/prim/datafile/system.262.715097535 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.263.715097499 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs3.269.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs2.270.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/example.272.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/users.268.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.273.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs1.271.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/system.264.710521021 conflicts with a file used by the target database+

Hi ,
I feel you are using ASM but still check the below details:
Cause
Production and Auxiliary have same directory structure and are running on two different machines. RMAN must be told not check that the target datafiles are sharing the same names as the duplicated files being created. Otherwise, the following errors will be returned:
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_03.dbf
conflicts with a file used by the target database
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_02.dbf
Solution
To implement the solution, please use nofilenamecheck in syntax as follows:
1. Connect to Target, auxiliary, and rman catalog and
2. use script as
run{
set until time "to_date('2005/09/17 14:00:00','yyyy/mm/dd HH24:MI:SS')";
allocate auxiliary channel aux1 type 'sbt_tape';
allocate auxiliary channel aux2 type 'sbt_tape';
duplicate target database for standby dorecover nofilenamecheck;
Make sure to use auxiliary type of channel so RMAN restore take place at auxiliary database.
Thanks,
Rafi.
http://rafioracledba.blogspot.com/

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.

RMAN-04005: error from target database:

Hi,
when I want register my target by
]$ rman catalog prdrman/prdrman@PRD target sys/manager@DEV
I receive this :
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
Do you have any idea ?
Many thanks before.

Here are some further hints from documentation:
ORA-01031: insufficient privileges
When : SQL> connect sym/sym as SYSDBA
Additional : init.ora remote_login_passwordfile=EXCLUSIVE or SHARED
Cause : Username/password is not correct (if the user is added by granting
SYSDBA to the user, this user is added to the passwordfile with the
password from the data dictionary)
or:
Password file has
-> incorrect name orapw<name_of_database>
-> is not in $ORACLE_HOME/dbs
-> has wrong privileges
They should be -rwSr-----
For example:
-rwSr----- 1 server sdb 1536 Mar 25 08:12 orapwv901
Solve : You can set the correct privileges (Unix) by issueing
$ chmod 4640 passwordfile
As a last resort, recreate the password file and remind to add
additional privileged (sysdba or sysoper) users

Failed to load database information

Post Author: ramya
CA Forum: General
Hi,
We were using the crsyatl reports 9 for a desktop application that connects to a webservice.We had an issue with memory leak in crystal reports and hence we installed crystal reports 7 and upgraded that to crysta reports 9.We later installed the service pack 7 for the crystal reports 9 which has the fix for this memory leak .We are using the dlls Version=9.2.3300.0.But after upgrading and applying the service pack we couldnot even view the report in the report windows forms viewer.A error was displayed as C:\Inetpub\wwwroot\Application\Reports\CapitalReports\Building Reports\Comprehensive Reports\exreport.rpt ,Failed to load the database information .This was working fine before upgrading.We cannot find the solution.
Any help will be kindly appreciated. ThankRamya

Post Author: Mark Lemoine
CA Forum: General
In trying to diagnose this problem, we have obtained our own 64bit h/w, installed the same Windows OS, and installed the same components in the same order (to the best of our ability) as on the customer machine (Framework 2, IIS, SQL 2005, Framework 1.1, etc.).
On our server, the reports work fine! No exception "Failed to load database information" generated.
We've also updated the customer's machine with the latest updates from MS (Framework 2 sp1, Framework 1.1 sp1, OS updates, security updates, etc.), but no joy . The reports still fail with the described exception.
What can we do to diagnose this? Are there any trace or logging options in Crystal that can be turned on? Why weren't we able to replicate the problem?
Thanks
Mark

Cannot enable broker configuration or showing database information

- I add the primary database and standby database into broker configuration :
DGMGRL> show configuration
Configuration - DGConfig1
Protection Mode: MaxPerformance
Databases:
TEST_PRI - Primary database
TEST_STD - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
- And enable configuration
DGMGRL> enable configuration;
Enabled.
- And show configuration again
DGMGRL> show configuration;
Configuration - DGConfig1
Protection Mode: MaxPerformance
Databases:
TEST_PRI - Primary database
TEST_STD - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
- But, when i show the database information
DGMGRL> show database TEST_PRI
Object "test_pri" was not found
- I notice that the "ENABLE" notation is not show up in the broker configuration, like this
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES <<<--------------------
Protection Mode: MaxPerformance
Databases:
pc00prmy - Primary database
pc00sby1 - Physical standby database
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
SUCCESS
---- Why my configuration does note have the notation : "Enabled : YES/NO" ???
---- And in the configuration, it list databases (pri and stdby), but why i can not use "show database TEST_PRI/TEST_STD"
Please help
So thanks
Ch

Hello;
You show :
show database TEST_PRI
I think it need to be :
show database 'TEST_PRI'
Additional examples :
DGMGRL> SHOW DATABASE 'TEST_PRI' 'StatusReport';
DGMGRL> SHOW DATABASE 'TEST_PRI' 'LogXptStatus';
DGMGRL> SHOW DATABASE 'TEST_PRI' 'InconsistentProperties';
DGMGRL> SHOW DATABASE 'TEST_PRI' 'InconsistentLogXptProps';
Best Regards
mseberg

How to upgrade RMAN catalog from 10.2.0.4 to 11?

Hi, we are on Oracle 10.2.0.4, Solaris 5.10. Our RMAN catalog is 10.2.0.4 version and we have several 11g databases that need to connect to the catalog and obviously cannot. So we need to upgrade the catalog to 11. Does anyone have any docs on how to do it. Do I need to upgrade RMAN database to 11 via conventional upgrade and then do UPGRADE CATALOG? Really confusing, any help would be very appreciated.
Thank you!

You need to:
1 - upgrade the recovery catalog database
2 - upgrade the recovery catalog Schema
Please check the details on note *452529.1 Recovery catalog for RMAN backup*.
Normally newer databases (target) can be cataloged on previous version catalog database, but with 11g there is the bug 6756872 (RMAN REGISTER OF 11G TARGET INTO 10G CATALOG FAILS WITH ORA-04028) which force you to upgrade the catalog.
You can also review RMAN Compatibility Matrix (Note 73431.1) which has all valid version combinations.
If your scenario is simple enough, another option could be create a new 11g RMAN catalog and register there your databases, without importing data from the 10.2 catalog.
Regards.

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

Similar Messages

Maybe you are looking for