RMAN catalog 11 GR 2 Update Catalog RMAN-06429

Similar Questions

• RMAN-06429: TARGET database is not compatible with this version of RMAN

  He Hi,.
  How can I solve this problem. How I will modernize the Rman. My database of production details are below
  ----------------------------------------------------------------
  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
  AMT for 32-bit Windows: Version 10.2.0.1.0 - Production
  NLSRTL Version 10.2.0.1.0 - Production
  
  while I'm setting up rman I get below error. Please help me.
  
  C:\Documents and Settings\vj.dcruz > target rman / catalog rman01/rman01@upp
  
  Recovery Manager: release 11.2.0.1.0 - Production Wed Sep 14 08:18:02 2011
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
  
  Recovery Manager incompatible with the TARGET database: required 8.0.4.0 to 10.2.0.0 RMAN
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-06429: TARGET database is not compatible with this version of RMAN
  
  Rgds,
  John

  Johnvd wrote:
  Hi Hemant,

  I do the same database connection 10.2.0.0 thing and configure the rman but while connect target its saying that my Recovery Manager: version 11.2.0.1.0 - Production the sea Sep 14 09:04:59 2011

  How its happens is there anywhere that I need to change the path.

  Kind regards
  John

  John, you should use the binary RMAN that is located in the bin folder of Oracle database (IE u01/oracle/product/10.2/db1/bin). You should not use "rman which comes with Oracle 11g client".

  If you are using windows, run the following commands at the command prompt, and then copy / paste the output:

  echo % 5ORACLE_HOME
  echo %path%

  If you use unix, run the following commands in the terminal and then copy / paste the output:

  echo $ORACLE_HOME
  echo $PATH

  Concerning

  Grosbois

• RMAN backup from 11g to 10g

  Hi all,
  
  I have a catalog DB 11 g and 10 g database. If I can take backup of catalog of 11g database 10g.
  
  When I try to connect to the rman, I get the error below.
  
  RMAN catalog=rman/rman@catalogdb target=sys@db10g_58
  
  Catalog DB is in 11g
  TargetDB in 10g
  
  OS: Windows 2003 Server on the servers.
  
  Please post suggestions.
  
  
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-06429: TARGET database is not compatible with this version of RMAN
  
  Kind regards
  Delphine K

  Go to this link

  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/compat002.htm

  Concerning
  Asif Kabir

• Possible to rman duplicate & oracle upgrade at the same time?

  We hoped we could use 'RMAN restore backups as part of an upgrade of database [ID 790559.1]' and duplicate a PRD 11.1 DB to another server that has only the 11.2 software. Anyone could do this?
  
  When I tried this, I got an error since the target DB is a version prior to the rman client - ' RMAN-06429: TARGET database is not compatible with this version of RMAN.
  
  I tried to connect to the target database and simply use the following syntax (duplicate "prd" DBID 123456789 to 'dev') to inform the backups, it would be necessary to NetBackup rman. Who also got an error - RMAN-01009: syntax error: found 'single-quoted-string': expected an a: "database, for, target, to. I tried other variations, but also had errors.
  
  I can tell him from a disk based backup, but must wait for a NFS mount big enough to fill it. The following syntax was in the docs of rman 11.2:
  DUPLICATE a 'PROD' dbid 8675309 to 'TEST' DATABASE
  Until TIME ' to_date (November 1, 2007 ',' DD/MM/YYYY "").
  The BACKUP LOCATION "/ backups NOFILENAMECHECK"
  PFILE='?/DBS/inittest.ora' db_file_name_convert = "prod", "test."
  
  If someone has done this or if it is not possible to do so, please let us know. Our goal is to not have to install the software on our new servers 11.1. Also, trying to avoid the restore with the same name and then rename the DB so that the ASM would have several directories for the DB.
  Thank you
  Brian
  
  
  OS: RHEL 6.3 for host target
  OS: RHEL 5.9 for the host target
  Target DB: 11.1.0.7.12 - PRD
  Auxiliary DB: 11.2.0.3.5 - DEV
  
  MML: Veritas NetBackup for Oracle - version 7.0
  
  DB using ASM & OMF

  Brian;

  The short answer is no.

  The RMAN executable will not match for one. If you need a document of MOS I can provide a.

  Frequently asked Questions about the restoration or duplication between different Versions and platforms [ID 369644.1]

  Best regards

  mseberg

  Published by: mseberg on February 6, 2013 17:55

