Snapshot controlfile enqueue wait.

Similar Questions

• Error when I configure snapshot controlfile RMAN

  Dear Experts,

  I have Oracle 11 g R2 DB primary and Standby in two Machines

  I have Window Server 2008

  I am new to RMAN tools

  I do set up RMAN primary side

  I made the OS address for a disk primary side

  Now I'm RMAN configuration as below:

  Configure default device the disk type;

  set up the device type disk parallelism 4 type of backup backupset.

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK to 'Z:\RmanControlFileBackup\cf%F ';

  Configure controlfile autobackup on;

  Configure controlfile autobackup peripheral type disc format to "+ FRA;

  Configure controlfile autobackup format for device type sbt to "backup_ % d_controlfile_ %f."

  Configure redundancy 4 retention strategy;

  Configure the None archivelog deletion policy;

  Configure snapshot controlfile name to 'Z:\RMANCONTROLFILEBACKUP\SNAPSHOT_EPPROD1_CF. CTL';

  Next, I get the following error... I don't know how I can delete that I did my research online, I found this link

  http://pavelermakov.WordPress.com/2011/11/08/ora-01580-error-creating-control-backup-file/

  RUN SYS. DBMS_BACKUP_RESTORE. CFILESETSNAPSHOTNAME('/U01/app/Oracle/product/11.2/DB/DBS/snapcf_db1. F') ;

  I could not implemented on my setup because I do not have snapcf_db1.f file... Please any help will be appreciated.

  anyone with any solution.

  I need to erase the last transactional... .configure the controlfile Snap to 'Z:\RMANCONTROLFILEBACKUP\SNAPSHOT_EPPROD1_CF. CTL' name; who make that mistake.

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of the command configure at 19/12/2013 08:44:57

  RMAN-03014: implicit recovery catalog Resync failed

  RMAN-03009: resync command failed complete default channel at 19/12/2013 08:44:57

  ORA-01580: Z:\RMANCONTROLFILEBACKUP\SNAPSHOT_EPPROD1_CF. CTL control backup file creation error

  ORA-27040: create file error, cannot create the file

  04002 - OSD: could not open the file

  S/O-error: (OS 3) the system cannot find the path specified.

  Hello

  > RMAN-03002: failure of the command configure at 19/12/2013 08:44:57

  > Implicit 03014 RMAN recovery catalog Resync failed:

  > RMAN-03009: resync command failed complete default channel at 19/12/2013 08:44:57

  "DO NOT CONNECT TO THE CATALOG.

  Thank you

• change snapshot controlfile name

  We use CARS.

  When I try to display the place of location of snapshot controlfile to catalog database and the target (as a sys) in a locaton shared the instance to help

  RMAN > configure snapshot controlfile name to ' / oracle/test_flash/ASYST/backupset/p1/snapcf_ASYST.f';

  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command configure at 01/09/2013 02:23:12
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-03009: resync command failed full to the default channel to 01/09/2013 02:23:12
  ORA-01580: error creating control file backup /f37back/oradata/flash_recovery_area/EDBT/backupset/p1/snapcf_EDBT.f
  ORA-27040: create file error, cannot create the file
  Linux-x86_64 error: 2: no such file or directory

  But when I connect to the target system database and run the below, the location of the controlfile bud

  
  Sys@ASYST1 > RUN SYS. DBMS_BACKUP_RESTORE. CFILESETSNAPSHOTNAME('/Oracle/test_flash/ASYST/backupset/P1/snapcf_ASYST.) F') ;

  PL/SQL procedure successfully completed.

  What is the difference between the two?

  It seems that the * supported * the RMAN command line method tries to create the snapshot controlfile while the * not taken in charge * the PLSQL API method does not attempt to do so.

  Who do you prefer to use, one that is taken in charge or one that is not documented, not supported?

  Hemant K Collette

