1 Overview
You can migrate the data from an on-premises database associated with Oracle Fusion Middleware 12.2.1.4.0 domain to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database in Oracle Cloud Infrastructure.
You can gain several advantages by moving data to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database.
- Why Migrate to an ATP-S database
Migration to Oracle Autonomous Transaction Processing-Shared (ATP-S) database simplifies your database provisioning, maintenance, and management operations. - Database Migration Terminology
- Migration Approaches
For all Oracle Fusion Middleware products certified with ATP-S database, you can migrate data using Database Migration (DMS) service. However, if you do not have access to the DMS service, then only for Oracle Identity Governance (OIG) and Oracle Access Manager (OAM), you can migrate data using Data Pump.
Why Migrate to an ATP-S database
Migration to Oracle Autonomous Transaction Processing-Shared (ATP-S) database simplifies your database provisioning, maintenance, and management operations.
You can have your own shared infrastructure in the Oracle Cloud, a Private Database Cloud within the Oracle Public Cloud. You can run your cloud instance without sharing your hardware with other cloud users, and Oracle’s cloud management software also can run on different hardware, further isolating it from security threats and malicious users.
An Oracle Fusion Middleware Infrastructure and the following Oracle Fusion Middleware products are certified with ATP-S database:
- Oracle Data Integrator
- Oracle Enterprise Data Quality
- Oracle Enterprise Scheduler
- Oracle Forms and Reports
- Oracle GoldenGate Veridata
- Oracle HTTP Server
- Oracle Identity Management Suite
- Oracle Internet Directory
- Oracle Access Manager
- Oracle Identity Manager
Note:
Oracle Identity Manager is also referred to as Oracle Identity Governance.
- Oracle Managed File Transfer
- Oracle SOA Suite and Oracle Business Process Management
- Oracle WebCenter Content
- Oracle WebCenter Portal
- Oracle WebCenter Sites
- Oracle WebLogic Server
Parent topic: Overview
Database Migration Terminology
The following concepts are essential for working with Database Migration.
- Migration
- Represents a single migration operation and contains the specifications by which the migration should run. Migration specifications include whether or not to perform bulk data copy, and/or capture ongoing changes, and the source and target database selections.
- Migration Job
- Represents an active or past migration execution. A migration job is created implicitly when you start a migration. A migration job is a snapshot with runtime information about the migration. You use this information to audit logs and investigate failures.
- Validation Job
- Validates the prerequisites and connectivity for source and target databases, Oracle GoldenGate instances, and Oracle Data Pump. A validation job is created when you evaluate the migration.
- Registered Database
- Represents a database instance, containing the database metadata and connection details. A data asset can have one or many connections to include all schemas within a database that need to be migrated. The registered database is also called a Connection in the APIs
- Schema
- Organizational concepts of databases to hold database objects such as tables, views, stored procedures, and so on.
Parent topic: Overview
Migration Approaches
For all Oracle Fusion Middleware products certified with ATP-S database, you can migrate data using Database Migration (DMS) service. However, if you do not have access to the DMS service, then only for Oracle Identity Governance (OIG) and Oracle Access Manager (OAM), you can migrate data using Data Pump.
See the following topics:
Parent topic: Overview