Database Migration Assessment Report: Executive Summary
Database Migration Assessment Report: Executive Summary
Executive summary
We completed the analysis of your Oracle source database and estimate that 99.8% of the database storage
objects and 99.2% of database code objects can be converted automatically or with minimal changes if you
select Amazon Aurora (PostgreSQL compatible) as your migration target. Database storage objects include
schemas, tables, table constraints, indexes, types, collection types, sequences, synonyms, view-constraints,
clusters and database links. Database code objects include triggers, views, materialized views, materialized view
logs, procedures, functions, packages, package constants, package cursors, package exceptions, package
variables, package functions, package procedures, package types, package collection types, scheduler-jobs,
scheduler-programs, scheduler-schedules and queuing-tables. Based on the source code syntax analysis, we
estimate 99.9% (based on # lines of code) of your code can be converted to Amazon Aurora (PostgreSQL
compatible) automatically. To complete the migration, we recommend 686 conversion action(s) ranging from
simple tasks to medium-complexity actions to complex conversion actions.
Migration guidance for database objects that could not be converted automatically can be found here
Schema
1
(1: 1/0/0/0)
Table
97% 429
(429: 417/11/1/0)
Constraint
100% 381
(381: 381/0/0/0)
Index
99.7% 352
(352: 351/0/0/1)
Sequence
100% 12
(12: 12/0/0/0)
Synonym
100% 111
(111: 111/0/0/0)
0 10 100 1000
View
70% 30% 1263
(1263: 885/378/0/0)
Procedure
92% 12
(12: 0/11/0/1)
Function
100% 3
(3: 0/3/0/0)
Package
100% 3
(3: 0/3/0/0)
Package function
67% 3
(3: 2/1/0/0)
Package procedure
47% 24% 24% 17
(17: 1/8/4/4)
Scheduler-job
1
(1: 0/0/0/1)
Package variable
100% 2
(2: 2/0/0/0)
Table Changes
Not all tables can be converted automatically. You'll need to address these issues manually.
Schemas.PVD_MART_53_KH.Tables.LM_REGULATORY_CONTACT_ADDL
+36 more
Index Changes
Not all indexs can be converted automatically. You'll need to address these issues manually.
View Changes
Not all views can be converted automatically. You'll need to address these issues manually.
Issue 5320: PostgreSQL doesn't support the view with invalid status
Recommended action: Perform a manual conversion.
Issue code: 5320 | Number of occurrences: 276 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/current/static/sql-createview.html
Schemas.PVD_MART_53_KH.Views.C_PMDA_GENERAL_UD_ADDL
Schemas.PVD_MART_53_KH.Views.DV_CASE_LABEL_LOCK_INFO_ADDL
Schemas.PVD_MART_53_KH.Views.DV_CASE_LOCK_INFO_ADDL
Schemas.PVD_MART_53_KH.Views.DV_CDR_CLOB_ALL
Schemas.PVD_MART_53_KH.Views.DV_CDR_CLOB_DATES_ALL
+271 more
Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.
Issue 5034: Transaction control is only possible from the top level or nested call
invocations without any other intervening command
Recommended action: Please revise transaction control.
Issue code: 5034 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://www.postgresql.org/docs/current/plpgsql-transactions.html
Schemas.PVD_MART_53_KH.Procedures.P_PROD_AE_LABEL_ASSESS_CLEANUP: Line 54:1625
Issue 5628: Converted code might be incorrect because of the dynamic SQL
Recommended action: Please check the dynamic SQL.
Issue code: 5628 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/current/static/plpgsql-statements.html
Schemas.PVD_MART_53_KH.Procedures.P_EXECUTE_SCRIPT: Line 4:56
Function Changes
Not all functions can be converted automatically. You'll need to address these issues manually.
Package Changes
Not all packages can be converted automatically. You'll need to address these issues manually.
Issue 5034: Transaction control is only possible from the top level or nested call
invocations without any other intervening command
Recommended action: Please revise transaction control.
Issue code: 5034 | Number of occurrences: 3 | Estimated complexity: Simple
Documentation references: https://www.postgresql.org/docs/current/plpgsql-transactions.html
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_EXECUTE_QUERY: Line 8:149
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public
procedures.P_INSERT_INIT_TRANSFORM_LOG: Line 69:2619
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public
procedures.P_INSERT_INIT_TRANSFORM_LOG: Line 81:2975
Issue 5035: A transaction cannot be ended inside a block with exception handlers
Recommended action: Revise your code to try move transaction control on side of application.
Issue code: 5035 | Number of occurrences: 4 | Estimated complexity: Simple
Documentation references: https://www.postgresql.org/docs/current/plpgsql-transactions.html
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public
procedures.P_INSERT_INIT_TRANSFORM_LOG: Line 69:2619
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public
procedures.P_INSERT_INIT_TRANSFORM_LOG: Line 81:2975
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_INSERT_STG_EXCP: Line
30:1032
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_INSERT_STG_EXCP: Line
34:1091
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_DROP_DICT_CONSTRAINTS:
Line 15:424
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_DROP_OBJECTS: Line 67:2304
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_DROP_OBJECTS: Line 76:2564
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_DROP_OBJECTS: Line
106:3432
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_DROP_OBJECTS: Line
119:3964
+3 more
Issue 5628: Converted code might be incorrect because of the dynamic SQL
Recommended action: Please check the dynamic SQL.
Issue code: 5628 | Number of occurrences: 13 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/current/static/plpgsql-statements.html
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_APP_TRG_ENABLE_DISABLE:
Line 13:375
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_APP_TRG_ENABLE_DISABLE:
Line 15:468
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_COMPILE_INVALID_OBJECTS:
Line 31:1074
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_CREATE_INDEX_SCRIPT: Line
99:3189
Schemas.PVD_MART_53_KH.Packages.PKG_ETL_MART_UTIL.Public procedures.P_CREATE_INDEX_SCRIPT: Line
111:3548
+8 more
Scheduler-job Changes
Not all scheduler-jobs can be converted automatically. You'll need to address these issues manually.