Oracle Autonomous Database Schema Advisor

Version 19.3

Date: Sep 2019

Table of Contents
DISCLAIMER ............................................................................................................................................................... - 3 -
INTENDED AUDIENCE ................................................................................................................................................... - 3 -
INTRODUCTION ........................................................................................................................................... - 4 -
ORACLE AUTONOMOUS DATABASE SCHEMA ADVISOR.................................................................................. - 4 -
INSTALLING THE ADVISOR ............................................................................................................................ - 4 -
SUPPORTED VERSIONS AND LICENSING ........................................................................................................................... - 4 -
DOWNLOAD............................................................................................................................................................... - 4 -
INSTALLATION STEPS ................................................................................................................................................... - 5 -
RUNNING THE ADVISOR ............................................................................................................................... - 6 -
ADVISOR OUTPUT ....................................................................................................................................................... - 7 -
SAMPLE REPORT FOR ATP ............................................................................................................................................ - 7 -
DE-INSTALLING THE ADVISOR ..................................................................................................................... - 13 -

Oracle Autonomous Database Schema Advisor -2-

Disclaimer
The following is intended to outline our general product direction. It is intended for information purposes
only and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing decisions. The development, release, and
timing of any features or functionality described for Oracle’s products remains at the sole discretion of
Oracle.

Intended Audience
Readers are assumed to have hands-on experience with Oracle Database technologies from the perspective of
a DBA or Data Administrator.

Oracle Autonomous Database Schema Advisor -3-

Introduction
Oracle is revolutionizing how data is managed with the introduction of the world’s first "self-driving"
database, the Oracle Autonomous Database. This ground-breaking Oracle Database technology automates
management to deliver unprecedented availability, performance, and security—at a significantly lower cost.

Autonomous Database is available exclusively through Oracle and is offered in two versions optimized to
meet the specialized requirements for Online Transaction Processing and Data Warehousing. Both use
machine learning and automation to eliminate complexity, human error, and manual management, helping to
ensure higher reliability, security, and more operational efficiency. Autonomous Transaction Processing
Service allows much simpler application development and deployment for enabling real-time analytics,
personalization, and fraud detection. Autonomous Data Warehouse delivers unprecedented reliability,
performance, and highly elastic data management that enables data warehouse deployment in seconds.

You can directly migrate your Oracle Database to the Oracle Autonomous Database and into different target
deployments on the Oracle Cloud depending on your requirements and business needs. Oracle provides a
well-defined set of tools for this purpose that not only allow you assess the existing databases, but also tools
to perform the actual migration in a hands-free and automated approach.

Oracle Autonomous Database Schema Advisor

The very first task that you would perform prior to the migration is to analyze the current Oracle Databases
and report any concerns that may arise during the migration. The ADB Schema Advisor is a light-weight
utility that analyzes the on-premise or cloud Oracle Database schemas for the suitability of migration to the
Autonomous Database. The Advisor discovers the schema objects and performs deep analysis to highlight is
any differences exist when the object gets created on Oracle Autonomous Data Warehouse or Oracle
Autonomous Transaction Processing database.

The Advisor will run on pre-existing Schema and generates a report that highlights :

• The counts of discovered objects and a summary of migration status.

• Objects that cannot be migrated to the Autonomous Database due to the restrictions and
lockdowns imposed by the Autonomous Database on certain data types, Database options and
SQL statements/clauses.
• The Objects that will migrate with modifications that are automatically done during the import
process or upon the execution of object creation DDL.
• Informational section containing certain best practice recommendations and guidance

Advisor’s output is described in detail in the Advisor Output section below.

Installing the Advisor

Supported Versions and Licensing
The Advisor can be installed on Oracle Database Version 11.2.0.4 and above. Currently there is no license
required to download and run the Advisor.

Download
Download the Advisor PL/SQL Package from the MOS Note 2462677.1

Oracle Autonomous Database Schema Advisor -4-

Installation Steps
1. Create a User in the same Database or the PDB as the schema that will be analyzed:
CREATE USER ADB_ADVISOR IDENTIFIED by <password> DEFAULT TABLESPACE <tablespace>;

