Problem registering database in RMAN on a different node

Here is the deal ..
setup a backup catalog instance name rcatdev1 .. with 9.2.0.5 code, registered a 9.2 database (dbname=TEST from same node) no problem installed 10gr2 upgraded catalog .. no problem .. upgraded TEST no problem, Registered (DBNAME=BUILD 9.2 code level same node) no problem .. now on a second node trying to connect and register this database (CERT) and am having issues
when I connect to the target I am getting
connected to target database: DUMMY (not mounted) or
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
now .. I can sqlplus over to that database no problem .. only when I try rman am I having issues ..
I am on AIX 5
Any Ideas?

Hi Hameed;
Its better to move your issue to Forum Home » Database » Database - General forum part
Regard
Helios

Similar Messages

Unable to register database in RMAN - RedHat 6.2 + Oracle 8.1.6

Is this a bug?? pls suggest the way out...
-Balaji
([email protected])
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------

Is this a bug?? pls suggest the way out...
-Balaji
([email protected])
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------

How do I move databases using RMAN with minimal downtime ?

How can I do the following using RMAN ?
DB version 10.2.0.4
Redhat 5.2
I am not using an rman catalogIn the past I have moved large databases from 1 server to another with 5 minutes downtime using backups done the old way by putting tablespaces in backup mode and making copies of the datafiles.
I used the following method :
========> Part 1
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE set DATABASE "VPMY" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 3
....etc
LOGFILE
......... log file names
DATAFILE
... list of datafiles
CHARACTER SET US7ASCII;
========> Part 2
Up until the scheduled downtime, I would copy the archive logs from the production server to the new and run the following to apply the latest archive logs:
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
->AUTO<-
========> Part 3
After applying the last archive log while in restrict mode -
ALTER DATABASE OPEN resetlogs;
My question is, how do I do Part 2 in RMAN. I have managed to duplicate databases and restore databases using rman to a different server, but this obviously only covers the data upto the backup point. How can I do the above parts 1 -3 with downtime of about 5 minutes like I have done using old methods ?
Any help is much appreciated/

you should be able to recover as you go with rman as well..
copy the archived logs from A to B and apply them as they come in.
run
set until sequence x thread 1;
recover database;
if you're not opening the database after recovery you can just increment the set until sequence as the logs come in and do a new recovery.

[RMAN] problem with registering database

Hello, we have RAC environment on two nodes. We created rman catalog database and then registered our database with REGISTER DATABASE command. After that we issued command SHOW ALL and encountered an error:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_easy1.f'; # default
this is new catalog database, which is to replace the old one
how to deal with this problem ?

So you are following up on datafile 74 in this other thread :
problem with datafile recovery
Hemant K Chitale

RMAN: Unable to register database

Hi all,
I have just renamed the db_name, dbid and SID of a database using the DBNEWID Utility.
When I satrt up the database, it seems to start without any errors.
I need to take a backup of this database using RMAN.
But when I try to register the database, I get an error -
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/22/2009 15:26:39
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/22/2009 15:26:39
ORA-01587: error during control file backup file copy
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 323
Additional information: 1036288
Could anyone please help me resolve this problem?

How do I find out, what path exact path is it trying to access?
When I do a SHOW ALL, all that RMAN does is show the error again.
This is what I get -
RMAN> SHOW ALL;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 06/23/2009 08:16:28
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/23/2009 08:16:28
ORA-01587: error during control file backup file copy
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 323
Additional information: 602112
Edited by: user10882764 on Jun 23, 2009 5:21 AM
Edited by: user10882764 on Jun 23, 2009 5:22 AM

Can't register a database in RMAN catalog (PL/SQL package not current)

Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
Regards

user13064912 wrote:
Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
Your rman client is higher than your target server. That could be the problem.
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

RMAN restore database from another backup of different database in the same host

Hi Experts,
I have taken FULL Database Backup using RMAN , now I want to Restore and Recover the same database on different instance on Same Host.
Could u suggest any document or Steps to achieve this task.....
Thanks,
Mouni.

