ApsaraDB RDS for PPAS instances are no longer available for purchase from May 16, 2021. Alibaba Cloud no longer updates or maintains ApsaraDB RDS for PPAS instances from May 16, 2022. To ensure service availability and continuity, we recommend that you migrate data from your ApsaraDB RDS for PPAS instance to a PolarDB for Oracle cluster at the earliest opportunity. PolarDB for Oracle is highly compatible with Oracle syntax, supports all features of ApsaraDB RDS for PPAS, and supports features such as elastic scaling. Each PolarDB for Oracle cluster contains one primary node and multiple read-only nodes.
Related service
ApsaraDB RDS for PPAS
Details
| Date | Description |
|---|---|
| May 16, 2021 | Alibaba Cloud stops the provision of purchase, upgrade, and renewal services for ApsaraDB RDS for PPAS instances. |
| November 16, 2021 | Alibaba Cloud stops the provision of after-sales services for ApsaraDB RDS for PPAS instances. |
| May 16, 2022 | Alibaba Cloud stops the provision of update and maintenance services for ApsaraDB RDS for PPAS instances. The service-level agreement (SLA) is not guaranteed. For more information, see SLA. |
Suggestions
If you are using an ApsaraDB RDS for PPAS instance, you can go to the Data Transmission Service (DTS) console to migrate data from your ApsaraDB RDS for PPAS instance to a PolarDB for Oracle cluster. For more information, see Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB for Oracle cluster.
- Make sure that the specifications of the PolarDB for Oracle cluster are higher than or equal to the specifications of your ApsaraDB RDS for PPAS instance. Otherwise, slow SQL queries or out of memory (OOM) error may occur because of insufficient CPU or memory resources after you migrate the data to the PolarDB for Oracle cluster. For more information about recommended specifications of PolarDB for Oracle clusters, see Mapping between specifications of ApsaraDB RDS for PPAS instances and recommended specifications of PolarDB for Oracle clusters.
- If you have special requirements for the number of connections and IOPS after migration, select appropriate specifications based on your business requirements. For more information, see Specifications of PolarDB for Oracle cluster.
- If you use a cluster endpoint to connect your application to a PolarDB for Oracle cluster, read/write splitting is enabled. Then, the system forwards read requests to read-only PolarDB for Oracle nodes. This reduces the loads on the primary PolarDB for Oracle node. For more information about how to obtain a cluster endpoint, see View or apply for an endpoint.
| Specifications of ApsaraDB RDS for PPAS instances | Recommended specifications of PolarDB for Oracle clusters | ||
|---|---|---|---|
| Instance type | CPU and memory | Instance type | CPU and memory |
| rds.ppas.t1.small | 1 core, 1 GB | polar.o.x4.medium | 2 cores, 8 GB |
| ppas.x4.small.2 | 1 core, 4 GB | polar.o.x4.medium | 2 cores, 8 GB |
| ppas.x4.medium.2 | 2 cores, 8 GB | polar.o.x4.medium | 2 cores, 8 GB |
| ppas.x8.medium.2 | 2 cores, 16 GB | polar.o.x4.large | 4 cores, 16 GB |
| ppas.x4.large.2 | 4 cores, 16 GB | polar.o.x4.large | 4 cores, 16 GB |
| ppas.x8.large.2 | 4 cores, 32 GB | polar.o.x4.xlarge | 8 cores, 32 GB |
| ppas.x4.xlarge.2 | 8 cores, 32 GB | polar.o.x4.xlarge | 8 cores, 32 GB |
| ppas.x8.xlarge.2 | 8 cores, 64 GB | polar.o.x8.xlarge | 8 cores, 64 GB |
| ppas.x4.2xlarge.2 | 16 cores, 64 GB | polar.o.x8.2xlarge | 16 cores, 128 GB |
| ppas.x8.2xlarge.2 | 16 cores, 128 GB | polar.o.x8.2xlarge | 16 cores, 128 GB |
| ppas.x4.4xlarge.2 | 32 cores, 128 GB | polar.o.x8.4xlarge | 32 cores, 256 GB |
| ppas.x8.4xlarge.2 | 32 cores, 256 GB | polar.o.x8.4xlarge | 32 cores, 256 GB |
| rds.ppas.st.h43 | 60 cores, 470 GB | polar.o.x8.8xlarge | 64 cores, 512 GB |