Note: You may choose a different user name if you like.

2. Grant the following privileges to ADB_ADVISOR User:

GRANT CREATE SESSION, CREATE PROCEDURE TO ADB_ADVISOR;

GRANT SELECT ON V_$VERSION TO ADB_ADVISOR;

GRANT SELECT ON V_$PARAMETER TO ADB_ADVISOR;

GRANT SELECT ON V_$INSTANCE TO ADB_ADVISOR;

GRANT SELECT ON V_$DATABASE TO ADB_ADVISOR;

GRANT SELECT ON NLS_DATABASE_PARAMETERS TO ADB_ADVISOR;

GRANT SELECT ON DBA_LOBS TO ADB_ADVISOR;

GRANT SELECT ON DBA_INDEXES TO ADB_ADVISOR;

GRANT SELECT ON DBA_OBJECTS TO ADB_ADVISOR;

GRANT SELECT ON DBA_SYNONYMS TO ADB_ADVISOR;

GRANT SELECT ON DBA_DEPENDENCIES TO ADB_ADVISOR;

GRANT SELECT ON DBA_TABLES TO ADB_ADVISOR;

GRANT SELECT ON DBA_TAB_COLS TO ADB_ADVISOR;

GRANT SELECT ON DBA_CONSTRAINTS TO ADB_ADVISOR;

GRANT SELECT ON DBA_DB_LINKS TO ADB_ADVISOR;

GRANT SELECT ON DBA_PROFILES TO ADB_ADVISOR;

GRANT SELECT ON DBA_USERS TO ADB_ADVISOR;

GRANT SELECT ON DBA_TYPES TO ADB_ADVISOR;

GRANT SELECT ON DBA_TAB_PARTITIONS TO ADB_ADVISOR;

GRANT SELECT ON DBA_TAB_SUBPARTITIONS TO ADB_ADVISOR;

GRANT SELECT ON DBA_EXTERNAL_TABLES TO ADB_ADVISOR;

GRANT SELECT ON DBA_SEGMENTS TO ADB_ADVISOR;

GRANT SELECT ON DBA_MVIEW_LOGS TO ADB_ADVISOR;

GRANT SELECT ON DBA_FEATURE_USAGE_STATISTICS TO ADB_ADVISOR;

Oracle Autonomous Database Schema Advisor -5-

Grant the following when you have Oracle XML DB installed:
GRANT SELECT ON DBA_XML_TABLES TO ADB_ADVISOR;

GRANT SELECT ON DBA_XML_TAB_COLS TO ADB_ADVISOR;

GRANT SELECT ON DBA_XML_SCHEMAS TO ADB_ADVISOR;

Also grant the following when installing in Database 12c and later:
GRANT SELECT ON DBA_ILMOBJECTS TO ADB_ADVISOR;

3. Install the Advisor PL/SQL Package using a SQL*Plus session:

$> sqlplus ADB_ADVISOR/<password> @adb_advisor.plb

4. Check for errors:

SQL> SHOW ERRORS;

Running the Advisor

Follow the steps outlined below to generate the ADB Schema Advisor report:

1) Start a SQL*Plus session as the ADB_ADVISOR user:

SQL> CONNECT ADB_ADVISOR/<password>

2) Setup the SQL*Plus environment:

SQL> SET SERVEROUTPUT ON FORMAT WRAPPED

SQL> SET LINES 200

3) Generate the Advisor report by executing ADB_ADVISOR package:

SQL> EXEC ADB_ADVISOR.REPORT(schemas=>'<List of Schemas>', adb_type=>'<adb_type>');

Where <List of Schemas> is a comma separated list of Schemas that you like to analyze, and <adb_type> is one
of the following migration destinations:

• 'ATP' for Autonomous Transaction Processing (Serverless)

• 'ADW' for Autonomous Data Warehouse (Serverless)
• 'ATPD' for Autonomous Transaction Processing (Dedicated)
• 'ADWD' for Autonomous Data Warehouse (Dedicated)

Note: You may specify a maximum of 30 schemas in a single advisor run.

