then consider changing RMAN ARCHIVELOG DELETION POLICY. 2.

Bac up files to tertiary device such as tape using RMAN 2. Bac up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. BACKUP RECOVERY AREA command. 3. Add dis space and increase db_recovery_file_dest_size parameter to 3. Add dis space and increase db_recovery_file_dest_size parameter to reflect the new space. reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. DELETE EXPIRED commands. ************************************************************************ ************************************************************************ Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc1_ 2151.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 38639616 bytes dis space from 4070572032 limit Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc2_ 2153.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 46556160 bytes dis space from 4070572032 limit ARC1: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_a rea/VICLINUX/archivelog/2010_06_28/o1_mf_1_317_%u_.arc' ARC2: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_a rea/VICLINUX/archivelog/2010_06_28/o1_mf_1_316_%u_.arc' ARCH: Archival stopped, error occurred. Will continue retrying ORACLE Instance viclinux - Archival Error ORA-16038: log 1 sequence# 316 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/viclinux/redo01.log' Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc2_ 2153.trc: ORA-16038: log 1 sequence# 316 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/viclinux/redo01.log' Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_ora_2 143.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% us ed, and has 0 remaining bytes available. ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Bac up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add dis space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_ora_2 143.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 46556160 bytes dis space from 4070572032 limit ARCH: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_a

rea/VICLINUX/archivelog/2010_06_28/o1_mf_1_316_%u_.arc' Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_ora_2 143.trc: ORA-16038: log 1 sequence# 316 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/viclinux/redo01.log' USER (ospid: 2143): terminating the instance due to error 16038 Instance terminated by USER, pid = 2143 Mon Jun 28 20:26:21 2010 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Pic ed latch-free SCN scheme 3 Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options. Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/db home_1/dbs/spfileviclinux.ora System parameters with non-default values: processes = 150 sga_target = 1488M control_files = "/u01/app/oracle/oradata/viclinux/control01.ctl" control_files = "/u01/app/oracle/flash_recovery_area/viclinux/contr ol02.ctl" db_bloc _size = 8192 compatible = "11.2.0.0.0" db_recovery_file_dest = "/u01/app/oracle/flash_recovery_area" db_recovery_file_dest_size= 3882M undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(protocol=TCP)" shared_servers = 2 local_listener = "LISTENER_VICLINUX" audit_file_dest = "/u01/app/oracle/admin/viclinux/adump" audit_trail = "DB" db_name = "viclinux" open_cursors = 300 pga_aggregate_target = 496M diagnostic_dest = "/u01/app/oracle" Mon Jun 28 20:26:22 2010 PMON started with pid=2, OS id=11518 Mon Jun 28 20:26:22 2010 VKTM started with pid=3, OS id=11520 at elevated priority Mon Jun 28 20:26:22 2010 GEN0 started with pid=4, OS id=11524 Mon Jun 28 20:26:22 2010 DIAG started with pid=5, OS id=11526 VKTM running at (10)millisec precision with DBRM quantum (100)ms Mon Jun 28 20:26:22 2010 DBRM started with pid=6, OS id=11528 Mon Jun 28 20:26:22 2010 PSP0 started with pid=7, OS id=11530 Mon Jun 28 20:26:22 2010

DIA0 started with pid=8, OS id=11532 Mon Jun 28 20:26:22 2010 MMAN started with pid=9, OS id=11534 Mon Jun 28 20:26:22 2010 DBW0 started with pid=10, OS id=11536 Mon Jun 28 20:26:22 2010 LGWR started with pid=11, OS id=11538 Mon Jun 28 20:26:22 2010 CKPT started with pid=12, OS id=11540 Mon Jun 28 20:26:22 2010 SMON started with pid=13, OS id=11542 Mon Jun 28 20:26:22 2010 RECO started with pid=14, OS id=11544 Mon Jun 28 20:26:22 2010 MMON started with pid=15, OS id=11546 starting up 1 dispatcher(s) for networ address '(ADDRESS=(PARTIAL=YES)(PROTOCOL =TCP))'... Mon Jun 28 20:26:22 2010 MMNL started with pid=16, OS id=11548 starting up 2 shared server(s) ... ORACLE_BASE from environment = /u01/app/oracle Mon Jun 28 20:26:23 2010 ALTER DATABASE MOUNT Successful mount of redo thread 1, with mount id 2423932655 Database mounted in Exclusive Mode Lost write protection disabled Completed: ALTER DATABASE MOUNT Mon Jun 28 20:26:28 2010 ALTER DATABASE OPEN LGWR: STARTING ARCH PROCESSES Mon Jun 28 20:26:28 2010 ARC0 started with pid=21, OS id=11562 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES Mon Jun 28 20:26:29 2010 ARC1 started with pid=22, OS id=11565 Mon Jun 28 20:26:29 2010 ARC2 started with pid=23, OS id=11567 ARC1: Archival started ARC2: Archival started ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH ARC2: Becoming the heartbeat ARCH Mon Jun 28 20:26:29 2010 ARC3 started with pid=24, OS id=11569 ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc1_ 11565.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% us ed, and has 0 remaining bytes available. Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc2_ 11567.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% us ed, and has 0 remaining bytes available. ************************************************************************ ************************************************************************ You have following choices to free up space from recovery area: You have following choices to free up space from recovery area:

