ORA-19502 is talking about oracle failing to write to a trace file.
ORA-27072 is talking about disk I/O error.
Oracle may have failed to write because disk i/o was a problem meaning (a) disk failed, (b) disk was full, (c) oracle didn't have permission to write to the particular folder it was trying to write the trace file to.

Your best bet is check file permissions on the directory you were trying to write to.

Gurmohan
www.onlymath.com - The place to learn and teach math.




-----Original Message-----
From: Dustin Hayden
[mailto:oracledba-ezmlmshield-x66417770.[Email address protected]
Sent: Thursday, October 27, 2005 1:46 PM
To: LazyDBA Discussion
Subject: archive logging errors.




What can cause the following problem?





*** 2005-10-27 04:06:24.886



kcrrfail: dest:1 err:19502 force:0



ORA-19502: write error on file "/ora1/arch/FSPRD88/ora_FSPRD88_2122.arc",
blockn



o 5121 (blocksize=1024)



ORA-27072: skgfdisp: I/O error



HPUX-ia64 Error: 2: No such file or directory



Additional information: 5121



ORA-19502: write error on file "/ora1/arch/FSPRD88/ora_FSPRD88_2122.arc",
blockn



o 5121 (blocksize=1024)



*** 2005-10-27 04:06:24.890



ARC0: Archiving not possible: error count exceeded



ORA-16038: log 6 sequence# 2122 cannot be archived



ORA-19502: write error on file "", blockno (blocksize=)



ORA-00312: online log 6 thread 1: '/ora3/oradata/FSPRD88/redo06.log'



Encountered disk I/O error 19502









This finally cleared up and finished archiving log 6





--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:http://www.lazydba.com/legal.html

Oracle LazyDBA home page