4) For example, to generate an Advisor report for SH, HR and SCOTT schemas when the target ADB type is an
Autonomous Transaction Processing (Dedicated), run the following command:

Oracle Autonomous Database Schema Advisor -6-

SQL> EXEC ADB_ADVISOR.REPORT(schemas => 'SH, HR, SCOTT', adb_type => 'ATPD');

Advisor Output
The report has 4 sections (see Sample Report for ATP):

• Section 1: Summary Section with object counts

• Section 2: List of objects that will not migrate to ADB
• Section 3: List of objects that will migrate with changes
• Section 4: Informational section and migration guidelines

Sample Report for ATP

======================================================================================
== ATPD SCHEMA MIGRATION REPORT FOR SH2,XDB
======================================================================================

Instance Name : orcl

Database Name : ORCL
Host Name : localhost.localdomain
Database Version : 19.0.0.0.0
Pluggable Database: PDB1
Schemas Analyzed : SH2,XDB
Analyzing for : Autonomous Transaction Processing (Dedicated)
Report date : 19-SEP-2019 15:49

--------------------------------------------------------------------------------------
-- ATPD MIGRATION SUMMARY
--------------------------------------------------------------------------------------

Objects Total
Object Objects Migrated Objects
Object Type Count Not Migrated With Changes Migrated
------------------------- -------------- -------------- -------------- -----------
CLUSTER 1 0 0 1
CONSTRAINT 163 0 0 163
DATABASE LINK 1 0 0 1
FUNCTION 6 0 0 6
INDEX 103 0 0 103
INDEX PARTITION 6 0 0 6
INDEXTYPE 2 0 0 2
LIBRARY 20 0 0 20
OPERATOR 7 0 0 7
PACKAGE 52 0 0 52
PACKAGE BODY 50 0 0 50
PROCEDURE 6 2 0 4
QUEUE 2 0 0 2
SEQUENCE 5 0 0 5
SYNONYM 3 2 0 1
TABLE 86 14 14 72
TABLE PARTITION 20 0 4 20
TABLE SUBPARTITION 80 0 17 80
TRIGGER 8 0 0 8
TYPE 97 0 0 97
TYPE BODY 5 0 0 5
VIEW 11 2 0 9

Oracle Autonomous Database Schema Advisor -7-

XML SCHEMA 44 0 0 44
XMLTYPE TABLE 25 21 0 4
XMLSCHEMA 17 17 0 0
User Objcts in SYS/SYSTEM 6 6 0 0

--------------------------------------------------------------------------------------
-- ATPD OBJECTS NOT MIGRATED
--------------------------------------------------------------------------------------

1. XMLType Tables will not migrate (Count=21):

----------------------------------------------
Note: XMLType Tables with CLOB or Object-Relational storage is not supported in
Autonomous Database. Use the BINARY storage option instead.

SH2.XMLTYPE_CLOB XDB.XDB$SIMPLE_TYPE
XDB.XDB$COMPLEX_TYPE
XDB.XDB$ALL_MODEL XDB.XDB$CHOICE_MODEL
XDB.XDB$SEQUENCE_MODEL
XDB.XDB$ELEMENT XDB.XDB$ATTRIBUTE
XDB.XDB$ANYATTR
XDB.XDB$ANY XDB.XDB$GROUP_DEF
XDB.XDB$GROUP_REF
XDB.XDB$ATTRGROUP_DEF XDB.XDB$ATTRGROUP_REF
XDB.XDB$SCHEMA
XDB.XDB$RESOURCE XDB.XDB$ACL
XDB.XDB$RESCONFIG
XDB.XDB$STATS XDB.XDB$CONFIG
SH2.PurchaseOrder51_TAB

2. Tables with XMLType Columns will not migrate (Count=3):

----------------------------------------------------------
Note: Tables with XMLType columns defined with CLOB or Object-Relational storage
are not supported in Autonomous Database. Use the BINARY storage option instead.

SH2.PO_XML_TAB XDB.XDB$DXPTAB
XDB.XDB$XTAB

3. XML Schema Objects will not migrate (Count=17):

