Hi Tom, Verification can be done using md5 checksums. You can run the command 'md5sum -b * >archive_sums' at the standby. Then transfer the file archive_sums to the archive_log directory on the primary, and run md5sum --check archive_sums'. This will report for every file whether the checksum is OK (files are identical) or not. Best regards, Carel-Jan Engel === If you think education is expensive, try ignorance. (Derek Bok) === On Mon, 2007-06-18 at 10:52 +0100, Tim Onions wrote: > Dear All > > It's Monday morning after a hard weekend's 9i->10g/Windows->Linux migration > and my brain is in a "London fog" so please excuse me if this is a RTFM > question (which I have done and googled to no result). > > I wish to verify my archive log files that are shipped via non-managed DG to > a server 1000km away before attempting to apply them. I recall Oracle > suggesting this was possible in the past but cannot find anything to > indicate how it is done. The DBV manual only talks about database files and > segments, google comes up with a lot of hits on verifying archive logs > backed up into RMAN. > > The "issue" I have is I do not want to try and apply an archive log file if > it got corrupted during transfer or transfer took place whilst Oracle was > still creating the file on the source server (ie the file is only partially > written). I was given the architecture so have no influence on using managed > DG instead. > > Environment is: > > Oracle 10.3, RAC, Linus RHEL64, EMC DMX-3 storage and SRDF-A > > Many thanks > > Tim Onions > > _________________________________________________________________ > The next generation of Hotmail is here! http://www.newhotmail.co.uk > > -- > //www.freelists.org/webpage/oracle-l > > === If you think education is expensive, try ignorance. (Derek Bok) === DBA!ert, Independent Oracle consultancy Kastanjelaan 61C 2743 BX Waddinxveen The Netherlands tel. +31 (0) 182 64 04 28 fax +31 (0) 182 64 04 29 e-mail careljan@xxxxxxxxxx