Skip to content
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.

Update Ora2pg Datastream Tutorial with Up-to-date Requirements and Limitations #1877

Merged
merged 5 commits into from
Jul 19, 2021
Merged

Update Ora2pg Datastream Tutorial with Up-to-date Requirements and Limitations #1877

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f608113
Merge pull request #1 from GoogleCloudPlatform/master
ktchana Jul 6, 2021
5676d11
Update Ora2pg Datastream Tutorial with Up-to-date Requirements and Li…
ktchana Jul 6, 2021
9317609
Merge branch 'master' into ora2pg-datastream
ToddKopriva Jul 16, 2021
e74dcd7
copy edit
ToddKopriva Jul 19, 2021
8d21dec
Merge branch 'master' into ora2pg-datastream
ToddKopriva Jul 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 4 additions & 12 deletions tutorials/migrate-oracle-postgres-using-datastream/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Use the [pricing calculator](https://cloud.google.com/products/calculator) to ge
## Source database requirements

For the migration to be successful, you must ensure that several requirements are satisfied on the source Oracle database, to ensure compatibility with the
toolchain used in this tutorial.
toolchain used in this tutorial. Refer to the [product documentation](https://cloud.google.com/datastream/docs/sources#versionsfororaclesourcedb) for the most up-to-date information.

* **Version**: Oracle 10g v10.2, 11g v11.2.0.4, 12c v12.1.0.2/1, 18c, or 19c

Expand All @@ -71,12 +71,6 @@ toolchain used in this tutorial.

* **Size**:

* Oracle databases up to 10 TB.

You can check the database size with this SQL query:

select sum(bytes)/1024/1024 size_in_mb from dba_segments;

* Tables of up to 100 GB.

This is a soft limit, and Datastream will attempt to perform backfill on any table that you supply. However, we recommend
Expand All @@ -94,7 +88,7 @@ toolchain used in this tutorial.
## Notable behaviors and limitations

This section describes notable behaviors and limitations of the migration process. It is important for you to understand these behaviors and limitations and plan
ahead to avoid running into problems during the migration.
ahead to avoid running into problems during the migration. Refer to the [product documentation](https://cloud.google.com/datastream/docs/sources#oracleknownlimitations) for the most up-to-date information.

* **Primary key and ROWID**: We recommend that you have a primary key on all tables.

Expand All @@ -109,11 +103,9 @@ ahead to avoid running into problems during the migration.

* **Column support**:

* **Not supported**: Abstract DataTypes (ADT), Collections (VARRAY), LOB, UDT, CACHESYNC_MESSAGE, UROWID, ANYDATA, LONG, LONG RAW, XMLType.

These replicate as null values for their columns.
* Columns of data types ANYDATA, BLOB, CLOB, LONG/LONG RAW, NCLOB, UDT, UROWID, XMLTYPE aren't supported, and will be replaced with NULL values.

* BLOB and CLOB data types are limited to a maximum size of 4 kilobytes.
* For Oracle 11g, tables that have columns of data types ANYDATA or UDT aren't supported, and the entire table won't be replicated.

* Deferred constraints are converted to non-deferred constraints as part of the standard conversion. This can be customized by setting `FKEY_DEFERRABLE=0` in
the `ora2pg.conf` configuration file.
Expand Down