Unanswered Questions tagged with Amazon Relational Database Service

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

[Announcement]: Urgent Action Required - Upgrade your RDS for PostgreSQL minor versions

This announcement is for customers that are running one or more Amazon RDS DB instances with a version of PostgreSQL, that has been deprecated by Amazon RDS and requires attention. The RDS PostgreSQL minor versions that are listed in the table below are supported, and any DB instances running earlier versions will be automatically upgraded to the version marked as "preferred" by RDS, no earlier than July 15, 2022 starting 12 AM PDT: | Major Versions Supported | Minor Versions Supported | | --- | --- | | 14 | 14.1 and later | | 13 |13.3 and later | | 12 | 12.7 and later | | 11 |11.12 and later | | 10 |10.17 and later| | 9 |none | Amazon RDS supports DB instances running the PostgreSQL minor versions listed above. Minor versions not included above do not meet our high quality, performance, and security bar. In the PostgreSQL versioning policy [1] the PostgreSQL community recommends that you always run the latest available minor release for whatever major version is in use. Additionally, we recommend that you monitor the PostgreSQL security page for documented vulnerabilities [2]. If you have automatic minor version upgrade enabled as a part of your configuration settings, you will be automatically upgraded. Alternatively, you can take action yourselves by performing the upgrade earlier. You can initiate an upgrade by going to the Modify DB Instance page in the AWS Management Console and change the database version setting to a newer minor/major version of PostgreSQL. Alternatively, you can also use the AWS CLI to perform the upgrade. To learn more about upgrading PostgreSQL minor versions in RDS, review the 'Upgrading Database Versions' page [3]. The upgrade process will shutdown the database instance, perform the upgrade, and restart the database instance. The DB instance may restart multiple times during the process. If you choose the "Apply Immediately" option, the upgrade will be initiated immediately after clicking on the "Modify DB Instance" button. If you choose not to apply the change immediately, the upgrade will be performed during your next maintenance window. Starting no earlier than July 15, 2022 12 AM PDT, we will automatically upgrade the DB instances running deprecated minor version to the preferred minor version of the specific major version of your RDS PostgreSQL database. (For example, instances running RDS PostgreSQL 10.1 will be automatically upgraded to 10.17 starting no earlier than July 15, 2022 12 AM PDT) Should you need to create new instances using the deprecated version(s) of the database, we recommend that you restore from a recent DB snapshot [4]. You can continue to run and modify existing instances/clusters using these versions until July 14, 2022 11:59 PM PDT, after which your DB instance will automatically be upgraded to the preferred minor version of the specific major version of your RDS PostgreSQL database. Starting no earlier than July 15, 2022 12 AM PDT, restoring the snapshot of a deprecated RDS PostgreSQL database instance will result in an automatic version upgrade of the restored database instance using the same upgrade process as described above. Should you have any questions or concerns, please see the RDS FAQs [5] or you can contact the AWS Support Team on the community forums and via AWS Support [6]. Sincerely, Amazon RDS [1] https://www.postgresql.org/support/versioning/ [2] https://www.postgresql.org/support/security/ [3] http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html [4] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html [5] https://aws.amazon.com/rds/faqs/ [search for "guidelines for deprecating database engine versions"] [6] https://aws.amazon.com/support
0
answers
1
votes
304
views
asked 7 months ago

[Announcement] Upgrade Amazon Aurora PostgreSQL 10.13, 10.14, 10.16, 11.8, 11.11, 12.4, and 12.6 minor versions by July 15, 2022

