Skip to content

RDS Oracle released on October 2024

0

I'm using AWS RDS Oracle with version 19.0.0.0.ru-2024-07.rur-2024-07.r1. I want to know if the new release 19.0.0.0.ru-2024-10.rur-2024-10.r1, to be announced, have the bug fix 34294070.

Have any ideas or suggestions?

asked 2 years ago738 views

4 Answers
0

I apologize, but I cannot provide information about a future release that has not been announced yet. The release you're asking about (19.0.0.0.ru-2024-10.rur-2024-10.r1) is not mentioned in the current available information about Amazon RDS for Oracle.

The latest confirmed Release Update (RU) for Oracle Database 19c on Amazon RDS is 19.0.0.0.ru-2024-07.rur-2024-07.r1, which is the version you're currently using. This was released in July 2024.

Regarding specific bug fixes like the one you mentioned (34294070), Amazon RDS doesn't typically provide detailed information about individual bug fixes included in each Release Update. The Release Updates generally include numerous bug fixes and security patches, but the exact list is not usually published.

If you're concerned about a specific bug, the best approach would be to:

  1. Wait for the official announcement of the October 2024 Release Update when it becomes available.
  2. Once announced, check the Amazon RDS for Oracle Release notes for any information about included fixes.
  3. If the information you need isn't in the release notes, you may need to contact AWS Support for more detailed information about specific bug fixes.

Remember that Amazon RDS automatically applies these updates if you have enabled the auto minor version upgrade option. These upgrades typically occur 6-8 weeks after the Release Update is made available by Amazon RDS for Oracle in your AWS Region.
Sources
Amazon RDS for Oracle now supports October 2023 Release Update
Amazon RDS for Oracle Database 21c (21.0.0.0) - Amazon Relational Database Service

answered 2 years ago

0

Hi,

To check the patches applied to RDS for Oracle database, you can verify the lsinventory-dbv.txt output available in the bdump location.

Please refer to the following AWS document on how to download and view the lsinventory-dbv.txt file, https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.Oracle.CommonDBATasks.Misc.html#Appendix.Oracle.CommonDBATasks.accessing-opatch-files

As per the Oracle support document (require Oracle Support Access), the following bugs are fixed in the patch 34294070.

The following are the bugs fixed by this patch:

33150645: INSERT INTO GTT SLOW WITH ON COMMIT DELETE ROWS IN TABLE DDL

33900807: GTT PERFORMANCE DECREASES AS NUMBER OF INSERTED ROWS INCREASES

You can check the lsinventory output for your database to verify if these bug fixes are applied to your database.

AWS

answered 2 years ago

0

The mentioned bug number is not available in the list of bugs fixed for the Update 19.0.0.0.ru-2024-10.rur-2024-10.r1 Reference :https://docs.aws.amazon.com/AmazonRDS/latest/OracleReleaseNotes/oracle-version-19-0.html#oracle-version-RU-RUR.19.0.0.0.ru-2024-10.rur-2024-10.r1

AWS

answered 2 years ago

0

Yes, the Two underlying bugs 33150645 and 33900807 resolved by patch 34294070 are part of RDS Oracle release 19.0.0.0.ru-2024-10.rur-2024-10.r1

Following SQL queries will help you verify:

Use below SQL to find all the lsinventory files on your RDS Oracle Instance

SELECT * FROM table(RDSADMIN.RDS_FILE_UTIL.LISTDIR('BDUMP')) where filename like 'lsinventory%' order by mtime desc;

Use below SQL to find if the bugs 33150645 and 33900807 are part of your RDS Oracle release. Replace with your file name for different version of RDS Oracle.

SELECT * FROM TABLE (rdsadmin.rds_file_util.read_text_file( p_directory => 'BDUMP', p_filename => 'lsinventory-19.0.0.0.ru-2024-10.rur-2024-10.r1.txt')) where text like '%33150645%' or text like '%33900807%';

Explanation:

Patch 34294070 is an interim merge request on top of Oracle version 19.13 ( as per Oracle support Doc ID 2898432.1) which includes bugs 33150645 and 33900807 since they conflicted each other. For upcoming releases you need to verify the underlying bugs solved but the merge patch rather than the merge patch itself.

Testing:

If you are impacted by the issue resolved by these oracle bugs, please test on non production instance first before putting it in production.

AWS

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.