ORA-16014: log4sequence # 1notarchived Solution

The following error is reported today when the slave uard slave database starts recover: ORA-16014: log4sequence #1 notarchived, noavailabledestinations solve the following

The following error is reported today when the slave uard slave database starts recover: ORA-16014: log 4 sequence #1 not archived, no available destinations solve the following

The following error is reported when the standby uard standby database starts a recover:
ORA-16014: log 4 sequence #1 not archived, no available destinations

Solution:
First look
SQL> show parameter db_recovery

NAME TYPE VALUE
-----------------------------------------------------------------------------
Db_recovery_file_dest string D: \ Oracle \ product \ 10.2.0/flash
_ Recovery_area
Db_recovery_file_dest_size big integer 2G

SQL> alter system set db_recovery_file_dest_size = 3G scope = both;

The system has been changed.

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

Next we will continue with this idea:
1). Check the usage of flash recovery area:

SQL> select * from v $ flash_recovery_area_usage;

FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
----------------------------------------------------------------------
CONTROLFILE. 33 0 1
ONLINELOG 7.32 0 3
ARCHIVELOG 25.06 0 35
BACKUPPIECE 67.69 0 4
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0

You have selected 6 rows.

. Calculate the space occupied by the flash recovery area:

SQL> select sum (percent_space_used) * 3/100 from v $ flash_recovery_area_usage;

SUM (PERCENT_SPACE_USED) * 3/100
-----------------------------
3.012

As you can see, here we have used GB, which indicates that the db_recovery_file_dest_size = 2 GB which we just set at the beginning cannot archive online redo logs. Here, we set the db_recovery_file_dest_size parameter, increase the flash recovery area to solve this problem.

(3). You can also delete unnecessary backups in the flash recovery area in rman to release the flash recovery area space to solve this problem:

(1). delete obsolete;

(2). crosscheck backupset;

Delete expired backupset;

Here, I manually delete a part of the archive file, and then use the following command to reduce the actual space of the flash recovery area. The problem is solved.
------------------

Later, I found that this method could not solve my problem because my archive path was changed.

First start to mount:
SQL> startup mount;
The ORACLE routine has been started.

Total System Global Area 603979776 bytes
Fixed Size 1250404 bytes
Variable Size 163580828 bytes
Database Buffers 436207616 bytes
Redo Buffers 2940928 bytes
The database has been loaded.
SQL> select database_role, open_mode from v $ database;

DATABASE_ROLE OPEN_MODE
--------------------------
PHYSICAL STANDBY MOUNTED

Take a look at the alert Log:

Successful mount of redo thread 1, with mount id 1778855572
Sat Dec 31 15:16:40 2011
Physical Standby Database mounted.
Completed: ALTER DATABASE MOUNT
Sat Dec 31 15:16:40 2011
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 1 (4)
ARCH: Archival stopped, error occurred. Will continue retrying
Sat Dec 31 15:16:41 2011
Errors in file c: \ oracle \ product \ 10.2.0 \ admin \ sheng \ bdump \ sheng_arc1_1836.trc:
ORA-16014: log 4 sequence #1 not archived, no available destinations
ORA-00312: online log 4 thread 1: 'C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ SHENG \ REDO04.LOG'

Later:

An error is reported in recover database;

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL
*
Row 3 has an error:
ORA-16136: managed Backup Recovery inactive

Take a look at the alert Log:

Sat Dec 31 15:20:15 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL
Sat Dec 31 15:20:15 2011
ORA-16136 signalled during: alter database recover managed standby database cancel...

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

The following problems must be solved one by one:

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

Take a look at the archive path below:
It seems that there is no problem. Here is a solution:
SQL>Alter database clear unarchived logfile group 4;

The database has been changed.

SQL> alter database clear unarchived logfile group 5;

The database has been changed.

SQL> alter database clear unarchived logfile group 6;

The database has been changed.

SQL> alter database clear unarchived logfile group 7;

The database has been changed.

------------
Shutdown immediate;
Startup mount;

Take a look at the alert Log:
Successful mount of redo thread 1, with mount id 1778822431
Sat Dec 31 16:35:50 2011
Physical Standby Database mounted.
Completed: ALTER DATABASE MOUNT

No problem.

SQL> alter database recover managed standby database disconnect from session;

The database has been changed.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

The database has been changed.

SQL> alter database open read only;
Alter database open read only
*
Row 3 has an error:
ORA-16004: backup database recovery required
ORA-01194: File 1 requires more recovery to maintain consistency
ORA-01110: Data File 1: 'C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ SHENG \ system01.dbf'

The reason is that the control file is copied before primary, and the datafile is copied after the dataguard is configured.

,