Newer versions of Amazon Aurora PostgreSQL-compatible edition are now available and database cluster(s) running Aurora PostgreSQL minor versions 10.13, 10.14, 10.16, 11.8, 11.11, 12.4, and 12.6 need to be upgraded by July 15, 2022. These newer minor versions include important updates that will improve the operations of your Aurora PostgreSQL instances and workloads. We strongly encourage you to upgrade to at least a recommended minimum minor version at your earliest convenience. * For PostgreSQL Minor Versions 10.13, 10.14 and 10.16, the recommended minimum minor version is 10.17. * For PostgreSQL Minor Versions 11.8 and 11.11, the recommended minimum minor version is 11.12. * For PostgreSQL Minor Versions 12.4 and 12.6, the recommended minimum minor version is 12.7. Starting on or after 12:00 PM PDT on July 15, 2022, if your Amazon Aurora PostgreSQL cluster has not been upgraded to a newer minor version, we will schedule the relevant recommended minimum minor version to be automatically applied during your next maintenance window. Changes will apply to your cluster during your next maintenance window even if auto minor version upgrade is disabled. Restoration of Amazon Aurora PostgreSQL 10.13, 10.14, 10.16, 11.8, 11.11, 12.4, and 12.6 database snapshots after July 15, 2022 will result in an automatic upgrade of the restored database to a supported version at the time. *How to Determine Which Instances are Running These Minor Versions?* * In the Amazon RDS console, you can see details about a database cluster, including the Aurora PostgreSQL version of instances in the cluster, by choosing Databases from the console's navigation pane. * To view DB cluster information by using the AWS CLI, use the describe-db-clusters command. * To view DB cluster information using the Amazon RDS API, use the DescribeDBClusters operation. You can also query a database directly to get the version number by querying the aurora_version() system function i.e., "SELECT * FROM aurora_version();". *How to Apply a New Minor Version * You can apply a new minor version in the AWS Management Console, via the AWS CLI, or via the RDS API. Customers using CloudFormation are advised to apply updates in CloudFormation. We advise you to take a manual snapshot before upgrading. For detailed upgrade procedures, please see the available User Guide [1]. Please be aware that your cluster will experience a short period of downtime when the update is applied. Visit the Aurora Version Policy [2] and the documentation [3] for more information and detailed release notes about minor versions, including existing supported versions. If you have any questions or concerns, the AWS Support Team is available on AWS re:Post and via Premium Support [4]. [1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.html [2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Updates.20180305.html [4] https://aws.amazon.com/support ****
0
answers
0
votes
131
views
asked 7 months ago

Announcement: Amazon RDS for SQL Server ending support for Microsoft SQL Server 2012

Microsoft announced they will end support for SQL Server 2012 on July 12, 2022. On that date, Microsoft will stop critical patch updates for SQL Server 2012. We strongly recommend that you upgrade your RDS for SQL Server 2012 database instance to a different major version at your earliest convenience \[1]. Starting September 1, 2021, we will begin disabling the creation of new Amazon RDS for SQL Server database instances using Microsoft SQL Server 2012. Starting June 1, 2022, we plan to end support of Microsoft SQL Server 2012 on Amazon RDS SQL Server. At that time, any remaining instances will be scheduled to migrate to SQL Server 2014 (latest minor version available) as described below. We recommend that you upgrade your Microsoft SQL Server 2012 instances to Microsoft SQL Server 2014 or later at a time convenient to you. You can schedule an upgrade to a different major version by going to the instance modify page in the AWS Management Console and changing the database version to a desired value. If you choose the "Apply Immediately" option, the upgrade will be initiated immediately after exiting the modify page. If you choose not to apply the change immediately, the upgrade will be scheduled during your maintenance window. Upgrade Options: We support five (or four on some regions) different major/minor version combinations of SQL Server 2012. These database instances can be upgraded to the latest minor version of SQL Server 2014, 2016, 2017, and 2019 directly. To find out more information on upgrading please reference this document \[2]. You will still be able to restore a SQL Server 2012 database to any major version supported instance on Amazon RDS SQL Server, even after the deprecation. For more information on restoring a database in RDS see here \[3]. Should you have any questions or concerns, the AWS Support Team is available via AWS Premium Support \[4]. \[1] https://docs.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012 \[2] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.SQLServer.html \[3] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/SQLServer.Procedural.Importing.html \[4] https://aws.amazon.com/support
0
answers
0
votes
741
views
tobyxu
asked 8 months ago

