- Newest
- Most votes
- Most comments
When using AWS DMS with an Oracle source database, the 30-byte object name limitation is an important consideration for your migration.
Based on the available information, AWS DMS doesn't support object names exceeding 30 bytes in length. This is validated through a premigration assessment (oracle-check-object-30-bytes-limit) that specifically checks whether object names exceed this limit.
For your full load followed by CDC scenario, you need to consider:
-
Since you're pre-creating all database objects on the target side, the primary concern is whether DMS can properly identify and work with the source objects during migration.
-
The limitation applies to all database objects that DMS needs to interact with directly, not just tables. This includes tables, constraints, indexes, and other objects you've mentioned.
-
Simply shortening table names alone may not be sufficient. DMS needs to interact with various objects during the migration process, especially during CDC where it tracks changes through constraints, keys, and indexes.
The recommended approach would be to:
- Shorten names for all database objects (tables, constraints, indexes, foreign keys, primary keys, unique constraints, and sequences) that exceed 30 bytes on the source side if possible
- If renaming source objects isn't feasible, you'll need to ensure your mapping rules in DMS properly handle the translation between the longer source object names and your pre-created target objects with shorter names
This limitation exists because DMS has specific handling requirements when working with Oracle databases, and the 30-byte limit is a constraint inherited from Oracle's own historical limitations on object name length.
Sources
Oracle assessments - AWS Database Migration Service
Relevant content
asked 5 years ago
asked 2 years ago
