RMAN catalog upgrade 11.2.0.4.7 with 11.2.0.4.0 database

Similar Questions

• Upgrade to 11.2.0.4 with the physics of the standby database

  Dear gurus,

  
  We have the obligation to upgrade databases 11.2.0.1 existing 11.2.0.4 and 11.2.0.2 to 11.2.0.4 running on AIX boxes. We have physical databases of Eve configured for these databases of different version.

  During the preparation of the documentation for upgrade, we observed that FORCE_LOGGING is disabled for the production databases and observed, there are objects along 350 + with journaling = No. and logging = NULL and patterns are SYS, SYSMAN, APEX_030200, OLAPSYS, XDB, SYSTEM, OIMDBUSER, MDSYS, EXFSYS, WMSYS, ORDDATA, PERFSTAT.

  My query:

  I can still proceed with the upgrade still under the document indicated for "upgrading a database with a physical Standby database in place" without you connect the data dictionary objects will be not be updated pending database.

  Can you please let me know your suggestions on this please?

  Kind regards

  Kumar

  Hello;

  Quote:

  "Keep the database in LOGGING mode FORCE as long as the backup database is necessary."

  Of

  Oracle® DataGuard of Concepts and Administration 11 g Release 2 (11.2) E10700-02

  I think I FORCE turn on CONNECTING to the primary database and rebuild the eve before doing the upgrade.

  Best regards

  mseberg

• Discover the owner of the catalog to make catalog upgrade

  Hello

  Oracle gives suggests that we need to run RMAN catalog upgrade after installing a hotfix for. How to know which account/schema should be used to update the catalog? Our database has been installed by the contractor, and according to my colleague, they also had difficulties with this problem. I tried to upgrade the system catalog, I got an error of "RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to the user SYSTEM. Will be that the database works very well if we simply install patches without upgrading the catalog until we could resolve the problem?

  Thanks for the help!

  Willy

  user6783497 wrote:

  Hello

  Oracle gives suggests that we need to run RMAN catalog upgrade after installing a hotfix for. How to know which account/schema should be used to update the catalog? Our database has been installed by the contractor, and according to my colleague, they also had difficulties with this problem. I tried to upgrade the system catalog, I got an error of "RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to the user SYSTEM. Will be that the database works very well if we simply install patches without upgrading the catalog until we could resolve the problem?

  Thanks for the help!

  Willy

  This would be better asked in the forum of rman, however...

  the UPGRADE CATALOG is from a client of rman linking the newly rivierra/improved ORACLE_HOME, like this:

  Catalog RMAN /@.

  where is the owner of the catalog, and is the password.

  Now, you don't know the owner, and the password?  How to connect your backup scripts to the catalog?

  You can do this to discover the owner

  -Connect to the server hosting the catalog database

  -the sid of the catalog database ORACLE_SID value

  -sqlplus / as sysdba

  SQL > select distinct master from dba_objects where object_name like '% RC;

• Control to the RMAN catalog file

  Dear friends,
  
  Now my RMAN backup is running using the control file. How can I change the catalog?
  
  Please guide me.
  
  Thanks in advance.

  If there is no drawback application RMAN catalog, then I guess I do it with her.

  Like when I want to recover the database in a new server with the backup and so on... >

  The downside is the maintenance you need to do for the catalog. He had some performance issues with the catalog in previous versions, but I think he's fine now.

  Do I need to back up the RMAN catalog or back up separately in addition to the backup of the database?

  Could I lose the catalog if I lose my database

  Just save as regularly as you can afford. RMAN or export. Losing the catalog is a hassle but not the end of the world.

• RMAN - catalog of recovery

  Hi all
  
  We have about 10-12 databases running - wanted to know your opinion on what is the advantage of using recovery catalog vs. just using controlfiles for rman backups?
  
  Thanks in advance

  Hi DBA115102,

  These are the advantages by using the rman catalog:
  - keep you metadata about backups in a same location record.
  - you can save scripts in a repository
  - you can make centralized (with your own scripts) backup reports
  - you can restore a database to a previous incarnation

  but also some constraints:
  - you can get into trouble between versions. See compatibility matrix: [http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/compat003.htm]
  - you must include the repository RMAN in a database upgrade strategy
  - architecture is more complex (at least a new scheme, but a new database will be safer)
  - you have more work with maintenance operations (intersection, resync, remove obsolete, register, unsubscribe...)

  For my personal experience (I bet that's what you're really asking) using the catalogue is easier if you have a homogeneous environment.