Announcement: Amazon Relational Database Service (Amazon RDS) for MariaDB 10.2 End-of-Life date is October 15, 2022

Amazon RDS is starting the end of life (EOL) process for MariaDB major engine version 10.2. We are doing this because the MariaDB community is planning to discontinue support for MariaDB 10.2 on May 23, 2022 \[1]. Amazon RDS for MariaDB 10.2 will reach end of life on October 15, 2022 00:00:01 AM UTC. While you will be able to run your Amazon RDS for MariaDB 10.2 databases between community MariaDB 10.2 EOL (May 23, 2022) and Amazon RDS for MariaDB 10.2 EOL (October 15, 2022), these databases will not receive any security patches during this extended availability period. We strongly recommend that you proactively upgrade your databases to major version 10.3 or greater before community EOL on May 23, 2022. MariaDB 10.3 offers improved Oracle compatibility, support for querying historical states of the database, features that increase flexibility for developers and DBAs, and improved manageability \[2]. Our most recent release, Amazon RDS for MariaDB 10.6, introduces multiple MariaDB features to enhance the performance, scalability, reliability and manageability of your workloads, including MyRocks storage engine, IAM integration, one-step multi-major upgrade, delayed replication, improved Oracle PL/SQL compatibility and Atomic DDL \[3]. If you choose to upgrade to MariaDB 10.6, you will be able to upgrade your MariaDB 10.2 instances seamlessly to Amazon RDS for MariaDB 10.6 in a single step, thus reducing downtime substantially. Both versions, MariaDB 10.3 and 10.6, contain numerous fixes to various software bugs in earlier versions of the database. If you do not upgrade your databases before October 15, 2022, Amazon RDS will upgrade your MariaDB 10.2 databases to 10.3 during a scheduled maintenance window between October 15, 2022 00:00:01 UTC and November 15, 2022 00:00:01 UTC. On January 15, 2023 00:00:01 AM UTC, any Amazon RDS for MariaDB 10.2 databases that remain will be upgraded to version 10.3 regardless of whether the instances are in a maintenance window or not. You can initiate an upgrade of your database instance to a newer major version of MariaDB — either immediately or during your next maintenance window — using the AWS Management Console or the AWS Command Line Interface (CLI). The upgrade process will shut down the database instance, perform the upgrade, and restart the database instance. The database instance may be restarted multiple times during the upgrade process. While major version upgrades typically complete within the standard maintenance window, the duration of the upgrade depends on the number of objects within the database. To avoid any unplanned unavailability outside your maintenance window, we recommend that you first take a snapshot of your database and test the upgrade to get an estimate of the upgrade duration. If you are operating an Amazon RDS for MariaDB 10.2 database on one of the retired instance types (t1, m1, m2), you will need to migrate to a newer instance type before upgrading the engine major version. To learn more about upgrading MariaDB major versions in Amazon RDS, review the Upgrading Database Versions page \[4]. We want to make you aware of the following additional milestones associated with upgrading databases that are reaching EOL. **Now through October 15, 2022 00:00:01 AM UTC **- You can initiate upgrades of Amazon RDS for MariaDB 10.2 instances to MariaDB 10.3 or 10.6 at any time. **July 15, 2022 00:00:01 AM UTC –** After this date and time, you cannot create new Amazon RDS instances with MariaDB 10.2 from either the AWS Console or the CLI. You can continue to restore your MariaDB 10.2 snapshots as well as create read replicas with version 10.2 until the October 15, 2022 end of support date. **October 15, 2022 00:00:01 AM UTC -** Amazon RDS will automatically upgrade MariaDB 10.2 instances to version 10.3 within the earliest scheduled maintenance window that follows. After this date and time, any restoration of Amazon RDS for MariaDB 10.2 database snapshots will result in an automatic upgrade of the restored database to a still supported version at the time. **January 15, 2023 00:00:01 AM UTC -** Amazon RDS will automatically upgrade any remaining MariaDB 10.2 instances to version 10.3 whether or not they are in a maintenance window. If you have any questions or concerns, the AWS Support Team is available on AWS re:Post and via Premium Support \[5]. \[1] https://mariadb.org/about/#maintenance-policy \[2] https://aws.amazon.com/about-aws/whats-new/2018/10/amazon-rds-now-supports-mariadb-10_3/ \[3] https://aws.amazon.com/about-aws/whats-new/2022/02/amazon-rds-mariadb-supports-mariadb-10-6/ \[4] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html \[5] http://aws.amazon.com/support
0
answers
1
votes
396
views
palK
asked 8 months ago

