Oracle Autonomous Database Cloud 2019 Specialist.

Data Pump can exclude migration of objects like indexes and materialized views that are not needed by Autonomous Database.

Data Pump is platform independent - it can migrate Oracle Databases running on any platform.

Data Pump is faster to migrate database than using RMAN.

Data Pump creates the tablespaces used by your Autonomous Database.

UPDATE_OBJECT_INFO

MODIFY_SNAPSHOT_SETTINGS

CREATE_BASELINE_TEMPLATE

MODIFY_BASELINE_WINDOW_SIZE

Backing up the database.

Mask your sensitive data.

Patching the database.

Automatically optimize the workload.

The DBMS_CLOUD.PUT_OBJECT procedure copies a file from Cloud Object Storage to the Autonomous Data Warehouse.

The DBMS_CLOUD.CREATE_CREDENTIAL procedure stores Cloud Object Storage credentials in the Autonomous Data Warehouse database.

The DBMS_CLOUD.VALIDATE_EXTERNAL_TABLE procedure validates the source files for an external table, generates log information, and stores the rows that do not match the format options specified for the external table in
abadfile table on Autonomous Data Warehouse.

The DBMS_CLOUD.DELETE_FILE procedure removes the credentials file from the Autonomous Data Warehouse database.

The DBMS_CLOUD.CREATE_EXTERNAL_TABLE procedure creates an external table on files in the cloud. You can run queries on external data from the Autonomous Data Warehouse.

Online Indexing

Flashback Database

Real Application Clusters (RAC)

Java in the Database

Data Sync can connect to any jdbc compatible source like MongoDB, RedShift and Sybase.

Data Sync can use a normal OCI (thick) client connection to connect to an Oracle database.

Data Sync can load your data in parallel in order to speed up the loading process.

Data Sync has default drivers available that supported loading data from DB2, Microsoft SQL Server, MySQL and Teradata.

In addition to the Oracle Client Credential Wallet, a user must have a username and password in order to connect to the Autonomous Database.

The Oracle Client Credential file is downloaded as a ZIP file.

The Wallet for the Autonomous Database is the same as the Transparent Data Encryption (TDE) wallet.

You MUST have an Oracle Client Credential Wallet in order to connect to the Autonomous Database.

ADBDEV

ADMIN

DWROLE

ADWC

CREATE ANALYTIC MEASURE

CREATE ANALYTIC LEVEL

CREATE ANALYTIC HIERARCHY

CREATE ANALYTIC VIEW

CREATE ATTRIBUTE DIMENSION

Oracle GoldenGate

Transportable Tablespace

RMAN Restore

Oracle Data Pump

SQL*Loader

Autonomous Transaction Processing memory usage optimizes workloads for parallel joins and aggregations.

Autonomous Data Warehouse workloads are optimized for mixed workloads.

Autonomous Transaction Processing workloads are optimized for data warehouse, data mart, and data lake.

Data that is bulk loaded, by default, uses the row format in Autonomous Transaction Processing where Autonomous Data Warehouse data format is columnar.

Active transactions continue running unaffected.

Active transactions are paused.

Scaling cannot happen while there are active transactions in the database.

Active transactions are terminated and rolled back.

User with DWROLE can still access the database.

Tools are no longer able to connect to a stopped instance.

CPU billing is halted based on full-hour cycles of usage.

In-flight transactions and queries are stopped.

Click on the Autonomous Data Warehouse in the menu, click a database name, then Choose DB Connection button, then Download the Wallet.

Click on the Autonomous Data Warehouse section, pick a database, then Choose Actions, then Download the Wallet.

Find the Service Console for your Autonomous Database, then pick Administration, then Download the Client Credentials (Wallet).

Click on the Object Storage and find your Autonomous Bucket and Download the Wallet Credentials. E. Click the Compute section of the menu, then choose Instance Configurations, then Download Wallet.

Two. They are called ATP and ADW.

None. There are no pre-defined service names in tnsnames.ora.

Three. They are called high, medium and low.

Five. They are called tpurgent, tp, high, medium and low.

tnsnames.ora

keystore.jks

sqlnet.ora

cwallet.sso

ojdbc.properties