• RMAN catalog 11 GR 2 Update Catalog RMAN-06429

  Hi all
  
  I have databases oracle 11 GR 1 material and GR 11, 2 in use.
  Last time I would upgrade the catalog with 'Upgrade catalog' database to backup databases the new 11 GR 2.
  
  The upgrade looks good, but after this task, I have 21 invalid objects in the RMAN catalog and it was not possible to compile without error. And all the other which backups using the catalog fails the RMAN-06429.
  -> Package PL/SQL BAKRMAN. DBMS_RCVCAT Version 11.02.00.02 in the RCVCAT too recent database.
  I therefore return to the action.
  
  What is the right way to use the catalog rman with levels of different database?
  How can I use the catalog also for 11 GR 2 databases without any side effect on my other 11 GR 1 material databases?
  The rman catalog reside on a 11.1.0.7.0 database.
  
  BR
  Daniel
  
  http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28273/compat003.htm
  Database TARGET RMAN-06429 is not Compatible with this Version of RMAN [245698.1 ID]

  Hello

  So, how I understand, I should send the command "upgrade catalog" new 11 GR 2 database server.

  Yes, the process of looking at this.

  Opening of session of rman 11 GR 2 binary upgrade CLI:

  $ rman catalog bakrman /@.

  connected to the recovery catalog database
  RMAN PL/SQL package. Version X.X.X.X in database RCVCAT DBMS_RCVCAT is too old

  RMAN > upgrade catalog;

  recovery catalog owner is BAKRMAN
  Enter the command of CATALOG to UPGRADE again to confirm the upgrade of the catalogue

  RMAN > upgrade catalog;

  Upgraded to version X.X.X.X recovery catalog
  DBMS_RCVMAN package updated to version X.X.X.X
  DBMS_RCVCAT package updated to version X.X.X.X

  After that this upgrade, only objects of schema in the recovery catalog database should be improved, right?

  Fix.

  Kind regards
  Tycho

  Edited by: tychos January 25, 2011 14:40

• Version of the RMAN catalog

  Hi, we are modernizing our databases 9i to 11g R2 R2 target, use us RMAN to make backups and our version of RMAN catlog is 10.2.0.2, I need to know if we continue with the current version of our data catalog RMAN or it must be upgraded to version equilent to our target databases You also have to configure Data protector with RMAN will be compatible with the lower version of the RMAN catalog database.
  
  Kind regards

  In our case when we improve our database to 10.2.0.2 to 10.2.0.4 didn't us connect with the catalogue. After the upgrade of the database catalog in 10.2.0.4 we took over with the RMAN backup.

  You can take the RMAN backup without a catalog database.

  Concerning
  Asif Kabir

• ORA-39080: cannot create queues during the backup from the rman catalog

  Hello
  I am trying to upgrade my database 10 g and 11 g and I'm trying to back up my rman catalog. However, I get an error. Can someone help me please-
  
  That's what I give-
  nohup expdp DIRECTORY = EXPORT_DIR userid=rman/adc1243@rmandb full = y job_name = full_rmandb_upg_exp DUMPFILE=EXPORT_DIR:rmandb_upg_exp%U_20100618.dmp LOGFILE = PARALLEL EXPORT_DIR:rmandb_upg_exp_20100618 = 3 &
  
  and I get this-
  
  Oracle @ < progd1 >: / home/oracle $tail f nohup.out
  ORA-31626: there is no job
  ORA-31637: could not create user RMAN FULL_RMANDB_UPG_EXP work
  ORA-06512: at "SYS." DBMS_SYS_ERROR', line 95
  ORA-06512: at "SYS." "KUPV$ FT_INT", line 600
  ORA-39080: cannot create queues ' KUPC$ C_1_20100618202950 ' and ' KUPC$ S_1_20100618202950 ' to Data Pump task
  ORA-06512: at "SYS." DBMS_SYS_ERROR', line 95
  ORA-06512: at "SYS." ' KUPC$ QUE_INT ', line 1606
  ORA-04031: unable to allocate 56 bytes of shared memory ('pool feed', 'unknown object', 'pool feed', 'set the allocation callback')

  ORA-04031: unable to allocate 56 bytes of shared memory ('pool feed', 'unknown object', 'pool feed', 'set the allocation callback')

  04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")"
  // *Cause:  More shared memory is needed than was allocated in the shared
  //          pool.
  // *Action: If the shared pool is out of memory, either use the
  //          DBMS_SHARED_POOL package to pin large packages,
  //          reduce your use of shared memory, or increase the amount of
  //          available shared memory by increasing the value of the
  //          initialization parameters SHARED_POOL_RESERVED_SIZE and
  //          SHARED_POOL_SIZE.
  //          If the large pool is out of memory, increase the initialization
  //          parameter LARGE_POOL_SIZE.  
  

  Stream uses system global area (SGA) memory to store the information required to capture and apply. To allocate memory from the SGA for use by water courses, establish a flow pool in the SGA by specifying the STREAMS_POOL_SIZE parameter. The default value for this setting is 0, which means that the stream instead uses the shared pool memory. If you leave the STREAMS_POOL_SIZE to its default value (0), water courses will be considering using up to 10 percent of the SHARED_POOL_SIZE, then Oracle recommends at least 200 MB for the STREAMS_POOL_SIZE parameter. The source and destination databases must take account of this memory in the SGA.

  Published by: sb92075 on June 18, 2010 19:17

