Log_archive_dest & fra

Similar Questions

• Double LOG_ARCHIVE_DEST places. One is FRA the other is regular ASM no disc. Cleaning question

  Double LOG_ARCHIVE_DEST places. One is FRA the other is regular ASM no disc.

  Oracle does not recommend manually delete logs archiving of the FRA, but rather let the FRA cleaning place based on archive political log deletion and backup retention policy, which works perfectly, but now that we have newspapers archive mirrored on a location not FRA to clean archives connects to this place with RMAN. How can we clean up the FRA NO cleaning is not the FRA through rman?

  Just use:

  RMAN > BACKUP AS ARCHIVELOG '+ DB_FRA/dborcl/archivelog/%' ENTRY DELETE;

  With the ENTRY to be REMOVED, RMAN only deletes the specific copy of the newspaper of archived recovery chosen for the backup set.

  REMOVE all THE ENTRIES, RMAN deletes each file backed up log redo archived log destinations archiving.

  It backs up from a specific location and delete it after backup.

• Using DB_RECOVERY_FILE_DEST and LOG_ARCHIVE_DEST - error ORA-16019

  Hello
  
  My database is currently configured to write files archivelog on two sites: / u01/app/oracle/archivelogs (which is the log_archive_dest parameter and is ranked number 1) and USE_DB_RECOVERY_FILE_DEST (10), which is
  under/u01/app/oracle/flash_recovery_area. I want to spend the two locations for separate discs.
  
  When I attempt to move or the other, I get the following errors:
  
  
  SQL > ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ' / u03/fra/MYDB/flash_recovery_area "SCOPE = BOTH;
  ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ' / u03/fra/MYDB/flash_recovery_area "SCOPE = BOTH
  *
  ERROR on line 1:
  ORA-02097: the parameter cannot be changed because specified value is not valid
  ORA-16019: cannot use db_recovery_file_dest with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  
  SQL > alter system set log_archive_dest = "/ u02/archive/MYDB";
  ALTER system set log_archive_dest = "/ u02/archive/MYDB '.
  *
  ERROR on line 1:
  ORA-02097: the parameter cannot be changed because specified value is not valid
  ORA-16018: cannot use LOG_ARCHIVE_DEST with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
  
  
  Any ideas?
  
  Thanks for any help.

  cool, finally you got. Thanks for pasting of output.

  Barry K.

• B1k43EA #UUW: Wifi slar fra

  WiFi slar konstant fra i forbindelse med nogle opdateringer therefore den indtil PC en bliver rebootet.

  Stupid WiFi constantly off the coast for some updates the work until the PC restart.

• Question about backup of FRA

  Hi all.

  I use 11g Rel2 and know that there is a command area backup recovery and backup recovery. I have these two questions:

  (1) either of these commands cause a consistent backup? I mean, for the copy of the FRA process, new archiving logs could be created. RMAN all these areas will also backup the destination to spare?. I guess it does, but want to hear expert advice on this.

  (2) could someone provide an example of how restore the FRA to such support?

  Thanks in advance!

  What needs to be "compliant"?  When you save the FRA, you save backups, not the database.

  As for your specific question on the archivelogs, I don't know the exact answer, but I would ask ' what?  What of the archivelog what is written 1 millisecond before the backup ends FRA?  That he is the one who ends 1 millisecond after the backup of the FRA end?

  Suppose you write archivelogs in a regular journal 1 / minute (which in itself is a problem, but for the sake of the current issue, in fact a practical number).

  Now suppose that, today, your FRA backup takes 5 minutes.

  Now assume that the behavior is that the backup of the FRA does not get the archivelogs written after the beginning of the backup.  OK, the 5 archivelogs get backed up the next time.

  Next day, because of the overload of system or something else, your FRA backup takes 2 minutes.  And the next day, 10 minutes.  So what?

  Now, repeat above with the assumption that the backup FRA gets all archivelogs that are carried out before the end of the backup of the FRA.

  This is not saving this time, next time will get saved.

• Management of the backups don't FRA not catalog

  Hi all

  I do backups RMAN in my database pending.

  I do not set up catalog FRA or rman.

  If I put a rman policy in my primary CONFIGURE ARCHIVELOG DELETION policy to APPLY ON ALL STANDBY;

  Archive logs are automatically removed or should I run an rman command to delete them?

  So if I understand correctly, in my first if I have political value to configure archivelog deletion apply pending all the

  the command delete archivelog all will remove them all the records that have been applied to all relief.

  Yes

  If I run the command delete obsolete and the retention policy is set UP RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS;

  It will remove the archives more than 3 days

  In this case, he would check for both conditions - retention and deletion policy policy. If the two conditions to hold good, so only archive will be deleted from the primary. Moreover, if archive has not been applied to the wait since the last 3 days (retention period), then you can imagine that you have a huge gap in the standby database.

  -Jonathan Rolland

