AWS prescriptive-guidance documentation change
Summary
Updated terminology from 'heterogeneous' to 'cross-platform', changed 'Snowball Edge' to 'Snowball', modified image reference, adjusted phase numbering/formatting, removed backticks from object types, fixed contractions, and removed validation phase mention.
Security assessment
Changes are editorial and terminological (e.g., 'Snowball Edge' to 'Snowball', formatting adjustments). No security vulnerabilities, configurations, or features are mentioned or modified. Removal of validation phase reference doesn't indicate security impact as it wasn't security-focused.
Diff
diff --git a/prescriptive-guidance/latest/migrate-bulky-oracle-databases/overview.md b/prescriptive-guidance/latest/migrate-bulky-oracle-databases/overview.md index c40c8a28c..0e119af17 100644 --- a//prescriptive-guidance/latest/migrate-bulky-oracle-databases/overview.md +++ b//prescriptive-guidance/latest/migrate-bulky-oracle-databases/overview.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating bulky Oracle databases to AWS for heterogeneous environments](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating bulky Oracle databases to AWS for cross-platform environments](introduction.html) @@ -7 +7 @@ -Prepare phaseRoll-forward phaseTransport phase +Phase 1 - Prepare phasePhase 2 - Roll-forward phasePhase 3 - Transport phase @@ -11 +11 @@ Prepare phaseRoll-forward phaseTransport phase -This is the conceptual process of migrating Oracle databases to AWS using Oracle XTTS and RMAN incremental backups with Snowball Edge, Direct Connect, and FSx for Lustre. +This is the conceptual process of migrating Oracle databases to AWS using Oracle XTTS and RMAN incremental backups with Snowball, Direct Connect, and FSx for Lustre. @@ -15 +15 @@ The following diagram shows the high-level migration steps for an Oracle databas - + @@ -19 +19 @@ The following diagram shows the high-level migration steps for an Oracle databas - 2. Use Snowball Edge to move the backup from the source stage to the target stage. + 2. Use Snowball to move the backup from the source stage to the target stage. @@ -36 +36 @@ Before cutover, you can minimize downtime by doing the following: - * Exporting and importing the metadata of nonsegment-based objects, including `USER`, `PACKAGE_SPEC`, `PACKAGE_BODY`, `PROCEDURE`, and `FUNCTION` + * Exporting and importing the metadata of nonsegment-based objects, including USER, PACKAGE_SPEC, PACKAGE_BODY, PROCEDURE, and FUNCTION @@ -47 +47 @@ Before cutover, you can minimize downtime by doing the following: -The Oracle document Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup ([2471245.1](https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=114983393292188&id=2471245.1)) explains how to use Oracle XTTS with RMAN incremental backups. The document also includes details on requirements and recommendations. The document doesn’t describe how to migrate an Oracle database from an on-premises environment to Oracle on AWS or how to parallelize each migration step to minimize downtime. +The Oracle document Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup ([2471245.1](https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=114983393292188&id=2471245.1)) explains how to use Oracle XTTS with RMAN incremental backups. The document also includes details on requirements and recommendations. The document doesn't describe how to migrate an Oracle database from an on-premises environment to Oracle on AWS or how to parallelize each migration step to minimize downtime. @@ -53 +53 @@ Following an initial setup phase, the high-level steps for using Oracle XTTS wit -## Phase 1 – Prepare phase +## Phase 1 - Prepare phase @@ -55 +55 @@ Following an initial setup phase, the high-level steps for using Oracle XTTS wit -The prepare phase consists of the following steps: +The prepare phase consists of the following steps. @@ -59 +59 @@ The prepare phase consists of the following steps: - 2. The backup copies are transferred using Snowball Edge to the target stage, which is FSx for Lustre integrated with Amazon Simple Storage Service (Amazon S3). + 2. The backup copies are transferred using Snowball to the target stage, which is FSx for Lustre integrated with Amazon Simple Storage Service (Amazon S3). @@ -66 +66 @@ The prepare phase consists of the following steps: -The steps in this phase are run only once during migration. The data being transported is fully accessible in the source database during this phase. +The steps in this phase are run only once during migration. The data being transported are fully accessible in the source database during this phase. @@ -68 +68 @@ The steps in this phase are run only once during migration. The data being trans -## Phase 2 – Roll-forward phase +## Phase 2 - Roll-forward phase @@ -70 +70 @@ The steps in this phase are run only once during migration. The data being trans -The roll-forward phase consists of the following steps: +The roll-forward phase consists of the following steps. @@ -83 +83 @@ You can run this phase multiple times. Each successive incremental backup should -## Phase 3 – Transport phase +## Phase 3 - Transport phase @@ -85 +85 @@ You can run this phase multiple times. Each successive incremental backup should -The third phase includes the following steps: +The third phase includes the following steps. @@ -106,2 +105,0 @@ Finally, the tablespaces are made read/write for full access on the destination -This phase is followed by a validation phase. -