Skip to content

AWS DMS with Oracle Source: Handling Object Names >30 Bytes

0

The AWS DMS documentation states that "AWS DMS does not support long object names (over 30 bytes)" when using Oracle as a source. I’d like to understand the practical implications of this limitation for our use case.

We plan to use DMS for a full load followed by CDC. All database objects (tables, constraints, indexes, etc.) will be pre-created on the target side—only the data will be migrated and kept in sync.

Our Oracle source includes:

  • tables
  • indexes
  • constraints
  • foreign keys
  • primary keys
  • unique constraints
  • sequences with names longer than 30 bytes

Key question: If we shorten the table names to meet the 30-byte limit, will that be sufficient for DMS to function correctly? Or do we also need to rename other objects (e.g., constraints, indexes, sequences) to stay within the limit?

Any clarification or experience with similar setups would be greatly appreciated.

1 Answer
0

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:

  1. 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.

  2. 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.

  3. 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

answered a year ago

AWS
SUPPORT ENGINEER

reviewed a year 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.