No Problem.
Please check this :
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmdupdb.htm#BRADV420
ORACLE-BASE - Duplicate a Database Using RMAN in Oracle Database 11g Release 2
Ensure you follow what Mr. Hemant has mentioned.
Regards
Karan

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Register database problem (oracle 8.1.6) on Linux 6.2

I'm unable to register my database using RMAN. I'm using Oracle 8.1.6 on Redhat Linux 6.2 (glibc - 2.2.14-5.0). Is there any known bug in Oracle 8.1.6 / rman on Linux 6.2.
These are the steps I followed:
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------
Actually I followed the same steps in my own PC with Oracle 8.1.7 on Win2k, It worked!!

Hello,
Narender,you have to include DISPLAY in your .bash_profile and set to your hostname, somewhat like this DISPLAY=hostname:0.0
or read the installation guides, installation of Oracle 8.1.6 in RHL 6.2 is straight forward.

Register Database error in Rman

Hi
I have been trying to register a database in RMAN . Here are the steps I took on OS linux Mandrake 8.1 using ORACLE version 9.2.0.1.0
SQL:
CONNECT sys/password@ora AS SYSDBA
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
rman catalog=rman/rman@ora
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
rman catalog=rman/rman@ora target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ora (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
This is returning the error message
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002:failure of register command at 07/16/03 12:56
RMAN-03014:implicit resyncof recovery catalog failed
RMAN-03009:failure of full resync command on default channel at 07/16/03
ORA01001- cursor not valide

Hi,
Change the name of your tablespace RMAN to CATTBS. I believe RMAN is a reserved word in oracle.

Restore Rman hotback in different machine with different Database name

Hi All,
I have oracle 11.2.0.3.0 in Windows 2003 R2 server 64 bit version,i have my production database "Proddb" in archivelog mode , I have taken RMAN hot backup at 9 AM and i want to restore this RMAN backup into new Machine with new Db Name "Testdb" at 1 PM ,in between 9 AM to 1 PM lots of transactions happened , lots of archivelogs got generated ..
Can anyone tell me how to restore RMAN Backup in different machine with new Db name and also how to apply those archive logs which got generated between 9 AM to 1 PM.
Thanks & Regards,
Vikash Jain

http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmrecov.htm#i1007814Yes you will have to apply all those archivelog after yours last backup 9:00 AM to 1:00 PM , someone give you good link to restore the RMAN backup from one machine ot another machine but it is missing one thing which you require is to restore database at new machine with new DB_NAME , for that you can do it in two ways after restoring and recovering the database.
1)After restoring with original name "Proddb" do not recover database ,Create contorlfile in control.txt format using alter database backup controlfile to trace,Shutdown restored database ,delete/rename contorolfile ,recreate controlfile from control.txt which by setting its first line as
Create controlfile set database "Testdb" resetlogs noarchivelogStartup mount with new created controlfile after defining new controlfile in pfile ,recover database at sql using backup controlfile "recover database using backup controlfile untill cancel" supply log till 1:00 PM ,Open database with resetlogs,run at comand prompt
sqlplus "/ as sysdba" @aduplib.sql so2)Or better approach is http://docs.oracle.com/cd/B28359_01/server.111/b28319/dbnewid.htm.
Khurram

Restore to a different node with RMAN and EMC Networker

