Encryption of files to archive log...

Similar Questions

• delete files from archive log with rman

  Hi guys,.

  I try to delete the log file archive on my backup site, but I get the following message. There are a lot of archive logs is present on the storage but rman may show that. No idea what I'm doing wrong here.

  RMAN > list archivelog all;

  specification does not match any newspaper archived in the repository

  RMAN >

  Kind regards

  Sorry about that. Its 11g 2 R (11.2.0.1) and OS Version is 2008 R2 64 bit. Sleep is in auto recovery mode. (hope this helps).

• RMAN > skip the file to archive log < string > already saved 1 time

  I'm trying to copy an Archivelog of ASM to the file system, but I get the following error message.
  
  How can I use the force to do? I can't understand the correct syntex. Please advise!
  

  RMAN> copy archivelog '+FRA/CCPROD/ARCHIVELOG/2011_01_31/thread_1_seq_131491.678.741834671' to '/NEW_backups/backups/thread_1_seq_131491.678.741834671';
  
  Starting backup at 31-JAN-11
  using channel ORA_DISK_1
  skipping archive log file +FRA/ccprod/archivelog/2011_01_31/thread_1_seq_131491.678.741834671; already backed up 1 time(s)
  Finished backup at 31-JAN-11

  Hello

  in RMAN, you have activated OPTIMAZTION as WE

  RMAN > SET UP OPTIMIZATION BACKUP;

  and try your previous order, it should work, if all post errors. Thank you.

• difference between online redolog files and archived log files

  What is the fundamental difference between archived log files and online redo log files? .. .plz keep things simple as m a newbie

  Online redo log:

  Redo online Oracle log files are filled with records of restoration by progression. A record of remake, also called entrance to roll forward, is composed of a group of agents of change, each of which is a description of a change to a single block in the database. Each instance of an Oracle database has an associated online redo log to protect data in case of failure of the instance.

  See here,
  http://download.Oracle.com/docs/CD/B10500_01/server.920/a96521/onlineredo.htm

  Archived redo log:

  Oracle Database allows you to save files to one or more destinations offline newspapers filled with repeat groups, known collectively as the archived redo log. An archived redo log file is a copy of one of the members of a group of redo log filled.

  See here,
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/archredo.htm

  Thank you

• Files to archive Log - 10 g r2

  Is there a database v$ view that stores the location (full path) of the offline archive logs? It's on 10g r2.
  
  Thank you
  Sylvie

  You can check

  Select name from v$ archived_log;

  It is cleared if RMAN deletes the archvie after saving

  Thank you

• Deleting files to archive log

  Hello
  
  I am aware that this command will remove a file, but would like to know it will delete all files from archive since there is a wild character.
  
  / ORA/db999/dbfra34/ARCHIVELOG/2008_03_30 # rm - rf *.arc
  
  Thank you

  Yes, it will delete all files of newspapers of the archives that he finds through .arc files.

  Concerning
  Asif Kabir

