19.30 RU – AutoUpgrade – Cannot find the latest Release Update

As many of you may already know, Oracle has re-released Release Updates (RUs) 19.29 and 19.30 to address an issue.
Additional details are available here.

Marcus Vinicius was testing AutoUpgrade (AU) as part of some improvements in his Composer setup and noticed that AU is not downloading RU 19.30. It is still downloading RU 19.28.

I did some tests and confirmed the issue.

My config file:

global.global_log_dir=/home/oracle/autoupgrade/log
global.keystore=/home/oracle/autoupgrade/keystore
patch1.log_dir=/home/oracle/autoupgrade/log/DB1
patch1.folder=/home/oracle/autoupgrade/patches
patch1.patch=RU
patch1.target_version=19
patch1.platform=LINUX.X64

Let’s try to ask AU to download the 19.30 RU:

global.global_log_dir=/home/oracle/autoupgrade/log
global.keystore=/home/oracle/autoupgrade/keystore
patch1.log_dir=/home/oracle/autoupgrade/log/DB1
patch1.folder=/home/oracle/autoupgrade/patches
patch1.patch=RU:19.30
patch1.target_version=19
patch1.platform=LINUX.X64

And AU was not able to find it:

I spoke with the AutoUpgrade (AU) developer, and he shared the following details:

RU 19.29
19.29 appears to be password-protected and is therefore not included in the ARU query results. It is only visible when querying directly by bug ID. There is likely nothing AU can do on its side to address this.

RU 19.30
RU 19.30 uses a different description format, which prevents AU from identifying it correctly. This is something that can be fixed on the AU side. The trailing text in the description is not in the expected format:

DATABASE RELEASE UPDATE 19.30.0.0.0 (REL-JAN260130)

If you are experiencing this issue, a fix should be available soon.