--------------------------------------------------
Note: XML Schemas are not supported in Autonomous Database.

XDB.http://xmlns.oracle.com/xdb/XDBSchema.xs
XDB.http://xmlns.oracle.com/xdb/XDBResource. XDB.http://www.w3.org/2001/csx.xml.xsd
XDB.http://xmlns.oracle.com/xdb/csx.xmltr.xs XDB.http://xmlns.oracle.com/xdb/acl.xsd
XDB.http://xmlns.oracle.com/xdb/dav.xsd
XDB.http://xmlns.oracle.com/xdb/XDBResConfig
XDB.http://xmlns.oracle.com/xdb/XDBStandard. XDB.http://www.w3.org/2001/xml.xsd
XDB.http://xmlns.oracle.com/xdb/xmltr.xsd XDB.http://www.w3.org/1999/xlink.xsd
XDB.http://www.w3.org/1999/csx.xlink.xsd
XDB.http://www.w3.org/2001/csx.XInclude.xsd XDB.http://xmlns.oracle.com/xdb/stats.xsd
XDB.http://xmlns.oracle.com/xdb/XDBFolderLis
XDB.http://xmlns.oracle.com/xdb/xdbconfig.xs
SH2.http://xmlns.oracle.com/xdb/documentatio

4. Tables with Media data types will not migrate (Count=11):

------------------------------------------------------------
Note: Columns with Media data types are not allowed in Autonomous Database. Consider
using SecureFiles LOB as Oracle Multimedia is desupported in 19c.

SH2.MEDIA_TAB1 SH2.MEDIA_TAB10
SH2.MEDIA_TAB11
SH2.MEDIA_TAB2 SH2.MEDIA_TAB3
SH2.MEDIA_TAB4

Oracle Autonomous Database Schema Advisor -8-

SH2.MEDIA_TAB5 SH2.MEDIA_TAB6
SH2.MEDIA_TAB7
SH2.MEDIA_TAB8 SH2.MEDIA_TAB9

5. User-defined objects in SYS and SYSTEM schemas will not migrate (Count=6):
-----------------------------------------------------------------------------
Note: User-defined objects were detected in SYS/SYSTEM schemas. Consider moving them
out prior to the migration.

Object Owner Object Type Object Name

-------------------- -------------------- ------------------------------
SYS DATABASE LINK SYS_HUB
SYS DIRECTORY MY_DIR
SYS LOB PARTITION SYS_LOB0000014863C00016$$
SYS LOB PARTITION SYS_LOB0000014863C00016$$
SYS LOB PARTITION SYS_LOB0000014863C00016$$
SYS VIEW QT73724_BUFFER

6. Objects that depend on user-defined objects in SYS and SYSTEM schemas will also not
migrate (Count=6):
--------------------------------------------------------------------------------------
-------------------
Note: Consider moving the user-defined objects in SYS and SYSTEM schemas prior to
migration. The following objects of the schemas being analyzed directly or indirectly
depend on those objects:

Object Owner Object Type Object Name Referenced

Owner Referenced Type Referenced Name
-------------------- -------------------- ------------------------------ ----------
---------- -------------------- ------------------------------
SH2 PROCEDURE ACCESSES_SYS_OBJECT_DIRECT SYS
VIEW QT73724_BUFFER
SH2 PROCEDURE ACCESSES_SYS_OBJECT_VIA_SYNONY SH2
SYNONYM BUFFER_SYN
SH2 SYNONYM BUFFER_SYN SYS
VIEW QT73724_BUFFER
SH2 SYNONYM MY_DIR_SYN SYS
DIRECTORY MY_DIR
SH2 VIEW VIEW_ACCESS_SYS_OBJECT_DIRECT SYS
VIEW QT73724_BUFFER
SH2 VIEW VIEW_ACCESS_SYS_OBJECT_SYNONYM SH2
SYNONYM BUFFER_SYN

--------------------------------------------------------------------------------------
-- ATPD OBJECTS MIGRATED WITH CHANGES
--------------------------------------------------------------------------------------

1. BASICFILE LOBs will be changed to SECUREFILE LOBs (Count=8):

