CIFS Filesystem on Linux Results in ORA-19510, ORA-27045, ORA-00317 & ORA-00334

Follow

Read our docs CIFS Filesystem (Common Internet File System (CIFS)) on Linux results in ORA-19510, ORA-27045, ORA-00317 & ORA-00334


Problem Details

Problem Statement

Common Internet File System(CIFS) on Linux

Applicable Error Code

ORA-19510, ORA-27045, ORA-00317 & ORA-00334

Affected Versions

Standby Versions

Affected Platforms

Linux platforms

 
Description

CIFS Filesystem is not supported by Oracle and should not be used.

As we execute Run-Interactive (default transfer-activelog) dbvisit DDC, in the alertlog for Primary database we are seeing the following message:

ORA-19510: failed to set size of 342578 blocks for file "/bktdb1/OracleBack/archive/thread_1_seq_50329.1023.860963407" (block size=512)
ORA-27045: unable to close the file
Linux-x86_64 Error: 5: Input/output error
Additional information: 4

Archive was successfully shipped to standby & when the apply was attempted, we received the following message in Standby alert log file (ORA-00317 & ORA-00334):

ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ...
ALTER DATABASE RECOVER CANCEL
ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
Sat Oct 11 16:36:23 2014
ALTER DATABASE RECOVER standby database NOPARALLEL
Media Recovery Start
Serial Media Recovery started
Managed Standby Recovery not using Real Time Apply
ORA-279 signalled during: ALTER DATABASE RECOVER standby database NOPARALLEL ...
ALTER DATABASE RECOVER LOGFILE '/bktdb1/OracleBack/archive/1_48187_852672259.arc'
Media Recovery Log /bktdb1/OracleBack/archive/1_48187_852672259.arc
Errors in file /u01/app/oracle/diag/rdbms/goldprd/GOLDPRD/trace/GOLDPRD_ora_1447.trc:
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/bktdb1/OracleBack/archive/1_48187_852672259.arc'
Errors with log /bktdb1/OracleBack/archive/1_48187_852672259.arc
Solution

Changing the ARCHDEST location to an ext3 filesystem resolves the issue of generating ORA-19510 - ORA-27045 for Dbvisit archived files in the ARCHDEST location, Primary Database. This also resulted in ceasing the false timestamp on the system & applying of the archive log files was successful.

References

  • Write To CIFS Filesystem on Linux Fails ( ORA-01119, ORA-27040 ) (Doc ID 1417168.1)

  • http://arjudba.blogspot.com/2010/12/ora-39097-ora-39065-ora-31643-ora-19510.html

  • Is use of CIFS Protocol for RMAN backups supported? [ID 444809.1]

    • CIFS is fine for RMAN files: backup pieces, datafile copies but it is NOT certified by Oracle.

    • Oracle Support: If there are any problems involved in using RMAN and CIFS, then we cannot get the RDBMS development involved.

  • Is use of CIFS Protocol for RMAN backups supported? (Doc ID 444809.1)

Donna Zehl October 17, 2014 05:29

Have more questions? Submit a request

Comments