Please, really need help :)
I took hotbackup using RMAN catalog which went to tape. Here is the script for that:
connect target sys/****@PROD;*
connect rcvcat rman/***@catalog;*
*run {*
allocate channel t1 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER="**",NSR_DATA_VOLUME_POOL=Oracle)';*
*backup database plus archivelog;*
*release channel t1;*
My settings include control file autobackup as follows:
*RMAN> show all;*
*RMAN configuration parameters are:*
*CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS;*
*CONFIGURE BACKUP OPTIMIZATION OFF; # default*
*CONFIGURE DEFAULT DEVICE TYPE TO DISK;*
*CONFIGURE CONTROLFILE AUTOBACKUP ON;*
*CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '/NMO_%F/';*
*CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default*
*CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default*
*CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default*
*CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default*
*CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/data/backups/PROD/ora_df%t_s%s_s%p';*
*CONFIGURE MAXSETSIZE TO UNLIMITED; # default*
*CONFIGURE ENCRYPTION FOR DATABASE OFF; # default*
*CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default*
*CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default*
*CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/data/backups/PROD/hotbkp/snapcf_PROD.f';*
I am trying to restore this backup that is on tape (EMC Networker) to a different node. I can do this outside of Networker without any problems. However, when I try to get the backup from tape I have this issue:
1. initPROD.ora is created and modified accordingly on a new server
2. Export sid, startup nomount on new server
export ORACLE_SID=PROD (on this new server)
*rman target /*
*startup nomount*
3. I then run the following and get this error:
*RMAN> run {*
*2> allocate channel t1 type 'SBT_TAPE'*
*3> send 'NSR_ENV=(NSR_SERVER="***",NSR_CLIENT="********")';*
*4> restore controlfile from autobackup;*
*5> sql 'alter database mount';*
*6> sql 'alter database rename file "/data/dbf/PROD/redo01.log" to "/data/scratch/dbf/PROD/redo01.log"';*
*7> sql 'alter database rename file "/data/dbf/PROD/redo02.log to "/data/scratch/dbf/PROD/redo02.log"';*
*8> sql 'alter database rename file "/data/dbf/PROD/redo03.log to "/data/scratch/dbf/PROD/redo03.log"';*
*9> set until sequence 22; (I get this from archive logs)*
*10> set newname for datafile 1 to '/data/scratch/dbf/PROD/system01.dbf';*
*11> set newname for datafile 2 to '/data/scratch/dbf/PROD/undotbs01.dbf';*
*12> set newname for datafile 3 to '/data/scratch/dbf/PROD/sysaux01.dbf';*
*13> set newname for datafile 4 to '/data/scratch/dbf/PROD/users01.dbf';*
*14> restore database;*
*15> switch datafile all;*
*16> recover database;*
*17> alter database open resetlogs;*
*18> }*
*allocated channel: t1*
*channel t1: sid=149 devtype=SBT_TAPE*
*channel t1: NMO v4.5.0.0*
*Starting restore at 27-FEB-09*
*released channel: t1*
*RMAN-00571: ===========================================================*
*RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
*RMAN-00571: ===========================================================*
*RMAN-03002: failure of restore command at 02/27/2009 22:10:43*
*RMAN-06495: must explicitly specify DBID with SET DBID command*
I cannot seem to pass this error. This error indicates that the db has to be either mounted or DBID set before the restore of teh controlfile. Mounting db before the restore of the controlfile does not work. Setting db id 1) does not make sense because if the primary db is down then I cannot get it, right? My primary is up now, so I was able to get db id, but setting it made the restore hang with the following:
*RMAN> run {*
*connect target*
*set dbid=466048808*
*2> allocate channel t1 type 'SBT_TAPE'*
*3> send 'NSR_ENV=(NSR_SERVER="***",NSR_CLIENT="********")';*
*4> restore controlfile from autobackup;*
*5> sql 'alter database mount';*
*6> sql 'alter database rename file "/data/dbf/PROD/redo01.log" to "/data/scratch/dbf/PROD/redo01.log"';*
*7> sql 'alter database rename file "/data/dbf/PROD/redo02.log to "/data/scratch/dbf/PROD/redo02.log"';*
*8> sql 'alter database rename file "/data/dbf/PROD/redo03.log to "/data/scratch/dbf/PROD/redo03.log"';*
*9> set until sequence 22; (I get this from archive logs)*
*10> set newname for datafile 1 to '/data/scratch/dbf/PROD/system01.dbf';*
*11> set newname for datafile 2 to '/data/scratch/dbf/PROD/undotbs01.dbf';*
*12> set newname for datafile 3 to '/data/scratch/dbf/PROD/sysaux01.dbf';*
*13> set newname for datafile 4 to '/data/scratch/dbf/PROD/users01.dbf';*
*14> restore database;*
*15> switch datafile all;*
*16> recover database;*
*17> alter database open resetlogs;*
*18> }*
*connected to target database: PROD (not mounted)*
*executing command: SET DBID*
*using target database control file instead of recovery catalog*
*allocated channel: t1*
*channel t1: sid=152 devtype=SBT_TAPE*
*channel t1: NMO v4.5.0.0*
*Starting restore at 27-FEB-09*
*channel t1: looking for autobackup on day: 20090227*
*channel t1: looking for autobackup on day: 20090226*
*channel t1: looking for autobackup on day: 20090225*
It looks like it cannot find the autbackup of controlfile? But when I list backup while connected to the target db and rman catalog, I see that autobackup is included in every hot backup that we do:
*BS Key Type LV Size Device Type Elapsed Time Completion Time*
*4639 Full 7.00M SBT_TAPE 00:00:04 27-FEB-09*
*BP Key: 4641 Status: AVAILABLE Compressed: NO Tag: TAG20090227T150141*
*Handle: /NMO_c-466048808-20090227-01/ Media:*
*Control File Included: Ckp SCN: 23352682865 Ckp time: 27-FEB-09*
*SPFILE Included: Modification time: 26-FEB-09*
I am stuck What I am doing wrong? Thank you!
Edited by: rysalka on Feb 28, 2009 8:35 AM

Do a list command to see if the controlfile backup is on tape.
RMAN> list backup of controlfile;
I suggest you to read the manual of EMC Networker or call EMC on how to restore the database to another node. I am using Veritas Netbackup, it may be similar to EMC Networke for your reference. There are a few things that need to be followed when you restore database to another node:
1) set DB_ID, which you have done
2) set NB_CLIENT (in your case NSR_CLIENT) to the primary node from where backup was taken
3) configure the backup server to allow redirect restore between the two nodes.
Hope this helps.

Recover Database in RMAN vs SQL*PLUS

Hello,
Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
Thanks.
h3. Solution Summary:
The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
Edited by: Dude on Jan 7, 2011 12:30 PM

Dude wrote:
I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
C:\Documents and Settings\chinar>rman target sys/sm
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area     138412032 bytes
Fixed Size                     1247708 bytes
Variable Size                 71304740 bytes
Database Buffers              58720256 bytes
Redo Buffers                   7139328 bytes
RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
2> ;
Starting restore at 07-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
Finished restore at 07-JAN-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 07-JAN-11
Starting implicit crosscheck backup at 07-JAN-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 07-JAN-11
Starting implicit crosscheck copy at 07-JAN-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 07-JAN-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
Finished restore at 07-JAN-11
RMAN> recover database;
Starting recover at 07-JAN-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
2.0\ORADATA\T\REDO02.LOG
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
media recovery complete, elapsed time: 00:00:03
Finished recover at 07-JAN-11
RMAN> exit
Recovery Manager complete.
C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
Database altered.
SQL> And above you see lines as
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
*2.0\ORADATA\T\REDO02.LOG*
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
alter database recover if needed
start until cancel using backup controlfile
Media Recovery Start
parallel recovery started with 2 processes
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile
Fri Jan 07 17:50:34 2011
alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
Fri Jan 07 17:50:34 2011
Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
Fri Jan 07 17:50:34 2011
Incomplete recovery applied all redo ever generated.
Recovery completed through change 665263
Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start until cancel using backup controlfile)
And these is not any difference.
Hope that help you and you got answer.

Unable to register database in catalog into emrep

Hello guys,
I have a RMAN catalog in one server that works fine, now I tried to move this catalog to the emrep database (In this database I have the Grid Control), as I can´t use export / import because the original database is 10.1.0.5 and the emrep database is 10.1.0.4, I have created a new catalog into the emrep database.
The problem appear when I try to register one database on it:
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/15/2009 12:10:43
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
So, my first question is: Is possible create a RMAN catalog in the same database of Grid Control?
If this is possible, any suggestions that can help me to resolve this errors?
Thanks.

Hello Damorgan, thanks for your answer.
I follow the steps in a remote database ( BEEVODES ) which I want register into catalog ( tstsuse11-emrep ):
oracle@srvdb01 ~]$ echo $ORACLE_BASE
*/u01/app/oracle*
oracle@srvdb01 ~]$ echo $ORACLE_HOME
*/u01/app/oracle/product/10.1.0/db_1*
oracle@srvdb01 ~]$ export ORACLE_SID=BEEVODES
oracle@srvdb01 ~]$ rman target / catalog rman@tstsuse11-emrep
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: BEEVODES (DBID=822996874)
recovery catalog database Password:
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/16/2009 12:12:49
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
But I continue with the same error.
I supose the instalation of emrep is ok, because the Grid Control ( installed there ) works fine.
Thanks again.