Announcement: Amazon RDS for Oracle - End of Support Timeline for 12c Oracle Release 2 (12.2.0.1) and Oracle Release 1 (12.1.0.2) Major Version

Oracle Corporation has announced the end of support for Oracle Database version 12.1.0.2 on July 31, 2022, and version 12.2.0.1 on March 31, 2022 [1]. After these dates, Oracle Support will no longer release Critical Patch Updates for these database versions, and these versions will no longer be available in Amazon RDS for Oracle. For Oracle Database version 12.2.0.1: Amazon RDS for Oracle will end the support for Oracle Database version 12.2.0.1 (all editions) for both License Included (LI) and Bring Your Own License (BYOL) models on March 31, 2022. For Oracle Database version 12.1.0.2: Amazon RDS for Oracle will end the support for Oracle Database version 12.1.0.2 (all editions) for both License Included (LI) and Bring Your Own License (BYOL) models on July 31, 2022. If you have already upgraded your DB instance(s) to 19c, no further action is required. We highly recommend you upgrade your existing 12.1.0.2 and 12.2.0.1 DB instances to version 19c and validate your applications before the automatic upgrades begin. Please keep in mind the following timeline for the 19c version: • 19c: The Premier Support for Oracle Database 19c ends on April 30, 2024, while the Extended Support ends on April 30, 2027. Amazon RDS for Oracle plans to support Oracle Database 19c until April 30, 2027. 12.2.0.1 Deprecation - Timeline summary: • Now - March 31, 2022 - You can upgrade 12.2.0.1 DB instances manually to the version of your choice. • From February 14, 2022 - You can upgrade 12.2.0.1 snapshots manually to the version of your choice. • From February 14, 2022 - Amazon RDS for Oracle disables new instance creates on 12.2.0.1, but you will be able to continue to restore 12.2.0.1 DB snapshots without being auto upgraded until March 31, 2022. • From April 1, 2022 - Amazon RDS for Oracle starts automatic upgrades of 12.2.0.1 DB instances to 19c. • From April 1, 2022 - Amazon RDS for Oracle starts automatic upgrades to 19c of DB instances restored from 12.2.0.1 snapshots. 12.2.0.1 Deprecation Timeline by Amazon RDS for Oracle (for both BYOL and LI): Starting on February 14, 2022, Amazon RDS for Oracle will disable the ability to create new DB instances using 12.2.0.1. If you are using 12.2.0.1, please upgrade your instance(s) to a later major version before March 31, 2022. Starting on April 1, 2022, Amazon RDS Oracle will automatically upgrade DB instances from 12.2.0.1 to the latest Release Update (RU) on RDS for Oracle Database 19c. We highly recommend that you test your application on 19c or whichever major version you plan on upgrading to. Starting on April 1, 2022, any 12.2.0.1 DB instance created from a snapshot restore or point-in-time restore will be automatically upgraded to the latest RU on RDS for Oracle 19c. Starting on February 14, 2022, you may upgrade your snapshots manually from 12.2.0.1 to a newer major engine version. For more information, see Upgrading an Oracle DB Snapshot [3]. If you have encrypted snapshots do plan to perform manual snapshot upgrade. 12.1.0.2 Deprecation - Timeline summary: • Now - July 31, 2022 - You can upgrade 12.1.0.2 DB instances manually to the version of your choice. • From June 1, 2022 - You can upgrade 12.1.0.2 snapshots manually to the version of your choice. • From June 1, 2022 - Amazon RDS for Oracle disables new instance creates on 12.1.0.2, but you will be able to continue to restore 12.1.0.2 DB snapshots without being auto upgraded until July 31, 2022. • From August 1, 2022 - Amazon RDS for Oracle starts automatic upgrades of 12.1.0.2 DB instances to 19c. • From August 1, 2022 - Amazon RDS for Oracle starts automatic upgrades to 19c of DB instances restored from 12.1.0.2 snapshots. 12.1.0.2 Deprecation Timeline by Amazon RDS for Oracle (for both BYOL and LI): Starting on June 1, 2022, Amazon RDS for Oracle will disable the ability to create new DB instances using 12.1.0.2. If you are using 12.1.0.2, please upgrade your instance(s) to a later major version before July 31, 2022. Starting on August 1, 2022, Amazon RDS Oracle will automatically upgrade DB instances from 12.1.0.2 to the latest Release Update (RU) on RDS for Oracle Database 19c. We highly recommend that you test your application on 19c or whichever major version you plan on upgrading to. Starting on August 1, 2022, any 12.1.0.2 DB instance created from a snapshot restore or point-in-time restore will be automatically upgraded to the latest RU on RDS for Oracle 19c. Starting on June 1, 2022, you may upgrade your snapshots manually from 12.1.0.2 to a newer major engine version. For more information, see Upgrading an Oracle DB Snapshot [3]. If you have encrypted snapshots, you need to plan to perform manual snapshot upgrade. Additional Notes: After the upgrade, if the SQL statements perform in an unexpected manner due to the change in the plans by the 19c optimizer, you can use the OPTIMIZER_FEATURES_ENABLE parameter to retain the behavior of the 12c optimizer. There is no impact to your current Reserved Instances (RI) due to the engine version deprecation of 12.1.0.2 and 12.2.0.1. For versions in Extended Support, BYOL model customers must have purchased Extended Support agreements from Oracle Support or upgrade to a version for which they have support. For the details on the Licensing and Support requirements for the BYOL model customers, refer to the Amazon RDS for Oracle FAQs [4]. To learn more about upgrading Oracle major versions in RDS, review Upgrading the Oracle DB engine [5]. Please contact us through AWS Support [6] should you have any questions or concerns. Oracle Database Version 19c: The Extended Support for Oracle Database 19c ends on April 30, 2027. Amazon RDS for Oracle will support Oracle Database 19c until April 30, 2027. We recommend you to upgrade your existing 12.1.0.2 or 12.2.0.1 DB instances to version 19c [7] because it is the long-term support release. Note for versions in Extended Support, BYOL model customers must have purchased Extended Support agreements from Oracle Support or upgrade to a version for which they have support. For the details on the Licensing and Support requirements for the BYOL model customers, refer to the Amazon RDS for Oracle FAQs [4]. Review the version specific deprecation details on the AWS forum [2]. To learn more about Amazon RDS policy for supporting database versions, please see the RDS FAQs and search for “guidelines for deprecating database engine versions” [8]. Please contact us through AWS Support [6] or the AWS Developer Forums [9] should you have any questions or concerns. [1] https://www.oracle.com/us/assets/lifetime-support-technology-069183.pdf [2] https://forums.aws.amazon.com/ann.jspa?annID=8593 [3] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBSnapshot.Oracle.html [4] https://aws.amazon.com/rds/oracle/faqs/ [5] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Oracle.html [6] https://aws.amazon.com/support [7] https://aws.amazon.com/about-aws/whats-new/2019/11/amazon-rds-for-oracle-now-supports-oracle-database-19c/ [8] https://aws.amazon.com/rds/faqs [9] https://forums.aws.amazon.com/forum.jspa?forumID=60
0
answers
0
votes
2100
views
asked 8 months ago

