0% found this document useful (0 votes)

33 views

Amazon RDS For Oracle

The document is a database migration assessment report that analyzes an Oracle source database and estimates conversion rates and required actions for migrating to various AWS database targets including Amazon RDS for MySQL, Amazon Aurora for MySQL, Amazon RDS for PostgreSQL, and Amazon Aurora for PostgreSQL. It finds that 99.5-100% of database storage objects and 91-98% of code objects can be converted automatically or with minimal changes depending on the target. It recommends 513-573 conversion actions to complete the migration.

Uploaded by

mulyono

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

33 views

Amazon RDS For Oracle

Uploaded by

mulyono

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 54

Database migration assessment report

Source database: [email protected]:32769:ORCLCDB

Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Executive summary
We completed the analysis of your Oracle source database and estimate that 99.5% of the database storage
objects and 92% of database code objects can be converted automatically or with minimal changes if you select
Amazon RDS for MySQL 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 and
scheduler-schedules. Based on the source code syntax analysis, we estimate 95% (based on # lines of code) of
your code can be converted to Amazon RDS for MySQL automatically. To complete the migration, we
recommend 571 conversion action(s) ranging from simple tasks to medium-complexity actions to complex
conversion actions.

If you select Amazon Aurora (MySQL compatible) as your migration target, we estimate that 99.5% of the
database storage objects and 92% of database code objects can be converted automatically or with minimal
changes. Based on the syntax analysis we estimate that 95% of your entire database schema can be converted
to Amazon Aurora (MySQL compatible) automatically. We recommend 559 conversion action(s) to complete the
conversion work.

If you select Amazon RDS for PostgreSQL as your migration target, we estimate that 100% of the database
storage objects and 98% of database code objects can be converted automatically or with minimal changes.
Based on the syntax analysis we estimate that 99.3% of your entire database schema can be converted to
Amazon RDS for PostgreSQL automatically. We recommend 513 conversion action(s) to complete the
conversion work.

If you select Amazon Aurora (PostgreSQL compatible) as your migration target, we estimate that 100% of the
database storage objects and 98% of database code objects can be converted automatically or with minimal
changes. Based on the syntax analysis we estimate that 99.3% of your entire database schema can be converted
to Amazon Aurora (PostgreSQL compatible) automatically. We recommend 522 conversion action(s) to
complete the conversion work.

If you select Amazon RDS for MariaDB 10.2 as your migration target, we estimate that 99.5% of the database
storage objects and 91% of database code objects can be converted automatically or with minimal changes.
Based on the syntax analysis we estimate that 95% of your entire database schema can be converted to Amazon
RDS for MariaDB 10.2 automatically. We recommend 573 conversion action(s) to complete the conversion work.

If you select Amazon RDS for MariaDB 10.3 as your migration target, we estimate that 99.5% of the database
storage objects and 92% of database code objects can be converted automatically or with minimal changes.
Based on the syntax analysis we estimate that 97% of your entire database schema can be converted to Amazon
RDS for MariaDB 10.3 automatically. We recommend 515 conversion action(s) to complete the conversion work.

Migration guidance for database objects that could not be converted automatically can be found here

Database objects with conversion actions for Amazon RDS for

MySQL
Of the total 479 database storage object(s) and 660 database code object(s) in the source database, we identifed
477 (99.5%) database storage object(s) and 606 (92%) database code object(s) that can be converted to Amazon
RDS for MySQL automatically or with minimal changes.
2 (0.5%) database storage object(s) require 2 complex user action(s) to complete the conversion.
54 (8%) database code object(s) require 2 medium and 175 complex user action(s) to complete the conversion.

AWS Schema Conversion Tool Version 1.0.632 Page 1 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Figure: Conversion statistics for database storage objects

Schema
1
(1: 1/0/0/0)

Table
100% 319
(319: 319/0/0/0)

Constraint
91% 9% 32
(32: 29/3/0/0)

Index
100% 78
(78: 78/0/0/0)

Collection type
100% 2
(2: 0/0/0/2)

Sequence
100% 47
(47: 47/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

Figure: Conversion statistics for database code objects

Trigger
9% 88% 32
(32: 3/28/1/0)

View
74% 23% 270
(270: 201/61/0/8)

Materialized view
1
(1: 0/0/0/1)

Procedure
49% 26% 24% 127
(127: 62/33/2/30)

Function
94% 187
(187: 175/4/0/8)

Package
100% 4
(4: 4/0/0/0)

Package procedure
63% 38% 8
(8: 5/0/0/3)

Package variable
100% 30
(30: 30/0/0/0)

Package collection type

1
(1: 0/0/0/1)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

AWS Schema Conversion Tool Version 1.0.632 Page 2 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Database objects with conversion actions for Amazon Aurora

(MySQL compatible)
Of the total 479 database storage object(s) and 660 database code object(s) in the source database, we identifed
477 (99.5%) database storage object(s) and 608 (92%) database code object(s) that can be converted to Amazon
Aurora (MySQL compatible) automatically or with minimal changes.
2 (0.5%) database storage object(s) require 2 complex user action(s) to complete the conversion.
52 (8%) database code object(s) require 2 medium and 177 complex user action(s) to complete the conversion.

Figure: Conversion statistics for database storage objects

Schema
1
(1: 1/0/0/0)

Table
100% 319
(319: 319/0/0/0)

Constraint
91% 9% 32
(32: 29/3/0/0)

Index
100% 78
(78: 78/0/0/0)

Collection type
100% 2
(2: 0/0/0/2)

Sequence
100% 47
(47: 47/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

AWS Schema Conversion Tool Version 1.0.632 Page 3 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Figure: Conversion statistics for database code objects

Trigger
9% 88% 32
(32: 3/28/1/0)

View
76% 22% 270
(270: 204/60/0/6)

Materialized view
1
(1: 0/0/0/1)

Procedure
49% 25% 25% 127
(127: 62/32/1/32)

Function
94% 187
(187: 176/4/0/7)

Package
100% 4
(4: 4/0/0/0)

Package procedure
63% 38% 8
(8: 5/0/0/3)

Package variable
100% 30
(30: 30/0/0/0)

Package collection type

1
(1: 0/0/0/1)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

Database objects with conversion actions for Amazon RDS for

PostgreSQL
Of the total 479 database storage object(s) and 660 database code object(s) in the source database, we identifed
479 (100%) database storage object(s) and 646 (98%) database code object(s) that can be converted to Amazon
RDS for PostgreSQL automatically or with minimal changes.
14 (2%) database code object(s) require 43 complex user action(s) to complete the conversion.

AWS Schema Conversion Tool Version 1.0.632 Page 4 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Figure: Conversion statistics for database storage objects

Schema
1
(1: 1/0/0/0)

Table
100% 319
(319: 319/0/0/0)

Constraint
97% 32
(32: 31/1/0/0)

Index
100% 78
(78: 78/0/0/0)

Collection type
100% 2
(2: 2/0/0/0)

Sequence
100% 47
(47: 47/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

Figure: Conversion statistics for database code objects

Trigger
91% 9% 32
(32: 29/3/0/0)

View
68% 32% 270
(270: 183/86/0/1)

Materialized view
1
(1: 1/0/0/0)

Procedure
53% 39% 6% 127
(127: 67/49/4/7)

Function
98% 187
(187: 183/4/0/0)

Package
100% 4
(4: 4/0/0/0)

Package procedure
75% 25% 8
(8: 6/0/0/2)

Package variable
100% 30
(30: 30/0/0/0)

Package collection type

1
(1: 1/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

AWS Schema Conversion Tool Version 1.0.632 Page 5 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Database objects with conversion actions for Amazon Aurora

(PostgreSQL compatible)
Of the total 479 database storage object(s) and 660 database code object(s) in the source database, we identifed
479 (100%) database storage object(s) and 645 (98%) database code object(s) that can be converted to Amazon
Aurora (PostgreSQL compatible) automatically or with minimal changes.
15 (2%) database code object(s) require 43 complex user action(s) to complete the conversion.

Figure: Conversion statistics for database storage objects

Schema
1
(1: 1/0/0/0)

Table
100% 319
(319: 319/0/0/0)

Constraint
97% 32
(32: 31/1/0/0)

Index
100% 78
(78: 78/0/0/0)

Collection type
100% 2
(2: 2/0/0/0)

Sequence
100% 47
(47: 47/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

AWS Schema Conversion Tool Version 1.0.632 Page 6 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Figure: Conversion statistics for database code objects

Trigger
91% 9% 32
(32: 29/3/0/0)

View
68% 32% 270
(270: 183/86/0/1)

Materialized view
1
(1: 1/0/0/0)

Procedure
51% 39% 6% 127
(127: 65/50/4/8)

Function
98% 187
(187: 183/4/0/0)

Package
100% 4
(4: 4/0/0/0)

Package procedure
75% 25% 8
(8: 6/0/0/2)

Package variable
100% 30
(30: 30/0/0/0)

Package collection type

1
(1: 1/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

Database objects with conversion actions for Amazon RDS for

MariaDB 10.2
Of the total 479 database storage object(s) and 660 database code object(s) in the source database, we identifed
477 (99.5%) database storage object(s) and 599 (91%) database code object(s) that can be converted to Amazon
RDS for MariaDB 10.2 automatically or with minimal changes.
2 (0.5%) database storage object(s) require 2 complex user action(s) to complete the conversion.
61 (9%) database code object(s) require 9 medium and 175 complex user action(s) to complete the conversion.

AWS Schema Conversion Tool Version 1.0.632 Page 7 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Figure: Conversion statistics for database storage objects

Schema
1
(1: 1/0/0/0)

Table
100% 319
(319: 319/0/0/0)

Constraint
97% 32
(32: 31/1/0/0)

Index
100% 78
(78: 78/0/0/0)

Collection type
100% 2
(2: 0/0/0/2)

Sequence
100% 47
(47: 47/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

Figure: Conversion statistics for database code objects

Trigger
9% 88% 32
(32: 3/28/1/0)

View
74% 22% 270
(270: 201/60/3/6)

Materialized view
1
(1: 0/0/0/1)

Procedure
49% 25% 24% 127
(127: 62/32/2/31)

Function
94% 187
(187: 175/4/1/7)

Package
100% 4
(4: 4/0/0/0)

Package procedure
100% 8
(8: 0/0/0/8)

Package variable
100% 30
(30: 30/0/0/0)

Package collection type

1
(1: 0/0/0/1)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

AWS Schema Conversion Tool Version 1.0.632 Page 8 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Database objects with conversion actions for Amazon RDS for

MariaDB 10.3
Of the total 479 database storage object(s) and 660 database code object(s) in the source database, we identifed
477 (99.5%) database storage object(s) and 606 (92%) database code object(s) that can be converted to Amazon
RDS for MariaDB 10.3 automatically or with minimal changes.
2 (0.5%) database storage object(s) require 2 complex user action(s) to complete the conversion.
54 (8%) database code object(s) require 9 medium and 167 complex user action(s) to complete the conversion.

Figure: Conversion statistics for database storage objects

Schema
1
(1: 1/0/0/0)

Table
100% 319
(319: 319/0/0/0)

Constraint
97% 32
(32: 31/1/0/0)

Index
100% 78
(78: 78/0/0/0)

Collection type
100% 2
(2: 0/0/0/2)

Sequence
100% 47
(47: 47/0/0/0)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

AWS Schema Conversion Tool Version 1.0.632 Page 9 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Figure: Conversion statistics for database code objects

Trigger
9% 88% 32
(32: 3/28/1/0)

View
93% 270
(270: 252/9/3/6)

Materialized view
1
(1: 0/0/0/1)

Procedure
60% 18% 21% 127
(127: 76/23/1/27)

Function
96% 187
(187: 179/2/1/5)

Package
100% 4
(4: 4/0/0/0)

Package procedure
100% 8
(8: 0/0/0/8)

Package variable
100% 30
(30: 30/0/0/0)

Package collection type

1
(1: 0/0/0/1)

0 10 100 1000

Objects automatically converted Objects with simple actions

Objects with medium-complexity actions Objects with complex actions

Detailed recommendations for Amazon RDS for MySQL migrations

If you migrate your Oracle database to Amazon RDS for MySQL, we recommend the following actions.

Storage object actions

Collection type Changes

Not all collection types can be converted automatically. You'll need to address these issues manually.

Issue 218: MySQL doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Collection Types.SPLIT_TBL
Schemas.PDV.Collection Types.T_ARY

AWS Schema Conversion Tool Version 1.0.632 Page 10 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Constraint Changes
Not all constraints can be converted automatically. You'll need to address these issues manually.

Issue 325: MySQL does not support check constraints. Emulating triggers created
Recommended action: Please revise generated code and modify it if is necessary.
Issue code: 325 | Number of occurrences: 2 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-table.html
Schemas.PDV.Tables.PID.Constraints.C178_116
Schemas.PDV.Tables.PID.Constraints.C178_117

Issue 326: MySQL doesn't support constraints with the status DISABLED
Recommended action: Drop the constraint.
Issue code: 326 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-table.html
Schemas.PDV.Tables.KASLINE.Constraints.KEY_KASLINE

Code object actions

Package collection type Changes

Not all package collection types can be converted automatically. You'll need to address these issues manually.

Issue 118: MySQL doesn't support the table type

Recommended action: Use an ordinary table.
Issue code: 118 | Number of occurrences: 1 | Estimated complexity: Medium
Documentation references: http://dev.mysql.com/doc/refman/5.7/en/create-table.html
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Issue 218: MySQL doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Package procedure Changes

Not all package procedures can be converted automatically. You'll need to address these issues manually.

Issue 28: Unable convert variable declaration of unsupported datatype

Recommended action: Perform a manual conversion.

AWS Schema Conversion Tool Version 1.0.632 Page 11 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue code: 28 | Number of occurrences: 1 | Estimated complexity: Complex

Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 273:295

Issue 30: Unable convert variable usage of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 30 | Number of occurrences: 56 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 536:536
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 567:567
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 600:600
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 633:633
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 667:667
+51 more

Issue 218: MySQL doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Packages.PCK_REPORT.Public procedures.INITIAL: 203:213
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 2871:2887

Issue 293: Unable to resolve objects

Recommended action: Verify if object JK is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 56 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 538:539
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 569:573
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 602:606
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 635:639
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 669:670
+51 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 1 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/string-functions.html
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 2770:2805

Issue 595: Unable to convert synonym on system object

Recommended action: Perform a manual conversion.
Issue code: 595 | Number of occurrences: 1 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 1935:1938

AWS Schema Conversion Tool Version 1.0.632 Page 12 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 9996: Internal Converter error occurred

Recommended action: Please submit report to developers.
Issue code: 9996 | Number of occurrences: 4 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 126:153
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 163:173
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 183:198
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 215:2217

Function Changes
Not all functions can be converted automatically. You'll need to address these issues manually.

Issue 118: MySQL doesn't support the table type

Issue 218: MySQL doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 19 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Functions.TRANS: 128:184
Schemas.PDV.Functions.TRANS: 189:199
Schemas.PDV.Functions.TRANS: 263:271
Schemas.PDV.Functions.TRANS: 286:294
Schemas.PDV.Functions.TRANS: 310:318
+14 more

Issue 332: MySQL doesn't support the procedure dbms_output.put_line

Recommended action: Try using INSERT in the log table. To do this, you must add code into
AWS_ORACLE_EXT.PUT_LINE.
Issue code: 332 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-table.html
Schemas.PDV.Functions.CONNUM_MAIN: 414:457

AWS Schema Conversion Tool Version 1.0.632 Page 13 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 338: The converted object is invalid

Recommended action: To correct this, update the original source code to convert to a valid object.
Issue code: 338 | Number of occurrences: 1 | Estimated complexity: Simple
Schemas.PDV.Functions.SHOW_PCK

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 5 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/string-functions.html
Schemas.PDV.Functions.INTDIV: 280:307
Schemas.PDV.Functions.RND: 1237:1251
Schemas.PDV.Functions.RND: 1377:1391
Schemas.PDV.Functions.SPLIT_KATA: 256:296
Schemas.PDV.Functions.SPLIT_KATA: 366:411

Issue 342: Unable to convert exceptions

Recommended action: Review the exception used, and if possible convert it to an exception using the SIGNAL or
RESIGNAL statement.
Issue code: 342 | Number of occurrences: 3 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/condition-handling.html
Schemas.PDV.Functions.CDATE: 159:164
Schemas.PDV.Functions.ISNUMBER: 150:155
Schemas.PDV.Functions.IS_DATE: 161:166

Issue 601: MySQL doesn't support given analytic function or it's options
Recommended action: Make use of user defined function.
Issue code: 601 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Functions.PBD_CARISANPER: 108:161

Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.

Issue 211: In MySQL NULL sorting, NULL values go first for an ascending order and last for
a descending order

AWS Schema Conversion Tool Version 1.0.632 Page 14 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Recommended action: Review your transformed code and modify it if necessary.

Issue code: 211 | Number of occurrences: 25 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/select.html
Schemas.PDV.Procedures.APPR_UMUM_PUMK: 212:222
Schemas.PDV.Procedures.APPR_UMUM_UMK: 211:221
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPP: 2810:2824
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPPJURNAL: 2843:2857
Schemas.PDV.Procedures.COPY_JURNAL: 283:297
+20 more

Issue 218: MySQL doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 18 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 52:76
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 79:88
Schemas.PDV.Procedures.PR_APP_SERAH: 46:70
Schemas.PDV.Procedures.PR_APP_SERAH: 73:82
Schemas.PDV.Procedures.PR_NEW_IA: 123:147
+13 more

Issue 293: Unable to resolve objects

Recommended action: Verify if object %s is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 37 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_CREATEROWREAL: 358:450
Schemas.PDV.Procedures.C_CREATEROWREAL: 465:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 356:452
Schemas.PDV.Procedures.C_CREATEROWSCH: 467:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 571:591
+32 more

Issue 332: MySQL doesn't support the procedure dbms_output.put_line

Recommended action: Try using INSERT in the log table. To do this, you must add code into
AWS_ORACLE_EXT.PUT_LINE.
Issue code: 332 | Number of occurrences: 5 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-table.html
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPP: 4750:4832
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPPJURNAL: 4696:4781
Schemas.PDV.Procedures.HAPUSJURNAL_ANGSPKPP: 385:476
Schemas.PDV.Procedures.SDM_PROSESGAJIKONTRAK: 1172:1213
Schemas.PDV.Procedures.SDM_PROSESGAJITETAP: 2146:2187

Issue 334: MySQL doesn't support the dynamic SQL statement EXECUTE IMMEDIATE
Recommended action: Review and modify the execution string.

AWS Schema Conversion Tool Version 1.0.632 Page 15 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue code: 334 | Number of occurrences: 99 | Estimated complexity: Simple

Documentation references: https://dev.mysql.com/doc/refman/5.7/en/execute.html
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 773:794
Schemas.PDV.Procedures.CR_REPORT_CASH: 1653:1673
Schemas.PDV.Procedures.CR_REPORT_D2SALDOAWAL: 595:615
Schemas.PDV.Procedures.CR_REPORT_D2SALDOMUTASI: 675:695
Schemas.PDV.Procedures.CR_REPORT_D5: 2604:2624
+94 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 38 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/string-functions.html
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 267:280
Schemas.PDV.Procedures.OPENING_BALANCE: 1664:1677
Schemas.PDV.Procedures.PR_CARI_KOPERASI: 225:234
Schemas.PDV.Procedures.PR_CREATE_IA: 280:289
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 393:402
+33 more

Issue 343: Unable to transform the SELECT statement for a cursor

Recommended action: Try rewriting the select statement.
Issue code: 343 | Number of occurrences: 5 | Estimated complexity: Complex
Documentation references: http://dev.mysql.com/doc/refman/5.7/en/cursors.html
Schemas.PDV.Procedures.PR_CR_IND_ACCOUNT_ALL: 675:1444
Schemas.PDV.Procedures.PR_CR_IND_ACCOUNT_SUM: 697:1561
Schemas.PDV.Procedures.PR_CR_TAB_LAN: 917:6499
Schemas.PDV.Procedures.PR_IND_GRAPH: 528:1315
Schemas.PDV.Procedures.PR_PROSES_BATALHP: 5172:5304

Issue 355: Converted code might be incorrect because of the dynamic SQL
Recommended action: Please check the dynamic SQL.
Issue code: 355 | Number of occurrences: 10 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
Schemas.PDV.Procedures.C_CREATEROWREAL: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 915:936
Schemas.PDV.Procedures.OPENING_BALANCE: 3336:3357
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 2825:2846
+5 more

Issue 9996: Internal Converter error occurred

Recommended action: Please submit report to developers.
Issue code: 9996 | Number of occurrences: 8 | Estimated complexity: Complex

AWS Schema Conversion Tool Version 1.0.632 Page 16 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Procedures.OPENING_BALANCE: 4617:5427
Schemas.PDV.Procedures.PBD_PROSBAYARPKPP: 958:3491
Schemas.PDV.Procedures.PBD_PROSBAYARPKPP: 1125:3476
Schemas.PDV.Procedures.PENEMPATAN: 665:4629
Schemas.PDV.Procedures.PR_NEW_IA: 2672:2721
+3 more

Materialized view Changes

Not all materialized views can be converted automatically. You'll need to address these issues manually.

Issue 94: MySQL doesn't support a materialized VIEW

Recommended action: Revise your code to replace materialized VIEW with another solution.
Issue code: 94 | Number of occurrences: 1 | Estimated complexity: Complex
Documentation references: http://dev.mysql.com/doc/refman/5.0/en/create-view.html
Schemas.PDV.Materialized Views.V_PKPPVSKAS321

View Changes
Not all views can be converted automatically. You'll need to address these issues manually.

Issue 75: MySQL doesn't support VIEW with the READ ONLY option
Recommended action: Use VIEW without this option instead.
Issue code: 75 | Number of occurrences: 9 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-view.html
Schemas.PDV.Views.SDMDIDIKAKHIR: 183:196
Schemas.PDV.Views.TAB_VIEW_TABBLN: 89:102
Schemas.PDV.Views.VKAS_BALANCING: 372:385
Schemas.PDV.Views.V_PEGAWAIKONTRAK: 150:163
Schemas.PDV.Views.V_PEGAWAITETAP: 150:163
+4 more

Issue 211: In MySQL NULL sorting, NULL values go first for an ascending order and last for
a descending order
Recommended action: Review your transformed code and modify it if necessary.
Issue code: 211 | Number of occurrences: 59 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/select.html
Schemas.PDV.Views.CTR_REKAPPKPPPEGAWAI: 200:260
Schemas.PDV.Views.C_V_CONVES: 518:530
Schemas.PDV.Views.C_V_CONVES: 617:629
Schemas.PDV.Views.C_V_CONVES: 726:738
Schemas.PDV.Views.C_V_CONVES: 1172:1223
+54 more

Issue 293: Unable to resolve objects

Recommended action: Verify if object id is present in the database. If it isn't, check the object name or add the

AWS Schema Conversion Tool Version 1.0.632 Page 17 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

object. If the object is present, transform the code manually.

Issue code: 293 | Number of occurrences: 52 | Estimated complexity: Simple
Schemas.PDV.Views.C_V_CONVES: 9:10
Schemas.PDV.Views.C_V_CONVES: 25:26
Schemas.PDV.Views.C_V_CONVES: 45:49
Schemas.PDV.Views.C_V_CONVES: 54:58
Schemas.PDV.Views.C_V_CONVES: 63:68
+47 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 8 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/string-functions.html
Schemas.PDV.Views.SYSTABLES: 95:105
Schemas.PDV.Views.TEST: 43:52
Schemas.PDV.Views.TEST: 191:200
Schemas.PDV.Views.V_REPORT_REKAPKAS_BEBAS: 560:583
Schemas.PDV.Views.V_REPORT_REKAPKAS_BEBAS: 585:607
+3 more

Issue 601: MySQL doesn't support given analytic function or it's options
Recommended action: Make use of user defined function.
Issue code: 601 | Number of occurrences: 3 | Estimated complexity: Complex
Schemas.PDV.Views.INV_MUTASI_DANA: 40:62
Schemas.PDV.Views.TAB_TABMASTER_PRSH: 97:118
Schemas.PDV.Views.V_VOUCHER_DUA_LOKASI: 164:185

Trigger Changes
Not all triggers can be converted automatically. You'll need to address these issues manually.

Issue 243: MySQL doesn't support the UPDATE OF clause

Recommended action: Perform a manual conversion, please.
Issue code: 243 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-trigger.html
Schemas.PDV.Tables.CASH_FLOW.Triggers.TGR_CASH_FLOW$(PDV)

Issue 312: MySQL doesn't support the DISABLED clause

Recommended action: Drop the trigger.
Issue code: 312 | Number of occurrences: 2 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-trigger.html
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.UMU_BAYAR_DETAIL.Triggers.BAYARDETAIL_BEFORE_INSERT$(PDV)

AWS Schema Conversion Tool Version 1.0.632 Page 18 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 524: MySQL doesn't support triggers for multiple events

Recommended action: Try to split the trigger on several independent triggers (one trigger - for one event).
Issue code: 524 | Number of occurrences: 29 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-trigger.html
Schemas.PDV.Tables.CASH_FLOW.Triggers.TGR_CASH_FLOW$(PDV)
Schemas.PDV.Tables.INV_CAIR_POKOK.Triggers.INVCAIRPOKOK_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERPEMINJAM.Triggers.INVMTRPEMINJAM_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERTRANSAKSI.Triggers.INVMTRTRANSAKSI_BEFORE_INSERT$(PDV)
+24 more

Detailed recommendations for Amazon Aurora (MySQL compatible)

migrations
If you migrate your Oracle database to Amazon Aurora (MySQL compatible), we recommend the following
actions.

Storage object actions

Collection type Changes

Not all collection types can be converted automatically. You'll need to address these issues manually.

Issue 218: MySQL doesn't support user types

Constraint Changes
Not all constraints can be converted automatically. You'll need to address these issues manually.

Issue 326: MySQL doesn't support constraints with the status DISABLED
Recommended action: Drop the constraint.
Issue code: 326 | Number of occurrences: 1 | Estimated complexity: Simple

AWS Schema Conversion Tool Version 1.0.632 Page 19 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Documentation references: https://dev.mysql.com/doc/refman/5.7/en/create-table.html

Schemas.PDV.Tables.KASLINE.Constraints.KEY_KASLINE

Code object actions

Package collection type Changes

Not all package collection types can be converted automatically. You'll need to address these issues manually.

Issue 118: MySQL doesn't support the table type

Issue 218: MySQL doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Package procedure Changes

Not all package procedures can be converted automatically. You'll need to address these issues manually.

Issue 28: Unable convert variable declaration of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 28 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 273:295

Issue 30: Unable convert variable usage of unsupported datatype

Issue 218: MySQL doesn't support user types

AWS Schema Conversion Tool Version 1.0.632 Page 20 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/stored-programs-views.html
Schemas.PDV.Packages.PCK_REPORT.Public procedures.INITIAL: 203:213
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 2871:2887

Issue 293: Unable to resolve objects

Issue 340: Unable to convert functions

Issue 595: Unable to convert synonym on system object

Recommended action: Perform a manual conversion.
Issue code: 595 | Number of occurrences: 1 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 1935:1938

Issue 9996: Internal Converter error occurred

Function Changes
Not all functions can be converted automatically. You'll need to address these issues manually.

Issue 118: MySQL doesn't support the table type

Recommended action: Use an ordinary table.
Issue code: 118 | Number of occurrences: 1 | Estimated complexity: Medium

AWS Schema Conversion Tool Version 1.0.632 Page 21 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Documentation references: http://dev.mysql.com/doc/refman/5.7/en/create-table.html

Schemas.PDV.Functions.TRANS: 128:184

Issue 218: MySQL doesn't support user types

Issue 332: MySQL doesn't support the procedure dbms_output.put_line

Issue 338: The converted object is invalid

Issue 340: Unable to convert functions

AWS Schema Conversion Tool Version 1.0.632 Page 22 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Recommended action: Create a user-defined function.

Issue code: 340 | Number of occurrences: 5 | Estimated complexity: Complex
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/string-functions.html
Schemas.PDV.Functions.INTDIV: 280:307
Schemas.PDV.Functions.RND: 1237:1251
Schemas.PDV.Functions.RND: 1377:1391
Schemas.PDV.Functions.SPLIT_KATA: 256:296
Schemas.PDV.Functions.SPLIT_KATA: 366:411

Issue 342: Unable to convert exceptions

Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.

Issue 211: In MySQL NULL sorting, NULL values go first for an ascending order and last for
a descending order
Recommended action: Review your transformed code and modify it if necessary.
Issue code: 211 | Number of occurrences: 23 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/select.html
Schemas.PDV.Procedures.APPR_UMUM_PUMK: 212:222
Schemas.PDV.Procedures.APPR_UMUM_UMK: 211:221
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPP: 2810:2824
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPPJURNAL: 2843:2857
Schemas.PDV.Procedures.COPY_JURNAL: 283:297
+18 more

Issue 218: MySQL doesn't support user types

AWS Schema Conversion Tool Version 1.0.632 Page 23 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 266: Unable to convert functions with analytic clause

Recommended action: Create a user-defined function.
Issue code: 266 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html
Schemas.PDV.Procedures.C_CREATEROWREAL: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 490:511

Issue 293: Unable to resolve objects

Recommended action: Verify if object %s is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 35 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_CREATEROWREAL: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 571:591
Schemas.PDV.Procedures.C_CREATEROWSCH: 606:663
Schemas.PDV.Procedures.C_CREATEROWSCH: 678:734
+30 more

Issue 332: MySQL doesn't support the procedure dbms_output.put_line

Issue 334: MySQL doesn't support the dynamic SQL statement EXECUTE IMMEDIATE
Recommended action: Review and modify the execution string.
Issue code: 334 | Number of occurrences: 101 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/execute.html
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 773:794
Schemas.PDV.Procedures.CR_REPORT_CASH: 1653:1673
Schemas.PDV.Procedures.CR_REPORT_D2SALDOAWAL: 595:615
Schemas.PDV.Procedures.CR_REPORT_D2SALDOMUTASI: 675:695
Schemas.PDV.Procedures.CR_REPORT_D5: 2604:2624
+96 more

Issue 340: Unable to convert functions

AWS Schema Conversion Tool Version 1.0.632 Page 24 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 267:280
Schemas.PDV.Procedures.OPENING_BALANCE: 1664:1677
Schemas.PDV.Procedures.PR_CARI_KOPERASI: 225:234
Schemas.PDV.Procedures.PR_CREATE_IA: 280:289
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 393:402
+33 more

Issue 343: Unable to transform the SELECT statement for a cursor

Issue 355: Converted code might be incorrect because of the dynamic SQL
Recommended action: Please check the dynamic SQL.
Issue code: 355 | Number of occurrences: 8 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/sql-syntax-prepared-statements.html
Schemas.PDV.Procedures.C_CREATEROWSCH: 915:936
Schemas.PDV.Procedures.OPENING_BALANCE: 3336:3357
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 2825:2846
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 3004:3025
Schemas.PDV.Procedures.PR_CR_TAB_LAN: 715:736
+3 more

Issue 9996: Internal Converter error occurred

Recommended action: Please submit report to developers.
Issue code: 9996 | Number of occurrences: 8 | Estimated complexity: Complex
Schemas.PDV.Procedures.OPENING_BALANCE: 4617:5427
Schemas.PDV.Procedures.PBD_PROSBAYARPKPP: 958:3491
Schemas.PDV.Procedures.PBD_PROSBAYARPKPP: 1125:3476
Schemas.PDV.Procedures.PENEMPATAN: 665:4629
Schemas.PDV.Procedures.PR_NEW_IA: 2672:2721
+3 more

Materialized view Changes

Not all materialized views can be converted automatically. You'll need to address these issues manually.

Issue 94: MySQL doesn't support a materialized VIEW

AWS Schema Conversion Tool Version 1.0.632 Page 25 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Materialized Views.V_PKPPVSKAS321

View Changes
Not all views can be converted automatically. You'll need to address these issues manually.

Issue 211: In MySQL NULL sorting, NULL values go first for an ascending order and last for
a descending order
Recommended action: Review your transformed code and modify it if necessary.
Issue code: 211 | Number of occurrences: 55 | Estimated complexity: Simple
Documentation references: https://dev.mysql.com/doc/refman/5.7/en/select.html
Schemas.PDV.Views.CTR_REKAPPKPPPEGAWAI: 200:260
Schemas.PDV.Views.C_V_CONVES: 1172:1223
Schemas.PDV.Views.INV_MUTASI: 858:933
Schemas.PDV.Views.INV_MUTASI_2: 654:729
Schemas.PDV.Views.INV_MUTASI_B: 827:906
+50 more

Issue 266: Unable to convert functions with analytic clause

Recommended action: Create a user-defined function.
Issue code: 266 | Number of occurrences: 4 | Estimated complexity: Complex
Documentation references: http://dev.mysql.com/doc/refman/5.7/en/group-by-functions.html
Schemas.PDV.Views.C_V_CONVES: 499:531
Schemas.PDV.Views.C_V_CONVES: 598:630
Schemas.PDV.Views.C_V_CONVES: 707:739
Schemas.PDV.Views.TAB_TABMASTER_THN: 47:111

Issue 293: Unable to resolve objects

Recommended action: Verify if object id is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 46 | Estimated complexity: Simple
Schemas.PDV.Views.C_V_CONVES: 9:10
Schemas.PDV.Views.C_V_CONVES: 25:26
Schemas.PDV.Views.C_V_CONVES: 45:49

AWS Schema Conversion Tool Version 1.0.632 Page 26 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Views.C_V_CONVES: 54:58
Schemas.PDV.Views.C_V_CONVES: 63:68
+41 more

Issue 340: Unable to convert functions

Trigger Changes
Not all triggers can be converted automatically. You'll need to address these issues manually.

Issue 243: MySQL doesn't support the UPDATE OF clause

Issue 312: MySQL doesn't support the DISABLED clause

Issue 524: MySQL doesn't support triggers for multiple events

AWS Schema Conversion Tool Version 1.0.632 Page 27 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Detailed recommendations for Amazon RDS for PostgreSQL migrations

If you migrate your Oracle database to Amazon RDS for PostgreSQL, we recommend the following actions.

Storage object actions

Constraint Changes
Not all constraints can be converted automatically. You'll need to address these issues manually.

Issue 5326: PostgreSQL doesn't support status definition in the CREATE statement for
triggers/constraints
Recommended action: Disable the trigger/drop the constraint manually if needed.
Issue code: 5326 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/sql-createtable.html
Schemas.PDV.Tables.KASLINE.Constraints.KEY_KASLINE

Code object actions

Package procedure Changes

Not all package procedures can be converted automatically. You'll need to address these issues manually.

Issue 5293: Unable to resolve objects

Recommended action: Verify if object Header_BalKas is present in the database. If it isn't, check the object name
or add the object. If the object is present, transform the code manually.
Issue code: 5293 | Number of occurrences: 104 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 275:287
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 536:539
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 567:573
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 600:606
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 633:639
+99 more

Issue 9993: Unable to transform statement due to references to unresolved object

Recommended action: Verify if unresolved object is present in the database. If it isn't, check the object name or
add the object. If the object is present, please submit report to developers.
Issue code: 9993 | Number of occurrences: 41 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 536:558
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 567:592
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 600:625
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 633:659
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 667:690
+36 more

Function Changes

AWS Schema Conversion Tool Version 1.0.632 Page 28 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Not all functions can be converted automatically. You'll need to address these issues manually.

Issue 5334: Unable to convert statements with dynamic SQL statement

Recommended action: Please perform a manual conversion.
Issue code: 5334 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.1/static/plpgsql-statements.html
Schemas.PDV.Functions.SALDO_MMD_PERBULAN: 2223:2262

Issue 5584: Converted functions depends on the time zone settings

Recommended action: Review the transformed code, and set time zone manually if necessary.
Issue code: 5584 | Number of occurrences: 3 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/functions-datetime.html
Schemas.PDV.Functions.RND: 957:963
Schemas.PDV.Functions.TIME: 159:165
Schemas.PDV.Functions.TODAY: 66:72

Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.

Issue 5226: PostgreSQL doesn't support TYPE ... IS REF CURSOR usage
Recommended action: It replaced by REFCURSOR datatype.
Issue code: 5226 | Number of occurrences: 6 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/datatype.html
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 52:76
Schemas.PDV.Procedures.PR_APP_SERAH: 46:70
Schemas.PDV.Procedures.PR_NEW_IA: 123:147
Schemas.PDV.Procedures.PR_PROSES_PHK_BATAL: 53:77
Schemas.PDV.Procedures.PR_REKAP_CASHFLOW: 72:96
+1 more

Issue 5293: Unable to resolve objects

Recommended action: Verify if object %s is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 5293 | Number of occurrences: 52 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_CREATEROWREAL: 358:450
Schemas.PDV.Procedures.C_CREATEROWREAL: 465:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 356:452
Schemas.PDV.Procedures.C_CREATEROWSCH: 467:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 571:591
+47 more

Issue 5334: Unable to convert statements with dynamic SQL statement

AWS Schema Conversion Tool Version 1.0.632 Page 29 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Recommended action: Please perform a manual conversion.

Issue code: 5334 | Number of occurrences: 79 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.1/static/plpgsql-statements.html
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 773:794
Schemas.PDV.Procedures.CR_REPORT_CASH: 1653:1673
Schemas.PDV.Procedures.CR_REPORT_D2SALDOAWAL: 595:615
Schemas.PDV.Procedures.CR_REPORT_D2SALDOMUTASI: 675:695
Schemas.PDV.Procedures.CR_REPORT_D5: 2604:2624
+74 more

Issue 5578: Unable to automatically transform the SELECT statement

Recommended action: Try rewriting the statement.
Issue code: 5578 | Number of occurrences: 2 | Estimated complexity: Complex
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 215:334
Schemas.PDV.Procedures.OPENING_BALANCE: 1622:1737

Issue 5584: Converted functions depends on the time zone settings

Recommended action: Review the transformed code, and set time zone manually if necessary.
Issue code: 5584 | Number of occurrences: 35 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/functions-datetime.html
Schemas.PDV.Procedures.APPROVEHASBANG: 316:322
Schemas.PDV.Procedures.APPROVEHASBANG: 445:451
Schemas.PDV.Procedures.APPROV_MINTABAYAR: 267:273
Schemas.PDV.Procedures.APPR_UMUM_PUMK: 2103:2109
Schemas.PDV.Procedures.APPR_UMUM_PUMK: 2123:2129
+30 more

Issue 5591: Unable to convert system object

Recommended action: Perform a manual conversion.
Issue code: 5591 | Number of occurrences: 2 | Estimated complexity: Simple
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 267:280
Schemas.PDV.Procedures.OPENING_BALANCE: 1664:1677

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: 31 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/plpgsql-statements.html
Schemas.PDV.Procedures.C_CREATEROWREAL: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 915:936
Schemas.PDV.Procedures.PR_CREATE_IA: 363:384
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 1082:1103
+26 more

AWS Schema Conversion Tool Version 1.0.632 Page 30 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

View Changes
Not all views can be converted automatically. You'll need to address these issues manually.

Issue 5075: PostgreSQL doesn't support VIEW with the READ ONLY option
Recommended action: Use VIEW without this option instead.
Issue code: 5075 | Number of occurrences: 9 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/sql-createview.html
Schemas.PDV.Views.SDMDIDIKAKHIR: 183:196
Schemas.PDV.Views.TAB_VIEW_TABBLN: 89:102
Schemas.PDV.Views.VKAS_BALANCING: 372:385
Schemas.PDV.Views.V_PEGAWAIKONTRAK: 150:163
Schemas.PDV.Views.V_PEGAWAITETAP: 150:163
+4 more

Issue 5293: Unable to resolve objects

Recommended action: Verify if object a.id is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 5293 | Number of occurrences: 56 | Estimated complexity: Simple
Schemas.PDV.Views.C_V_CONVES: 7:10
Schemas.PDV.Views.C_V_CONVES: 23:26
Schemas.PDV.Views.C_V_CONVES: 43:49
Schemas.PDV.Views.C_V_CONVES: 52:58
Schemas.PDV.Views.C_V_CONVES: 61:68
+51 more

Issue 5320: PostgreSQL doesn't support the view with invalid status
Recommended action: Perform a manual conversion.
Issue code: 5320 | Number of occurrences: 75 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/sql-createview.html
Schemas.PDV.Views.C_V_CONVES
Schemas.PDV.Views.DOWNLOADKOPERASI
Schemas.PDV.Views.INV_MUTASI_DANA
Schemas.PDV.Views.INV_REPORTSALDOBULAN
Schemas.PDV.Views.INV_SCHEDULEAKTIF
+70 more

Issue 5584: Converted functions depends on the time zone settings

Recommended action: Review the transformed code, and set time zone manually if necessary.
Issue code: 5584 | Number of occurrences: 13 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/functions-datetime.html
Schemas.PDV.Views.C_V_CONVES: 219:225
Schemas.PDV.Views.V_ADUDEPOSITO: 255:261
Schemas.PDV.Views.V_LIHATANGSMMD: 646:652
Schemas.PDV.Views.V_PAJAKLIEUR: 210:216
Schemas.PDV.Views.V_PAJAKLIEUR: 249:255

AWS Schema Conversion Tool Version 1.0.632 Page 31 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

+8 more

Trigger Changes
Not all triggers can be converted automatically. You'll need to address these issues manually.

Issue 5326: PostgreSQL doesn't support status definition in the CREATE statement for
triggers/constraints
Recommended action: Disable the trigger/drop the constraint manually if needed.
Issue code: 5326 | Number of occurrences: 2 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/sql-createtable.html
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.UMU_BAYAR_DETAIL.Triggers.BAYARDETAIL_BEFORE_INSERT$(PDV)

Issue 5584: Converted functions depends on the time zone settings

Recommended action: Review the transformed code, and set time zone manually if necessary.
Issue code: 5584 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.6/static/functions-datetime.html
Schemas.PDV.Tables.ACCOUNT.Triggers.ACCOUNT_AFTERINSERT$(PDV): 26:32

Detailed recommendations for Amazon Aurora (PostgreSQL compatible)

migrations
If you migrate your Oracle database to Amazon Aurora (PostgreSQL compatible), we recommend the following
actions.

Storage object actions

Constraint Changes
Not all constraints can be converted automatically. You'll need to address these issues manually.

Code object actions

Package procedure Changes

Not all package procedures can be converted automatically. You'll need to address these issues manually.

AWS Schema Conversion Tool Version 1.0.632 Page 32 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 5293: Unable to resolve objects

Issue 9993: Unable to transform statement due to references to unresolved object

Function Changes
Not all functions can be converted automatically. You'll need to address these issues manually.

Issue 5334: Unable to convert statements with dynamic SQL statement

Issue 5584: Converted functions depends on the time zone settings

Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.

AWS Schema Conversion Tool Version 1.0.632 Page 33 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 5293: Unable to resolve objects

Recommended action: Verify if object %s is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 5293 | Number of occurrences: 52 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_CREATEROWREAL: 358:450
Schemas.PDV.Procedures.C_CREATEROWREAL: 465:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 356:452
Schemas.PDV.Procedures.C_CREATEROWSCH: 467:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 571:591
+47 more

Issue 5334: Unable to convert statements with dynamic SQL statement

Recommended action: Please perform a manual conversion.
Issue code: 5334 | Number of occurrences: 79 | Estimated complexity: Simple
Documentation references: http://www.postgresql.org/docs/9.1/static/plpgsql-statements.html
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 773:794
Schemas.PDV.Procedures.CR_REPORT_CASH: 1653:1673
Schemas.PDV.Procedures.CR_REPORT_D2SALDOAWAL: 595:615
Schemas.PDV.Procedures.CR_REPORT_D2SALDOMUTASI: 675:695
Schemas.PDV.Procedures.CR_REPORT_D5: 2604:2624
+74 more

Issue 5350: Unable automatically convert statements that explicitly apply or cancel a
transaction
Recommended action: Revise your code to try move transaction control on side of application.
Issue code: 5350 | Number of occurrences: 9 | Estimated complexity: Simple
Documentation references: https://www.postgresql.org/docs/11/plpgsql-transactions.html
Schemas.PDV.Procedures.HAPUSJURNAL_ANGSPKPP: 891:896
Schemas.PDV.Procedures.INV_REPAIR_RINCIAN: 845:850
Schemas.PDV.Procedures.INV_REPAIR_RINCIAN: 1094:1099
Schemas.PDV.Procedures.INV_REPAIR_RINCIAN: 1349:1354
Schemas.PDV.Procedures.INV_REPAIR_RINCIAN: 1604:1609
+4 more

AWS Schema Conversion Tool Version 1.0.632 Page 34 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 5578: Unable to automatically transform the SELECT statement

Issue 5584: Converted functions depends on the time zone settings

Issue 5591: Unable to convert system object

View Changes
Not all views can be converted automatically. You'll need to address these issues manually.

AWS Schema Conversion Tool Version 1.0.632 Page 35 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Views.TAB_VIEW_TABBLN: 89:102
Schemas.PDV.Views.VKAS_BALANCING: 372:385
Schemas.PDV.Views.V_PEGAWAIKONTRAK: 150:163
Schemas.PDV.Views.V_PEGAWAITETAP: 150:163
+4 more

Issue 5293: Unable to resolve objects

Issue 5584: Converted functions depends on the time zone settings

Trigger Changes
Not all triggers can be converted automatically. You'll need to address these issues manually.

Issue 5326: PostgreSQL doesn't support status definition in the CREATE statement for
triggers/constraints
Recommended action: Disable the trigger/drop the constraint manually if needed.

AWS Schema Conversion Tool Version 1.0.632 Page 36 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue code: 5326 | Number of occurrences: 2 | Estimated complexity: Simple

Documentation references: http://www.postgresql.org/docs/9.6/static/sql-createtable.html
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.UMU_BAYAR_DETAIL.Triggers.BAYARDETAIL_BEFORE_INSERT$(PDV)

Issue 5584: Converted functions depends on the time zone settings

Detailed recommendations for Amazon RDS for MariaDB 10.2 migrations

If you migrate your Oracle database to Amazon RDS for MariaDB 10.2, we recommend the following actions.

Storage object actions

Collection type Changes

Not all collection types can be converted automatically. You'll need to address these issues manually.

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Collection Types.SPLIT_TBL
Schemas.PDV.Collection Types.T_ARY

Constraint Changes
Not all constraints can be converted automatically. You'll need to address these issues manually.

Issue 326: MariaDB doesn't support constraints with the status DISABLED
Recommended action: Drop the constraint.
Issue code: 326 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Tables.KASLINE.Constraints.KEY_KASLINE

Code object actions

Package collection type Changes

Not all package collection types can be converted automatically. You'll need to address these issues manually.

AWS Schema Conversion Tool Version 1.0.632 Page 37 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 118: MariaDB doesn't support the table type

Recommended action: Use an ordinary table.
Issue code: 118 | Number of occurrences: 1 | Estimated complexity: Medium
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Package procedure Changes

Not all package procedures can be converted automatically. You'll need to address these issues manually.

Issue 28: Unable convert variable declaration of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 28 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 273:295

Issue 30: Unable convert variable usage of unsupported datatype

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Packages.PCK_REPORT.Public procedures.INITIAL: 203:213
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT: 2871:2887

Issue 293: Unable to resolve objects

Recommended action: Verify if object JK is present in the database. If it isn't, check the object name or add the

AWS Schema Conversion Tool Version 1.0.632 Page 38 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

object. If the object is present, transform the code manually.

Issue code: 293 | Number of occurrences: 56 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 538:539
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 569:573
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 602:606
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 635:639
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 669:670
+51 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 7 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/string-functions/
Schemas.PDV.Packages.PCK_DATA.Public procedures.CLOSE_FILE: 38:55
Schemas.PDV.Packages.PCK_DATA.Public procedures.INITIAL: 50:68
Schemas.PDV.Packages.PCK_DATA.Public procedures.OPEN_FILE: 69:133
Schemas.PDV.Packages.PCK_REPORT.Public procedures.CLOSE_FILE: 37:54
Schemas.PDV.Packages.PCK_REPORT.Public procedures.INITIAL: 34:52
+2 more

Issue 595: Unable to convert synonym on system object

Recommended action: Perform a manual conversion.
Issue code: 595 | Number of occurrences: 1 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 1935:1938

Issue 9996: Internal Converter error occurred

Function Changes
Not all functions can be converted automatically. You'll need to address these issues manually.

Issue 118: MariaDB doesn't support the table type

Recommended action: Use an ordinary table.
Issue code: 118 | Number of occurrences: 1 | Estimated complexity: Medium
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Functions.TRANS: 128:184

AWS Schema Conversion Tool Version 1.0.632 Page 39 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 19 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Functions.TRANS: 128:184
Schemas.PDV.Functions.TRANS: 189:199
Schemas.PDV.Functions.TRANS: 263:271
Schemas.PDV.Functions.TRANS: 286:294
Schemas.PDV.Functions.TRANS: 310:318
+14 more

Issue 332: MariaDB doesn't support the procedure dbms_output.put_line

Recommended action: Try using INSERT in the log table. To do this, you must add code into
AWS_ORACLE_EXT.PUT_LINE.
Issue code: 332 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Functions.CONNUM_MAIN: 414:457

Issue 338: The converted object is invalid

Issue 340: Unable to convert functions

AWS Schema Conversion Tool Version 1.0.632 Page 40 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Functions.RND: 1237:1251
Schemas.PDV.Functions.RND: 1377:1391
Schemas.PDV.Functions.SPLIT_KATA: 256:296
Schemas.PDV.Functions.SPLIT_KATA: 366:411

Issue 342: Unable to convert exceptions

Recommended action: Review the exception used, and if possible convert it to an exception using the SIGNAL or
RESIGNAL statement.
Issue code: 342 | Number of occurrences: 3 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/declare-condition/
Schemas.PDV.Functions.CDATE: 159:164
Schemas.PDV.Functions.ISNUMBER: 150:155
Schemas.PDV.Functions.IS_DATE: 161:166

Issue 365: Unable to convert analytic functions

Recommended action: Perform a manual conversion.
Issue code: 365 | Number of occurrences: 1 | Estimated complexity: Medium
Schemas.PDV.Functions.PBD_CARISANPER: 108:161

Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.

Issue 211: In MariaDB NULL sorting, NULL values go first for an ascending order and last
for a descending order
Recommended action: Review your transformed code and modify it if necessary.
Issue code: 211 | Number of occurrences: 23 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/select/
Schemas.PDV.Procedures.APPR_UMUM_PUMK: 212:222
Schemas.PDV.Procedures.APPR_UMUM_UMK: 211:221
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPP: 2810:2824
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPPJURNAL: 2843:2857
Schemas.PDV.Procedures.COPY_JURNAL: 283:297
+18 more

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 18 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 52:76
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 79:88
Schemas.PDV.Procedures.PR_APP_SERAH: 46:70
Schemas.PDV.Procedures.PR_APP_SERAH: 73:82
Schemas.PDV.Procedures.PR_NEW_IA: 123:147
+13 more

AWS Schema Conversion Tool Version 1.0.632 Page 41 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 293: Unable to resolve objects

Recommended action: Verify if object %s is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 38 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_CREATEROWREAL: 358:450
Schemas.PDV.Procedures.C_CREATEROWREAL: 465:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 356:452
Schemas.PDV.Procedures.C_CREATEROWSCH: 467:487
Schemas.PDV.Procedures.C_CREATEROWSCH: 571:591
+33 more

Issue 332: MariaDB doesn't support the procedure dbms_output.put_line

Recommended action: Try using INSERT in the log table. To do this, you must add code into
AWS_ORACLE_EXT.PUT_LINE.
Issue code: 332 | Number of occurrences: 5 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPP: 4750:4832
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPPJURNAL: 4696:4781
Schemas.PDV.Procedures.HAPUSJURNAL_ANGSPKPP: 385:476
Schemas.PDV.Procedures.SDM_PROSESGAJIKONTRAK: 1172:1213
Schemas.PDV.Procedures.SDM_PROSESGAJITETAP: 2146:2187

Issue 334: MariaDB doesn't support the dynamic SQL statement EXECUTE IMMEDIATE
Recommended action: Review and modify the execution string.
Issue code: 334 | Number of occurrences: 99 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/execute-statement/
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 773:794
Schemas.PDV.Procedures.CR_REPORT_CASH: 1653:1673
Schemas.PDV.Procedures.CR_REPORT_D2SALDOAWAL: 595:615
Schemas.PDV.Procedures.CR_REPORT_D2SALDOMUTASI: 675:695
Schemas.PDV.Procedures.CR_REPORT_D5: 2604:2624
+94 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 38 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/string-functions/
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 267:280
Schemas.PDV.Procedures.OPENING_BALANCE: 1664:1677
Schemas.PDV.Procedures.PR_CARI_KOPERASI: 225:234
Schemas.PDV.Procedures.PR_CREATE_IA: 280:289
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 393:402
+33 more

AWS Schema Conversion Tool Version 1.0.632 Page 42 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 343: Unable to transform the SELECT statement for a cursor

Recommended action: Try rewriting the select statement.
Issue code: 343 | Number of occurrences: 5 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/cursor-overview/
Schemas.PDV.Procedures.PR_CR_IND_ACCOUNT_ALL: 675:1444
Schemas.PDV.Procedures.PR_CR_IND_ACCOUNT_SUM: 697:1561
Schemas.PDV.Procedures.PR_CR_TAB_LAN: 917:6499
Schemas.PDV.Procedures.PR_IND_GRAPH: 528:1315
Schemas.PDV.Procedures.PR_PROSES_BATALHP: 5172:5304

Issue 355: Converted code might be incorrect because of the dynamic SQL
Recommended action: Please check the dynamic SQL.
Issue code: 355 | Number of occurrences: 10 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/prepared-statements/
Schemas.PDV.Procedures.C_CREATEROWREAL: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 490:511
Schemas.PDV.Procedures.C_CREATEROWSCH: 915:936
Schemas.PDV.Procedures.OPENING_BALANCE: 3336:3357
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 2825:2846
+5 more

Issue 366: Function result could vary from Oracle because of the different result of sorting
Recommended action: Perform a manual conversion.
Issue code: 366 | Number of occurrences: 2 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_CREATEROWREAL: 358:450
Schemas.PDV.Procedures.C_CREATEROWSCH: 356:452

Issue 9996: Internal Converter error occurred

Recommended action: Please submit report to developers.
Issue code: 9996 | Number of occurrences: 5 | Estimated complexity: Complex
Schemas.PDV.Procedures.OPENING_BALANCE: 4617:5427
Schemas.PDV.Procedures.PBD_PROSBAYARPKPP: 958:3491
Schemas.PDV.Procedures.PBD_PROSBAYARPKPP: 1125:3476
Schemas.PDV.Procedures.PENEMPATAN: 665:4629
Schemas.PDV.Procedures.PR_SKEDULMK: 366:1360

Materialized view Changes

Not all materialized views can be converted automatically. You'll need to address these issues manually.

Issue 94: MariaDB doesn't support a materialized VIEW

AWS Schema Conversion Tool Version 1.0.632 Page 43 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Materialized Views.V_PKPPVSKAS321

View Changes
Not all views can be converted automatically. You'll need to address these issues manually.

Issue 75: MariaDB doesn't support VIEW with the READ ONLY option
Recommended action: Use VIEW without this option instead.
Issue code: 75 | Number of occurrences: 9 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-view/
Schemas.PDV.Views.SDMDIDIKAKHIR: 183:196
Schemas.PDV.Views.TAB_VIEW_TABBLN: 89:102
Schemas.PDV.Views.VKAS_BALANCING: 372:385
Schemas.PDV.Views.V_PEGAWAIKONTRAK: 150:163
Schemas.PDV.Views.V_PEGAWAITETAP: 150:163
+4 more

Issue 211: In MariaDB NULL sorting, NULL values go first for an ascending order and last
for a descending order
Recommended action: Review your transformed code and modify it if necessary.
Issue code: 211 | Number of occurrences: 55 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/select/
Schemas.PDV.Views.CTR_REKAPPKPPPEGAWAI: 200:260
Schemas.PDV.Views.C_V_CONVES: 1172:1223
Schemas.PDV.Views.INV_MUTASI: 858:933
Schemas.PDV.Views.INV_MUTASI_2: 654:729
Schemas.PDV.Views.INV_MUTASI_B: 827:906
+50 more

Issue 293: Unable to resolve objects

Recommended action: Verify if object id is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 52 | Estimated complexity: Simple
Schemas.PDV.Views.C_V_CONVES: 9:10
Schemas.PDV.Views.C_V_CONVES: 25:26
Schemas.PDV.Views.C_V_CONVES: 45:49
Schemas.PDV.Views.C_V_CONVES: 54:58
Schemas.PDV.Views.C_V_CONVES: 63:68
+47 more

Issue 340: Unable to convert functions

AWS Schema Conversion Tool Version 1.0.632 Page 44 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Views.TAB_TABMASTER_THN: 47:64
Schemas.PDV.Views.TEST: 43:52
Schemas.PDV.Views.TEST: 191:200
Schemas.PDV.Views.V_REPORT_REKAPKAS_BEBAS: 560:583
+4 more

Issue 365: Unable to convert analytic functions

Recommended action: Perform a manual conversion.
Issue code: 365 | Number of occurrences: 6 | Estimated complexity: Medium
Schemas.PDV.Views.C_V_CONVES: 499:531
Schemas.PDV.Views.C_V_CONVES: 598:630
Schemas.PDV.Views.C_V_CONVES: 707:739
Schemas.PDV.Views.INV_MUTASI_DANA: 40:62
Schemas.PDV.Views.TAB_TABMASTER_PRSH: 97:128
+1 more

Trigger Changes
Not all triggers can be converted automatically. You'll need to address these issues manually.

Issue 243: MariaDB doesn't support the UPDATE OF clause

Recommended action: Perform a manual conversion, please.
Issue code: 243 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-trigger/
Schemas.PDV.Tables.CASH_FLOW.Triggers.TGR_CASH_FLOW$(PDV)

Issue 312: MariaDB doesn't support the DISABLED clause

Recommended action: Drop the trigger.
Issue code: 312 | Number of occurrences: 2 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-trigger/
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.UMU_BAYAR_DETAIL.Triggers.BAYARDETAIL_BEFORE_INSERT$(PDV)

Issue 524: MariaDB doesn't support triggers for multiple events

Recommended action: Try to split the trigger on several independent triggers (one trigger - for one event).
Issue code: 524 | Number of occurrences: 29 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-trigger/
Schemas.PDV.Tables.CASH_FLOW.Triggers.TGR_CASH_FLOW$(PDV)
Schemas.PDV.Tables.INV_CAIR_POKOK.Triggers.INVCAIRPOKOK_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERPEMINJAM.Triggers.INVMTRPEMINJAM_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERTRANSAKSI.Triggers.INVMTRTRANSAKSI_BEFORE_INSERT$(PDV)
+24 more

AWS Schema Conversion Tool Version 1.0.632 Page 45 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Detailed recommendations for Amazon RDS for MariaDB 10.3 migrations

If you migrate your Oracle database to Amazon RDS for MariaDB 10.3, we recommend the following actions.

Storage object actions

Collection type Changes

Not all collection types can be converted automatically. You'll need to address these issues manually.

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Collection Types.SPLIT_TBL
Schemas.PDV.Collection Types.T_ARY

Constraint Changes
Not all constraints can be converted automatically. You'll need to address these issues manually.

Code object actions

Package collection type Changes

Not all package collection types can be converted automatically. You'll need to address these issues manually.

Issue 118: MariaDB doesn't support the table type

Recommended action: Use an ordinary table.
Issue code: 118 | Number of occurrences: 1 | Estimated complexity: Medium
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 2 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER

AWS Schema Conversion Tool Version 1.0.632 Page 46 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Issue 598: MariaDB doesn't support the RETURN TYPE for the cursor
Recommended action: Use cursor declaration without this statement. Also please check if there are variables
depends on this cursor %rowtype and modify them to base %rowtype if necessary.
Issue code: 598 | Number of occurrences: 1 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_REPORT.Public collection types.T_HEADER: 0:62

Package procedure Changes

Not all package procedures can be converted automatically. You'll need to address these issues manually.

Issue 28: Unable convert variable declaration of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 28 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 273:295

Issue 30: Unable convert variable usage of unsupported datatype

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.
Issue code: 218 | Number of occurrences: 1 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Packages.PCK_REPORT.Public procedures.INITIAL: 203:213

Issue 293: Unable to resolve objects

Recommended action: Verify if object Fios is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 93 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 275:278
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 280:287
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 538:539
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 569:573
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 602:606
+88 more

AWS Schema Conversion Tool Version 1.0.632 Page 47 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 6 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/string-functions/
Schemas.PDV.Packages.PCK_DATA.Public procedures.CLOSE_FILE: 38:55
Schemas.PDV.Packages.PCK_DATA.Public procedures.INITIAL: 50:68
Schemas.PDV.Packages.PCK_DATA.Public procedures.OPEN_FILE: 69:133
Schemas.PDV.Packages.PCK_REPORT.Public procedures.CLOSE_FILE: 37:54
Schemas.PDV.Packages.PCK_REPORT.Public procedures.INITIAL: 34:52
+1 more

Issue 576: Unparsed SQL

Recommended action: Perform a manual conversion.
Issue code: 576 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Packages.PCK_REPORT.Public procedures.REFORMAT

Issue 595: Unable to convert synonym on system object

Recommended action: Perform a manual conversion.
Issue code: 595 | Number of occurrences: 1 | Estimated complexity: Simple
Schemas.PDV.Packages.PCK_DATA.Public procedures.LOAD_D2: 1935:1938

Function Changes
Not all functions can be converted automatically. You'll need to address these issues manually.

Issue 28: Unable convert variable declaration of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 28 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Functions.TRANS: 189:199

Issue 30: Unable convert variable usage of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 30 | Number of occurrences: 17 | Estimated complexity: Complex
Schemas.PDV.Functions.TRANS: 263:271
Schemas.PDV.Functions.TRANS: 286:294
Schemas.PDV.Functions.TRANS: 310:318
Schemas.PDV.Functions.TRANS: 333:341
Schemas.PDV.Functions.TRANS: 357:365
+12 more

AWS Schema Conversion Tool Version 1.0.632 Page 48 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 118: MariaDB doesn't support the table type

Recommended action: Use an ordinary table.
Issue code: 118 | Number of occurrences: 1 | Estimated complexity: Medium
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Functions.TRANS: 128:184

Issue 218: MariaDB doesn't support user types

Issue 332: MariaDB doesn't support the procedure dbms_output.put_line

Recommended action: Try using INSERT in the log table. To do this, you must add code into
AWS_ORACLE_EXT.PUT_LINE.
Issue code: 332 | Number of occurrences: 1 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Functions.CONNUM_MAIN: 414:457

Issue 338: The converted object is invalid

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 5 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/string-functions/
Schemas.PDV.Functions.INTDIV: 280:307
Schemas.PDV.Functions.RND: 1237:1251
Schemas.PDV.Functions.RND: 1377:1391
Schemas.PDV.Functions.SPLIT_KATA: 256:296
Schemas.PDV.Functions.SPLIT_KATA: 366:411

AWS Schema Conversion Tool Version 1.0.632 Page 49 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue 365: Unable to convert analytic functions

Recommended action: Perform a manual conversion.
Issue code: 365 | Number of occurrences: 1 | Estimated complexity: Medium
Schemas.PDV.Functions.PBD_CARISANPER: 108:161

Issue 576: Unparsed SQL

Recommended action: Perform a manual conversion.
Issue code: 576 | Number of occurrences: 1 | Estimated complexity: Complex
Schemas.PDV.Functions.SALDO_MMD_PERBULAN

Procedure Changes
Not all procedures can be converted automatically. You'll need to address these issues manually.

Issue 28: Unable convert variable declaration of unsupported datatype

Recommended action: Perform a manual conversion.
Issue code: 28 | Number of occurrences: 6 | Estimated complexity: Complex
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 79:88
Schemas.PDV.Procedures.PR_APP_SERAH: 73:82
Schemas.PDV.Procedures.PR_NEW_IA: 150:158
Schemas.PDV.Procedures.PR_PROSES_PHK_BATAL: 80:89
Schemas.PDV.Procedures.PR_REKAP_CASHFLOW: 99:108
+1 more

Issue 29: Unable convert variable usage of unsupported datatype

Recommended action: The stub-code created. Please perform a manual conversion.
Issue code: 29 | Number of occurrences: 6 | Estimated complexity: Complex
Schemas.PDV.Procedures.PR_NEW_IA: 3393:3394
Schemas.PDV.Procedures.PR_NEW_IA: 3469:3470
Schemas.PDV.Procedures.PR_REKAP_CASHFLOW: 2574:2575
Schemas.PDV.Procedures.PR_REKAP_CASHFLOW: 2897:2898
Schemas.PDV.Procedures.PR_REKAP_CASHFLOWPERIODE: 2253:2254
+1 more

Issue 218: MariaDB doesn't support user types

Recommended action: Revise your architecture with a custom solution to substitute the user type using.

AWS Schema Conversion Tool Version 1.0.632 Page 50 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue code: 218 | Number of occurrences: 15 | Estimated complexity: Complex

Documentation references: https://mariadb.com/kb/en/library/stored-routines/
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 52:76
Schemas.PDV.Procedures.PR_APP_SERAH: 46:70
Schemas.PDV.Procedures.PR_NEW_IA: 123:147
Schemas.PDV.Procedures.PR_NEW_IA: 3393:3394
Schemas.PDV.Procedures.PR_NEW_IA: 3434:3435
+10 more

Issue 293: Unable to resolve objects

Recommended action: Verify if object %s is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 24 | Estimated complexity: Simple
Schemas.PDV.Procedures.C_INS_M_TRANSAKSI: 360:372
Schemas.PDV.Procedures.C_INS_M_TRANSAKSI: 375:379
Schemas.PDV.Procedures.C_INS_M_TRANSAKSI: 382:385
Schemas.PDV.Procedures.C_INS_M_TRANSAKSI: 388:397
Schemas.PDV.Procedures.C_INS_M_TRANSAKSI: 400:405
+19 more

Issue 332: MariaDB doesn't support the procedure dbms_output.put_line

Recommended action: Try using INSERT in the log table. To do this, you must add code into
AWS_ORACLE_EXT.PUT_LINE.
Issue code: 332 | Number of occurrences: 5 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-table/
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPP: 4750:4832
Schemas.PDV.Procedures.BUATJURNAL_ANGSPKPPJURNAL: 4696:4781
Schemas.PDV.Procedures.HAPUSJURNAL_ANGSPKPP: 385:476
Schemas.PDV.Procedures.SDM_PROSESGAJIKONTRAK: 1172:1213
Schemas.PDV.Procedures.SDM_PROSESGAJITETAP: 2146:2187

Issue 334: MariaDB doesn't support the dynamic SQL statement EXECUTE IMMEDIATE
Recommended action: Review and modify the execution string.
Issue code: 334 | Number of occurrences: 104 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/execute-statement/
Schemas.PDV.Procedures.CANCEL_OPENING_BALANCE: 773:794
Schemas.PDV.Procedures.CR_REPORT_CASH: 1653:1673
Schemas.PDV.Procedures.CR_REPORT_D2SALDOAWAL: 595:615
Schemas.PDV.Procedures.CR_REPORT_D2SALDOMUTASI: 675:695
Schemas.PDV.Procedures.CR_REPORT_D5: 2604:2624
+99 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 38 | Estimated complexity: Complex

AWS Schema Conversion Tool Version 1.0.632 Page 51 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Documentation references: https://mariadb.com/kb/en/library/string-functions/

Issue 355: Converted code might be incorrect because of the dynamic SQL
Recommended action: Please check the dynamic SQL.
Issue code: 355 | Number of occurrences: 5 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/prepared-statements/
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 2825:2846
Schemas.PDV.Procedures.PR_CREATE_REPORT_PKPP_KOP: 3004:3025
Schemas.PDV.Procedures.PR_PROSES_BATALHP: 3135:3177
Schemas.PDV.Procedures.PR_PROSES_HP: 4327:4369
Schemas.PDV.Procedures.PR_PROSES_HP_PTK: 4333:4375

Issue 598: MariaDB doesn't support the RETURN TYPE for the cursor
Recommended action: Use cursor declaration without this statement. Also please check if there are variables
depends on this cursor %rowtype and modify them to base %rowtype if necessary.
Issue code: 598 | Number of occurrences: 6 | Estimated complexity: Simple
Schemas.PDV.Procedures.PR_APP_BATAL_SERAH: 52:76
Schemas.PDV.Procedures.PR_APP_SERAH: 46:70
Schemas.PDV.Procedures.PR_NEW_IA: 123:147
Schemas.PDV.Procedures.PR_PROSES_PHK_BATAL: 53:77
Schemas.PDV.Procedures.PR_REKAP_CASHFLOW: 72:96
+1 more

Materialized view Changes

Not all materialized views can be converted automatically. You'll need to address these issues manually.

Issue 94: MariaDB doesn't support a materialized VIEW

Recommended action: Revise your code to replace materialized VIEW with another solution.
Issue code: 94 | Number of occurrences: 1 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/create-view/
Schemas.PDV.Materialized Views.V_PKPPVSKAS321

View Changes
Not all views can be converted automatically. You'll need to address these issues manually.

Issue 75: MariaDB doesn't support VIEW with the READ ONLY option
Recommended action: Use VIEW without this option instead.
Issue code: 75 | Number of occurrences: 9 | Estimated complexity: Simple

AWS Schema Conversion Tool Version 1.0.632 Page 52 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Documentation references: https://mariadb.com/kb/en/library/create-view/

Schemas.PDV.Views.SDMDIDIKAKHIR: 183:196
Schemas.PDV.Views.TAB_VIEW_TABBLN: 89:102
Schemas.PDV.Views.VKAS_BALANCING: 372:385
Schemas.PDV.Views.V_PEGAWAIKONTRAK: 150:163
Schemas.PDV.Views.V_PEGAWAITETAP: 150:163
+4 more

Issue 293: Unable to resolve objects

Recommended action: Verify if object id is present in the database. If it isn't, check the object name or add the
object. If the object is present, transform the code manually.
Issue code: 293 | Number of occurrences: 52 | Estimated complexity: Simple
Schemas.PDV.Views.C_V_CONVES: 9:10
Schemas.PDV.Views.C_V_CONVES: 25:26
Schemas.PDV.Views.C_V_CONVES: 45:49
Schemas.PDV.Views.C_V_CONVES: 54:58
Schemas.PDV.Views.C_V_CONVES: 63:68
+47 more

Issue 340: Unable to convert functions

Recommended action: Create a user-defined function.
Issue code: 340 | Number of occurrences: 9 | Estimated complexity: Complex
Documentation references: https://mariadb.com/kb/en/library/string-functions/
Schemas.PDV.Views.SYSTABLES: 95:105
Schemas.PDV.Views.TAB_TABMASTER_THN: 47:64
Schemas.PDV.Views.TEST: 43:52
Schemas.PDV.Views.TEST: 191:200
Schemas.PDV.Views.V_REPORT_REKAPKAS_BEBAS: 560:583
+4 more

Issue 365: Unable to convert analytic functions

Trigger Changes
Not all triggers can be converted automatically. You'll need to address these issues manually.

Issue 243: MariaDB doesn't support the UPDATE OF clause

Recommended action: Perform a manual conversion, please.

AWS Schema Conversion Tool Version 1.0.632 Page 53 of 54

03/06/2020 11:41AM
Database migration assessment report
Source database: [email protected]:32769:ORCLCDB
Oracle Database 12c Enterprise Edition 12.2.0.1.0 (64bit Production), Enterprise edition

Issue code: 243 | Number of occurrences: 1 | Estimated complexity: Simple

Documentation references: https://mariadb.com/kb/en/library/create-trigger/
Schemas.PDV.Tables.CASH_FLOW.Triggers.TGR_CASH_FLOW$(PDV)

Issue 312: MariaDB doesn't support the DISABLED clause

Recommended action: Drop the trigger.
Issue code: 312 | Number of occurrences: 2 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-trigger/
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.UMU_BAYAR_DETAIL.Triggers.BAYARDETAIL_BEFORE_INSERT$(PDV)

Issue 524: MariaDB doesn't support triggers for multiple events

Recommended action: Try to split the trigger on several independent triggers (one trigger - for one event).
Issue code: 524 | Number of occurrences: 29 | Estimated complexity: Simple
Documentation references: https://mariadb.com/kb/en/library/create-trigger/
Schemas.PDV.Tables.CASH_FLOW.Triggers.TGR_CASH_FLOW$(PDV)
Schemas.PDV.Tables.INV_CAIR_POKOK.Triggers.INVCAIRPOKOK_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERPEMINJAM.Triggers.INVMTRPEMINJAM_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERRINCIAN.Triggers.INVMTRRINCIAN_BEFORE_INSERT$(PDV)
Schemas.PDV.Tables.INV_MASTERTRANSAKSI.Triggers.INVMTRTRANSAKSI_BEFORE_INSERT$(PDV)
+24 more