Problems connecting databases

Hi gurus,
I having a very documented problem but can't resolved by myself. I need a bit of help.
I have two databases in my laptop, both 11.2.0.1 running in windows 7 (i know that it was unsupported yet but this is not the problem).
Now i want duplicate ORIGINAL to COPY database with rman but i'm having:
RMAN-04006: error from auxiliary database: ORA-12505: TNS:listener does not currently know of SID given in connect
Both databases are running and working well, i can connect in different windows:
set ORACLE_SID=ORIGINAL
sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Jue Ago 2 11:02:47 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Conectado a:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select name from v$database;
NAME
ORIGINAL
in other window:
set ORACLE_SID=COPY
sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Jue Ago 2 11:02:47 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Conectado a:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select name from v$database;
NAME
COPYso i check the tnsnames:
# tnsnames.ora Network Configuration File: C:\Users\my_user\miBBDD\product\11.2.0\dbhome_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
COPY=
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = copy)
ORIGINAL=
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = ORIGINAL)
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (CONNECT_DATA =
      (SID = CLRExtProc)
      (PRESENTATION = RO)
LISTENER_COPY =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
LISTENER_ORIGINAL =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))All shows normal so check listener services:
C:\Users\my_user>lsnrctl services;
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 02-AGO-2012 11:30
:28
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Conectßndose a (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
Resumen de Servicios...
El servicio "CLRExtProc" tiene 1 instancia(s).
La instancia "CLRExtProc", con estado UNKNOWN, tiene 1 manejador(es) para este
servicio...
    Manejador(es):
      "DEDICATED" establecido:0 rechazado:0
         LOCAL SERVER
El servicio "DDBBXDB" tiene 1 instancia(s).
La instancia "original", con estado READY, tiene 1 manejador(es) para este servicio...
    Manejador(es):
      "D000" establecidos:0 rechazados:0 actuales:0 mßximo:1022 estado:ready
         DISPATCHER <machine: MY_USER, pid: 4356>
         (ADDRESS=(PROTOCOL=tcp)(HOST=MY_USER)(PORT=54428))
El servicio "original" tiene 1 instancia(s).
La instancia "original", con estado READY, tiene 1 manejador(es) para este servicio...
    Manejador(es):
      "DEDICATED" establecido:0 rechazado:0 estado:ready
         LOCAL SERVER
El comando ha terminado correctamenteListener.ora
# listener.ora Network Configuration File: C:\Users\my_user\miBBDD\product\11.2.0\dbhome_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = CLRExtProc)
      (ORACLE_HOME = C:\Users\my_user\miBBDD\product\11.2.0\dbhome_1)
      (PROGRAM = extproc)
      (ENVS = "EXTPROC_DLLS=ONLY:C:\Users\my_user\miBBDD\product\11.2.0\dbhome_1\bin\oraclr11.dll")
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
ADR_BASE_LISTENER = C:\Users\my_user\miBBDDand sqlnet.ora
# sqlnet.ora Network Configuration File: C:\Users\my_user\miBBDD\product\11.2.0\dbhome_1\network\admin\sqlnet.ora
# Generated by Oracle configuration tools.
# This file is actually generated by netca. But if customers choose to
# install "Software Only", this file wont exist and without the native
# authentication, they will not be able to connect to the database on NT.
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)I don't know why and how to resolve it, so any idea will be apreciated.
Thanks,

I have two databases in my laptop, both 11.2.0.1 running in windows 7 (i know that it was unsupported yet but this is not the problem).+
how could not be problem , please describe to us this sentence ?
It is recommended to run the duplicate database from the Auxiliary database only.
Please run the RMAN duplicate from auxiliary database only.
OR
Make a static entry of the service used in the service name to connect to the auxiliary database.
Back to
RMAN-04006 And ORA-12514 During RMAN Duplicate [ID 883490.1]

Problem registering database in RMAN on a different node

Similar Messages

Maybe you are looking for