hussainkhan22
asked on
Oracle RMAN error
When I am running the below command getting the following error. I really appreciate your help.
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
RMAN-00571: ========================== ========== ========== ========== ===
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ========================== ========== ========== ========== ===
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "archivelog, bac
kup, backupset, channel, check, copies, controlfilecopy, cumulative, current, da
tabase, datafile, datafilecopy, device, diskratio, filesperset, format, full, fo
rce, incremental, keep, (, maxsetsize, nochecksum, noexclude, nokeep, not, parms
, proxy, pool, skip, spfile, setsize, tablespace, tag, validate"
RMAN-01008: the bad identifier was: AS
RMAN-01007: at line 1 column 8 file: standard input
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
RMAN-00571: ==========================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ==========================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "archivelog, bac
kup, backupset, channel, check, copies, controlfilecopy, cumulative, current, da
tabase, datafile, datafilecopy, device, diskratio, filesperset, format, full, fo
rce, incremental, keep, (, maxsetsize, nochecksum, noexclude, nokeep, not, parms
, proxy, pool, skip, spfile, setsize, tablespace, tag, validate"
RMAN-01008: the bad identifier was: AS
RMAN-01007: at line 1 column 8 file: standard input
what version of oracle/rman are you using?the syntax is usable as of oracle 10g, not before ...
ASKER
I have 2 database one is oracle10g and another one is oracle9i on windows system. But I connect to oracle10g and issuing this commands. How can I find which version is my RMAN. How can I also find which database I am connected and what version at the RMAN prompt.
you surely connect with the rman from the oracle9 home ...
ensure you go to the path of oracle10 home, and run the rman from there.
ensure you go to the path of oracle10 home, and run the rman from there.
>>How can I find which version is my RMAN
When you type RMAN at the command prompt it displays the version.
>> How can I also find which database I am connected and what version at the RMAN prompt.
I don't know of an RMAN command that provides this information. You should already know the database you are connecting to. Once you know that you can connect using sql*plus version.
When you type RMAN at the command prompt it displays the version.
>> How can I also find which database I am connected and what version at the RMAN prompt.
I don't know of an RMAN command that provides this information. You should already know the database you are connecting to. Once you know that you can connect using sql*plus version.
ASKER
C:\oracle\product\10.2.0\d b_1\BIN>se t ORACLE_SID=oracle10
C:\oracle\product\10.2.0\d b_1\BIN>rm an catalog rman/rman@oracle10 target oracle1
0
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Oct 20 08:06:27 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: ORACLE10 (DBID=2460547249)
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
Starting backup at 20-OCT-10
current log archived
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
RMAN-00571: ========================== ========== ========== ========== ===
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ========================== ========== ========== ========== ===
RMAN-03002: failure of backup plus archivelog command at 10/20/2010 08:07:23
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06429: RCVCAT database is not compatible with this version of RMAN
C:\oracle\product\10.2.0\d
0
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Oct 20 08:06:27 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: ORACLE10 (DBID=2460547249)
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
Starting backup at 20-OCT-10
current log archived
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
RMAN-00571: ==========================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ==========================
RMAN-03002: failure of backup plus archivelog command at 10/20/2010 08:07:23
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06429: RCVCAT database is not compatible with this version of RMAN
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
C:\Documents and Settings\Administrator>sql plus rman/rman@oracle10
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Oct 20 09:06:15 2010
Copyright (c) 1982, 2002, Oracle Corporation. 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> select * from v$version;
BANNER
-------------------------- ---------- ---------- ---------- --------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Oct 20 09:06:15 2010
Copyright (c) 1982, 2002, Oracle Corporation. 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> select * from v$version;
BANNER
--------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
C:\oracle\product\10.2.0\d
C:\oracle\product\10.2.0\d
c:\oracle\product\10.2.0\d
C:\oracle\product\10.2.0\d
C:\oracle\product\10.2.0\d
0
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Oct 20 09:15:12 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: ORACLE10 (DBID=2460547249)
connected to recovery catalog database
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
Starting backup at 20-OCT-10
current log archived
PL/SQL package RMAN.DBMS_RCVCAT version 09.02.00 in RCVCAT database is too old
RMAN-00571: ==========================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ==========================
RMAN-03002: failure of backup plus archivelog command at 10/20/2010 09:15:40
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06429: RCVCAT database is not compatible with this version of RMAN
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm guessing here but based on some of your previous questions: Did you by chance do a FULL import from the 9i database into the 10g database?
ASKER
No I didn't do import full database anytime. Why are you asking this, just want to know so that I wont make that mistake in future
I'm just not sure how a fresh creation of a 10g database ends up with a 9i RMAN catalog.