• ORA-00230: forbidden operation: snapshot controls unavailable file enqueue

  Hello

  Get this error for a while now.

  From control file and SPFILE Autobackup 3 November 2014 06:05:11

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

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

  RMAN-03009: failure of command of file control and SPFILE Autobackup on channel ORA_DISK_1 at 03/11/2014 07:08:13

  ORA-00230: forbidden operation: snapshot controls unavailable file enqueue

  Complete recovery manager.

  ------------------------------------------------------------------------------

  Recovery Manager: release 11.2.0.3.0 - Production on Mon 3 Nov 07:08:17 2014

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

  connected to target database: EMDEV (DBID = 1134683784) connected to the recovery catalog database

  RMAN > RMAN > catalog resync;

  2 > 2 >

  waiting for snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting for the snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting snapshot control file enqueue waiting for the snapshot control file enqueue can't do a snapshot control file

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03009: failure of command resync to the default channel to 03/11/2014 08:11:19

  ORA-00230: forbidden operation: snapshot controls unavailable file enqueue

  Tried to watch what may now be the queue:

  PROGRAM MODULE ACTION Logon ADDR KADDR TY ID1 ID2 LMODE SID SID ASKS CTIME BLOCK user

  141 SYS rman@hq4dr015343 (TNS V1 - V3) rman@hq4dr015343 FINISHED67 (TNS V1 - V3) 0000003 8 October 14 000000015FCD83E0 000000015FCD8438 141 0 2 4 0 2280088 FC 0

  but he said it's OVER. Any suggestions?

  I have reset:

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  TO

  CONFIGURE CONTROLFILE AUTOBACKUP

  and then once again changed it back to:

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  Test ran backups and they ran fine.

• Controlfile on ASM performance issue

  See the Controlfile Enqueue performance tips, review are to go the separator control file diskgroup(need outage)? or add a disc (different LUN, (I prefer this approach) in the same disk group, seems to slow down disc boxes for that matter...)
  
  
  2nd question: snapshot controlfile can be placed on the storage of the ASM?

  The following can help:
  -Separate control to an another diskgroup file can make things even worse in case that the total number of discs is not in the new disk group.
  -Those who control claim file questions are usually nothing to do with storage throughput you have, but the number of operations that require different levels of exclusion on the control files.
  -Given that several copies of controlfiles are updated at the same time a possible, sometimes, it's the secondary copy of controlfile is slower than the other. Please check that this is not the question (different storage levels can cause such problems)

  Kind regards
  Hüsnü Sensoy

• Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

  Here's my question after tons of research and test without have the right solutions.

  Target:

  (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

  (2) I created physical standby database "stbydb" on the server "node2".

  (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

  (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

  (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

  (6) I do RMAN backup (database and archivelog) on the site of relief only.

  (7) I want to use this backup for full restore of the database on the primary database.

  He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

  Here is how to save, on the database pending:

  (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

  (2) RMAN > backup database;

  (3) RMAN > backup archivelog all;

  I got elements of backup and copied to primary db Server something like:

  /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

  /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

  /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

  So here's how to restore, on the main site:

  I clean all the files (data files, controlfiles oder all gone).

  (1) restore spfile from pfile

  RMAN > startup nomount

  RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  (2) modify pfile to convert to db primary content. pFile shows below

  *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

  * .audit_trail = "db".

  * full = '12.1.0.2.0'

  *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

  * .db_block_size = 8192

  * .db_domain = "

  *.db_file_name_convert='/testdb/','/testdb /'

  * .db_name = "testdb".

  * .db_recovery_file_dest ='/ orafra'

  * .db_recovery_file_dest_size = 10737418240

  * .db_unique_name = "testdb".

  *.diagnostic_dest='/opt/Oracle/DB '

  * .fal_server = "stbydb".

  * .log_archive_config = 'dg_config = (testdb, stbydb)'

  * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

  * .log_archive_dest_state_2 = 'ENABLE '.

  *.log_file_name_convert='/testdb/','/testdb /'

  * .memory_target = 1800 m

  * .open_cursors = 300

  * runoff = 300

  * .remote_login_passwordfile = "EXCLUSIVE."

  * .standby_file_management = "AUTO".

  * .undo_tablespace = "UNDOTBS1.

  (3) restart db with updated file pfile

  SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

  SQLPLUS > the judgment

  SQLPLUS > startup nomount

  (4) restore controlfile

  RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  RMAN > change the editing of the database

  (5) all elements of backup catalog

  RMAN > catalog starts by ' / home/oracle/backupset / '.

  (6) restore and recover the database

  RMAN > restore database;

  RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

  (7) open resetlogs

  RMAN > alter database open resetlogs;

  Everything seems perfect, except one of the file log roll forward pending is not generated

  SQL > select * from v$ standby_log;

  ERROR:

  ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

  ORA-27037: unable to get file status

  Linux-x86_64 error: 2: no such file or directory

  Additional information: 3

  no selected line

  I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

  So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

  And I got the same missing log file.

  The problem is:

  (1) complete alert.log filled with this error, not the concern here

  (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

  (3) I can't delete and re-create this log file

  Then I tried several and found:

  The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

  For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

  ---------- ---------- ---------- ----------

  4 19 ACTIVE 133632

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  So until I take the backup, I tried on the primary database:

  SQL > alter system set log_archive_dest_state_2 = delay;

  This was the Group of standby_log side Eve #4 was released:

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

  ---------- ---------- ---------- ----------

  4 0 0 UNASSIGNED

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  Then, the backup has been restored correctly without missing standby logfile.

  However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

  Finally, my real questions come:

  (1) what I do may not do on parameter change?

  (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

  I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

  And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

  I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

  Your idea is very much appreciated.

  Thank you!

  Hello

  1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

  2nd--> when we opened the ORL database should be deleted and created

  3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

  DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

  THREAD # SEQUENCE # GROUP # STATUS

  ---------- ---------- ---------- ----------

  1 233 4 ACTIVE

  1 238 5 ACTIVE

  DR sys@cdb01 SQL > select * from v$ logfile;

  GROUP # STATUS TYPE MEMBER IS_ CON_ID

  ---------- ------- ------- ------------------------------ --- ----------

  3 /u03/cdb01/cdb01/redo03.log no. 0 online

  /U03/cdb01/cdb01/redo02.log no. 0 2 online

  1 /u03/cdb01/cdb01/redo01.log no. 0 online

  4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

  /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

  DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

  DR sys@cdb01 SQL > alter database force claire logfile 4;

  change the database group claire logfile 4

  *

  ERROR on line 1:

  ORA-01156: recovery or current flashback may need access to files

  DR sys@cdb01 SQL > alter database recover managed standby database cancel;

  Database altered.

  DR sys@cdb01 SQL > change the database group claire logfile 4;

  Database altered.

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

  DR sys@cdb01 SQL >

  If you do, you can recreate the controlfile without waiting for redo log entry...

  If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

  Thank you

• strange error with configure snapshot controlfie

  If I put the path snapshot controlfile to the db name hardcoded in the path, it works:

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / var/backup/IDB00246/snapcf_%d.f';

  From control file and SPFILE Autobackup 10 December 14
  room handle=/var/backup/IDB00246/controlc-2380395869-20141210-05.ctl comment = NONE
  Control finished and Autobackup SPFILE file to 10 December 14

  RMAN >

  Complete recovery manager.

  But if I put the path using %d, he doesn't seem to like it:

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / var/backup/%d/snapcf_%d.f';

  From control file and SPFILE Autobackup 10 December 14
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of command of file control and SPFILE Autobackup on channel ORA_DISK_1 at 15:07:40 10/12/2014
  ORA-01580: error creating control file backup /var/backup/%d/snapcf_%d.f
  ORA-27040: create file error, cannot create the file
  Linux-x86_64 error: 2: no such file or directory
  Additional information: 1

  RMAN >

  Complete recovery manager.

  I can use %d for these two orders with no problems:

  FORMAT 1 CONFIGURE CHANNEL DEVICE TYPE DISK MAXOPENFILES ' / var/backup/%d/dumps%d_%T_s%s_p%p.bus';

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / var/backup/%d/control%F.ctl';

  Then why can't it be used for snapshot controlfile?

  On the snapshot Controlfile: when RMAN must resynchronize the catalog of recovery with a consistent read version of the control file, it creates a TEMPORARY snapshot control file. RMAN needs a snapshot control file when the resynchronization with recovery catalog or before you perform a backup of the current control file.

  Why you should use variables in a temporary file internal?

  RMAN does not have a snapshot unique to each backup file, RMAN automatically overwrites the file if it exists. You can use the same file and location all the time, for example ' / u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_dborcl.f'

  If I put the path snapshot controlfile to the db name hardcoded in the path, it works:

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / var/backup/IDB00246/snapcf_%d.f';

  You have this file "snapcf_%d.f" not "snapcf_IDB00246.f" in "/ var/backup/IDB00246 / ', because 'CONFIGURE SNAPSHOT CONTROLFILE NAME' does not support variables.

  You must create a file snapshot controlfile name unique for each database.

• backup of controlfile to 11g

  Hello

  11 g (11.2.0.3) are automatically saved controlfiles?

  If so where are they stored?

  Thank you.

  Thank you.

  We have:

  CONFIGURE CONTROLFILE AUTOBACKUP

  And:

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' L:\ORACLE\PRODUCT\11.2.0\... SNCFMYDB. ORA'; # by default

  This means that a snapshot of the control file is done? Then it can risk an Ora-600 [900]?

  ===============================Doc ID 1442397.1================

  ORA-00600: internal error code, arguments: [2103], [0], [0], [1], [900], [], [], [] while the backup control file.

  Solution

  • Set the hidden according to _CONTROLFILE_ENQUEUE_TIMEOUT > 900.

  ========================End of Doc=======================

  We had this accident last Saturday and want to be sure if he came when you perform the snapshot (about the same time).

  Thank you and best regards.

• ORA-15001 and ORA-15204 when I try to configure the snapshot to controfile name

  Hi all
  
  I create a backup to a new db script.
  
  After registry dthe db in the catalog, I tried a full backup, but otherwise, I read that the snapshot controlfile is under $ORACLE_HOME/dbs in a single node of the rac environment.
  
  I'm trying to change, in order
  
  RMAN > CONFIGURE SNAPSHOT CONTROLFILE NAME to "+ RECO_II01/DBASSET/CONTROLFILE/snapcf_ASSE1.f";
  I get the message:
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the command configure at 27/12/2012 12:31:41
  RMAN-03014: implicit recovery catalog Resync failed
  RMAN-03009: resync command failed full to the default channel to the 27/12/2012 12:31:41
  ORA-01580: error creating control file backup +RECO_II01/dbasset/controlfile/snapcf_.f
  ORA-17502: ksfdcre:3 cannot create the +RECO_II01/dbasset/controlfile/snapcf_.f file
  ORA-15001: diskgroup 'RECO_II01' does not exist or is not mounted
  ORA-15204: version 11.2.0.0.0 of the database is not compatible with diskgroup RECO_II01
  
  When I try to go back to the default, I get the same error.
  
  Do you have any suggestions to fix?

  Try with the compatible version database identical to the compatible version of ASM diskgroup.

  This isn't a question of RMAN it's a configuration problem.

• ALTER database open resetlog with ora-01666: controlfile is in standby

  I have a problem after I have restore / recovered a backup of the source.
  
  On the target, restoration/recovery all finished successfully, but change open resetlog of database with the following errors:
  
  ORA-01666.
  
  My steps are:
  
  (1) make a backup as follows on the source (which is a prod before) complete
  Configure controlfile autobackup on;
  Configure snapshot controlfile name to ' / oracle_backup/rman/snapf.f'
  BACKUP OF DATABASE TAG 'FULL '.
  (2) CPC backupsets above the target
  (3) in rman, set the dbid as the dbid of source, restored the snapf.f and then added the location.
  (4) then restore, recover (everything is fine).
  (5) when I alter database open resetlogs, it gives me error ora-01666.
  (6) change the database open worked, but the PB is now in sleep mode and readonly.
  
  I checked the settings, the dbname points to the dbname in source and db_unique_name point test on the target name. These two parameters have been reset by RMAN Duplicate.
  
  We do not want a standby db, we need a test copied from the sourc.e environment
  
  How should I proceed from here?
  
  Thank you

  Hello again;

  And there is the problem, the only file of control is a watch. Compare your this example of mine:

  BS Key Type LV Size Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  4170117 Full 9.70M DISK 00:00:03 29-NOV-12
          BP Key: 4170119 Status: AVAILABLE Compressed: NO Tag: TAG20121129T125327
          Piece Name: /u01/oradata/RECOVER2_cold/control_RECOVER2_2821_20121129.bak
  Control File Included: Ckp SCN: 1307992402301 Ckp time: 29-NOV-12
  
  BS Key Type LV Size Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  4170127 Full 9.73M DISK 00:00:01 29-NOV-12
          BP Key: 4170129 Status: AVAILABLE Compressed: NO Tag: TAG20121129T125332
          Piece Name: /u01/app/oracle/flash_recovery_area/RECOVER2/autobackup/2012_11_29/o1_mf_s_800628756_8chcsf10_.bkp
  Control File Included: Ckp SCN: 1307992402301 Ckp time: 29-NOV-12
  

  Note the version of ".bak" auto backup and y.

  I think you need to take another backup. If you use Oracle 11 I have even more options.

  For example, I update my test system using this:

  http://www.Visi.com/~mseberg/RMAN/diff_database_duplicating.html

  Sometimes I save on users, roles etc and replace later to hide.

  Subsequently

  You may be able to save what you have by creating a trace on the source file and then use it to re-create a control on the copy file.

  If you run a backup trace command daily you can probably pull some SQL from your daily trace file like this.
  
  CREATE CONTROLFILE REUSE DATABASE "RECOVER2" NORESETLOGS  NOARCHIVELOG
      MAXLOGFILES 16
      MAXLOGMEMBERS 3
      MAXDATAFILES 100
      MAXINSTANCES 8
      MAXLOGHISTORY 292
  LOGFILE
  ...
  ...
  

  You can save as say cf.sql, then:

  SQL> startup nomount 
  
  Run the SQL as shown above
  
  SQL> @cf.sql
  
  Control file created.
  
  SQL>
  
  Check the status of the database
  
  SQL> select status from v$instance;
  
  -- should be mounted
  
  If the database is mounted, can it be opened?
  
  Open the database
  
  SQL> alter database open;
  
  Database altered.
  

  Best regards

  mseberg

  Published by: mseberg on November 29, 2012 19:10

• backup controlfile

  Hello world!
  
  I have a very dull question.
  
  My oracle is always full due to my controlfile record.
  
  I have to remove them, and I think that they are not buy useful, I'm not sure.
  
  I daily make a backup with this rman script:
  
  Run {}
  assign the channel c1 type disc format ' / oraclebck/backup_%d_set%s_piece%p_%T_%U';
  backup of database filesperset 1;
  backup current controlfile;
  backup ARCHIVELOG all delete them all entries;
  output channel c1;
  }
  
  
  which makes the controlfile backup in the backup piece, isn't?
  
  I have it configured in rman
  
  
  RMAN > show all.
  
  RMAN configuration parameters are:
  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / backup/ora_df%t_s%s_s%p';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / casa/oracle/product/9.2/dbs/snapcf_adaiasrv.f'; # by default
  
  Can I configure CONTROLFILE AUTOBACKUP off, since I make a backup of controlfile with rman?
  
  Thank you

  Controlfile autobackup can vary.
  or alternatively, you can change the location of the setting below
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  importance: -.
  RMAN can be configured to automatically back up the control file and the server settings file every time that metadata from database structure in control of changes in the file and each time a backup folder is added. Automatic backup RMAN can recover data even if the current control file, catalog and server parameter file are lost.
  Because the file name for the backup uses a well known format, RMAN can get without access to a repository and restore the server settings file. After you start the instance with the restored server settings file, RMAN can restore a backup control file. Once you mount the control file, the RMAN Repository is available and RMAN can restore the data files and find that the archived redo log.

• Restore the snapshot control file

  Hello
  
  The following configuration will create the snapshot control file as RMAN.
  
  CONFIGURE SNAPSHOT CONTROLFILE NAME to 'product/10.2.0/dbs/snapcf_PROD.f '; # by default
  
  My question is how to restore the control file of this snapshot to another location.
  
  Concerning
  Krishna

  VV of Krishna wrote:
  Hello

  The following configuration will create the snapshot control file as RMAN.

  CONFIGURE SNAPSHOT CONTROLFILE NAME to 'product/10.2.0/dbs/snapcf_PROD.f '; # by default

  My question is how to restore the control file of this snapshot to another location.

  Concerning
  Krishna

  HI. You actually mingle a few questions. You cannot restore controlfile from this snapshot controlfile. Snapshot controlfile goal being the other. At the resynchronization with recovery catalog RMAN must snapshot controlfile. That means and this purpose. You can restore controlfile from automatic backup or backup (controlfile) compatible.

• Update BACKUPSET to USB

  Hi Experts:
  
  My RMAN setting are as follows:
  
  
  Database with db_unique_name ORCL RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  CONFIGURE BACKUP OPTIMIZATION
  SET UP DEFAULT DISK DEVICE TYPE;
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / media/disk/UATRMAN/ora_cf%F';
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE;
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / media/disk/UATRMAN/ora_df%t_s%s_s%p';
  CONFIGURE MAXSETSIZE TO UNLIMITED;
  CONFIGURE THE DATABASE ENCRYPTION
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128";
  CONFIGURE COMPRESSION ALGORITHM 'BZIP2 ';
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oracle/product/11.1.0/db_1/dbs/snapcf_orcl.f';
  
  
  My Script is for Rman is:
  
  Run
  {
  allocate channel c1 device type disk;
  allocate channel c2 device type disk;
  allocated channel c3 device type disk;
  allocate channel c4 device type disk;
  database backup incremental level 0;
  cross-checking of backup;
  overlap backupset;
  delete noprompt obsolete;
  output channel c1;
  output channel c2.
  output channel c3.
  output channel c4.
  }
  Exit;
  
  Problem I'm facing is that the backup runs at 20.00 hours every night my flash recovery area is 30 GB which is complete in
  BACKUPSET in flash recover space & don't have much room Everthing HD internally is not in my/Media... except BACKUPSET!
  How can I move this folder my "/ media/disk/UATRMAN/blah_blah_blah.
  
  Please guide
  Thank you

  Hello;

  You can take backup on USB, but it will be very slow. A local hard disk will be much faster.

  You will see backup RMAN to wait events if you are using USB.

  Check:

  RMAN-06900, backup RMAN-06901 and ORA-03135 of errors on a disk [604494.1 ID] USB device

  If possible configure RMAN directly talk to Ribbon.

  You can make this change, but you will probably want to cancel it shortly after.

  Best regards

  mseberg

• Catalogue of how?

  Hello
  10 g R2 on Win 2003,.
  How many catalog may exist in an RMAN repository database?
  How to know the number of those that exist today?
  Thank you.

  Dear user522961,

  As far as I know there may be more than one, but it is important to manage the snapshot controlfile queue problem.

  ORA-00230:
       operation disallowed: snapshot control file enqueue unavailable
  Cause:      The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
  Action:      Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.
  

  http://ORA-00230.ora-code.com/

  When you are about to do a job on the target database when you are connected to the recovery catalog database, it starts a full resynchronization of the catalog. You can also do it manually by typing;

  RMAN> resync catalog;
  

  If you want to do a treatment with several repositories of catalog at the same time, you should be careful with that one.

  You can find the answer to your question here;

  http://download.Oracle.com/docs/CD/B14117_01/server.101/B10734/rcmrepos.htm

  +"+
  * + Check of multiple databases in a recovery catalog + *.

  + You can register multiple target databases in a single recovery catalog, if they did not have a dbid in doubles. RMAN uses the DBID to distinguish one database from another. +

  + In general, if you use the RMAN DUPLICATE command or the CREATE DATABASE SQL statement, the created database is assigned a unique DBID. If you create a database by other means, for example a copy maintained by users, the new database can have the DBID as well as which it was copied. You will not be able to save the two databases in the same recovery catalog until you change the DBID of the database copied using the DBNEWID utility. +

  * + Note that you can save a single target database in multiple recovery catalogs. + *
  +"+

• RMAN-20033 control file sequence # too low & ORA-00230

  The two RMAN below errors occasionally I think that the cause is if an archive backup is running during a database backup, the controlfile is supported by both and can (but not always) cause these errors. The backup of the database is generally successful and that's just the backup controlfile who complains. I looked at how to avoid this, but it is not easy. Some backups of large database, especially for a full backup, run it for hours so archives have yet to be backed up and deleted.
  
  It might have started when ON CONFIGURE CONTROLFILE AUTOBACKUP has been set up. I don't know if this can be changed for backups of archive without affecting full/comú backups. Any ideas are appreciated.
  
  
  From control file and SPFILE Autobackup July 23, 10
  handful of piece = c-3756288473-20100723-2nd comment = 2.0, MMS Version 5.4.1.0 API Version
  File control finished and Autobackup SPFILE to July 23, 10
  output channel: T1
  output channel: T2
  output channel: T3
  output channel: T4
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03008: error when executing automatic resynchronization of the recovery catalog
  RMAN-20033: control file sequence # too low
  
  
  From backup 6 August 10
  channel T1: starting full datafile backupset
  channel T1: specifying datafile (s) in backupset
  output channel: T1
  output channel: T2
  output channel: T3
  output channel: T4
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on channel T1 at 2010-08-06 11:43:52
  ORA-00230: forbidden operation: snapshot controls unavailable file enqueue

  Dear DBA2008,

  Please find the explanation of the error first;

  ORA-00230: operation disallowed: snapshot control file enqueue unavailable
  Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
  Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates. 
  

  There could be an enqueu for the snapshot controlfile and he should be released in order to continue operating.

  The other mistake is;

  Oracle Error :: RMAN-20033
  control file SEQUENCE# too low
  
  Cause
  the control file sequence is less than the one of the previous resync
  
  Action
  make sure that the right control file is used
  

  Thus, there could be another session which was try to resynchronize the catalog or simply access the snapshot controlfile.

  Can you connect please for the usual recovery with the connection string manager and type;

  RESYNC CATALOG;
  

  Do you still take the enqueue snapshot controlfile error?

  Hope that helps.

  Ogan