oracle redundant configuration archive

--创建本地归档目录
[oracle@XLJ181 admin]$ mkdir -p /u01/app/oracle/archive2
[oracle@XLJ181 admin]$ mkdir -p /u01/app/oracle/archive3
--配置log_archive_dest_n参数
SYS@cams> alter system set log_archive_duplex_dest='';
  
System altered.
  
SYS@cams> alter system set log_archive_dest='';
  
System altered.
  
SYS@cams> alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST';
  
System altered.
  
SYS@cams> ALTER System SET LOG_ARCHIVE_DEST_2 = ' LOCATION = / u01 / App / Oracle / as archive2 ' ; 
  
. The System Altered 
  
the SYS @ CAMS > ALTER System SET LOG_ARCHIVE_DEST_3 = ' LOCATION = / u01 / App / Oracle / archive3 ' ; 
  
. The System Altered 
note counter empty order to avoid errors following 

the SYS @ CAMS > System ALTER SET LOG_ARCHIVE_DEST = '' ; 
ALTER System SET LOG_ARCHIVE_DEST = '' 
* 
eRROR AT Line . 1 : 
ORA - 02097 : Parameter CAN BE Not Modified Because specified value iS invalid
ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is
non-NULL
需要将LOG_ARCHIVE_DEST和LOG_ARCHIVE_DUPLEX_DEST参数置空,以免出现如下问题:

SYS@cams> alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST';
alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16019 : CAN not use LOG_ARCHIVE_DEST_1 with the LOG_ARCHIVE_DEST or 
LOG_ARCHIVE_DUPLEX_DEST
 - switch log, archive log write trigger 
SYS @ CAMS > the ALTER System Switch logfile; 
  
System the Altered. 
View archived log files generated new, apparently consistent with the newly generated archive size and file name. Two mutually redundant archive logs. 

[Oracle @ XLJ181 ADMIN] $ LL / u01 / App / Oracle / as archive2 
Total 5440 is 
-rw-R & lt ----- . 1 Oracle the oinstall 4,416,512 On Dec 18 is  . 19 : 09 1_27_994950965.dbf
 -rw-R & lt ----- . 1 Oracle oinstall 1,148,416 Dec 18  19 : 231_28_994950965.dbf 
[Oracle @ XLJ181 ADMIN] $ LL / u01 / App / Oracle / archive3 
Total 5440 is 
-rw-R & lt ----- . 1 Oracle the oinstall 4416512 On Dec 18 is  . 19 : 09 1_27_994950965.dbf
 -rw-R & lt ---- - 1 the Oracle oinstall 1148416 Dec 18  19 : 23 1_28_994950965.dbf 
view the trace log, you see an error message, suggesting DB_RECOVERY_FILE_DEST not set value 

Tue Dec 18  19 : 23 : 59  2018 
errors in File / u01 / App / the Oracle / diag / the RDBMS / cams / cams / trace /cams_arc3_29341.trc:
ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
Errors in file /u01/app/oracle/diag/rdbms/cams/cams/trace/cams_arc3_29341.trc:
ORA-16032: parameter LOG_ARCHIVE_DEST_1 destination string cannot be translated
ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
Archived Log entry 25 added for thread 1 sequence 28 ID 0x9e3b45f3 dest 2 : 
Archived the Log entry 26 is added for Thread . 1 Sequence 28 ID 0x9e3b45f3 dest . 3 : 
is DB_RECOVERY_FILE_DEST parameters values, hand-over log 

the SYS @ CAMS > ALTER System SET DB_RECOVERY_FILE_DEST = ' / u01 / App / Oracle / fast_recovery_area ' ;               
  
the System Altered. 
  
The SYS @ CAMS > the ALTER System Switch logfile; 
  
. the Altered System 
  
SYS @ CAMS > the ALTER System Switch logfile; 
  
. the Altered System 
view trace log, you can see at the same time last written three archive path 

Tue Dec18 19:27:58 2018
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
   then disabled.
**********************************************************
ALTER SYSTEM SET db_recovery_file_dest='/u01/app/oracle/fast_recovery_area' SCOPE=BOTH;
Tue Dec 18 19:27:58 2018
db_recovery_file_dest_size of 10240 MB is 5.63% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Dec 18 19:28:01 2018
Thread 1 cannot allocate new log, sequence 30
Private strand flush not complete
  Current log# 2 seq# 29 mem# 0: /u01/app/oracle/oradata/cams/redo02.log
Thread 1 advanced to log sequence 30 (LGWR switch)
  Current log# 3 seq# 30 mem# 0: /u01/app/oracle/oradata/cams/redo03.log
Tue Dec 18 19:28:01 2018
Archived Log entry 27 added for thread 1 sequence 29 ID 0x9e3b45f3 dest 2:
Archived Log entry 28 added for thread 1 sequence 29 ID 0x9e3b45f3 dest 3:
Tue Dec 18 19:33:38 2018
Thread 1 cannot allocate new log, sequence 31
Private strand flush not complete
  Current log# 3 seq# 30 mem# 0: /u01/app/oracle/oradata/cams/redo03.log
Thread 1 advanced to log sequence 31 (LGWR switch)
  Current log# 1 seq# 31 mem# 0: /u01/app/oracle/oradata/cams/redo01.log
Tue Dec 18 19:33:39 2018
Expanded controlfile section 11 from 28 to 62 records
Requested to grow by 34 records; added 2 blocks of records
Archived Log entry 29 added for thread 1 sequence 30 ID 0x9e3b45f3 dest 1:
Archived Log entry 30 added for thread 1 sequence 30 ID 0x9e3b45f3 dest 2:
Archived Log entry 31 added for thread 1 sequence 30ID 0x9e3b45f3 3 :

 

Guess you like

Origin www.cnblogs.com/dayu-liu/p/11424331.html