• Because of the archivelogs had places in + FRA diskgroup

  Dear Sir.

  Because of the archivelogs had places in + FRA diskgroup

  Thanks in advance,

  IVW

  The quick recovery area is a directory managed by Oracle. Once configured, RMAN would use FRA as the default location for files backup and restore RMAN. Archivelogs and files of RMAN backup effective additional 1 used for the restoration of the database.

  Archivelogs do not need to be stored in FRA and you can specify a different location, but there are several advantages, for example, RMAN automatically identify and find the backup and restore files stored in FRA.

• Backup RMAN when FRA is configured

  I configured on a db Flash recovery area 11.2.0.4;  I want RMAN full backup to a different location of FRA.

  I ran the full backup of rman with specified format...

  backup in the database format compressed more archivelog backupset ' / backup/BKPD15/%U';

  I see, some files will FRA and a few other small files are there in /backup/BKPD15 location as well.

  
  

  What is the right way to take backup to any location of fra.
  

  Hello

  1. According to my knowledge, you must use two format, since the format applies to only backup of database archives goes for fra (see demo below)

  Demo:

  SYS@demo1 December 27, 15 > db_rec setting sho

  VALUE OF TYPE NAME

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

  db_recovery_file_dest string/u04/temp_data/demo1

  whole large db_recovery_file_dest_size 10G

  db_recycle_cache_size large integer 0

  [oracle@host1 test_backup] $ pwd

  u04 / / test_backup

  [oracle@host1 test_backup] $ ls - tl

  Total 0

  VALUE OF TYPE NAME

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

  db_recovery_file_dest string/u04/temp_data/demo1

  whole large db_recovery_file_dest_size 10G

  db_recycle_cache_size large integer 0

  [oracle@host1 test_backup] $ pwd

  u04 / / test_backup

  [oracle@host1 test_backup] $ ls - tl

  Total 0

  RMAN > backup as database format compressed more archivelog backupset ' / u04/test_backup/%U';

  From December 27, 15 backup

  Current archived log

  using channel ORA_DISK_1

  channel ORA_DISK_1: starting compressed archived log backup set

  channel ORA_DISK_1: specifying the newspapers archived in the backup set

  archived journal thread = 1 = 3 sequence entry RECID = STAMP 3 = 899558724

  channel ORA_DISK_1: from room 1 to 27 December 15

  channel ORA_DISK_1: finished piece 1 to December 27, 15

  total, handle = / u04/test_backup/01qpsba4_1_1 tag = TAG20151227T132524 comment = NONE - location no fra

  channel ORA_DISK_1: complete set of backups, time: 00:00:01

  Backup over at December 27, 15

  From December 27, 15 backup

  using channel ORA_DISK_1

  channel ORA_DISK_1: from complete compressed datafile backup set

  channel ORA_DISK_1: specifying datafile (s) in the backup set

  Enter a number of file datafile = 00005 name=/u02/demo1/oradata/demo1/example01.dbf

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/mssm_tbs.dbf 00002

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/assm_tbs.dbf 00007

  Enter a number of file datafile = 00001 name=/u02/demo1/oradata/demo1/system01.dbf

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/sysaux01.dbf 00003

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/undotbs01.dbf 00004

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/users01.dbf 00006

  channel ORA_DISK_1: from room 1 to 27 December 15

  channel ORA_DISK_1: finished piece 1 to December 27, 15

  piece handle=/u04/temp_data/demo1/DEMO1/backupset/2015_12_27/o1_mf_nnndf_TAG20151227T132526_c7z6cgf1_.bkp tag = TAG20151227T132526 comment = NONE - fra position control file

  channel ORA_DISK_1: complete set of backups, time: 00:01:05

  channel ORA_DISK_1: from complete compressed datafile backup set

  channel ORA_DISK_1: specifying datafile (s) in the backup set

  including the current control in the backup set file

  including current SPFILE in the backup set

  channel ORA_DISK_1: from room 1 to 27 December 15

  channel ORA_DISK_1: finished piece 1 to December 27, 15

  piece handle=/u04/temp_data/demo1/DEMO1/backupset/2015_12_27/o1_mf_ncsnf_TAG20151227T132526_c7z6fjyk_.bkp tag = TAG20151227T132526 comment = NONE - fra location spfile

  channel ORA_DISK_1: complete set of backups, time: 00:00:02

  Backup over at December 27, 15

  From December 27, 15 backup

  Current archived log

  using channel ORA_DISK_1

  channel ORA_DISK_1: starting compressed archived log backup set

  channel ORA_DISK_1: specifying the newspapers archived in the backup set

  archived journal thread = 1 = 4 sequence entry RECID = STAMP 4 = 899558794

  channel ORA_DISK_1: from room 1 to 27 December 15

  channel ORA_DISK_1: finished piece 1 to December 27, 15

  total, handle = / u04/test_backup/04qpsbca_1_1 tag = TAG20151227T132634 comment = NONE - location no fra

  channel ORA_DISK_1: complete set of backups, time: 00:00:01

  Backup over at December 27, 15

  channel ORA_DISK_1: complete set of backups, time: 00:00:02

  Backup over at December 27, 15

  From December 27, 15 backup

  Current archived log

  using channel ORA_DISK_1

  channel ORA_DISK_1: starting compressed archived log backup set

  channel ORA_DISK_1: specifying the newspapers archived in the backup set

  archived journal thread = 1 = 4 sequence entry RECID = STAMP 4 = 899558794

  channel ORA_DISK_1: from room 1 to 27 December 15

  channel ORA_DISK_1: finished piece 1 to December 27, 15

  total, handle = / u04/test_backup/04qpsbca_1_1 tag = comment TAG20151227T132634 = NONE

  channel ORA_DISK_1: complete set of backups, time: 00:00:01

  Backup over at December 27, 15

  Correct way:

  RMAN > run {}

  2 > allocate channel backup_disk1 type disk;

  3 > backup format COMPRESSED BACKUPSET DATABASE TAG 'DB' ' / u04/test_backup/%U.db'

  4 > format PLUS ARCHIVELOG ' / u04/test_backup/%U.arc';

  {5 >}

  output channel: ORA_DISK_1

  allocated channel: backup_disk1

  channel backup_disk1: SID = 48 type device = DISK

  From December 27, 15 backup

  Current archived log

  channel backup_disk1: compressed boot archived log backup set

  channel backup_disk1: specifying the newspapers archived in the backup set

  archived journal thread = 1 = 3 sequence entry RECID = STAMP 3 = 899558724

  archived journal thread = 1 = 4 sequence entry RECID = STAMP 4 = 899558794

  archived journal entry thread = 1 sequence = RECID 5 = 5 STAMP = 899559573

  channel backup_disk1: from room 1 to 27 December 15

  channel backup_disk1: finished piece 1 to December 27, 15

  piece handle=/u04/test_backup/05qpsc4l_1_1.arc tag = TAG20151227T133933 comment = NONE

  channel backup_disk1: complete set of backups, time: 00:00:01

  Backup over at December 27, 15

  From December 27, 15 backup

  channel backup_disk1: from complete compressed datafile backup set

  channel backup_disk1: specifying datafile (s) in the backup set

  Enter a number of file datafile = 00005 name=/u02/demo1/oradata/demo1/example01.dbf

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/mssm_tbs.dbf 00002

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/assm_tbs.dbf 00007

  Enter a number of file datafile = 00001 name=/u02/demo1/oradata/demo1/system01.dbf

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/sysaux01.dbf 00003

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/undotbs01.dbf 00004

  Enter a number of file datafile = name=/u02/demo1/oradata/demo1/users01.dbf 00006

  channel backup_disk1: from room 1 to 27 December 15

  channel backup_disk1: finished piece 1 to December 27, 15

  piece handle=/u04/test_backup/06qpsc4m_1_1.db tag = comment DB = NONE

  channel backup_disk1: complete set of backups, time: 00:00:55

  channel backup_disk1: from complete compressed datafile backup set

  channel backup_disk1: specifying datafile (s) in the backup set

  including the current control in the backup set file

  including current SPFILE in the backup set

  channel backup_disk1: from room 1 to 27 December 15

  channel backup_disk1: finished piece 1 to December 27, 15

  piece handle=/u04/test_backup/07qpsc6d_1_1.db tag = comment DB = NONE

  channel backup_disk1: complete set of backups, time: 00:00:01

  Backup over at December 27, 15

  From December 27, 15 backup

  Current archived log

  channel backup_disk1: compressed boot archived log backup set

  channel backup_disk1: specifying the newspapers archived in the backup set

  archived journal entry thread = 1 sequence = RECID 6 = 6 STAMP = 899559632

  channel backup_disk1: from room 1 to 27 December 15

  channel backup_disk1: finished piece 1 to December 27, 15

  piece handle=/u04/test_backup/08qpsc6g_1_1.arc tag = TAG20151227T134032 comment = NONE

  channel backup_disk1: complete set of backups, time: 00:00:01

  Backup over at December 27, 15

  output channel: backup_disk1

  RMAN >

  RMAN > list backupset;

  List of backup sets

  ===================

  Time of accomplishment time BS key size Device Type

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

  5.89 5 M DISK 00:00:00 DECEMBER 27, 15

  BP key: 5 location: AVAILABLE Tablet: YES Tag: TAG20151227T133933

  Part name: /u04/test_backup/05qpsc4l_1_1.arc

  List of newspapers archived on backup the value 5

  The next time that THRD Seq YVERT low low time next YVERT

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

  1 3 2871101 DECEMBER 27, 15 2875107 27 DECEMBER 15

  1 4 2875107 27 DECEMBER 15 2875234 27 DECEMBER 15

  1 5 2875234 27 DECEMBER 15 2875749 27 DECEMBER 15

  Time of accomplishment BS key Type LV size device Type elapsed time

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

  6 integer M DISK 00:00:55 360,54 27 December 15

  BP key: 6 location: AVAILABLE Tablet: YES Tag: DB

  Part name: /u04/test_backup/06qpsc4m_1_1.db

  List of files of backup data the value 6

  Name of file LV Type cash SNA cash time

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

  2875757 full 1 /u02/demo1/oradata/demo1/system01.dbf December 27, 15

  2 full 2875757 /u02/demo1/oradata/demo1/mssm_tbs.dbf 27 December 15

  3 full 2875757 /u02/demo1/oradata/demo1/sysaux01.dbf 27 December 15

  4 integer 2875757 /u02/demo1/oradata/demo1/undotbs01.dbf 27 December 15

  5 integer 2875757 /u02/demo1/oradata/demo1/example01.dbf 27 December 15

  6 integer 2875757 /u02/demo1/oradata/demo1/users01.dbf 27 December 15

  7 full 2875757 /u02/demo1/oradata/demo1/assm_tbs.dbf 27 December 15

  Time of accomplishment BS key Type LV size device Type elapsed time

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

  7 full 1.03 M DISK 00:00:02 27 December 15

  BP key: 7 location: AVAILABLE Tablet: YES Tag: DB

  Part name: /u04/test_backup/07qpsc6d_1_1.db

  SPFILE included: Change Date: 27 December 15

  SPFILE db_unique_name: DEMO1

  Control file included: cash SNA: 2875780 cash time: 27 December 15

  Time of accomplishment time BS key size Device Type

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

  13.50 8 K DISK 00:00:00 DECEMBER 27, 15

  BP key: situation 8: AVAILABLE Tablet: YES Tag: TAG20151227T134032

  Part name: /u04/test_backup/08qpsc6g_1_1.arc

  List of newspapers archived in backup set of 8

  The next time that THRD Seq YVERT low low time next YVERT

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

  1 6 2875749 DECEMBER 27, 15 2875786 27 DECEMBER 15

  It may be useful

  -Pavan Kumar N

