Re: CLUVFY Fails with Set RAT_REMOTE_PYCOPY_WAIT to higher value

From: John Piwowar <jpiwowar_at_gmail.com>
Date: Sun, 15 Jan 2023 10:44:33 -0800
Message-ID: <CAJgcjADzi8cTa+Phpr=ybKe7j6oObM2CkUr90Lqs46WWPkH7rQ_at_mail.gmail.com>



I haven’t encountered this myself, and not at my keyboard to do any research. But based on the name and format, my under-educated guess is that this is an environment variable that governs how long the utility will wait to finish copying files before deciding something broke.

If you haven’t already done so, try something like “export RAT_REMOTE_PYCOPY_WAIT=30”
(or 60, or whatever) in the shell session from which you’re applying the patch.

If you’ve already tried that without improved results, you’re probably in SR territory.

On Sun, Jan 15, 2023 at 9:59 AM David Barbour <david.barbour1_at_gmail.com> wrote:

> Good Morning All and a Belated Happy New Year.
>
> We are trying to apply the October 2022 CPU (19.17) and cluvfy is failing
> with
>
> '|Node node4 is configured for ssh user equivalency for grid user|||Failed
> to copy
> necessary binaries to the remote node.
> *Set RAT_REMOTE_PYCOPY_WAIT to higher value* and try again (Default
> is set to 5 seconds)'
>
> This is RHEL release 8.6 (Ootpa) and Oracle EE Version 19.15.0.0.0
>
> I cannot find where this is set to change it. Have tried MOS, Redhat
> Support and Googled for hours without success.
>
> I'm sure I'm not the first one to encounter this.
>
> Anybody know how/where to change this?
>

-- 
Regards, John P. (Typed with thumbs on a mobile device. Lowered
expectations appreciated)

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Jan 15 2023 - 19:44:33 CET

Original text of this message