Error Specifications & Troubleshooting

This topic delivers comprehensive guidance on error specifications and troubleshooting, empowering you to rapidly detect and resolve issues during code transformation. Prompt error capture and resolution are vital to:

Minimize operational disruptions
Preserve transformation integrity

By leveraging this advice on effective error logging and troubleshooting strategies, you’ll be able to swiftly pinpoint root causes. Our detailed support resources are provided in a range of message formats, including:

Info: Contextual insights for informed decision-making.
- Format: **Info**: [Brief Description] – [Additional Context/Details]
- Example: Info: Alter Sequence is not supported in the selected source.
Error: Clear explanations for swift issue resolution.
- Format: **Error**: [Brief Description] – [Additional Context/Details] – [Immediate Required Action]
- Example: Error: Issue encountered while opening cursor object.
Warning: Proactive alerts for potential pitfalls.
- Format: **Warning**: [Brief Description] – [Additional Context/Details] – [Urgent Recommended Action]
- Example: Warning: Metadata not found for table.
ToDo: Actionable steps for efficient troubleshooting.
- Format: **ToDo: Manual intervention required.** <Message>
- Example: ToDo: Manual intervention required. The selected target does not directly support Collect Stats.
Alert: Urgent notifications for critical issues.
- Format: **Alert**: [Brief Description] – [Additional Context/Details] – [Recommended Action]
- Example: Alert: Your conversion quota has been exhausted. Contact us at info@leaplogic.io to renew the license and ensure a seamless experience.

The table below displays various categories of issues you may encounter when transforming legacy workloads to cloud-native stack.

Category	Description
BTEQ	This error category includes code transformation issues that occur in BTEQ scripts or queries coming in BTEQ blocks. For instance, incorrect syntax, unsupported commands (e.g., auto-conversion of command logon is not supported on the target platform), etc.
DDL	This error category includes code transformation issues that occur in DDL scripts or queries. For instance, incorrect syntax, missing Primary Key details, Unique Primary Index is not supported in the target, etc.
NOT_SUPPORTED_IN_TARGET	This error category includes issues related to the patterns, clauses, statements, constraints, etc., for which auto-conversion is not supported in the target. These issues are often caused by target environment incompatibilities and may require manual intervention to ensure a smooth transformation.
DML	In workload transformation, code transformation issues that occur in DML scripts or queries are categorized as DML related issues.
FUNCTION	This error category includes code transformation issues that are related to functions such as syntax errors, unsupported functions, incompatibilities, etc. For instance, auto-conversion of the UNPIVOT function is not supported in the target, the function has an invalid number of arguments, etc.
FLD	This error category includes code transformation issues that occur in FLD scripts.
PROCEDURE	This error category includes code transformation issues related to the transformation of stored procedures.
VARIABLE	This error category includes code transformation issues related to variables in queries. For instance, some variables could not be auto converted to the target or could not auto-convert the fetched record from the cursor assigned to the variable.
EXPRESSION	This error category includes code transformation issues related to expressions in queries. For instance, could not auto-convert various expressions such as date format, mathematical expressions, etc., to the target.
METADATA_NOT_FOUND	This error category includes code transformation issues caused by missing metadata for tables, columns, databases, and queries. These issues can arise when necessary metadata is unavailable or incorrectly defined in the input file.
DATA_TYPE_ISSUE	This error category includes code transformation issues related to various data types in queries. For instance, the auto-conversion of certain data types may not be supported on the target platform.
UNSUPPORTED	This error category includes code transformation issues related to various unsupported statements, operations, arguments, etc. For instance, auto-conversion of various statements such as signal and resignal is not supported on the target platform.
EXCEPTION	This error category includes code transformation issues caused by unexpected errors such as handler exceptions in stored procedures.

You can review the detailed error specifications associated with the transformations in the converted artifacts inline within the Transformation report > Package section.

Furthermore, for a comprehensive overview of the Transformation report, refer On-premises to Cloud Transformation Report.