• Difference between redo logfiles, Undo Tablespace, Archive log data file

  Can some please highlight the difference between Undo and Redo Logs
  Also why we need to separate the archive logs when the recovery log data can be written directly in data files...
  
  Help you will be highly appreciated...

  Hello

  Ed gave you a very good answer.

  Rememeber database files are online and they are written to by DBWR process. So we have the database files, redo log files and archive logs.
  In order to avoid all the crawl log when you perform a recovery, database performs control points that summarize the State of the database. This operation of control point provides a shortcut to the recovery. At the checkpoint, the database knows that all incorrect pages were written to disk (for example, database files). At the time of recovery, the log (which includes-finished and unfinished transactions) is used to bring the database to a consistent state. The system locates the time of the last checkpoint and returned to this position in the log file. Then he restores forward all completed transactions (read committed) that occurred after the last checkpoint and rolls back all transactions that were not committed, but that began before the last checkpoint. This is where online log files are used.

  Now imagine that you need to back up your database GB 100 + all 10 minutes. It would be a waste of space! So you take a backup of your database at time t and backups of archiver process redo logs periodically to check the newspapers so that redo log files can be replaced and RMAN will use the last backup and archive the log files to recover your database at the time.

  Now, I mentioned the checkpoint process. The Checkpoint process regularly launches a control point that uses DBWR to rewrite all the blocks Sales in the data files, so synchronize the database. Imagine one dam is running and have exhausted all the redo log files. At this point, Oracle will wait until all Sales already queued blocks have been written to the buffer on disk (database files) foremost him redo log files can be considered as superfluous and available for re-use (i.e. can be overwritten). This will result in the following message in the alert.log:

  Thread 1 advanced to log sequence 17973
    Current log# 3 seq# 17973 mem# 0: /oracle/data/HAM1/log3aHAM1.dbf
    Current log# 3 seq# 17973 mem# 1: /oracle/data/HAM1/log3bHAM1.dbf
  Thread 1 cannot allocate new log, sequence 17974
  Checkpoint not complete
    Current log# 3 seq# 17973 mem# 0: /oracle/data/HAM1/log3aHAM1.dbf
    Current log# 3 seq# 17973 mem# 1: /oracle/data/HAM1/log3bHAM1.dbf
  Thread 1 advanced to log sequence 17974
  

  I am sure you have done the following:

  alter database mount;
  
  Database altered.
  

  When you mount a database, Oracle combines the instance started the database. Oracle control files are opened and read. However, no checking such as the restore/recovery is performed

  alter database open;
  
  Database altered.
  

  An open command opens the data files, recovery logs, it performs automatic and consistency of database recovery. At this point, the database is now ready to be used by all valid users.

  HTH,

  Mich

  Published by: Mich Talebzadeh on November 19, 2011 16:57

• Archive log file bloat - is currently out of cold back to the top of the best strategy?

  Hi friends,
  
  I have a database 10 g. / WinSvr2003 making heavy spatial processing of the Oracle.
  
  Previously, I ran the database in log mode archive and sparked a lot of files to archive log. 150 G (the worst week).
  
  I got fed up with backups (incremental) RMAN night heavy and put the database in a mode non - archive journal. (I was also worried about the time to get the data back out of band).
  
  Now, I come to launch the next nightly bat file: -.
  
  oradim-stop-sid DEV - syspwd *.
  
  del /S /Q D:\oracleBackup\DEV\*
  
  XCopy/e D:\oracle\product\10.2.0\oradata\DEV D:\oracleBackup\DEV
  
  oradim-startup-sid DEV - syspwd *.
  
  ----------------------------------------------------------------------------------------------------------
  
  1 week ago - when I arrived-in the morning the database had not restarted due to an inconsistency of data file.
  Recover the database fixed.
  
  I guess he had something that this necessary in the redo log files? (its mode no - archive).
  
  I have a DB 24/7.
  
  This cold offline backup is the best strategy to avoid the bloat of log file archive
  
  I can always use RMAN and do not back up files of newspaper Archives? How can I make sure that it is a consistent RMAN backup if she has no access to archive the log files. (I just use RMAN after an immediate stop - restart?)
  
  How instruct you RMAN is not to get the files to archive log?
  
  DATABASE INCREMENTAL LEVEL 0 BACKUP; <-this leaves archive the log file out of the backup.
  
  Thanks in advance.
  
  See you soon,.
  
  AA
  
  P.S. This is my first post on this forum. Yes!

  If you
  a. make a backup of the database CONSISTENT (that is to say in MOUNT but not OPEN) with RMAN
  b. do not save the ArchiveLogs
  c. yet the ArchiveLogs to create the database in ARCHIVELOG mode,

  You can still use the combination of consistent backup and ArchiveLogs generated since the backup database (assuming that the ArchiveLogs are still on the disk) in the method of 'Refresh '.

  In other words, RESTORE (but not RETRIEVE and OPEN) the database of the RMAN.
  Using sql RESTORE DATABASE with the HELP of BACKUP CONTROLFILE to 'Updating' then apply ArchiveLogs for what is just restored.

  See http://hemantoracledba.blogspot.com/2007/05/rollforward-from-cold-backup.html

  Hemant K Collette