• 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

• 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

• ORA-25408: can not read the appeal during a duplicate backup with rman catalog database safely

  Hello

  I did a database duplicate backup with rman catalog connection and got the ORA-25408: cannot read error call safely.

  The catalog database is running in a Data Guard environment.

  During the double process database failover occurred because of a server restart.

  The restore of the data files was successful:

  RMAN-08023: channel t1: restored the backup part 1

  RMAN-08180: channel t1: restoration complete, duration: 00:01:15

  RMAN-03091: finished the restoration at 27.08.2014 09:27:10

  During execution of script memory:

  RMAN-08161: content of the Script from memory:

  {

  switch from clone datafile;

  }

  RMAN-08162: execution of Script memory

  I got this error:

  RMAN-08162: execution of Script memory

  RMAN-08031: output channel: t1

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of Db in dual at 27/08/2014 09:27:10

  RMAN-05501: abandonment of duplicate target database

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06004: ORACLE recovery catalog database error: ORA-25408: cannot read safely call

  Dual boot time: 16:00

  Failover time: 18:00

  Error time: 09:00 the next day

  DB version: 11.2.0.4.0, not the RAC environment, single instances

  That's happened? My My db catalog rman session did not survive? Why the error happened at 09:00 (and not 17:00)? Why the session called the catalog rman during switching of the data files?

  Can someone explain it to me?

  Thank you!

  Hello

  The connection of the RMAN catalog remains inactive during the backup/restore process, once rman completes the task and try to activate the connection it gets error.

  What is expected as you said the rebooted server. If this happens because of the expiration time, we went with the parameter net expire_time to maintain the connection.

  Thank you

  Bigot

• RMAN catalog by default for all databases of the value

  Hello

  I run a catalog RMAN 11 GR 1 material.

  I wonder if it is possible to change a default setting in the RMAN catalog so that he will inherit all new databases.

  For example, I would that all new data entered in the catalog for:

  BACKUP OPTIMIZATION

  REDUNDANCY 7 RETENTION STRATEGY

  Thank you

  Massi

  No, the catalogue cannot "dictate" configurations for databases.  Each database maintains configuration in the controlfile and this can be changed that by rman connection (i.e. rman connection to the database target). The command SETS in rman is used to define a "permanent" for a database configuration parameter but must be issued individually for each database.

  Hemant K Collette

• Moving the RMAN catalog

  Hello
  My question concerns the RMAN catalog. A few months ago we moved from solaris zones linux servers. A new catalog of recovery was created on linux servers (same name as the catalog of recovery on solaris zones). There are a few databases that couldn't be moved on the linux server and I would like to re - run databases on solaris zones to use the linux RMAN catalog. Should what steps I follow? Thank you.
  
  J

  A new catalog of recovery was created on linux servers (same name as the catalog of recovery on solaris zones).

  Since its new catalogue, then you will need to register your database in this catalogue and use this database schema name while making the connection to this rman catalog.

• How to save a database to use the RMAN catalog using the OEM 11 g grid

  How to save a database to use the RMAN catalog using the OEM 11 g grid?
  
  ---------------------------------------------------------------------
  Enterprise Manager Version: 11.2.0.2

  See the availability tab, and then click 'Recovery catalog settings' under the Backup/Restore Configuration.

  Choose the option 'Use Recovery Catalog'. Click the 'Add Recovery Catalog' button to add the recovery catalog. And fill required fields like username, host, port, sid, etc..

  Talip Hakan Öztürk
  http://taliphakanozturken.WordPress.com/

• connect to the RMAN catalog

  Hello
  10 g R2 on AIX. I want to backup using RMAn in a shell script:

  rman catalog rman/password@rmanrepo  target /

  How can I avoid the password:
  RMAN/Password@rmanrepo
  
  Thank you.

  The connection information in a batch file and ensure that only a privileged user (normally the 'oracle' user) has read/write access to this file.

  Batch file:

  trigger the echo;
  @ connect catalog rman/password @ target;
  echo setting
  
       
  $ rman cmdfile

  Werner