This content has been marked as final. Show 4 replies
I suspect you got it figured out by now but this looks like you ran out of disk space or someone deleted rf004174. It could be that the server/collector process that does the writing on the target crashed from some reason as well, but that's a very simple and stable component. I don't think I've ever seen it crash. Regardless, I'll bet a restart of the pump got around it (if/once disk space was not an issue). But please feel free to let the thread know how you got around this.
2010-11-24 10:01:19 ERROR OGG-01031 There is a problem in network communication, a remote file problem, encryption keys for target and source do not match (if using ENCRYPT) or an unknown error. (Reply received is Unable to open file "/orcl/goldengate/dirdat/trail_f/rf004174" (error 11, Resource temporarily unavailable)).
If you have a shared file system and the OS doesn't shutdown cleanly, you may have file locks on files held by the file system preventing OGG from obtaining and exclusive lock on the file.
Move the original file to another name, then copy that file back to the original name
a. Move the file /orcl/goldengate/dirdat/trail_f/rf004174 to /orcl/goldengate/dirdat/trail_f/rf004174_backup
b. Then copy /orcl/goldengate/dirdat/trail_f/rf004174_backup to /orcl/goldengate/dirdat/trail_f/rf004174
c. Then restart Extract.
d. Once it restarts, You can delete the backup file /orcl/goldengate/dirdat/trail_f/rf004174_backup
Also a new UNLOCKEDTRAILFILES parameter was added for GLOBALS as a workaround for problems with trail files that remain locked by Collector if there is a network outage that affects the target system. As of GoldenGate version 10.4, Collector began locking a trail file when writing data to it, to prevent corruption from other processes that may attempt to write to the same trail. UNLOCKEDTRAILFILES prevents Collector from locking the trail files.
Hope this information helps.
Thanks & Regards