1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Bac up files to tertiary device such as tape using RMAN 2. Bac up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. BACKUP RECOVERY AREA command. 3. Add dis space and increase db_recovery_file_dest_size parameter to 3. Add dis space and increase db_recovery_file_dest_size parameter to reflect the new space. reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. DELETE EXPIRED commands. ************************************************************************ ************************************************************************ Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc1_ 11565.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 46556160 bytes dis space from 4070572032 limit Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc2_ 11567.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 38639616 bytes dis space from 4070572032 limit ARC1: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_a rea/VICLINUX/archivelog/2010_06_28/o1_mf_1_316_%u_.arc' ARC2: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_a rea/VICLINUX/archivelog/2010_06_28/o1_mf_1_317_%u_.arc' ARCH: Archival stopped, error occurred. Will continue retrying ORACLE Instance viclinux - Archival Error ORA-16038: log 2 sequence# 317 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/viclinux/redo02.log' Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_arc2_ 11567.trc: ORA-16038: log 2 sequence# 317 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/viclinux/redo02.log' Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_ora_1 1560.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 100.00% us ed, and has 0 remaining bytes available. ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Bac up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add dis space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_ora_1 1560.trc:

ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 46556160 bytes dis space from 4070572032 limit ARCH: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_a rea/VICLINUX/archivelog/2010_06_28/o1_mf_1_316_%u_.arc' Errors in file /u01/app/oracle/diag/rdbms/viclinux/viclinux/trace/viclinux_ora_1 1560.trc: ORA-16038: log 1 sequence# 316 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/viclinux/redo01.log' USER (ospid: 11560): terminating the instance due to error 16038 Instance terminated by USER, pid = 11560 oracle@VictorPC:/u01/app/oracle/diag/rdbms/viclinux/viclinux/trace> What is the "default" way to disable archive log mode in a database where archiv e log mode is currently active? Is the easiest way to disable archive log mode to shutdown the database and afte rwards disable archive log mode and than startup the database again ? Answer: The method for disabling archive log mode described above is the only way to dis able archive log mode. Shutdown edit pfile / spfile (spfile when instance is up of course) to say log_a rchive_start = false. startup mount alter database noarchivelog; alter database open; Remember that once you disable archive log mode you need to ta e a fresh bac up once archive log mode is turned bac on. The Oracle documentation says the following about enabling and disabling archive logging in RAC environments: "To enable archive logging in RAC environments, the database must be mounted but not open. Then start RAC in a disabled state. To do this: Disabling Archive log mode: 1. Shut down all instances. 2. Reset the CLUSTER_DATABASE parameter to false on one instance. If you are usi ng the server parameter file, ma e a sid-specific entry for this. 3. Add settings for the LOG_ARCHIVE_DEST_n, LOG_ARCHIVE_FORMAT, and LOG_ARCHIVE_ START parameters to the parameter file. You can multiplex the destination to up to ten locations, and the LOG_ARCHIVE_FORMAT parameter should contain the %t par ameter to include the thread number in the archived log file name. 4. Start up the instance on which you have set CLUSTER_DATABASE to false. 5. Enter the following statement: ALTER DATABASE ARCHIVELOG 6. Shut down the instance.

7. Change the value of the CLUSTER_DATABASE parameter to true. 8. Restart your instances. These steps should allow you to disable archive log mode. To disable archive logging, follow the same steps but use the NOARCHIVELOG claus e of the ALTER DATABASE statement."