• DataGuard archiving log not applied

  Hello
  
  I met archive log apply errors in the physical standby database. Below are the errors.
  
  
  
  SQL > SELECT SEQUENCE #, FIRST_TIME, NEXT_TIME, APPLIED from V$ ARCHIVED_LOG SEQUENCE ORDER #;
  
  SEQUENCE # FIRST_TIM NEXT_TIME APP
  ---------- --------- --------- ---
  10 24 AUGUST 11 NO. 24 AUG 11
  10 24 AUGUST 11 NO. 24 AUG 11
  11 AUGUST 24, 11 NO. 24 AUG 11
  12 24 AUGUST 11 NO. 25 AUG 11
  13 25 AUGUST 11 NO. 25 AUG 11
  14-25 AUGUST 11 NO. 25 AUG 11
  
  6 selected lines.
  
  SQL > select database_role, open_mode from v$ database;
  
  DATABASE_ROLE OPEN_MODE
  ---------------- ----------
  FIRST READING WRITING
  
  SQL > select message from v$ dataguard_status;
  
  
  ARCs: Started archiving
  CRAT: Started archiving
  CJACBR: become the "no FAL' ARCH
  CJACBR: become the "no SRL" ARCH
  ARCm: Become the heartbeat ARCH
  
  Message
  --------------------------------------------------------------------------------
  Again shipping customer logged in as PUBLIC
  -User is valid
  RFS [1]: assigned to the RFS 3389 process
  RFS [1]: do not use real application clusters
  LGWR: Error 16009 creation archivelog file "DBSOURCE.
  LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
  Again shipping customer logged in as PUBLIC
  -User is valid
  RFS [2]: assigned to the RFS 3393 process
  RFS [2]: do not use real application clusters
  FAL [server, ARCo]: error 16009 file creation remote archivelog 'DBSOURCE.
  
  Message
  --------------------------------------------------------------------------------
  Again shipping customer logged in as PUBLIC
  -User is valid
  RFS [3]: assigned to the RFS 3397 process
  RFS [3]: do not use real application clusters
  Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.
  Again shipping customer logged in as PUBLIC
  -User is valid
  RFS [4]: assigned to the RFS 3429 process
  RFS [4]: do not use real application clusters
  Heartbeat PING [ARCm]: Unable to connect to the eve "DBSOURCE. The error is 16009.
  
  54 selected lines.
  
  
  Of the primary alerts on DB log errors
  Using the default value for the parameter STANDBY_ARCHIVE_DEST as/u01/app/oracle/oradata/DBSOURCE
  Again shipping customer logged in as PUBLIC
  -User is valid
  RFS [1]: assigned to the RFS 3389 process
  RFS [1]: do not use real application clusters
  Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3389.trc file:
  ORA-16009: destination of the journal archive remote must be a database of the EVE
  Game Aug 25 12:17:10 2011
  Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_lns1_3349.trc file:
  ORA-16009: destination of the journal archive remote must be a database of the EVE
  LGWR: Error 16009 creation archivelog file "DBSOURCE.
  LNS: Impossible to archive log 3 thread 1 sequence 15 (16009)
  Game Aug 25 12:17:30 2011
  Again shipping customer logged in as PUBLIC
  -User is valid
  RFS [2]: assigned to the RFS 3393 process
  RFS [2]: do not use real application clusters
  Errors in the /u01/app/oracle/diag/rdbms/dbsource/DBSOURCE/trace/DBSOURCE_rfs_3393.trc file:
  ORA-16009: destination of the journal archive remote must be a database of the EVE
  
  initDBSOURCE.ora params
  DB_NAME = DBSOURCE
  DB_UNIQUE_NAME = DBSOURCE
  LOG_ARCHIVE_CONFIG = 'DG_CONFIG = (DBSOURCE, DBTARGET)'
  LOG_ARCHIVE_DEST_1 =
  "LOCATION = / u01/app/oracle/oradata/DBSOURCE"
  VALID_FOR = (ALL_LOGFILES, ALL_ROLES)
  DB_UNIQUE_NAME = DBSOURCE'
  LOG_ARCHIVE_DEST_2 =
  "SERVICE = DBSOURCE LGWR ASYNC
  VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE)
  DB_UNIQUE_NAME = DBTARGET'
  LOG_ARCHIVE_DEST_STATE_1 = ENABLE
  LOG_ARCHIVE_DEST_STATE_2 = ENABLE
  REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE LOCK
  LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
  LOG_ARCHIVE_MAX_PROCESSES = 30
  
  
  
  I have 1 more question. I copied all db files, control files, and archived logs of the remote db DBTARGET but with the standby control file I could mount the db in the remote server but the dbname is always DBSOURCE instead of DBTARGET.
  
  I tried running NEST to change on the site of relief the dbname but it errored out with
  Copyright (c) 1982, 2007, Oracle. All rights reserved.
  
  Connected to database DBSOURCE (DBID = 977273159)
  
  NEST-00131: control file is not current
  
  
  Change of database name failed during validation - database is intact.
  
  Could if apply the newspaper ceased due to the DBNAME is the same on the eve of primary and physical please help
  
  Edited by: 880215 August 25, 2011 10:02

  dbname is still DBSOURCE instead of DBTARGET
  

  The database must be DBSOURCE on both. It's the same data in two different roles, role PRINCIPAL and ROLE of the day BEFORE.

  Oracle, said by the DB_UNIQUE_NAME parameter.

  What I have is copy the control file before on the basis of pending data down and then copy and rename the control file that are there.

  Does make sense?

  I have some notes here if it helps:

  http://www.Visi.com/~mseberg/data_guard_on_oracle_11_step_by_step.html

  Best regards

  mseberg