• RMAN error 6429

  Hi Experts,
  
  I have 3 databases on 10.1.0.2 and 1 Database 10.2.0.1 on windows.
  When I start RMAN I get following error.
  
  RMAN > Connect target /.
  Recovery Manager incompatible with the TARGET database: RMAN req 8.0.4.0 to 10.1.0.0
  Unlike
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-06429: TARGET database is not compatible with this version of RMAN
  
  When he is interviewed got after the version of RMAN.
  SQL > select dbms_rcvman.getpackageversion from double;
  
  GETPACKAGEVERSION
  --------------------------------------------------------------------------------
  08.00.04.00
  
  Thank you

  I guess you've changed ORACLE_HOME, but not the path. So always the wrong RMAN executable is invoked.

  C:\oracle\product\10.1.0\db_2\bin\rman or change the path.

  Edited by: oradba the 16.04.2011 09:16

• Registration of database

  Hello world
  
  I have two Production DB. One is Oracle 9.2.0.1.0(on RHEL4.5) and another is Oracle 10.2.0.1.0(on RHEL 5.2). Now, I created a DB (10.2.0.1.0) more to use it as a DB catalog. Now when I'm Truing to to connect to Oracle 10.2.0.1.0 DB (target rman/catalogue rmancat/rmancat@prod1) it works fine, but when I try to connect the 9.2.0.1.0(rman Oracle / catalogue rmancat/rmancat@prod1) target, it gives me following error:
  
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-06429: target database is not compatible with this version of RMAN.
  
  Help, please.

  Hi, PARTHA.

  You must use the executable against the 9.2.0 9i oracle rman database.
  (installed in the ORACLE_HOME/bin of the installation of oracle 9i on RHEL4.5)

  If you want to use a remote client on windows, it should be less than or equal to the version of RDBMS.

  Please see the compatibility matrix.

  Kind regards

  Tycho

