AWS prescriptive-guidance documentation change
Summary
Updated document title, simplified section headers, fixed punctuation, and improved table formatting. Changed 'Prepare phase' to 'Phase 1: Prepare phase'.
Security assessment
Changes are cosmetic and structural (title updates, formatting improvements). No security vulnerabilities, configurations, or features are mentioned or modified.
Diff
diff --git a/prescriptive-guidance/latest/migrate-bulky-oracle-databases/phase0.md b/prescriptive-guidance/latest/migrate-bulky-oracle-databases/phase0.md index af0f8f098..0d85ee473 100644 --- a//prescriptive-guidance/latest/migrate-bulky-oracle-databases/phase0.md +++ b//prescriptive-guidance/latest/migrate-bulky-oracle-databases/phase0.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,3 +7 @@ -# Phase 0 – Initial setup phase - -###### +# Phase 0: Setup phase @@ -15 +13 @@ -You must verify whether the target database instance has the same time zone and character set as source database. Otherwise, this migration approach will fail +You must verify whether the target database instance has the same time zone and character set as source database. Otherwise, this migration approach will fail. @@ -20,5 +18,3 @@ To check that the time zone version in both the source and target is same, run t - FILENAME VERSION CON_ID - ----------------------- ------------- ---------- - timezlrg_14.dat 14 0 - - + FILENAME VERSION CON_ID + ----------------------- ------------- ---------- + timezlrg_14.dat 14 0 @@ -29,6 +25,5 @@ To check that both the DB character set and the national character set are the s - where parameter in ('NLS_CHARACTERSET','NLS_NCHAR_CHARACTERSET'); - PARAMETER VALUE - -------------------------------------------- -------------------- - NLS_NCHAR_CHARACTERSET UTF8 - NLS_CHARACTERSET AL32UTF8 - + where parameter in ('NLS_CHARACTERSET','NLS_NCHAR_CHARACTERSET'); + PARAMETER VALUE + -------------------------------------------- -------------------- + NLS_NCHAR_CHARACTERSET UTF8 + NLS_CHARACTERSET AL32UTF8 @@ -38 +33 @@ To check that both the DB character set and the national character set are the s -On the source system, download and extract the script file, [rman_xttconvert_VER4.zip](https://support.oracle.com/epmos/main/downloadattachmentprocessor?attachid=2471245.1%3ARMAN_XTTS_VER4&docType=REFERENCE&action=download) from Oracle document 2471245.1. Modify the parameters in the `xtt.properties` file with the specific configuration. Then copy `xtt.properties` and `xttdriver.pl` scripts to the destination system. +On the source system, download and extract the script file, [rman_xttconvert_VER4.zip](https://support.oracle.com/epmos/main/downloadattachmentprocessor?attachid=2471245.1%3ARMAN_XTTS_VER4&docType=REFERENCE&action=download) from Oracle document 2471245.1. Modify the parameters in the xtt.properties file with the specific configuration. Then copy xtt.properties and xttdriver.pl scripts to the destination system. @@ -51 +46 @@ Migration phases -Prepare phase +Phase 1: Prepare phase