• ORA-19504: failed to create the file, ORA-00270: creation of the archiving log error

  Hello
  
  Oracle 11 g 2 on windows 7, I of primary and standby on the same system (learning).
  
  When I check on status of primary and secondary use under request it gives applied log is 'NO '.
  
  SQL > select sequence #, used from v$ archived_log;
  
  SEQUENCE # APPLIED
  ---------- ---------
  516 NO.
  517 NO.
  NO. 523
  NO. 524
  525 NO.
  531 NO.
  NO. 532
  533 NO.
  NO. 541
  544 NO.
  
  When I checked error on DB primary .he give me more erro.
  SQL > SELECT 'ID', 'DB_status' STATUS DEST_ID, EXCURSION place "Archive_dest', 'ERROR' OF V$ ARCHIVE_DEST WHERE DEST_ID < = 5;
  ---------- ---------
  Error Archive_dest
  ------------------------------------------------------------------------------------------------------------------------------------------------------
  1 D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG ORA-19504: cannot create the file «»
  
  2 STAND ORA-00270: creation of the archiving log error
  
  I checked the space on the system... is there enough free space on the disk.
  
  On primary DB (destination of the journal archive)
  
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
  More old sequence of journal online 564
  Log sequence archive 566
  Current log sequence 566
  
  On standby DB (list of newspapers of record)
  
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
  More old sequence of journal online 564
  Log sequence archive 566
  Current log sequence 566
  
  Please guide it's because of the destination of the journal archive even shared by the standby and primary?
  
  If yes how do I change the destination of the newspaper archive on standby DB?
  
  Thank you.
  
  Edited by: 977220 April 18, 2013 20:49

  change initialization parameter

