RMAN: To Register 8i Database in 9i Catalog

Dear friends,
I am working with Oracle 9.0.1.1 under W2K. Recently I configured Recovery Catalog database in our 9i server. Now I wanted to register two target databases that are running in another server Oracle 8i (same network).
When I tried to register, I encounter the error like "RMAN version not combatible with Oracle 9.0.1.1 ... Target database version is too old"
Is it possible to register the target database 8i into 9i catalog??? If not, what could be the alternative?
Thanks in advance,
M M Sheriff

Hey Sheriff,
have a look at the link below. It shows you all the compatibilities of RMAN catalog and target databases
and executables. I'm sure that you can use the 8i catalog and executable for oracle9i targets.
Hope this was a little helpful...
Cheers,
Ralf
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=73431.1

Similar Messages

Registering Clone database in Recovery catalog

Can we able to register the clone database in recovery catalog database without changing dbid?
I don't want to use dbid utility.
Is that any parameter?
Regards,
Latha

Well you can register it without changing any parameters in oracle 10.2
That does not mean you should do it.
I would have answered as follows:
It is not a good idea to register a clone database in the same recovery catalog as the original database as the recovery catalog uses the dbid to identify the database and having two databases with the same dbid essentially corrupts the recovery catalog.
If you change the dbid then it is perfectly okay to store the cloned database in the same recovery catalog.

Error while Registering the Database with Catalog..

I m creating recovery catalog in same database, and getting the errors.
1. I have created TOOLS tablespace
2.CREATE USER RMAN2
SQL> CREATE USER rman IDENTIFIED BY cat
2 TEMPORARY TABLESPACE temp
3 DEFAULT TABLESPACE tools
4 QUOTA UNLIMITED ON tools;
CREATE USER rman IDENTIFIED BY cat
ERROR at line 1:
ORA-01920: user name 'RMAN' conflicts with another user or role name
SQL> ed
Wrote file afiedt.buf
1 CREATE USER rman2 IDENTIFIED BY cat
2 TEMPORARY TABLESPACE temp
3 DEFAULT TABLESPACE tools
4* QUOTA UNLIMITED ON tools
SQL> /
User created.
3. GRANT RECOVERY_CATALOG_OWNER
SQL> GRANT RECOVERY_CATALOG_OWNER TO rman2;
Grant succeeded.
4. To create the recovery catalog:
1. Connect to the database that will contain the catalog as the catalog owner.
H:\>rman catalog rman2/cat@rock
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 10:45:52 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to recovery catalog database
2. Run the CREATE CATALOG command to create the catalog.
RMAN> CREATE CATALOG;
recovery catalog created
3. Optionally, start SQL*Plus and query the recovery catalog to see which tables were created:
H:\>sqlplus
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Sep 5 11:53:36 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: rman2/cat
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select count(*) from cat;
COUNT(*)
91
SQL> ed
Wrote file afiedt.buf
1 select owner, table_name, tablespace_name
2 from dba_tables
3* where table_name='DB'
SQL> /
OWNER TABLE_NAME
TABLESPACE_NAME
RMAN2 DB
TOOLS
RMAN DB
ABAMCO_TEST
Next step is to registering the Database in the Recovery Catalog.
Registering a Database in the Recovery Catalog
H:\>rman TARGET / CATALOG rman2/cat@rock
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 11:56:09 2008
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
I m getting above error while registering the Database with Catalog,
Can anybody help me how can I register the Database with Catalog.????
Waiting for Reply!!!!!!!

