ORA-19502 ORA-16055

ORACLE Instance nsndb – Archival Error. Archiver continuing.
Wed Nov 28 05:56:16 2012
Errors in file /export/home/oracle/admin/nsndb/bdump/nsndb_arc0_998.trc:
ORA-19502: write error on file "", blockno  (blocksize=)
Wed Nov 28 05:56:17 2012
FAL[server, ARC0]: FAL archive failed, see trace file.
Wed Nov 28 05:56:17 2012
Errors in file /export/home/oracle/admin/nsndb/bdump/nsndb_arc0_998.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing


Wed Nov 28 05:56:17 2012
ORACLE Instance nsndb – Archival Error. Archiver continuing.
Wed Nov 28 05:56:19 2012
Errors in file /export/home/oracle/admin/nsndb/bdump/nsndb_arc0_998.trc:
ORA-19502: write error on file "", blockno  (blocksize=)
FAL[server, ARC0]: FAL archive failed, see trace file
.

Sol:
1 check file system space at os level on standby:
df -h

2. archival area will be 100% full then free some space free.

–Check whether Managed Recovery Process (MRP) is running on the standby and delay for the target standby :

SQL> SELECT PROCESS, CLIENT_PROCESS, SEQUENCE#, STATUS,DELAY_MINS FROM V$MANAGED_STANDBY;

PROCESS   CLIENT_P  SEQUENCE# STATUS       DELAY_MINS
——— ——– ———- ———— ———-
ARCH      ARCH           7422 OPENING               0
ARCH      ARCH           7422 OPENING               0
RFS       UNKNOWN           0 IDLE                  0

–Perform recovery on standby:
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

3. check all the archived are appllied or not ,if not then let it apply.

4. when apllied then remove applied archived logs from os level.

 

You can skip to the end and leave a response. Pinging is currently not allowed.

Leave a Reply