OGG trailfile to NAS

From: Herring, David <"Herring,>
Date: Tue, 24 Dec 2019 14:58:02 +0000
Message-ID: <CH2PR02MB666414575C7C6D0657965AFDD4290_at_CH2PR02MB6664.namprd02.prod.outlook.com>

Folks, I'm having a rather difficult time tracking down exactly what is wrong in our configuration related to OGG and writing to it's trailfile directory.

OGG Version -, RHEL 7.6

We created a symlink pointing the directory "dirdat" to a NAS:

% ln -s /dnbusr1/dnbinas/gg_dnbi/dirdat /u01/app/oracle/ACS/OGG/gg19c/dirdat

The NAS is mounted as:

<NAS> on /dnbusr1/dnbinas type nfs (rw,relatime,sync,vers=3,rsize=32768,wsize=32768,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,noac,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=<IP addr>,mountvers=3,mountport=635,mountproto=udp,local_lock=none,addr=<IP addr>)

Once the extract starts we get the error:

ERROR OGG-01454 Unable to lock file "/u01/app/oracle/ACS/OGG/gg19c/dirdat/E0000000000" (error 37, No locks available).

Research says nfslock service needs to be restarted (done), mount options changed (done), permissions changed (done), yet we still get the same problem. If we repoint the symlink to local storage the OGG extract process works fine, so it's got to be something with the NAS yet we can't figure out what. I even strace'd the extract process which showed the following, yet wasn't helpful (to me):

[pid 83896] openat(AT_FDCWD, "/u01/app/oracle/ACS/OGG/gg19c/dirdat/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC <unfinished ...>
[pid 83897] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)

Any ideas on how to find out exactly what the issue is? We're stuck as we need a ton of space for the extract files and there's no way to allocate that much space to local storage.




Received on Tue Dec 24 2019 - 15:58:02 CET

Original text of this message