Data Sync can only load files into tables (insert-only), the customer has to write the additional code.

Data Sync can not transform your data while loading it into the destination table.

Data Sync can load a combination of data source, such as .csv, .xlsx and Oracle relational files.

Data Sync can only load data from one source into one destination table.

The migration can be technically a success but the 3-rd party vendor needs to support the result.

The suggested datapump version will create an alias for non-standard tablespace names so the migration is successful.

The tablespace names will result in a blocking error during datapump import because of ADB limitations.

The migration can be a success, both technically and functional due to datapump enhancements.

Migration to ADB is not possible using Golden Gate because the apply-process cannot be installed on ADB.

Only the migration to ADB is possible from an on-premise installation of Golden Gate.

Golden Gate on premise is not certified with ADB because Golden Gate Cloud Service exists for this.

The fallback scenario is not possible using Golden Gate because the capture-process cannot be installed on ADB.

The described scenario is correct, can be used for migration and fallback scenarios.

Place the credential files on a share drive that all users can use to connect to the database.

The Transparent Data Encryption (TDE) wallet can be used for your client credentials to connect to your database.

Store credential files in a secure location and share the files only with authorized users to prevent unauthorized access to the database.

When you share the credential files with authorized users, mail the wallet password and the file in the same email.

In the TEST phase of the wizard, a subset of accepted records is displayed based on your definition.

In the TEST phase of the wizard a list is generated containing the records that would be rejected during import.

In the Column Definition Phase, the system cross-references with the file-contents and shows the conflicts with the definition.

In the TEST phase, a temporary table will be populated with the records before inserting them in the destination table.

On the Autonomous Database Console.

SSH keys are not required in Oracle Cloud Infrastructure.

SSH keys cannot be added from console. They have to be added using REST APIs only.

Navigate to Identity, select Users panel on the console and select "Add Public Key".

You can call PL/SQL procedures and functions using a database link.

Connect from Autonomous Database to remote database using a database link.

Connect to Autonomous Database from remote database using a database link.

Create a database link from one Autonomous Database to another Autonomous Database instance.

Using Database Configuration Assistant (DBCA) on the database server.

It cannot be done.

Connecting to the Cloud Infrastructure Command console via SSH wallet.

Using the Oracle Cloud Infrastructure Command Line interface tool or REST API calls.

Autonomous Transaction Processing.

Autonomous Data Warehouse.

Neither service ignores hints by default.

Both services ignore hints by default.

Replicate the table using Golden Gate

Create a Data Set

Load data using Data Pump

Import Table

TDE but not Data Redaction.

Data Redaction and TDE are both supported.

Data Redaction but not TDE.

Neither Data Redaction nor TDE are supported.

One Year

7 days

60 days.

30 days

90 days

Data is encrypted at rest using transparent data encryption.

Network connections from clients to Autonomous Database are encrypted using the client credentials wallet.

Users are given OS logons or SYSDBA privileges to prevent phishing attacking.

Oracle automatically applies security updates to ensure data is not vulnerable to known attack vectors.

XML

TXT

JSON

SQL

ASCII

Autonomous Databases monitoring for usage and query performance.

Creating schemas.

Creating and scaling of Autonomous Database service.

Wizard to download connection wallet for connection from desktop tools.

SCOTT

ADMIN

SYS

DWDEV

A "POST" REST call

A "PUT" REST call

An "INSERT" REST call

A "GET" REST call

AIX

Linux

Windows

Solaris

VALIDATE_LEVELS

VALIDATE_HIERARCHY

VALIDATE_DIMENSION

VALIDATE_ANALYTIC_VIEW

VALIDATE_MEASURES

Backups

Firmware Patching

Data Loading

Database Upgrades

Application User Creation

Since the application needs to be highly available, it should to be deployed on a Kubernetes Cluster.

ADW since operational reporting is a higher priority in this scenario.

It is best to build a separate data warehouse, and move the OLTP data on a nightly basis.

ATP. Using 'tpurgent' and 'high' TNS services to separate connection types.

HIGH

TP

MEDIUM

TPURGENT

The source file can be in either Oracle Standard Storage or Oracle Archive Storage bucket in the Object Store.

