Connect to Azure SQL Managed Instance using a SQL client, and then complete
the following steps:
Create a GGADMIN user:
CREATE login GGADMIN with password = 'W3lcome@1234'
Create user GGADMIN for login GGADMIN
ALTER SERVER ROLE sysadmin ADD MEMBER GGADMIN
Note:
The
sysadmin role is only required to add TRANDATA
and Heartbeat tables. You can then remove
the sysadmin privileges and instead use db_owner: ALTER ROLE
db_owner ADD MEMBER GGADMIN;
Create a database:
Create database SRC_OCIGGLL
Disconnect and reconnect as the newly created user
(GGADMIN) and database
(SRC_OCIGGLL).
Enable Change Data Capture (CDC) at the database level:
In the Oracle Cloud console, select your ATP instance from the
Autonomous Databases page to view its details.
Click Database Actions.
Unlock the GGADMIN user:
Under Administration, click Database
Users.
Locate GGADMIN, and then click its ellipsis
menu (three dots) and select Edit.
In the Edit User panel, enter the GGADMIN password,
confirm the password, and then deselect Account is
Locked.
Click Apply Changes.
Load the target sample schema and data:
From the Database Actions menu, under
Development, select SQL.
Copy and paste the script from
OCIGGLL_OCIGGS_SETUP_USERS_ADW.sql into the
SQL worksheet.
Click Run Script. The Script Output tab
displays confirmation messages.
Clear the SQL worksheet and then copy and paste the
SQL from
OCIGGLL_OCIGGS_SRC_MIRROR_USER_SEED_DATA.sql.
To verify that the tables were created
successfully, close the SQL window and reopen it again. In the
Navigator tab, look for the SRC_OCIGGLL schema
and then select tables from their respective dropdowns.
Task 1: Create the OCI GoldenGate
Resources
This quickstart example requires deployments and connections for both
the source and target.
Create deployments for the
source SQL Server and target Oracle database.
Create the Initial Load and Change Data Capture Extracts.
On the Deployments page, select the SQL Server deployment created in Task
1.
On the deployment Details page, click Launch Console.
Sign in to the source SQL Server deployment console using the Administrator
credentials specified when you created the deployment in Task 1.
Add transaction information
In the navigation menu, click DB Connections, then the source
database, and then TRANDATA.
On the Trandata page, click Add TRANDATA (plus icon).
In the Add Trandata panel, for Schema Name, enter
SRC_OCIGGLL, and then click Submit.
Tip:
The screen will not refresh on submit. To confirm the
TRANDATA was added, enter the SRC_OCIGGLL into the
search field and then click Search.
SRC_OCIGGLL is returned and 6 tables are
prepared for instantiation.
Next, in the navigation menu, select Tasks, then Purge Change Data and complete the following:
Click on the Add Purge Change Data (add icon).
Enter a name.
Click Submit.
Add the Initial Load Extract.
On the Extracts page, click Add Extract (plus icon), and then
complete the form as follows:
On the Extract Information
page:
For Extract
type, select Initial
Load.
For Process Name, enter
EIL.
Click Next.
On the Paramter File page, replace MAP *.*,
TARGET *.*; with the following:
TABLE SRC_OCIGGLL.*;
Click Create and Run.
You return to the Extracts page, where it may take a moment for the
Extract to start. You can then select the Extract to review its details and
review the Report file. It lists all the tables and the number of exported
records for each.
Add the Integrated Extract.
In the navigation menu, click Extracts.
On the Extracts page, click Add Extract (plus icon), and then
complete the form as follows:
On the Extract Information page:
For Extract
type, select Change Data
Capture.
For Process Name, enter
ECDC.
Click Next.
On the Extract Options page:
For Source credentials, select the Doman
and Alias of your source database.
For Extract Trail Name,
enter a two-character name, such as
C1.
Click Next.
On the Paramter File page, replace MAP *.*, TARGET
*.*; with the following:
TABLE SRC_OCIGGLL.*;
Click Create and Run.
Task 3: Create the Distribution Paths
If using GoldenGate credential store, create a user for the Distribution Path in the target Oracle deployment, and a
Path Connection in the source SQL Server deployment. If using IAM credential
store, skip this step.