Unable to start replication with External MySQL master

I am getting the below error while starting replication in RDS for external master. The Master is hosted in EC2 within the same VPC mysql> show slave status\G *************************** 1. row *************************** Slave_IO_State: Connecting to master Master_Host: 54.89.210.126 Master_User: repl Master_Port: 3306 Connect_Retry: 60 Master_Log_File: TEST-mysql-bin.000002 Read_Master_Log_Pos: 846 Relay_Log_File: relaylog.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: TEST-mysql-bin.000002 Slave_IO_Running: Connecting Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: mysql.plugin,mysql.rds_monitor,mysql.rds_sysinfo,innodb_memcache.cache_policies,mysql.rds_history,innodb_memcache.config_options,mysql.rds_configuration,mysql.rds_replication_status Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 846 Relay_Log_Space: 354 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 1045 Last_IO_Error: error connecting to master 'repl@54.89.210.126:3306' - retry-time: 60 retries: 1 Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 0 Master_UUID: Master_Info_File: mysql.slave_master_info SQL_Delay: 0 SQL_Remaining_Delay: NULL Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates Master_Retry_Count: 86400 Master_Bind: Last_IO_Error_Timestamp: 220228 08:14:01 Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec) In my Master log, I am getting unusual error. Please see below : 2022-02-28T07:22:21.141497Z 0 [Note] /mysqldatabase/product/binary/5.7.37/bin/mysqld: ready for connections. Version: '5.7.37-log' socket: '/mysqldatabase/TEST/admin/mysql.sock' port: 3306 MySQL Community Server (GPL) 2022-02-28T07:40:24.426990Z 4 [Warning] Hostname 'ec2-52-21-161-100.compute-1.amazonaws.com' does not resolve to '52.21.161.100'. 2022-02-28T07:40:24.427029Z 4 [Note] Hostname 'ec2-52-21-161-100.compute-1.amazonaws.com' has the following IP addresses: 2022-02-28T07:40:24.427034Z 4 [Note] - 172.31.70.67
0
answers
0
votes
15
views
asked 9 months ago