The source files can reside in Oracle Object Storage, Amazon S3 Object storage, or Azure Blob storage.

A valid credential must be created prior to running the DBMS_CLOUD.COPY_DATA procedure.

The source file will be automatically removed after the DBMS_CLOUD.COPY_DATA procedure finishes successfully.

The target table will be created in Autonomous Database if it does not already exist.

In Autonomous Data Warehouse direct access to the database node and the local file system is allowed.

Degree of parallelism for SQL statements is set based on the number of OCPUs in the system and the database service the user is connecting to.

Adding, removing, or modifying tablespaces is allowed.

Compression is not enabled by default and you must specify the compression method for your tables with the compression clause in your CREATE TABLE and ALTER TABLE commands.

Transparent Data Encryption

Encrypted Database Links

SQL Net Encryption

One SYSDBA account

Read Only access to OS Audit logs

Original Import/Export tools

Physical migration method like database cloning

Data Pump

RMAN backup & restore

An OCI region is a localized geographic area, and an availability domain is one or more data centers located within a region.

Because availability domains do not share infrastructure such as power or cooling, or the internal availability domain network, a failure at one availability domain within a region is unlikely to impact the availability of the others within
thesame region.

A single fault domain can be associated with multiple regions and availability domains.

Regions are dependent on other regions and must be located with 5 thousand kilometers of each other.

through the Oracle Cloud Infrastructure service console

through SQL/Developer

using DBMS_CLOUD_ADMIN package

through SQLPIus

TPURGENT

MEDIUM

HIGH

TPPERFORMANT

LOW

Storage in TB cannot be larger than the number of OCPUs.

OCPUs and storage must remain in sync.

Increasing OCPUs will automatically increase storage.

OCPUs and storage can be scaled independently.

Backup and recovery must be done using Recovery Manager(RMAN).

Select the snapshot of the backup.

Select the archived redo logs.

Select the backup from which restore needs to be done.

Specify the point in time (timestamp) to restore.

Database name

Service name

Wallet file

Username and password

Golden Gate

Recovery Manager (RMAN)

CSV files copied to Autonomous Database block storage

Data Pump

Terraform

REST API

Dlocker

Enterprise Manager

Create, Query, Update, List, Start

Create, Get, List, Stop, Restore

Start, Delete, Update, Query, Stop

Create, Query, List, Stop, Restore

Use DBMS_CLOUD_ADMIN package

SQL/Developer

Oracle Cloud Infrastructure Console

Client tools

SQL Developer can be used to export/move/import of a database to ADB in 1 set of wizard steps.

SQL Developer can import files (.dmp and .csv for example) into ADB which are located on Amazon S3 Object storage.

SQL Developer can import .csv files into ADB which are located on the system where SQL Developer is running.

SQL Developer can only export/move/import files using datapump from databases running on Linux systems.

18.1 onwards

Any version

17.4 onwards

12c Release 2 onwards

Pluggable databases cannot be migrated to ADB using plug, unplug or clone.

Create a database link from source database to the ADB environment and clone the PDB.

Unplug to an xml file so database files and xml file can be uploaded to object storage.

Unplug into a pdb archive which can be uploaded to object storage.

Create Oracle Machine Learning User

Create workspaces

Create Notebooks

Run SQL Scripts

Create projects

Memory

Concurrency

Sessions

Parallelism

Storage

If "Dependents" is checked as a DDL Option, for non-privileged users, only dependent objects in their schema are exported.

Export DDL includes features such as "Show schema," "Storage," and "Terminator."

If "Grants" is checked as a DDL Option, GRANT statements are included for any grant objects on the exported objects, including those owned by the SYS schema.

If "Clipboard" is selected as the "Output," the output will be placed on the system clipboard, so that it can be pasted into a file, a command line, or other location appropriate for the format.

TNSNAMES.ORA

CWALLET.SSO

OJDBC.PROPERTIES

SQLNET.ORA

Medium provides intermediate resource and concurrency, and queries run in a serial.

Low provides highest concurrency, lowest resources, and DoP =1.

High provides highest resources, lowest concurrency, and DoP is 1.

High provides highest concurrency and lowest resources, and DoP is 1.