---------------------------------------------------------------
Note: Table has BASICFILE LOBs. All Basicfile LOBs will be automatically converted
to SECUREFILE LOBs at import time.

SH2.LOCATIONS_IOT SH2.MEDIA_TAB1
SH2.MEDIA_TAB10
SH2.MEDIA_TAB2 SH2.MEDIA_TAB3
SH2.MEDIA_TAB4
XDB.XDB$H_INDEX XDB.XDB$XIDX_IMP_T

2. NOLOGGING storage attribute will be changed to LOGGING (Count=22):

--------------------------------------------------------------------
Note: Table, Partition or Subpartition created with NOLOGGING will automatically
be created in ATP and ADW as LOGGING.

Oracle Autonomous Database Schema Advisor -9-

SH2.SALES_NOLOG(TABLE=1) SH2.SALES_PART_NOLOGGING(PARTS=2)
SH2.SALES_SUBPARTITIONS(PARTS=2)
SH2.SALES_SUBPARTITIONS(SUBPARTS=16) XDB.XDB$XIDX_IMP_T(TABLE=1)

3. External Table will be created as regular table (Count=1):

-------------------------------------------------------------
Note: Consider using DBMS_CLOUD package on ADB to create External Tables that use
Cloud Object Storage. If you try to create a non-Cloud Object Storage External table,
it will be created as a non-External table.

SH2.COUNTRIES_EXT

4. Index Organized table will be created as regular table (Count=3):

--------------------------------------------------------------------
Note: Index Organized tables are disallowed in ADB. When you create an IOT in ADB,
the table gets created as non-IOT (regular table). When the Data Pump export file
contains tables with IOT, use 'dwcs_cvt_iots:y' transformation at import time to
transform IOTs are regular tables.

SH2.DR$MYINDEX$N SH2.DR$MYINDEX3$N
SH2.LOCATIONS_IOT

5. Table Cluster will be created as regular table (Count=1):

------------------------------------------------------------
Note: Table Clusters are disallowed in ADB. When you create a table with a CLUSTER
clause on the ADB, the table gets created as a regular table.

SH2.EMPLOYEES_CLUST

6. INMEMORY Tables will be created as regular tables (Count=2):

---------------------------------------------------------------
Note: Database In-Memory is not enabled in ADB. All In-Memory tables and partitions
will be created with NO INMEMORY clause.

SH2.DBIM_ONETAB (TABLE=1) SH2.QUARTERLY_REGIONAL_SPART_INMEM