• Catalog RMAN 11g XE

  First of all, personally, I'm a novice of the oracle, more than one linux administrator myself.  But I support troubleshooting of errors with backups RMAN of a database.

  We are connecting to Enterprise Edition of Oracle (11.2.0.4.0) to back up the database.  Our catalog of recovery is the use of Oracle 11 g Express edition (I think that the version number is specifically 11.2.0.2.0)

  The backup sends a pretty normal RMAN backup script.  We get the result of our newspapers:

  Recovery Manager: release 11.2.0.4.0 - Production Wed Feb 26 10:17:17 2014

  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

  connected to target database: LIVEDB (DBID = #)

  connected to the recovery catalog database

  PL/SQL package CATALOG. DBMS_RCVCAT 11.02.00.02 in the RCVCAT database version is not current

  PL/SQL package CATALOG. DBMS_RCVMAN 11.02.00.02 in the RCVCAT database version is not current

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03009: failure to allocate command to the channel ch00 at 26/02/2014 10:17:19

  RMAN-10015: error compiling program PL/SQL

  RMAN-10014: PL/SQL error on line 102 12 column 0: statement ignored

  RMAN-10014: PL/SQL 302 on column error line 102 24: component 'THROTTLE_ME' must be declared

  Complete recovery manager.

  (Note: the renowned CATALOG database and target recovery catalog name renamed to LIVEDB to keep things generic)

  I'm assuming that the issue is ORACLE XE has an outdated version of the recovery catalog from the RMAN on the target database (11.2.0.4.0 vs 11.2.0.2).

  So, two questions:

  (1) does a version problem as I guess, or is there something else?

  (2) at - it something we can do using the software oracle XE as the recovery catalog?

  I have the RMAN script, if I need to publish.

  So we have successfully our catalog updated 11.2.0.4 and made a backup.

  The solution, which may have been easier than easy, had to use RMAN (11.2.0.4) client to connect to our catalogue (11.2.0.2).  Then, run the upgrade catalog command.

  Simple.

  Basically

  RMAN > connect username/password@CATALOG

  RMAN > upgrade catalog

  Obviously, CATALOG is the name of your catalog of recovery and probably should have a tnsnames.ora entry and others.

  We got it to work.

  clcarter, thanks for the bread crumbs - I never thought to use the updated backend catalog rman client.

• CATALOG RMAN WITH DIFFERENT PLATFORM

  Respected by all,
  my linux platform database and can create rman catalog in the windows platform?
  
  
  Thank you all for the reply.

  This is the same mechanism of functioning of the LINK DB in heterogeneous platforms like Oracle to SQL server, and vice versa.

  When you be able to update the database of different platforms, why not possible when the operating system is different.
  It will keep the repository with ORACLE, nothing to do with the OS.

• The Rman catalog must be registered?

  Hello experts,

  Don't you think that would be recorded in the database catalog Rman or not? If so could be in the same Rman catalog or in other different database?

  In the documentation of Rman something about this?

  My 11.2.0.3 Rman catalog database have a controlfile and default 15-day CONTROL_FILE_RECORD_KEEP_TIME.

  My media layer has a 90-day supply. So if I would to restore an older version of 15 days from the catalog in another machine I had to sign up former backups before games.

  Would be, this example above, a real possibility that I had to listen to extracts?

  Thank you and best regards.

  Francesco

  user4339084 wrote:

  Hello

  Thanks for the reply,

  but do you think useful registry the Rman catalog database in the catalog itself? Or is nonsense? a why?

  Thanks and greetings

  Of course, it is absurd to register in the database catalog with himself.  The entire purpose of the catalog is to help the recovery.  So how the catalog database can help in recovery if the catalog database needs recovery.

  https://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmcatdb.htm#BRADV89662

• Information on RMAN catalog database using and any catalog (controlfile)

  Hi all.

  I´d like some clarification on the subjects of RMAN RMAN usage with or without a recovery catalog (database / schema):

  (1) will be the database controfile target always store ALL changes made on RMAN? For example, configure changes persistent RMAN as a retention strategy, controfile autobackup, backup optimization and so forth, these will always record on the target database controlfile, even if we're connecting to RMAN with a recovery catalog?

  (2) what happens if we stop using the recovery catalog? I mean, if you don't use stored scripts and shot through the OS jobs or same EM control database, may continue to use then and do not connect more on the recovery catalog? It will be a problem? My target database stops?

  I will be the legacy a few databases to administer and they connects to a catalog of recovery of database / schema, it's good, but I want to set up my own backup and restore policies / procedures in a two-step process: (1) have each configuration of RMAN database on controlfile, Later (2) in view of the use of the recovery catalog to centralized databases and keep more disk backup and restore.

  Thanks in advance!

  (1) Yes, everything about the structure of data is stored in the controlfile. The location of the backup controlfile is also stored in the controlfile.

  The backup controlfile location is also stored in the catalog if you synchronize to it.

  (2) you can stop immediately using the catalog if you choose, and as long as you have a backup RMAN script file, you can always backup using this file.

  The catalog is used to store the location of the backupsets, and copy image. If you have any scripts to store, it can store these too. Really, it's all done catalog.

  You can back up and restore/recover without a catalog, as long as you know where all backups are retained.

• RMAN catalog upgrade 11.2.0.4.7 with 11.2.0.4.0 database

  Hello

  One of my new database received from group fixes 11.2.0.4.7.

  When I want to join this real my rman catalog database, I "PL/SQL package RMAN. DBMS_RCVCAT version 11.02.00.03 in the RCVCAT database is not current."

  I can easily do a "catalogue of upgrade", but is there an impact on my other databases running 11.2.0.4.0, which cannot receive the patches group before long.

  Thank you for your kind reply.

  Eric

  Hello

  Having the RMAN catalog with a newer version than the database version and will not create any problem.

  (Doc ID 73431.1) RMAN compatibility matrix

  Thank you

  Sundar

• How to create the file controlf from scratch when there is no backup rman, catalog, or trace.

  Hello

  I am a beginner, I know that we can restore with RMAN control file configure automatic backup feature or by connecting the catalog

  charge the Alter database backup controlfile to trace.

  But suppose that there is no backup. You have the database running in nomount. I came across a blog which was responsible for creating the control file manually and when there is no planned block number error came, the blogger has used the forumale something as expected number of block * 1024 / something. Lost the link to this blog

  was wondering is it possible to create a controlfile from scratch. with little information as the location of the data file, repeat the log size / location.

  Please can someone let me know it in detail or shoot me this link!

  Thank you

  2638616 wrote:

  Hello

  I am a beginner, I know that we can restore with RMAN control file configure automatic backup feature or by connecting the catalog

  charge the Alter database backup controlfile to trace.

  But suppose that there is no backup. You have the database running in nomount. I came across a blog which was responsible for creating the control file manually and when there is no planned block number error came, the blogger has used the forumale something as expected number of block * 1024 / something. Lost the link to this blog

  was wondering is it possible to create a controlfile from scratch. with little information as the location of the data file, repeat the log size / location.

  Please can someone let me know it in detail or shoot me this link!

  Thank you

  1. Yes, you can do this

  2 Controlfile script is standard... link doc oracle: http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_5003.htm

  3. prepare with the location of the data files and of redologs online then create it.

  Note - If you have placed the name of the different database, then, it will check with datafile and it give error (if you need correct the name of the database)

  As you have not indicated whether or not the last stop of database is compatible (we assume that there are his uniform and mandatory ORL and archives)

  -Pavan Kumar N

• Firewall rules RMAN target database and RMAN catalog database

  Hi, we are on Oracle 11.2.0.4 and we just build a new environment, in which case the RMAN catalog is located on a seprate from the target database server. I'm trying to figure if the firewall between these two rules should be two-way, so that the target database and RMAN catalog database can ping each other. If bi-directional rules in place, so what's the reason for this? I understand that during RMAN backup entries are made in the RMAN catalog database, but do not know if the RMAN catalog database must always meet target db. Thank you!

  If you run the rman command on the target database server, it acts as a client to the catalog database server by connecting on sqlnet to the catalog database.

  If you run the rman command on the catalog database server, it's a sqlnet connection join the target database server.

  In both cases, rman is simply a client that connects to the two databases.

  Hemant K Collette

• RMAN: we have a window of recovery of 130 days defined and we use a catalog of recovery, but report need backup doesn't report anything.

  Our first backup was made on April 28, 2015. Some how report need backup don't recount everything that needs to be backed up. Please let me know why it is like that.

  Hello

  When you run rman phrase 'report need backup '?. just after completing a backup complete (including the arch files)?

  If you made a backup today,"report needed backup; ' returns 0.

  I tested in oracle 10 and oracle 11, with the default of 60 days and archivelog retention policy backup every 3 hours.

  * "report need backup 300 recovery window days."

  Returns the value 0.

  * "list backupset summary"

  return values of 60 days so far.

  I reproduced with and without connecting to the catalog.

  Please read the old note:

  How does the REPORT the WINDOW to RETRIEVE NEED BACKUP? (Doc ID 301704.1)

  This is for oracle 9i, but I think you can always apply on oracle 11g

• migrate catalog basic rman 10.2 11.2

  My rman catalog is currently in a 10.2.0.4 IS based on Windows.

  I'm moving it to 11.2.0.4 SE on Linux.

  I thought at first it would be a simple the schema of the source expdp, impdp rman which target.

  The database is created. The user created "rman" and recovery_catalog_owner granted to him.

  Exported from the current catalog with "" expdp system / * directory = dpump dumpfile = exp_rmcat_catalog.dmp = logfile = exp_rmcat_catalog.log rman schemas "»

  "Copy the dump file to the new server and import with."

  Impdp ${localuser} / patterns$ {localpwd} = directory of rman dumpfile logfile = DPUMP = rmcat_import.log = ${dumpfile} table_exists_action = replace

  But in a second trial of the importation, he threw a lot of mistakes like

  ORA-39111: type of dependent object OBJECT_GRANT: "RMAN" ignored, basic VIEW object type: "RMAN". "' TSATT_V ' already exists

  OK, I understand that the 'table_exists_action"applies to the tables and objects not non-table.  I was a bit surprised to find non-table that the rman schema objects, but it occurs to me that since they are, and they come from a 10 g database, could it be questions their import in a an 11 g database?  Would I better off clean start, issuing a CATALOG to CREATE then import only tables?

  All of the databases being backed up with rman are 11.2.0.2 or 11.2.0.4.  The catalog rman itself is the last database 10g I.

  Ah, I forgot the IMPORT CATALOG command.

  So...

  create the rman schema owner in new catalog databsae

  create the catalog in the new database

  catalog import not unregister, a database at a time.