On 04/01/2011 01:14 PM, John Gardner wrote: >> So everything works fine as long as the temp file is being written to. >> The out file is the issue. > Not exactly, the temp file is always written to whether the temp file is > located on OCFS2 or sym linked to the EXT3 partition. The problem occurs > right at the end of the process; > > When tmp file is located on OCFS2, the log file is written to it, the log > file completes, creates the out file (wth nothing in it) and resets the tmp > file to 0kb. > When tmp file is located on EXT3, the log file is written to it, the log file > completes, creates the outfile and copies the contents to it, then resets the > tmp file to 0kb. > >> How is the file copied from temp to out? >> mv? cp? >> And please don't guess. > This copying action is a standard Oracle Concurrent Manager action so I have > no way of knowing how Oracle is programmatically performing this, as it is > Oracle code.
OK. Please log a bug with Oracle support. Against the concurrent manager product. _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