(SUBPARTS

--------------------------------------------------------------------------------------
-- ATPD MIGRATION ADDITIONAL INFO
--------------------------------------------------------------------------------------

1. Parallel DEGREE > 1 specified on INDEX (Count=1):

----------------------------------------------------
Note: If a PARALLEL clause is specified on the index in your current database, it
remains with the index when it gets created, via data pump or manual, in both ATP
Serverless and Dedicated. This can lead to SQL statements running in parallel
unbeknownst
to the end user. To specify serial execution, change the INDEX parallel clause to
NOPARALLEL or set the PARALLEL degree to 1.

SH2.SALES_NOPART_PAR32_IDX1

2. Columns are defined using BYTE semantics in a single-byte DB characterset

(Count=423):
--------------------------------------------------------------------------------------
Note: Characterset used by the Autonomous Database is AL32UTF8 (Multi-byte). But
if you create a table with a column that uses BYTE semantics, it may not allow you
to fit all characters as "Multi-byte" needs more bytes to store one character. Ensure
that your BYTE columns are transformed to CHARACTER semantics before the migration
as Oracle Data Pump currently does not do this.

Oracle Autonomous Database Schema Advisor - 10 -

SH2.CONTEXTDOCS_TAB (COLS=1) SH2.DR$MYINDEX3$N (COLS=1)
SH2.MYTABLE1 (COLS=1)
SH2.QUARTERLY_REGIONAL_SPART_INMEM (COLS=2) XDB.X$NM46MP5MEPA004NE0KWN0SK0K1LN
(COLS=1) XDB.XDB$ANY (COLS=14)
XDB.XDB$COMPLEX_TYPE (COLS=49) XDB.XDB$D_LINK (COLS=1)
XDB.XDB$H_LINK (COLS=1)
XDB.XDB$SEQUENCE_MODEL (COLS=3) XDB.XDB$XIDX_PART_TAB (COLS=3)
XDB.XDB$XTABCOLS (COLS=1)
XDB.JSON$USER_COLLECTION_METADATA (COLS=5) XDB.XDB$ROOT_INFO_V (COLS=10)
SH2.VIEW_ACCESS_SYS_OBJECT_DIRECT (COLS=6)
SH2.MEDIA_TAB11 (COLS=1) SH2.MYTABLE_TEXT (COLS=1)
XDB.XDB$ATTRGROUP_DEF (COLS=3)
XDB.XDB$IMPORT_QN_INFO (COLS=1) XDB.XDB_INDEX_DDL_CACHE (COLS=11)
XDB.RESOURCE_VIEW (COLS=1)
SH2.MEDIA_TAB10 (COLS=8) SH2.MEDIA_TAB4 (COLS=8)
SH2.MEDIA_TAB9 (COLS=1)
XDB.XDB$ATTRIBUTE (COLS=12) XDB.XDB$GROUP_DEF (COLS=3)
XDB.XDB$MOUNTS (COLS=2)
XDB.XDB$RESOURCE (COLS=6) XDB.XDB$SCHEMA (COLS=6)
XDB.XDB$XIDX_PARAM_T (COLS=1)
SH2.MEDIA_TAB2 (COLS=13) SH2.MEDIA_TAB5 (COLS=1)
SH2.ORDERS_QT (COLS=14)
SH2.ZIGGY_BITMAP (COLS=1) XDB.JSON$COLLECTION_METADATA (COLS=6)
XDB.XDB$ALL_MODEL (COLS=3)
XDB.XDB$ATTRGROUP_REF (COLS=3) XDB.XDB$IMPORT_NM_INFO (COLS=1)
XDB.XDB$XIDX_IMP_T (COLS=3)
SH2.DBIM_ONETAB (COLS=1) SH2.DR$MYINDEX3$I (COLS=1)
SH2.MEDIA_TAB3 (COLS=8)
SH2.MEDIA_TAB7 (COLS=1) SH2.QUARTERLY_REGIONAL_SALES (COLS=2)
SH2.SALES_SUBPARTITIONS (COLS=1)
XDB.JSON$USERS (COLS=2) XDB.JSON$USER_ROLES (COLS=2)
XDB.XDB$ANYATTR (COLS=14)
XDB.XDB$PATH_INDEX_PARAMS (COLS=4) XDB.XDB$ROOT_INFO (COLS=10)
SH2.AQ$ORDERS_QT (COLS=14)
SH2.COUNTRIES_EXT (COLS=3) SH2.LOCATIONS_IOT (COLS=1)
SH2.MEDIA_TAB8 (COLS=1)
XDB.XDB$CHOICE_MODEL (COLS=3) XDB.XDB$GROUP_REF (COLS=4)
XDB.XDB$IMPORT_TT_INFO (COLS=1)
XDB.XDB$NLOCKS (COLS=1) XDB.XDB$NONCEKEY (COLS=1)
XDB.XDB$SIMPLE_TYPE (COLS=39)
SH2.DR$MYINDEX$N (COLS=1) SH2.MEDIA_TAB1 (COLS=9)
SH2.SALES_CLUSTER_LO (COLS=1)
SH2.SALES_PART_NOLOGGING (COLS=1) XDB.APP_USERS_AND_ROLES (COLS=2)
XDB.XDB$TTSET (COLS=1)
XDB.XDB$XTAB (COLS=2) XDB.DOCUMENT_LINKS (COLS=4)
SH2.AQ$_ORDERS_QT_F (COLS=11)
SH2.VIEW_ACCESS_SYS_OBJECT_SYNONYMS (COLS=6) SH2.DR$MYINDEX$I (COLS=1)
SH2.EMPLOYEES_CLUST (COLS=1)
SH2.MEDIA_TAB6 (COLS=1) XDB.JSON$USER_CREDENTIALS (COLS=2)
XDB.X$QN46MP5MEPA004NE0KWN0SK0K1LN (COLS=1)
XDB.XDB$DBFS_VIRTUAL_FOLDER (COLS=1) XDB.XDB$DXPTAB (COLS=2)
XDB.XDB$ELEMENT (COLS=24)
XDB.JSON$COLLECTION_METADATA_V (COLS=29)

3. Schema owner User attributes will be modified in ADB (Count=1):

------------------------------------------------------------------
Default PROFILE will be Modified for XDB from 'MAQPROFILE' to 'DEFAULT'

4. User PROFILEs will not migrate to ADB (Count=1):

---------------------------------------------------
Note: In ATP and ADW, all users will be assigned the 'DEFAULT' Profile. Additionally,
you are not allowed to create additional User PROFILEs.

Oracle Autonomous Database Schema Advisor - 11 -

MAQPROFILE

5. DEFAULT user PROFILE will be altered in the ADB at migration time (Count=32):
--------------------------------------------------------------------------------
Note: In ADB a user's profile will be set to 'DEFAULT' and you are not allowed to
create additional PROFILEs. Below are the differences in user's current profile
and the DEFAULT profile in ADB.

Profile DEFAULT vs. ADB's DEFAULT profile (assigned to SH2):

------------------------------------------------------------

RESOURCE CURRENT LIMITS IN DB NEW LIMITS IN ADB

------------------------------ ------------------------------ ------------------
PASSWORD_LIFE_TIME 180 360
PASSWORD_REUSE_MAX UNLIMITED 4
PASSWORD_REUSE_TIME UNLIMITED 1
PASSWORD_VERIFY_FUNCTION NULL
CLOUD_VERIFY_FUNCTION

Profile MAQPROFILE vs. ADB's DEFAULT profile (assigned to XDB):

---------------------------------------------------------------

RESOURCE CURRENT LIMITS IN DB NEW LIMITS IN ADB

------------------------------ ------------------------------ ------------------
COMPOSITE_LIMIT 60000000 UNLIMITED
CONNECT_TIME 30 UNLIMITED
CPU_PER_SESSION 60000 UNLIMITED
FAILED_LOGIN_ATTEMPTS 3 10
IDLE_TIME DEFAULT UNLIMITED
INACTIVE_ACCOUNT_TIME DEFAULT UNLIMITED
LOGICAL_READS_PER_CALL DEFAULT UNLIMITED
LOGICAL_READS_PER_SESSION 1000 UNLIMITED
PASSWORD_GRACE_TIME 3 7
PASSWORD_LIFE_TIME 90 360
PASSWORD_LOCK_TIME 3 1
PASSWORD_REUSE_MAX DEFAULT 4
PASSWORD_REUSE_TIME 180 1
PASSWORD_VERIFY_FUNCTION DEFAULT
CLOUD_VERIFY_FUNCTION
PRIVATE_SGA 102400 UNLIMITED
SESSIONS_PER_USER DEFAULT UNLIMITED

6. Database Options currently in use but will not be available in the ADB (Count=4):
------------------------------------------------------------------------------------
Note: The following Database Options are detected as being used. ADB does not have
these Options installed. Please verify if the application/schema to be migrated
depends on these options.

Database Resident Connection Pooling

Java in DB
Oracle Multimedia
Tuning Pack

7. Database Parameters are set in your database but can't be set in the ADB (Count=2):
--------------------------------------------------------------------------------------
Note: The following init parameters are set in your database that you would not be
able to set in ADB. Please refer to the Oracle Autonomous Database documentation
on the parameters that you are allowed to modify/set in the autonomous database.

enable_pluggable_database
memory_target

Oracle Autonomous Database Schema Advisor - 12 -

PL/SQL procedure successfully completed.

De-installing the Advisor

If you wish to de-install the Advisor from your database, execute the following statement with DBA
privileges:

SQL> DROP USER ADB_ADVISOR CASADE;

Oracle Autonomous Database Schema Advisor - 13 -