Best practices for creating and reorganizing data with additional storage volumes in Amazon RDS for Oracle

This article explains best practices for using additional storage volumes in Amazon RDS for Oracle, enabling storage expansion beyond 64 TiB with independent volume configuration.

• Add up to three additional storage volumes (rdsdbdata2-4) to expand total capacity to 256 TiB
• Configure each volume independently with gp3 or io2 storage types and different performance characteristics
• Create new database files on additional volumes using db_create_file_dest parameter configuration
• Move datafiles, tablespaces, tables, and indexes between volumes using Oracle procedures and commands
• Use additional volumes for temporary staging, data loading, and separating active from historical data
• Support for Oracle Data Pump, transportable tablespaces, and Amazon S3 integration on additional volumes
• Monitor per-volume CloudWatch metrics independently; each volume scales separately
• Snapshots include all volumes; datafile moves require post-operation snapshots for accuracy
• Online data movement available only in Oracle Enterprise Edition; Standard Edition requires offline operations
• Replicas automatically configured with additional volumes; subsequent primary modifications not auto-applied

Additional storage volumes provide cost optimization by placing high-performance and cost-effective storage strategically, enabling flexible database scaling and improved performance tuning for RDS Oracle instances.