• Arc1: 19504 error creating archive log file... after the NFS configuration

  I use an Oracle 11.2.0.3 on RHEL 5.7 (no ASM or RAC) database
  
  We have our archiving logs off copied to a backup location external via a cron job and rsync command, and I want to switch to NFS.
  

  NAME                         TYPE      VALUE
  ------------------------------------ ----------- ------------------------------
  log_archive_format               string      RCAT_%t_%s_%r.arc
  log_archive_dest_1               string      location=USE_DB_RECOVERY_FILE_DEST
  
  SQL> !df -h
  Filesystem                 Size  Used Avail Use% Mounted on
  ...
  ...
  backups:/ARCHLOG/rman       12T  7.8T  3.5T  70% /mnt/nfs_archlog
  
  SQL> alter system set log_archive_dest_2='LOCATION=/mnt/nfs_archlog optional' scope=both;
  
  System altered.

  When I run 'alter system archive log current', I see the error message archiver in the alert below log...
  

  Wed Aug 29 14:42:08 2012
  ALTER SYSTEM ARCHIVE LOG
  Wed Aug 29 14:42:08 2012
  Thread 1 advanced to log sequence 23044 (LGWR switch)
    Current log# 4 seq# 23044 mem# 0: /u01/oradata/RCAT/redo_4a.dbf
    Current log# 4 seq# 23044 mem# 1: /u02/oradata/RCAT/redo_4b.dbf
  Wed Aug 29 14:42:14 2012
  ARC1: Error 19504 Creating archive log file to '/mnt/nfs_archlog/RCAT_1_23043_602355789.arc'
  Archived Log entry 24282 added for thread 1 sequence 23043 ID 0x165341cd dest 1:

  However, when I check the NFS location I see that the file is there.

  [oracle@rman nfs_archlog]$ ls -la
  total 72
  drwxr-x--- 14 oracle oinstall   4096 Aug 29 14:42 .
  drwxr-xr-x  3 root   root       4096 Aug 29 14:16 ..
  -rw-r-----  1 oracle oinstall 204288 Aug 29 14:42 RCAT_1_23043_602355789.arc

  On the NFS host, I see

  [root@backups archivelog]# ls -la
  total 68
  drwxr-x---. 14 500 500   4096 Aug 29 14:42 .
  drwxrwxr--.  3 500 500   4096 May  8 13:54 ..
  -rw-r-----.  1 500 500 204288 Aug 29 14:42 RCAT_1_23043_602355789.arc

  The/etc/exports on NFS host has the permissions set to read/write, no_root_squash.
  
  Is there something obvious that I'm missing?

  the folder is created by newspaper archive must have atleat authorisation from 770.

• Why archive log file size constantly change?

  I have a question related to the size of the archive log file:
  I constantly receive a different size to the size of the log file archive, of course, they are smaller than to the size of the log file.
  A guru can explain to me: what possible reason could be?
  Thanks in advance!

  It can happen due to several reasons:

  When you perform a manual archive (via ALTER SYSTEM ARCHIVE LOG CURRENT/ALL)
  When Oracle must respect your ARCHIVE_LAG_TARGET (defined in seconds)

  Unless you do a manual check-in, your parameter ARCHIVE_LAG_TARGET is the reason why you see Archives of logs with different sizes as Oracle has archived the redo log as soon as the time ARCHIVE_LAG_TARGET is reached. Even if the redo log is not full, Oracle will always have to archive the redo log.

• Removal of the Archive Log files

  Hello
  
  I put my test DB to archive log mode and it generated 10 GB of archivelog files and the server ran out of space!
  So I reset the newspapers, the DB value no. Archive Log and deleted the files from the server through the shell.
  
  However,.
  If I select * from v$ archived_log
  Oracle, DBMS thinks that the files are still there.
  
  Where can I remove these filed from the RDBMS?
  
  
  ---
  OS version:
  Linux CentOS 5.4 (Final) output
  
  
  RDBMS version:
  Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - production
  PL/SQL Release 10.2.0.4.0 - Production
  "CORE 10.2.0.4.0 Production."
  AMT for Linux: release 10.2.0.4.0 - Production
  NLSRTL Version 10.2.0.4.0 - Production

  delete the logs of the archives at the OS level will not make your database the missing note

  connecting to RMAN:

  rman target $ /.

  run an overlap in RMAN:

  RMAN > overlap archivelog all;

  It happens that the entries are EXPIRED, so remove them:

  RMAN > delete all. expired archivelog

• archive log file count

  How to archive log file created by day in a database? How will I know?
  
  Please make this solution.
  
  Thanks in advance...

  Piku says:
  Sorry to say... can't find anything useful... is available all useful QUERY SQL abt that?

  select * from v$archived_log where COMPLETION_TIME > sysdate -1;
  

  I will give you the number of logs archived in the last 24 hours.

  HTH
  Johan

• Redo archive log file extension

  Version: 11 g
  OPERATING SYSTEM: AIX 5.3
  
  After you have enabled archiving, I noticed that archives logs files have the extension * .dbf. Is this normal?

  close the database and putting into service again.

  Then, check the setting.

  Concerning
  Asif Kabir