Re: FW:NFS issues

Goulet, Dick wrote:

>
> Yes we can write files on the NFS mount, and the syslogs have
> nothing in them. But the DB sure is having a pile of fun with it.
> Alter log says it's creating the archive log, but nothing shows up and
> the db just hangs.

I've seen similar problems while writing secondary archivelogs on a nfs mount. Once in a blue moon (about once or twice per month actually) the file just contained a few bytes at the start and then nulls till the end, size being the same size as the primary archivelog file. Despite investigation we never found the real reason but everyone we asked recommended to stay away from nfs.

Nowadays we're just writing archivelogs to the machine oracle is running on. Then we're copying them at system level with rsync and a 20 minutes delay to make sure the archivelogs are really really fully written and not changed anymore. rsync called in a cron job running every 10 minutes. Works smoothly. (With rsync the delay could probably be shortened down to a minute or so as it just copies the file again if changed but 20 minutes delay is ok for us.)

That the db hangs might stem from your configuration: Do you force oracle to write the archivedlog (MANDATORY)? It makes sense to enforce writing of at least one archivelog destination but only when you can assure that at least one destination DOES work. Else the database will hang, as you just experienced.

Disclaimer: If I'm wrong concerning newer versions, don't whack me. My knowledge is taken from 8.1.7

Stephan

--
http://www.freelists.org/webpage/oracle-l