Dear Manoj I can log in at TARGET Database.
H:\>rman
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 12:41:59 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target sys/rock
connected to target database: ROCK (DBID=3255117147)
RMAN>
============================================================
USING CONNECT STRING as you said.
H:\>rman target "sys/rock@rock as sysdba" catalog rman2/cat@rock
Argument Value Description
target quoted-string connect-string for target database
catalog quoted-string connect-string for recovery catalog
nocatalog none if specified, then no recovery catalog
cmdfile quoted-string name of input command file
log quoted-string name of output message log file
trace quoted-string name of output debugging message log file
append none if specified, log is opened in append mode
debug optional-args activate debugging
msgno none show RMAN-nnnn prefix for all messages
send quoted-string send a command to the media manager
pipe string building block for pipe names
timeout integer number of seconds to wait for pipe input
checksyntax none check the command file for syntax errors
Both single and double quotes (' or ") are accepted for a quoted-string.
Quotes are not required unless the string contains embedded white-space.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00552: syntax error in command line arguments
RMAN-01009: syntax error: found "as": expecting one of: "append, at, auxiliary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, nocatalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 0 column 16 file: command line arguments
H:\>rman
It didnt work either.
I have only one database rock, and created recovery catalog in it. I want to register rock database with recovery catalog.

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

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

Unregister database from the catalog

Is it possible to cancel the registration of a database from the catalog?

First you should delete all backups from the catalog database for the target. This isn't required but is easier accomplished with the target still registered.
Next, you'll need to obtain the DB_KEY and DBID from the RC_DATABASE view in the RMAN schema in the catalog database. Then you'll run the following as the RMAN user connected to the RMAN catalog database in SQL*Plus.
execute dbms_rcvcat.unregisterdatabase(DB_KEY,DBID);

About database incarnations in catalog versus non-catalog

Hi all
Listing out the incarnations of my target database when not connected to the recovery catalog :
RMAN> list incarnation of database testdb;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       TESTDB   2539541829       PARENT 1          11-JUL-11
2       2       TESTDB   2539541829       PARENT 591584     12-JUL-11
3       3       TESTDB   2539541829       PARENT 2061948    19-JUL-11
4       4       TESTDB   2539541829       ORPHAN 1345130669 13-MAY-13
5       5       TESTDB   2539541829       CURRENT 1345130669 15-MAY-13And listing out the incarnations when connected to the catalog:
RMAN> list incarnation of database testdb;
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1178485 1178523 TESTDB   2539541829       PARENT 1          11-JUL-11
1178485 1178524 TESTDB   2539541829       PARENT 591584     12-JUL-11
1178485 1178525 TESTDB   2539541829       PARENT 2061948    19-JUL-11
1178485 1178526 TESTDB   2539541829       ORPHAN 1345130669 13-MAY-13
1178485 1178486 TESTDB   2539541829       CURRENT 1345130669 15-MAY-13Why are INC KEY numbers not matching? Is this a bug or is it expected behaviour?
Please help me shed some light on this..
Thanks.

Hi,
Manual said:
DB Key- When combined with the Inc Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key to unregister a database from a recovery catalog, that is, delete all the rows associated with that database from the recovery catalog.
INC Key- When combined with DB Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key in RESET DATABASE TO INCARNATION when recovering the database to a time before the most recent RESETLOGS.
<<http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta027.htm#CHDGGAFF>>
recovery-catalog and control file-catalog is a catalog of different, So not match.
Regards,

Rman backup for oracle11g database

Hi,
I want to take the rman backup of 11.2.0.1.0 database, but my catalog database is 10.2.0.1. So Is it possible to take it.
Please suggest me.
My target database : 11.2.0.1.0
OS: windows 2003 R2 server
My catalog database: 10.2.0.1
OS: windows 2003 R2 server

here you go : http://www.comp.dit.ie/btierney/oracle11gdoc/backup.111/b28273/compat.htm

RMAN-07518: Reason: Foreign database fil

Hi,
on 10g R2 on AIX ,
I recreated a database (withe the same name)
when trying to catalog ancient backup files I receive the RMAN-07518 error :
File Name: /appli/oracle/BACKUP/RMAN/FULL/MYDB/df_MYDB_20110409_117_1
RMAN-07518: Reason: Foreign database file DBID: 1486281403 Database Name: MYDBIs there any solution for that ?
Thank you.

7518, 3, "Reason: Foreign database file DBID: %s Database Name: %s"
// *Cause: This is an informational message only.
// *Action: No action is required.

Error RMAN connection to auxiliary database ORA- 12514

Hi,
I'm trying to make a clone of my database in another server but when I'm trying to connect as follow the RMAN return
to me the error ORA-12514.
C:\Documents and Settings\joses.morales>rman TARGET sys/pass@iswgen nocatalog
AUXILIARY sys/[email protected]
Recovery Manager: Release 8.1.7.4.1 - Production
RMAN-06005: connected to target database: ISWGEN (DBID=2348350645)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
For more information:
- the auxiliary database is started whit nomount option.
- this is my listener.ora in the auxiliary host
     LISTENER =
     (DESCRIPTION =
     (ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
     SID_LIST_LISTENER =
     (SID_LIST =
     (SID_DESC =
     (GLOBAL_DBNAME = oracle8)
     (ORACLE_HOME = C:\oracle\ora81)
     (SID_NAME = iswgen)
     (SID_DESC =
     (GLOBAL_DBNAME = oracle8)
     (ORACLE_HOME = C:\oracle\ora81)
     (SID_NAME = oracle8)
- this is my tnsnames.ora in the auxiliary host
     ISWGEN =
     (DESCRIPTION =
     (ADDRESS_LIST =
     (ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
     (CONNECT_DATA =
     (SERVICE_NAME = iswgen)
     ORACLE8 =
     (DESCRIPTION =
     (ADDRESS_LIST =
     (ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
     (CONNECT_DATA =
     (SERVICE_NAME = oracle8)
- this is my tnsnames.ora in the target host
iswgen =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = gdcoracle)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
     iswgen.wssp61 =
     (DESCRIPTION =
     (ADDRESS_LIST =
     (ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
     (CONNECT_DATA =
     (SERVICE_NAME = iswgen)
- target server: gdcoracle
- auxiliary server: wssp61
- global name in auxiliary: Oracle8
- intances in auxiliary: Oracle8 & Iswgen
I was expecting the follow message:
connected to target database: ISWGEN (DBID=519338572)
using target database control file instead of recovery catalog
connected to auxiliary database: ISWGEN.WSSP61 (not mounted)
Can anybody help me to resolve this error ORA-12514??
Thanks

I'm try to connect to the auxiliary server at SQLPLUS and I get the follow:
C:\Documents and Settings\joses.morales>sqlplus /nolog
SQL*Plus: Release 8.1.7.0.0 - Production on Sex Jun 1 12:26:09 2007
(c) Copyright 2000 Oracle Corporation. All rights reserved.
SQL> conn sys@iswgen
Informe a senha:
ERROR:
ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
descitor de conexao
SQL> conn sys@iswgen as sysdba
Informe a senha:
ERROR:
ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
descitor de conexao
SQL> conn internal as sysdba
Conectado.
SQL>
Any sugestions?
Thanks everyone and regards

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 can i do a RMAN backup of my database from the network ?

i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.

Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus

RMAN restore from active database, ASM

I'm attempting to refresh a stage database from a prod database using RMAN restore from active database. Both are on ASM. After working through various hurdles, I've got one issue I'm a bit stuck on. I've got a handful of data files that do NOT have OMF names (ie MSTRDATA/mstrmdpd/datafile/gsa_indx instead of MSTRDATA/mstrmdpd/datafile/gsa_indx.351.714779777) and these are failing when I do the restore. The syntax I'm using in RMAN is as follows:
duplicate target database to dwstage
from active database
spfile parameter_value_convert 'dwprod','dwstage'
SET DB_FILE_NAME_CONVERT '+DWPROD','+DWSTAGE'
SET LOG_FILE_NAME_CONVERT '+DWPROD','+DWSTAGE';
The error message I'm getting is this:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/21/2011 13:26:24
ORA-17628: Oracle error 19505 returned by remote Oracle server
continuing other job steps, job failed will not be re-run
Normally from what I've seen/read this error can be traced back to needing to pre-create the directories for the controlfiles etc, but since 90% of the datafiles copied correctly...
Any suggestions as to a way around this, or am I going to be forced to restore from a backupset?

This fails saying that "ORA-12528: TNS:listener: all appropriate instances are blocking new connections" which is quite normal given that the listener is havig a handle in BLOCKED state for this AUXDB as it is in NOMOUNT state.
Could you please help me on how to proceed?
One option can be to create the controlfile manually and mount the instance before doing the duplicate. I hope Rman can continue from there.
Another option is to go for backup based duplicate.
Is there any other way to go?
Provide static registration on AUXILIARY side for your auxiliary instance and try again.For example change listener.ora file as
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = AUXDB)
      (ORACLE_HOME = <your oracle home>)
      (SID_NAME = AUXDB)
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = <auxiliary host/ip>)(PORT = 1521))
)And restart listener on auxiliary host then try again

Rman backup with standby database

Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance

726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance
"I scanned thru MOS but could find solutions for rman with active DG."
Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

Registering a database in an AppServer

I use the Sun Application Server (most updated version I guess) and I was trying to register my database in the Application Server. I understand that to do this I have to create a connection pool by going to the admin console of the AppServer. I have done this and there are fields to be keyed in. I am trying to connect to a Microsoft Access Database and the first field to fill in the AppServer is the DataSource. Basically there are parameters to be field in the AppServer and I have tried and tried but I cant seem to get it right. Can anyone please tell me how I can register my Access Database called "studData.mdb" located in the root directory in the AppServer so I create a DataSource object that I would use in my EJBs.

It depends on the app server, of course.
If you're connecting to M$ Access, you need to create a Resource where you give it the JNDI lookup name, the JDBC-ODBC bridge driver class sun.jdbc.odbc.JdbcOdbcDriver, and the URL to your Access file.
Check the docs to see how Sun's app server wants you to do it. If Tomcat is involved, they have explicit docs to tell you how on their Tomcat site. Sun app server should be similar. Could give you the start you need.

RMAN: To Register 8i Database in 9i Catalog

Similar Messages

Maybe you are looking for