==================================================================================================================================== Cloud Premigration Advisor Tool (CPAT) Report ==================================================================================================================================== Report Details ~~~~~~~~~~~~~~ Analysis Mode: SCHEMA CPAT Application Version: 24.11.1 CPAT Checks Version: 24.11.1 Target Cloud Type: ATPS Migration Method(s): DATAPUMP Report Generated On: 2025-02-06T10:30:10Z Report Result: Review Required Database Details ~~~~~~~~~~~~~~~~ Source Database Applications: No Known Applications Detected Source Cloud Vendor: Amazon Web Services (Relational Database Service) Source Database Container Name: RDSSS Source Database Host Name: ip-172-23-2-16 Source Instance Name: RDSSS Source Database Name: RDSSS Source Database Platform ID: 13 Source Database Port String: x86_64/Linux 2.4.xx Source Oracle SID: RDSSS Source DB Block Size in KB: 8 Source DB Combined Size of DATA, TEMP, LOG, and CONTROL File Usage in GB: 2.443 Source DB Size of DATA File Usage in GB: 1.837 Source DB Size of TEMP File Usage in GB: 0.098 Source DB Size of LOG File Usage in GB: 0.5 Source DB Size of CONTROL File Usage in GB: 0.009 Source Database Username: ADMIN Report Analysis Notes ~~~~~~~~~~~~~~~~~~~~~ Note # Note Info ------ --------------------------------------------------------------------------------------------------------------------------- 1 CAUSE: Informational: No analysis properties file found on the command line. Source analysis will not be as complete as possible. ACTION: See the help text for information on using an analysis properties file. 2 CAUSE: Informational: This report was generated by CPAT running in SCHEMA mode thus SCHEMA_ONLY scoped checks were executed but INSTANCE scope checks were not. ACTION: If FULL mode was intended then omit the --schemas option or include the --full option. See Oracle Support Document ID 2758371.1 for more information about CPAT analysis 'mode' and check 'scopes'. 3 CAUSE: Warning: CPAT has detected the database being analyzed is not Oracle Enterprise Edition. The instance is not fully supported by CPAT and results are on a 'best effort' basis. Some validation checks may not work properly, and extra care must be assumed by the user when interpreting results. ACTION: Please run CPAT in an Oracle Enterprise Edition. Source Database Version Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PRODUCT VERSION VERSION_FULL STATUS --------------------------------------- ---------- ------------ ---------- Oracle Database 19c Standard Edition 2 19.0.0.0.0 19.25.0.0.0 Production Source Database Compatible Version: 19.0.0 Source Database Version: 19.25.0.0.0 Source Database Patch Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ COMMENTS SOURCE_VERSION TARGET_VERSION ACTION ACTION_TIME --------------------------------------------------------------------- -------------- -------------- --------- -------------------- RDBMS_19.25.0.0.0DBRU_LINUX.X64_241010 19 BOOTSTRAP Patch applied on 19.25.0.0.0: Release_Update - 241010184253 19.0.0.0.0 RU_APPLY 18-OCT-2024 03:19:39 OJVM RELEASE UPDATE: 19.25.0.0.241015 (36878697) 19.1.0.0.0 19.25.0.0.0 APPLY 18-OCT-2024 03:17:16 Database Release Update : 19.25.0.0.241015 (36912597) 19.1.0.0.0 19.25.0.0.0 APPLY 18-OCT-2024 03:19:39 DBMS_STATS FAILING WITH ERROR ORA-01422 WHEN GATHERING STATS FOR USER 19.1.0.0.0 19.25.0.0.0 APPLY 18-OCT-2024 03:19:42 $ TABLE ------------------------------------------------------------------------------------------------------------------------------------ Premigration Advisor Report Check Summary ------------------------------------------------------------------------------------------------------------------------------------ Number of checks run: A total of 45 checks were performed Number of schemas analyzed: 1 Number of schemas in source DB: 25 List of schemas analyzed: HR Fatal Checks: There were 0 checks with Failed results Action Required Checks: There were 0 checks with Action Required results Review Required Checks: There were 1 checks with Review Required results: timezone_table_compatibility_higher_serverless (1 relevant objects) Review Suggested Checks: There were 4 checks with Review Suggested results: dp_has_low_streams_pool_size (3 relevant objects), has_index_organized_tables (1 relevant objects), has_default_tablespace_not_data (1 relevant objects), standard_traditional_audit_adb Passing Checks: There were 40 checks with Passed results: has_users_with_10g_password_version, nls_national_character_set, has_java_objects, has_java_source, has_columns_with_media_data_types_adb, has_external_tables_serverless, has_db_links, has_tables_with_xmltype_column, has_xmltype_tables, has_unstructured_xml_indexes, has_xmlschema_objects, has_logging_off_for_tables, has_logging_off_for_partitions, has_logging_off_for_subpartitions, has_basic_file_lobs, has_ilm_ado_policies, has_clustered_tables, has_db_link_synonyms, has_parallel_indexes_enabled, has_data_in_other_tablespaces_serverless, has_profile_not_default, has_refs_to_user_objects_in_sys, has_role_privileges, has_sys_privileges, nls_character_set_conversion, nls_nchar_ora_910, has_libraries_serverless, has_refs_to_restricted_packages_serverless, has_dbms_credentials, has_incompatible_jobs, has_columns_with_spatial_data_types, has_sqlt_objects_adb, has_noexport_object_grants, has_mining_model_issues, has_public_synonyms, has_csmig_schema, has_illegal_characters_in_comments, unified_and_standard_traditional_audit_adb, has_columns_with_local_timezone, has_disallowed_triggers ------------------------------------------------------------------------------------------------------------------------------------ Premigration Advisor Check Details List ------------------------------------------------------------------------------------------------------------------------------------ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: timezone_table_compatibility_higher_serverless Check Result: Review Required ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: The source database TZ_VERSION cannot be higher than the target TZ_VERSION. Failure Impact: Migration is not possible until the target TZ_VERSION is the same or higher than the source database TZ_VERSION Status Message: The target Time Zone version property was not supplied so a reasonable substitute was inferred based on the target database version or the target cloud parameter. Please ensure the inferred timezone version is appropriate. Action: Update Time Zone File Version executing this SQL and then restart your instance BEGIN DBMS_CLOUD_ADMIN.ENABLE_FEATURE( feature_name => 'AUTO_DST_UPGRADE'); END; / By default, automatic time zone file updates are disabled because the time zone file upgrade process can have an impact on performance. If you want to turn the AUTO_DST_UPGRADE feature off execute this SQL. BEGIN DBMS_CLOUD_ADMIN.DISABLE_FEATURE( feature_name => AUTO_DST_UPGRADE); END; / For more information on updating the Time Zone File Version feature see the instructions here: https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/manage-time-zone-file-version.html #GUID-BACC9C4A-C0FA-4912-862A-1A2A24D6A0C2 Relevant Objects: TARGET_TZ_VERSION SOURCE_TZ_VERSION ----------------- ----------------- 32 43 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: dp_has_low_streams_pool_size Check Result: Review Suggested ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Verify the STREAMS_POOL_SIZE amount is large enough for Data Pump migrations to start and work efficiently. Failure Impact: Data Pump jobs may fail or perform poorly. Action: STREAMS_POOL_SIZE has not been pre-allocated. Pre-allocating a streams pool may speed up Oracle Data Pump export performance. Hence, it is recommended to define a minimum value for streams_pool_size in the source database before export. Please execute SQL such as: ALTER SYSTEM SET streams_pool_size=256M SCOPE=BOTH; -- or larger And restart your instance if necessary. Relevant Objects: NAME VALUE ----------------- ---------- streams_pool_size 0 sga_target 0 memory_target 1392508928 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_index_organized_tables Check Result: Review Suggested ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Index Organized tables are not allowed in Autonomous databases. Failure Impact: Index-organized tables are not supported, but attempting to create one does not generate an error. Instead, a heap-organized table with a primary key index is created. Action: No action require as the tables gets created as non-IOT (regular table). Relevant Objects: OWNER TABLE_NAME ----- ---------- HR COUNTRIES ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_default_tablespace_not_data Check Result: Review Suggested ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Schema Owner's default tablespace must be 'DATA'. Failure Impact: Schema Owner's DEFAULT TABLESPACE will be modified in ADB to be 'DATA'. Action: If a user has quota on multiple tablespaces, ensure that the proper quota is set post migration. Relevant Objects: USERNAME DEFAULT_TABLESPACE -------- ------------------ HR USERS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: standard_traditional_audit_adb Check Result: Review Suggested ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Traditional audit, deprecated since 21c, is desupported starting with 23c. Traditional Audit configurations have been detected in this database. Failure Impact: Traditional audit is de-supported in 23c. It is strongly recommended to start using Unified auditing. Action: Delete the traditional auditing configurations using the instructions found in Oracle Support Document ID 2909718.1. The audit_sys_operations value, TRUE, is not correct and should be set to FALSE. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_users_with_10g_password_version Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Case-sensitive passwords are required on ADB. Failure Impact: Post migration the identified users will see ORA-1017 errors attempting to connect. During Data Pump migration ORA-39384 warnings will be seen. Action: To avoid Data Pump migration warnings change the passwords for the listed users before migration. Alternatively, modify these users passwords after migration to avoid login failures. See Oracle Support Document ID 2289453.1 for more information. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: nls_national_character_set Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Check for issues caused by the conversion of character data from the source to the target national character set, such as expansion of character values beyond data type limits or loss of invalid character codes. Failure Impact: During migration you may encounter ORA-01401 or loss of invalid character codes due to character set conversion from the source to the target national character set. Action: If possible, provision the target cloud database with the same national character set as the source database and enable extended data types in the target cloud database. See the Oracle Cloud Infrastructure Documentation for information on choosing a national character set when creating a database instance. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_java_objects Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Java objects will not migrate by default. Failure Impact: When the JAVAVM feature is not enabled on the target system, any applications relying on Java objects will fail. Action: Enable the JAVAVM feature on the target system by executing this SQL and then restart your instance BEGIN DBMS_CLOUD_ADMIN.ENABLE_FEATURE( feature_name => 'JAVAVM' ); END; / For more information on enabling the JAVAVM feature see the instructions here: https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-oracle-java.html#GUID-2516EE33-B38D -4270-BE52-30A4F9014E8B ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_java_source Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Java sources will not migrate by default. Failure Impact: When the JAVAVM feature is not enabled on the target system, any applications relying on Java objects will fail. Action: Enable the JAVAVM feature on the target system by executing this SQL and then restart your instance BEGIN DBMS_CLOUD_ADMIN.ENABLE_FEATURE( feature_name => 'JAVAVM' ); END; / For more information on enabling the JAVAVM feature see the instructions here: https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-oracle-java.html#GUID-2516EE33-B38D -4270-BE52-30A4F9014E8B ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_columns_with_media_data_types_adb Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Multimedia object types such as those from ORDSYS cannot be used in Autonomous databases. Failure Impact: Columns with Media data types are not allowed in Autonomous Database. Migration of tables with multimedia columns will fail. Action: Follow the instructions in the Oracle Multimedia README.txt file in /ord/im/admin/README.txt, or Oracle Support Document ID 2555923.1 to determine if Oracle Multimedia methods and packages are being used. If Oracle Multimedia is being used, refer to Oracle Support Document ID 2347372.1 for suggestions on replacing Oracle Multimedia. Refer to Oracle Support Document ID 2375644.1 "How To Migrate Data From Oracle Multimedia Data Types to BLOB columns" for information on how to move data stored in Oracle Multimedia object types to SecureFiles LOBs. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_external_tables_serverless Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: External tables in ADB must be recreated using Object Storage Service or File Storage Service. Failure Impact: Attempting to create external tables that are neither Cloud Object Storage nor File Storage Service will result in those tables being created as empty non-External tables. Action: Drop the empty imported table. Use the DBMS_CLOUD package to create External Tables using Cloud Object Storage Service or use File Storage Service for more info see https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/load-oci-file-storage.html #GUID-B9A7E58E-E1C0-4859-B16B-EF88942704BF. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_db_links Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Database Links must be created natively in ADBS Failure Impact: Until DB links are recreated applications that rely on the links will not work. Action: Pre-create Database Links manually in ADB using DBMS_CLOUD_ADMIN.CREATE_DATABASE_LINK in the respective schema(s) prior to migration. The proper sequence of statements would be: 1) create the schema(s) that own the link(s). 2) create the links using DBMS_CLOUD_ADMIN.CREATE_DATABASE_LINK. 3) import the schema(s) being migrated. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_tables_with_xmltype_column Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Tables with XMLType column will not migrate unless the STORAGE_TYPE is BINARY. Failure Impact: Any applications relying on XMLType columns not stored as BINARY will fail. Action: Tables with XMLType columns defined with CLOB or Object-Relational storage are not supported in Autonomous Database. When the relevant objects column XMLSCHEMA is not empty this indicates your application uses XML Schema Objects and additional work may be required. For non-schema types the BINARY storage option must be used. See Oracle Support Document ID 1581065.1 for information converting CLOB columns to BINARY. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_xmltype_tables Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: XMLType Tables will not migrate unless the STORAGE_TYPE is BINARY. Failure Impact: Any applications relying on XMLType tables not stored as BINARY will fail. Action: XMLType Tables with CLOB or Object-Relational storage is not supported in Autonomous Database. Change the XMLType storage option to BINARY. When the relevant objects column XMLSCHEMA is not empty this indicates your application uses XML Schema Objects and additional work may be required. For non-schema based storage types, the BINARY storage option must be used. See Oracle Support Document ID 1581065.1 for information converting CLOB columns to BINARY. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_unstructured_xml_indexes Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Unstructured XML Indexes are not supported on ADB Failure Impact: Attempting to create an unstructured XML index will fail. Import errors should be expected when migrating unstructured XML indexes. Action: Unstructured XML Indexes are not supported in Autonomous Database. Recreate the indexes using XML Search Index. See https://docs.oracle.com/en/database/oracle/oracle-database/21/adxdb/indexes-for-XMLType-data.html#GUID-A48B77D9 -A4C1-47B9-9664-D921D070AF55 for more information on how create and use XML Search Index. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_xmlschema_objects Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: XML Schema Objects will not migrate. Failure Impact: XML Schemas are not supported in Autonomous Database. Action: Modify your application to not use XML Schema Objects. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_logging_off_for_tables Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Table's NOLOGGING storage attribute will be changed to LOGGING. Failure Impact: Table created with NOLOGGING will automatically be created in ADB as LOGGING. Check the LOGGING attribute in DBA_TABLES. Action: No action required. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_logging_off_for_partitions Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Partition's NOLOGGING storage attribute will be changed to LOGGING. Failure Impact: Partitions created with NOLOGGING will automatically be created in ADB as LOGGING. Check the LOGGING attribute in DBA_TAB_PARTITIONS. Action: No action required. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_logging_off_for_subpartitions Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Subpartition's NOLOGGING storage attribute will be changed to LOGGING. Failure Impact: Subpartitions created with NOLOGGING will automatically be created in ADB as LOGGING. Check the LOGGING attribute in DBA_TAB_SUBPARTITIONS. Action: No action required. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_basic_file_lobs Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: BASICFILE LOBs are not allowed in ADB. Failure Impact: All BASICFILE LOBs will be automatically converted to SECUREFILE LOBs at import time. Action: No action required. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_ilm_ado_policies Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: ILM Automatic Data Optimization Policies will not migrate to ADB Failure Impact: Tables with ILM ADO Policies (12c and later) will be created without the ILM ADO Policy in ATP and ADW. Action: No action required. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_clustered_tables Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Table clusters are not allowed in ADB. Failure Impact: When you create a table with a CLUSTER clause on the ADB, the table gets created as a regular table. Action: While no action is required for migration customers may want to do performance testing to be certain of no adverse effects. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_db_link_synonyms Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Database Links must be created natively in ADBS so synonyms with DB Links require attention after migration. Failure Impact: Application relying on the synonym will fail until recreated. Action: After database Links have been created manually in ADB using DBMS_CLOUD_ADMIN.CREATE_DATABASE_LINK then recreate the synonyms. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_parallel_indexes_enabled Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Parallel DEGREE greater than 1 specified on INDEX can cause unexpected behavior post-migration. Failure Impact: When migrating to ATP, if a PARALLEL clause is specified on the index in your database, it will remain with the index when it gets created, via Data Pump or manual methods. This can lead to SQL statements running in parallel unbeknownst to the end user. Action: To specify serial execution, change the INDEX parallel clause to NOPARALLEL or alter the PARALLEL degree to 1 before or after the migration. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_data_in_other_tablespaces_serverless Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Look for data subject to tablespace restrictions when migrating to Autonomous Databases on Serverless Infrastructure. Failure Impact: User defined tablespaces are not allowed in ATP-S and ADW-S (Serverless Infrastructure). Each database in this cloud environment has a single 'DATA' tablespace. Errors may be seen during migration if users do not have privileges (sufficient quota) on the 'DATA' tablespace. Action: ADB-S will ignore the tablespace clause in most SQL statements thereby ensuring a successful migration. However, should a user be assigned quota in multiple tablespaces there is a risk that the migrated data exceeds the quota that is ultimately assigned to 'DATA' for that user. In all cases, you should assess your application for any dependencies on specific tablespace names. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_profile_not_default Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Identify schemas whose PROFILE is not available on the target system. Failure Impact: Creation of the schema will fail due to the missing PROFILE. Action: Either use full mode in Data Pump and CPAT; or pre-create the needed profiles on the target system and use the "--analysisprops" option with a properties file created by using CPAT with "--gettargetprops" option. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_refs_to_user_objects_in_sys Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Objects in user schemas that depend on user-defined objects in SYS/SYSTEM schemas will not migrate. Failure Impact: Migration will fail for objects that reference user-defined objects in SYS/SYSTEM. Action: Move required user-defined objects in SYS and SYSTEM schemas prior to migration and update the references. Consider dropping any user-defined objects that are no longer required. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_role_privileges Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Some role privileges used in the source DB are prohibited in the target ADB. Failure Impact: Applications may encounter operation failures due to role privilege issues. Status Message: The analysis property for allowed TargetInstanceProp.ROLEPRIVILEGE was not supplied so a reasonable substitute was inferred. Please ensure the inferred list of TargetInstanceProp.ROLEPRIVILEGE is appropriate. To locate the inferred property values, please refer to the log file. Check that the values are compatible with your target instance. Action: Replace prohibited roles with alternatives that are available in ADB, for example, GRANT PDB_DBA TO ; for those schemas in ADB instances. Similarly, schemas granted DATAPUMP_IMP_FULL_DATABASE or IMP_FULL_DATABASE may want to substitute DATAPUMP_CLOUD_IMP in ADB instances. Whether such alternatives are appropriate can only be determined by experts familiar with the applications in question and with testing. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_sys_privileges Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Some system privileges used in the source DB are prohibited in the target ADB. Failure Impact: Operation failures due to system privilege issues. Status Message: The analysis property for allowed TargetInstanceProp.SYSPRIVILEGE was not supplied so a reasonable substitute was inferred. Please ensure the inferred list of TargetInstanceProp.SYSPRIVILEGE is appropriate. To locate the inferred property values, please refer to the log file. Check that the values are compatible with your target instance. Action: Replace prohibited system privileges with alternatives that are available in ADB, for example, GRANT CREATE JOB TO ; for those schemas in ADB instances. Whether such alternatives are appropriate can only be determined by experts familiar with the applications in question and with testing. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: nls_character_set_conversion Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Conversion of character data from the source to the target database character set may cause issues such as expansion of character values beyond column length or loss of invalid character codes. Failure Impact: During migration you may encounter ORA-1401 or loss of invalid character codes due to character set conversion from the source to the target database character set. Status Message: The source and the target database character set are both AL32UTF8. There should not be any issue caused by character set conversion when migrating to the cloud database. Action: Either, 1) provision a new target instance using the same character set as the source, or, 2) scan the schemas to be migrated using Database Migration Assistant for Unicode (DMU) and analyze all possible convertibility issues. See the Oracle Cloud Infrastructure Documentation for information on choosing a character set when creating a database instance. Note that Oracle recommends using the default database character set, AL32UTF8. For more information on The Database Migration Assistant for Unicode (DMU) Tool see Oracle Support Document ID 1272374.1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: nls_nchar_ora_910 Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Check for NCHAR and NVARCHAR2 columns whose character length are greater than the maximum NCHAR and NVARCHAR2 column length for the national database character set of the target database. Failure Impact: During migration you may encounter ORA-00910 due to the difference of the maximum character length of NCHAR and NVARCHAR2 columns between the source and the target database. Status Message: The length of the all NCHAR and NVARCHAR2 columns are valid in the target cloud database. Action: If possible, provision the target cloud database with the same national character set as the source database and enable the Extended Data Types in the target cloud database. See the Oracle Cloud Infrastructure Documentation for information on choosing a national character set when creating a database instance. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_libraries_serverless Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: The CREATE LIBRARY statement is not allowed on ADB. Failure Impact: Applications that depend on these libraries will fail because the libraries will not be created on the target instance. Action: Applications must be updated to remove their dependencies on any listed libraries. Consider using OCI Marketplace EXTPROC Stack Application as a replacement. For more information on OCI Marketplace EXTPROC Stack Application see https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/user-defined-functions-external.html #GUID-FB998DB9-82DC-455E-ACFA-CE06BAB6FC2B Alternatively, using Functions for business logic previously implemented in external libraries. For more information see https://docs.oracle.com/en-us/iaas/Content/Functions/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_refs_to_restricted_packages_serverless Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Some packages are either not supported or only partially supported in ADB Failure Impact: Applications that reference packages that are unsupported or restricted-use on ADB may fail Action: Applications referencing unsupported packages must be modified before migration to ADBS;Applications referencing partially supported packages require testing and validation to ensure they only utilize unrestricted functions and procedures. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_dbms_credentials Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Credentials that were created with DBMS_CREDENTIAL or DBMS_SCHEDULER cannot be migrated Failure Impact: On import users will see ORA-27486 errors related to credentials originally created with DBMS_CREDENTIAL or DBMS_SCHEDULER packages. Such credentials cannot be automatically migrated to ADBS. Action: Recreate required credentials using DBMS_CLOUD.CREATE_CREDENTIAL. See Oracle Support Document ID 2746284.1 for more information. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_incompatible_jobs Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Scheduler Jobs and Programs other than PLSQL_BLOCK or STORED_PROCEDURE are not supported on ADB. Failure Impact: Scheduler Jobs and Programs types such as EXECUTABLE and EXTERNAL_SCRIPT will not run on ADB Action: Recreate required Job or Programs using types allowed in ADB. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_columns_with_spatial_data_types Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Check for Spatial objects that are not fully supported with Autonomous Databases on Serverless Infrastructure. Failure Impact: Not all the functionality associated with these Spatial objects is available on ADBS until the JAVAVM feature is enabled on ADBS. Action: Enable the JAVAVM feature on the target system by executing this SQL and then restart your instance BEGIN DBMS_CLOUD_ADMIN.ENABLE_FEATURE( feature_name => 'JAVAVM' ); END; / For more information on enabling the JAVAVM feature see the instructions here: https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/autonomous-oracle-java.html#GUID-2516EE33-B38D -4270-BE52-30A4F9014E8B For more information on using Spatial on ADB see https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/spatial-autonomous-database.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_sqlt_objects_adb Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: SQLTXPLAIN (SQLT) is not supported on ADB. Failure Impact: Objects related to SQLTXPLAIN will fail to be imported on ADB, possibly causing import errors. Action: Use the "sqdrop.sql" script found in the "install" directory under the SQLTXPLAIN installation to drop all SQLTXPLAIN and SQLTXADMIN objects.See Oracle Support Document ID 1614107.1 for more information. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_noexport_object_grants Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Not all object grants are exported by Data Pump. Failure Impact: Object grants required for your application may be missing on the target instance. Action: Recreate any required grants on the target instance. See Oracle Support Document ID 1911151.1 for more information. Note that any SELECT grants on system objects will need to be replaced with READ grants; SELECT is no longer allowed on system objects. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_mining_model_issues Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Mining Models with unexpected or incorrect attributes will not migrate Failure Impact: Mining Models with issues will not be exported properly causing ORA-39083 errors on import Action: Download and apply Patch ID 33270686 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_public_synonyms Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Data Pump does not migrate Public Synonyms in SCHEMA mode Failure Impact: Applications relying on Public Synonyms will not work correctly until the Public Synonyms are recreated on the target instance. Action: Recreate the listed relevant objects on the target instance, or, use Data Pump in FULL mode. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_csmig_schema Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: The CSSCAN utility is no longer supported and has been replaced by the Database Migration Assistant for Unicode (DMU) Tool. Failure Impact: Migration tools can ignore any objects, users, or roles related with CSSCAN utility. Action: Remove the CSMIG user and any objects created by the CSSCAN utility. BEGIN FOR REC IN (SELECT SYNONYM_NAME FROM DBA_SYNONYMS WHERE TABLE_OWNER = 'CSMIG') LOOP EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM ' || REC.SYNONYM_NAME; END LOOP; END; / DROP VIEW SYS.CSMV$KTFBUE; DROP USER CSMIG CASCADE; Use The Database Migration Assistant for Unicode (DMU) Tool to scan for character set migration issues. For more information on DMU see Oracle Support Document ID 1272374.1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_illegal_characters_in_comments Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Search TABLE and COLUMN comments as well as PL/SQL sources for characters that are not legal in the databases character set. Failure Impact: Illegal characters may result in ORA-39346 "data loss" errors during import and the illegal characters will be replaced with the default replacement character. Action: Delete any illegal characters or replace them with valid characters. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: unified_and_standard_traditional_audit_adb Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Traditional Audit, deprecated since 21c, is desupported starting with 23c. Traditional Audit configurations have been detected in this database which is using Pure Unified Audit. Failure Impact: Performance might degrade unless the traditional audit configurations in the database are deleted. Status Message: The check unified_and_standard_traditional_audit_adb was not executed because the value for "V$OPTION/'Unified Auditing'" in the source database was set, or defaulted, to "FALSE". This value indicates there is no need to execute the check. Action: It is strongly recommended to delete the traditional audit configurations in the database. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_columns_with_local_timezone Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: Identify tables being migrated that have columns using TIMESTAMP WITH LOCAL TIME ZONE datatypes when the source instance DBTIMEZONE does not match the target instance DBTIMEZONE. Failure Impact: Migrated data will appear to be corrupted as it will be interpreted with an incorrect time zone. This can cause unexpected data and other application issues. Status Message: The check has_columns_with_local_timezone was not executed because the value for "DBTIMEZONE" in the source database, "+00:00", matches the expected value in the target database. A matched value indicates there is no need to execute this check. Action: Set the DBTIMEZONE on the target instance to match the source instance. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Name: has_disallowed_triggers Check Result: Passed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Description: The creation of triggers for database STARTUP and SHUTDOWN events is not supported in ADB (Serverless). Failure Impact: Triggers that execute during STARTUP or SHUTDOWN events in your database will not function after migration to ADB (Serverless). Action: Please refer to the Oracle Autonomous Database documentation for details on unsupported triggers and alternatives. For more information, see https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/autonomous-sql-commands.html#GUID -791E7112-07F7-46F0-BD81-777C8FAD83A0 ------------------------------------------------------------------------------------------------------------------------------------ REPORT LEGEND ------------------------------------------------------------------------------------------------------------------------------------ Report and Check Result Values ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Check Result Result Description ---------------- ----------------------------------------------------------------------------------------------------------------- Passed The Cloud Premigration Advisor analysis indicates migration should succeed and applications should see no difference in behavior. Review Suggested The Cloud Premigration Advisor analysis indicates migration should succeed and applications will likely see no functional difference but database administrators should evaluate each Check with this status to look for any unforeseen consequences. Review Required The Cloud Premigration Advisor analysis indicates migration may succeed (at least in part) but not everything is expected to work exactly like before or some work post migration must be done to bring the target instance into alignment with the source database. Action Required The Cloud Premigration Advisor analysis discovered something that would likely cause the migration to be unsuccessful. Checks with this result typically need to be resolved before attempting migration. Failed The Cloud Premigration Advisor was unable to complete its analysis. Please contact Oracle Support Services. Report Notes ~~~~~~~~~~~~ Note # Note Info ------ --------------------------------------------------------------------------------------------------------------------------- 1 Relevant objects are any objects pertinent to the check being performed. Relevant objects may literally be database objects such as tables. Relevant objects may be database parameters or other settings. While frequently the case the absence of relevant objects does not necessarily mean a check will pass. Nor does the presence of relevant objects mean that a check will not pass. ====================================================================================================================================