Announcement: Amazon RDS for Oracle - End of Support Timeline for DB snapshots

[Source: https://forums.aws.amazon.com/ann.jspa?annID=8848] **End of Support Timeline for DB snapshots on versions 11.2.0.2, 11.2.0.3 and 12.1.0.1** **Updated February 4, 2022** Extended the deletion timeline from Feb 15, 2022 to April 31, 2022. **Old DB snapshots Deprecation - Timeline summary:** • Now through April 31, 2022: You can upgrade 11.2.0.2, 11.2.0.3 and 12.1.0.1 DB snapshots manually to the supported snapshot versions. Please review the documentation for the supported upgrade paths [[1]]. • May 1, 2022: Amazon RDS for Oracle starts the automatic deletion of these old DB snapshots. **Updated October 20, 2021** Amazon RDS for Oracle deprecated 11.2.0.2, 11.2.0.3 and 12.1.0.1 database versions. As a result, we are deprecating the DB snapshots taken from these deprecated databases. If you currently have one or more Amazon RDS for Oracle DB snapshots, taken from the deprecated database versions. You must upgrade these old snapshots to ensure continued availability of these snapshots. **Old DB snapshots Deprecation - Timeline summary:** • Now through Apr 31, 2022: You can upgrade 11.2.0.2, 11.2.0.3 and 12.1.0.1 DB snapshots manually to the supported snapshot versions. Please review the documentation for the supported upgrade paths [[1]]. • May 1, 2022: Amazon RDS for Oracle starts the automatic deletion of these old DB snapshots. Additional Notes: For a step-by-step guide on how to update your DB snapshots, please review the Best Practices for upgrading Amazon RDS for Oracle DB snapshots blog [[2]] To learn more about upgrading an oracle DB snapshots, review the documentation [[1]]. Please contact us through AWS Support [[3]] or the AWS Developer Forums [[4]] should you have any questions or concerns. [[1]] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBSnapshot.Oracle.html [[2]] https://aws.amazon.com/blogs/database/best-practices-for-upgrading-amazon-rds-for-oracle-database-snapshots/ [[3]] https://aws.amazon.com/support [[4]] https://forums.aws.amazon.com/forum.jspa?forumID=60
0
answers
0
votes
88
views
asked 10 months ago