• Window 2 day using FRA more than expected recovery.

  Hello, can someone please help me understand why my 2 day recovery window uses a lot more space FRA than I expected.

  Here is some basic information.

  Oracle 11g R2

  Windows 2008R2

  The database size = 16.77 GB

  I have my FRA

  Newspaper archives = 10.5 GB (approximately 2-3GBs daily)

  Backupset = 1.63 GB (500MB per day)

  Control file = 16.3 MB

  Copy of image DB 13.7 GB

  Journal online = 30MB

  I use the Oracle out of the box back up strategy

  Run {}

  allocate channels oem_disk_backup device type of disk.

  retrieve the copy of the database with the tag "ORA_OEM_LEVEL_0".

  extra strength 1 cumulative backup copies = 1 to retrieve the copy with the tag database 'ORA_OEM_LEVEL_0 ';

  }

  FRA my height is 60 GB.

  I do not perform backups on tape (which RMAN knows)

  Everything is on disk.

  I expect at some point that Oracle will review files outside of my window of recovery to be recoverable, but I am struggling to figure out when.

  Now, if I put a window of recovery of 1 day (it's the current setting). It builds up to about 23 GB then it will start to have recoverable files. If I put a 2 day recovery window, it will consume all of 60GB and ends up falling. Why a 2 day recovery window is to consume as much space (more than double)?

  I know that everything is on the disk and maybe that's my problem. In my scenario when oracle would consider to be recoverable files?

  I thank very you much for your time.

  Hello again;

  on "oracle considers the files to be recovered.

  The only answer I have ever seen on this is when "Oracle feels the pressure of space", rather vague.

  Be careful when you use the window of recovery that you put it high enough to cover yourself.

  Worth the trip:

  Hemant Oracle DBA blog: understand the Obsolescence of RMAN backups

  Best regards

  mseberg

• Question of space FRA

  Hallo,

  I had ORA-00257: archiver error. Connect internal only, until this just released. (DBD ERROR: OCISessionBegin) in our Test database.

  I understand that this has to do with the space of the FRA. I've removed all expired backups and archivelogs with RMAN. When I check using the FRA use the query below
  

  
  

  Select * from v$ recovery_file_dest;
  

  
  

  NAME	SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES SPACE_LIMIT

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

  / db04/Oracle/flash_recovery_area

  9, 6637E + 11 2, 9091E + 12

  0

  41

  I guess it's very clear that I have space in FRA, but again the archivelogs cannot be copied and I get the error in the alert.log below.

  ORA-19815: WARNING: 966367641600 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.

  Could someone help me on this please?

  Thank you very much. I got it today. I assumed that when I change place FRA I have to give the size of the new location only which is false.

• DBCA SHOWING NO DATA AND FRA... Help, please?

  Hi, I was trying the new installation of Oracle 11 g. Executing command (DBCA), to the DATA CONFIGURATION WIZARD, step 6 of 12: location of the database files. In the database box, I click to BROSE BUTTON but it does not show DATA or FRA. You will find the attached screenshot for more clear.

  

  PROBLEM WAS SOLVED... because we know that /dev/raw / * must contain the ORACLE as USER AND OINSTALL as a GROUP in order to distribute the ASM for DATA and FRA... No ONE including ME REMARQUERAIT the USER AND GROUP that I presented above. I am again submitting the above information here as well, or you can check the same information [root@example dev] # ls - ld/dev/raw / * of the above. So this is what the user and group was before. Because to show DATA AND FRA drive to the title of the ASM, the/dev/RAW/expected to be under ORACLE as USER AND OINSTALL as GROUP but before /dev/raw / * was under ROOT as USER and DRIVE as a GROUP and because of this it was not showing the DATA and FRA assigned disk while using the DBCA COMMAND

  [root@example dev] # ls - ld/dev/raw / *.

  CRW - rw-. 1 root disk 162, 1 Jan 29 21:29 / dev/raw/raw1

  CRW - rw-. 1 root disk 162, 2 Jan 29 21:29 / dev/raw/raw2

  CRW - rw-. 1 root disk 162, 3 Jan 29 21:29 / dev/raw/raw3

  CRW - rw-. 1 root disk 162, 4 Jan 29 21:29 / dev/raw/raw4

  CRW - rw-. 1 root disk 162, 5 Jan 29 21:29 / dev/raw/raw5

  CRW - rw-. 1 root disk 162, 6 Jan 29 21:29 / dev/raw/raw6

  CRW - rw-. 1 oracle oinstall 162, 0 Jan 29 21:29 / dev/raw/rawctl

  THE MAIN PROBLEM in MY CASE WAS ON AFTER, if you give OR type chown-r oracle: oinstall/dev/raw, chmod 770/dev/raw, chmod 660/dev/raw/raw * MANUALLY then it will display the correct GROUPS and USERS

  [root@example Desktop] # chown r oracle: oinstall/dev/raw

  [root@example Desktop] # chmod 770/dev/raw

  [root@example Desktop] # chmod 660/dev/raw/raw *.

  [root@example Desktop] # ls - ld/dev/raw / *.

  CRW - rw-. 1 oracle oinstall 162, 1 Jan 30 09:35 / dev/raw/raw1

  CRW - rw-. 1 oracle oinstall 162, 2 Jan 30 09:35 / dev/raw/raw2

  CRW - rw-. 1 oracle oinstall 162, 3 Jan 30 09:35 / dev/raw/raw3

  CRW - rw-. 1 oracle oinstall 162, 4 Jan 30 09:35 / dev/raw/raw4

  CRW - rw-. 1 oracle oinstall 162, 5 Jan 30 09:35 / dev/raw/raw5

  CRW - rw-. 1 oracle oinstall 162, 6. Jan 30 09:35 / dev/raw/raw6

  CRW - rw-. 1 oracle oinstall 162, 0 Jan 30 09:16 / dev/raw/rawctl

  [root@example Desktop] #.

  WHILE

  If you the same things chown-r oracle: oinstall/dev/raw, chmod 770/dev/raw, chmod 660/dev/raw/raw * in /etc/rc.d/rc.local then it shows USERS and DRIVE as root and disc.

  [root@example ~] vi /etc/rc.d/rc.local

  ! / bin/sh

  #

  # This script will be executed * after * all the other init scripts.

  # You can put your own stuff of initialization here if you do not

  # want to do the full Sys V style init stuff.

  touch/var/lock/subsys/local

  / dev/raw/raw1 gross/dev/sda11

  / dev/raw/raw2 gross/dev/sda12

  / dev/raw/raw3 gross/dev/sda13

  / dev/raw/raw4 gross/dev/sda14

  / dev/raw/raw5 gross/dev/sda15

  / dev/raw/raw6 gross/dev/sda16

  chown-r oracle: oinstall/dev/raw

  chmod 770/dev/raw

  chmod 660/dev/raw/raw *.

  [root@example dev] # reboot or refresh

  AFTER THEN AGAIN if YOU CHECK the USER AND the GROUP using ls - ld/dev/raw / * then his root watch and the disk commands as the user and group. It shows the root and the disc where it should be ORACLE and OINSTALL under USERS and GROUPS. I couldn't find the reason why even after put chown-r oracle: oinstall/dev/raw, chmod 770/dev/raw, chmod 660/dev/raw/raw * shows the wrong USER AND GROUP?

  [root@example dev] # ls - ld/dev/raw / *.

  CRW - rw-. 1 root disk 162, 1 Jan 29 21:29 / dev/raw/raw1

  CRW - rw-. 1 root disk 162, 2 Jan 29 21:29 / dev/raw/raw2

  CRW - rw-. 1 root disk 162, 3 Jan 29 21:29 / dev/raw/raw3

  CRW - rw-. 1 root disk 162, 4 Jan 29 21:29 / dev/raw/raw4

  CRW - rw-. 1 root disk 162, 5 Jan 29 21:29 / dev/raw/raw5

  CRW - rw-. 1 root disk 162, 6 Jan 29 21:29 / dev/raw/raw6

  CRW - rw-. 1 oracle oinstall 162, 0 Jan 29 21:29 / dev/raw/rawctl

  SO HERE'S WHAT I DID... THE SOLUTION WORKING for me is that I created the shell script file named test.sh.

  STEP 1: CREATE the SHELL SCRIPT FILE test.sh

  [root@example Desktop] # cat /root/test.sh

  chown-r oracle: oinstall/dev/raw

  chmod 770/dev/raw

  chmod 660/dev/raw/raw *.

  STEP 2: Place rc.local file test.sh

  [root@example ~] vi /etc/rc.d/rc.local

  ! / bin/sh

  #

  # This script will be executed * after * all the other init scripts.

  # You can put your own stuff of initialization here if you do not

  # want to do the full Sys V style init stuff.

  touch/var/lock/subsys/local

  / dev/raw/raw1 gross/dev/sda11

  / dev/raw/raw2 gross/dev/sda12

  / dev/raw/raw3 gross/dev/sda13

  / dev/raw/raw4 gross/dev/sda14

  / dev/raw/raw5 gross/dev/sda15

  / dev/raw/raw6 gross/dev/sda16

  /root/test.sh

  STEP 3: REFRESH rc.local or you can RESTART the pc once more

  [root@example Desktop] # /etc/rc.d/rc.local

  STEP 4: CHECK the USERS and GROUPS as mentioned below: -.

  [root@example Desktop] # ls - ld/dev/raw / *.

  CRW - rw-. 1 oracle oinstall 162, 1 Jan 30 09:35 / dev/raw/raw1

  CRW - rw-. 1 oracle oinstall 162, 2 Jan 30 09:35 / dev/raw/raw2

  CRW - rw-. 1 oracle oinstall 162, 3 Jan 30 09:35 / dev/raw/raw3

  CRW - rw-. 1 oracle oinstall 162, 4 Jan 30 09:35 / dev/raw/raw4

  CRW - rw-. 1 oracle oinstall 162, 5 Jan 30 09:35 / dev/raw/raw5

  CRW - rw-. 1 oracle oinstall 162, 6. Jan 30 09:35 / dev/raw/raw6

  CRW - rw-. 1 oracle oinstall 162, 0 Jan 30 09:16 / dev/raw/rawctl

  [root@example Desktop] #.

  asmca $ [grid@example Desktop]

  

  DATA AND FRA PROBLEM SOLVED

• FRA full and cannot connect to rman

  Hello

  I have on my FRA database at 100%, I try to connect to the rman delete archivelog (all met before ' sysdate-1' "). But the connection is not established, the prompt is not displayed

  When I try to sqlplus system / *-> ORA-00257: archiver error. Connect internal only, until that releases.

  When I cancel rman I have this error:

  Recovery Manager: release 11.2.0.4.0 - Production Wed 27 Aug 10:42:16 2014

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

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-00554: initialization of the package manager internal collection failed

  RMAN-06003: target ORACLE database error:

  ORA-00604: an error has occurred at the SQL level 1 recursive

  ORA-01013: user has requested the cancellation of the current operation

  ORA-06508: PL/SQL: called program unit is not found: 'SYS. DBMS_RCVMAN ".

  ORA-06512: at line 1

  How can I remove the old archivelog to clean an ETF.

  Best regards

  Just

  Thank you for your update, I increase db_recovery_file_dest_size. It has solved my problem.

• Issue of FRA

  I have a question to FRA.  I get "alerts" when my db_recovery_file_dest_size was 85% and I get a critical when alert my it reached 95%.  This database has a retainer

  4 day window.  IE CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 4 DAYS;  My nightly backups are about 20.8 GB.  My db_recovery_file_dest_size is located at 150 GB.  I can see from my

  Enterprise Manager as 6 days ago from backups stored on the disk.  I understand that FRA pushes the backups and auto cleans itself.

  What I don't understand is why is he alert me and also I think with the script below the amount of recoverable space would not 0.   I could increase my FRA but I think that

  I'd eventually get the same question, because it does not grow on older backups until they need to free up space.  I guess I could disable the alert but then if I did not really

  a question that I will not be informed.  Any ideas?

  My 6 disk 20.82 + 20.77 + 20.77 + 20.77 + 20,79 + 20.78 backup = 124.71

  My flashback zone is 2.5 GB

  My archive logs is 96

  My AutoSave folder is 160 MB

  NAME LIMIT_GB USED_GB RECLAIM_GB PAS_DE_FICHIER

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

  / oRA2/fra 150,0 127,2.0 60

  COL name FORMAT A20

  COL limit_gb FORMAT 9,999.9

  COL used_gb FORMAT 9,999.9

  COL reclaim_gb FORMAT 9,999.9

  SELECT name,

  space_limit/1024/1024/1024 limit_gb

  space_used/1024/1024/1024 used_gb,

  reclaim_gb space_reclaimable/1024/1024/1024,

  NUMBER_OF_FILES pas_de_fichier

  V $ recovery_file_dest

  Hello

  You can use delete noprompt obsolete in your backup script, it will remove the backups that are not necessary.

  Kind regards
  Ivica

• File system for FRA and external backups

  Oracle 11g R2.

  The FRA drive is formatted using Linux x 83 put on Diskgroup + FRA system.

  Backups are stored outside on an ext3 file system.

  Suppose now the database gets completely crashed and I need to recover by continuing external backups.  I will copy the external backups to the + FRA disk and then perform the recovery from there.

  My question is, given that external backups are on ext3 file system, while the FRA is the Oracle ASM filesystem, there will be a problem for the use of the file systems of the two difference?

  Thank you

  Scott

  scottjhn wrote:

  To summarize the issue:

  In my system, the database will be on ASM disk group + DATA (disk1 disk2).

  I will use another disk, disk3 (ext3 file system) for FRA, to organize data files backups and multiplexed logs (archive logs, online newspapers and control files).

  Earlier you said "I'll use the + FRA (ASM disk group) for the fast recovery area that holds that archiving multiplexed logs, recovery online logs, and control files.»  Nothing else. »

  Now, I need one more place to hold the copy of the multiplexed logs.

  Wouldn't not on the same + (ABOVE)?  Alternatively, use a disk full-fledged, disk4 (ext3 file system)?

  Thank you

  Scott

  First of all, the reason for multiplexing online redo logs and control files is not the same as that of multiplexing archivelogs. Do it online and the control file are actually a part of the database.  The database will not work without them.  This is why it is so important to have multiplex.  Archivelogs, on the other hand, are part of your backup strategy.  The database itself really doesn't care if you have any archivelogs at all.  The archivelogs multiplexing is much less common.  I have never multiplexed mine, but I do not have a task that runs every hour to copy any newly created on a server off-site.

  If your database is on ASM, at least a control file and a member of each group of redo log must be in ASM.  Technically, is not having to be, but it's really foolish not to do so.  Where to put the second copy?  Probably several schools of thought on this.  If your FRA is on ext3, so it seems a simple decision... a FRA copy, a copy in its default location in ASM.

• FRA, Journal multiplexing and request emergency

  Oracle 11g R2 under 64-bit Linux.  ASM for data files.   I have several questions regarding the backup process:

  For the backup and the multiplexing of newspaper, I intend to use the following method to save the data file, online newspapers, archive redo logs and control files (I deliberately put back on two different file system, i.e., one on the raw disk (file system managed by Oracle) and the other as cooks it filesystem ext3 (System)) :

  1, put disc in shape like the raw disk for FRA (for data files, online newspapers, archived redo logs and control files)

  Disc 2 to the regular file system format, that is, the ext3 file system (for the multiplexing of online newspapers, archived redo logs and control files).

  My understanding is that at the time of execution, the RMAN automatically backups data file, control files, online redo logs and newspapers archived on FRA drive.

  (1) for the online redo logs, I believe that it is saved to the FRA and multiplxed in continuous and simultaneous mode to keep data in sync with it again connects to the CMS, right?

  (2) for the data file, backups RMAN for the FRA at some point.  What might be at this time?  02:00 every day or any time I can specify?

  (3) for remote backup.  I use the OEM to schedule a backup, say, increatmental in week and a full backup on weekends.  Where will the data come from?  The disc of FRA? or the ASM disks?

  Thank you

  Scott

  scottjhn wrote:

  I think my confusion of the concept of automated backup came here (with the exception of the doc):

  For all installations, you must choose the storage option that you want to use for the Oracle database files. If you want to enable backups automated installation, you must also choose the storage option that you want to use for recovery files (the area of fast recovery).

  
  

  So I thought that if I have activated the automatic backups, Oracle automatically back to the FRA.  Now, I understand that I must manually adjust upward (via OEM/RMAN) in order to achieve the "'automatic backups". "

  Another thing is on the online redo log backup.

  There is no backup of the recovery online newspapers - that's why it is strongly advised you the multiplex.

  We know the redo logs are written in alternating.  Once the online journal are full, they are moved to archive (known as archived redo logs).

  The redologs online are not moved anywhere.  They are copied to archive the redo logs.

  Now suppose a synario, while online redo logs are loaded into the overall area of the system.

  This is the second time that you referenced online redo logs as being in the SGA.  No, they are never in the SGA.  Where are you that?  Log buffers are in the LMS, but this is not the same as the files

  and being written on, the system gets crashed.  This online redo log should be stored somewhere,

  Yes, they must be stored somewhere.  And somewhere on the disk, exactly to the place specified when the redo log group has been defined.  MEMBER SELECT FROM V$ LOGFILE to see.

  If not, when do the recovery lateron, information will be missing.

  What information do you think will be absent?  Your transaction is not completed, command does not return to you, until the BONE confirmed to oracle changed data wrote in the redologs online - located on the disk.

  For what I understand, it is that while online newspapers are written to execution, at the same time, they are multiplxed to other places, asssume I have already the dest locations, such as the FIU or/u01/oradata/onlinelogs.  This way, when do the lateron of recovery, it will be: data files, control files, archive logs + line newspapers.   But I don't know that I'm right?

  No, you are not right.  You're confusing instance recovery (aka crash recovery) with recovery of the media database.  Spend time in the manual of Concepts and use the index to find all references to 'redo '.  Read especially the section on the recovery of body and keep firmly in mind that instance recovery is not the recovery of database.

  Thank you

  Scott