Alternative, if you just want to verify the integrity of the logfiles without dumping their contents, you can specify a non-existent layer and opcode as follows ...
alter system dump logfile 'filespec' layer 99 opcode 99;That will read the log file and check the layer and opcode of each change vector. Of course, none will match 99.99 so the trace file will only contain the dump of the file header and then the redo read statistics that would normally be right at the end of the dump.
@ Regards, @ Steve Adams @ http://www.ixora.com.au/ - For DBAs @ http://www.christianity.net.au/ - For all -----Original Message----- Date: Mon, 18 Jun 2007 08:14:06 -0400 From: rjamya <rjamya@xxxxxxxxx> To: daniel.fink@xxxxxxxxxxxxxx Subject: Re: DBverify like utility for archive log files Cc: att755@xxxxxxxxxxx, Oracle-L@xxxxxxxxxxxxx
and make sure that you have enough space in your *_dump_dest location to hold the files ....RajOn 6/18/07, *Daniel W. Fink* < daniel.fink@xxxxxxxxxxxxxx <mailto:daniel.fink@xxxxxxxxxxxxxx>> wrote:Try ALTER SYSTEM DUMP LOGFILE <filename>; This will read the entries in the logfile using the same mechanism that is used for recovery purposes.