1. On the Overview page in the Oracle Data Safe service, find the Oracle Databases on Compute tile and click Start Wizard. The wizard displays the Data Safe Target Information form.
2. Select either ORACLE CLOUD INFRASTRUCTURE or AWS OR OTHER CLOUD ENVIRONMENT.
3. If you selected ORACLE CLOUD INFRASTRUCTURE then at SELECT COMPUTE INSTANCE, select the OCI compute instance on which your database is running. If your compute instance does not reside in the compartment shown, click CHANGE COMPARTMENT, then locate and select the compute instance.
   This field does not appear if you select OTHER CLOUD ENVIRONMENT.
4. At DATA SAFE TARGET DISPLAY NAME, enter a target display name that is meaningful to you. Data Safe uses this name in its reports. All characters are accepted. The maximum number of characters is 255.
5. At COMPARTMENT, select the compartment where you want to store the target database. If you want to register the database in a compartment other than the OCI compartment where the database is stored, select a different compartment from the drop-down list.
6. (Optional) In the DESCRIPTION field, add a description that is meaningful to you.
7. At DATABASE SERVICE NAME, enter the service name of the PDB or CDB.
8. If you selected AWS OR OTHER CLOUD ENVIRONMENT, then at DATABASE IP ADDRESS, enter the IP address of the database.
   This field does not appear if you select ORACLE CLOUD INFRASTRUCTURE.
9. At DATABASE PORT NUMBER, enter the port number of your database listener.
10. Perform this step if you did not already grant roles to the database user in the preregistration tasks.
    Click Download Privilege Script and save the datasafe_privileges.sql script to your computer. The script includes instructions on how to use it to grant privileges to the Oracle Data Safe service account on your target database. You should also refer to the preregistration task Grant Roles to the Oracle Data Safe Service on a Non-Autonomous Database for some additional details.
11. At Database user name and Database password, enter the name and password of the user you created in the preregistration tasks. If the user name is mixed case, enclose it in double-quotes (" ").
    Oracle Data Safe uses this account to connect to the database.
12. Optionally, click Show advanced options to tag the notification.
    1. Click Add tag to create an additional optional tag to organize and track resources in your tenancy.
    2. Select a Tag namespace from the drop-down list.
    3. Provide a Tag key and Tag value.
13. Click Next.

1. At Choose a connectivity option, click either On-Premises Connector or Private Endpoint.

   Note:

   If you select Private Endpoint, then if the database is configured with a private IP address and an Oracle Data Safe private endpoint is already configured for the VCN of the database, that private endpoint is automatically selected. (You can have only one Oracle Data Safe private endpoint per VCN.)
2. At TCP/TLS, select the network protocol.
   If you select the TLS protocol and choose Private Endpoint, then you are presented with two options: One way TLS and Mutual TLS. If you select One way TLS, then do the following:

   • Upload the TrustStore of your database in the format of PEM file, PKCS#12 wallet, or JKS wallet and optionally, enter the wallet password. This file is required whether client authentication is enabled or disabled on your target database.

   If you select Mutual TLS, then do the following:

   • Upload the TrustStore of your database in the format of PEM file, PKCS#12 wallet, or JKS wallet and enter the wallet password. This file is required whether client authentication is enabled or disabled on your target database.
   • When client authentication is enabled on your target database, upload the KeyStore of your database in the format of PEM file, PKCS#12 wallet, or JKS wallet. This file is not required when client authentication is disabled.
   If you select TCP at TCP/TLS, you are not prompted for any additional details.
3. If you chose On-Premises Connector in Step 1, then at DO YOU WANT TO USE AN EXISTING ON-PREMISES CONNECTOR?, click YES or NO. If you select YES, then from SELECT ON-PREMISES CONNECTOR, use the drop-down menu to select the on-premises connector that you want to use. If you select NO, the wizard prompts for basic information it needs to create a new on-premises connector for the target database.
4. If instead you chose Private Endpoint in Step 1, then at DO YOU WANT TO USE AN EXISTING PRIVATE ENDPOINT?, click YES or NO. If you select YES, then from SELECT PRIVATE ENDPOINT, use the drop-down menu to select the private endpoint that you want to use. If you select NO, the wizard prompts for basic information it needs to create a new private endpoint for the target database. The private endpoint needs to be in a VCN that can access your on-premises database.
5. At COMPARTMENT use the drop-down menu to select the compartment where you want to store the on-premises connector or private endpoint.
6. At NAME, provide a name of your choice.
7. At DESCRIPTION, enter a description.
8. Click Next.
   If you selected Private Endpoint in Step 1, the wizard proceeds to Step 3: Add Security Rule.
   If you selected On-Premises Connector in Step 1, the wizard bypasses Step 3: Add Security Rule and takes you directly to Step 4: Review and Submit.

If you're registering an Active Data Guard associated database then you can add the standby databases at this step. If you're not registering an Active Data Guard associated database, then skip this step by clicking Next.

1. Click Add row on the Add additional Data Guard peer database(s) (Optional) page.

   It is also possible to register standby databases after the primary database has been registered. See Manage Peer Databases Associated with a Registered Active Data Guard Primary Database for more information.

2. Enter the following information for the peer databases:
   • Peer display name
   • Database service name
   • Database IP address
   • Database port number
   • TCP/TLS
3. Add more peer databases by clicking Add row.
4. Click Next.

   If you selected Private Endpoint in Step 1, the wizard proceeds to Step 4: Add security rules.

   If you selected On-Premises Connector in Step 1, the wizard takes you directly to Step 5: Review and submit.

1. At Do you want to add the security rules now? , select either Yes or No.
   If you select No, you can then click Next to bypass the security rules configuration and proceed to Review and Submit. You can configure the security rules later in the Oracle Cloud Infrastructure Console (under Networking). You may want to skip this step now if you already have security rules that you want to apply. Note that the target database remains inactive in Oracle Data Safe until the security rules are configured either in the Oracle Data Safe wizard or in the Oracle Cloud Infrastructure console.
2. If you select Yes, then at Add Ingress Security Rule, select either Security List or Network Security Group. Then use the drop-down menu to select the Security List or Network Security Group to which you want to add the ingress rule.
   In the Ingress Rule tile, the wizard shows you the ingress rule to be added to the security list or network security group you selected.
3. At Add Egress Security Rule, select either Security List or Network Security Group.
4. At the next prompt, select the security list or network security group where you want to add the rule.

   Note:

   The same egress rule is created for the database and for each peer database.
5. Click Next to go to Review and Submit.

1. Review the information on this page.
2. If all of the settings are correct, click Register. If not, you can click Previous to redo any of the earlier steps, or click Cancel.