SnowConvert: Issues Report

What is an “Issue”?

An issue is a message that provides relevant information about the transformations done by SnowConvert.

Where can I find it?

The issues report can be found in a folder named “Reports”, in the output folder of your conversion. The name of the file itself starts with “Issues” so it can easily be located.

The format of the file is .CSV.

What information does it contain?

The issues report contains the following information about all the issues added during the conversion:

ColumnDescription
Session IDThe session ID of the transformation. This is a unique identifier for the transformation session.
SeverityOne of the following values: Critical, High, Medium, Low, or None. This is an indicator of how much effort it takes to manually solve the problem. The None severity does not punish the conversion rate of the code unit.
CodeA unique identifier for the issue.
NameThe name of the issue message.
DescriptionThe final message that was added to the output code. Something important to take into account is that some of the issues might have slightly different descriptions even though they have the same issue code, this happens because some of the descriptions have dynamic values.
Parent FileThe relative path of the file where the issues is generated.
LineThe text line within the parent file where the issue is generated.
ColumnThe column within the line where the issue is generated.
Code Unit DatabaseThe database name (if applicable) of the code unit that contains the issue message. It might be empty because the generated issue has no explicit database name or it is not generated inside a code unit with a name that identifies it.
Code Unit SchemaThe schema name (if applicable) of the code unit that contains the issue message. It might be empty because the generated issue has no explicit schema name or it is not generated inside a code unit with a name that identifies it.
Code Unit PackageThe package name (if applicable) of the code unit that contains the issue message. It might be empty because the generated issue has no explicit schema name or it is not generated inside a code unit with a name that identifies it. This column only applies to Oracle SQL migrations.
Code Unit NameThe name of the code unit, without database and or schema qualification. This column only applies to code units that have a name that identifies them.
Code Unit IDA string that uniquely identifies the code unit. The name of the object, without database and or schema qualification.
Code UnitThe code unit that contains the issue.
Code Unit SizeA size classification of the code unit, based on its line of code. The available measurements are XS, S, M, L, and XL.

Report Example

Given the following Oracle SQL input code, SnowConvert will add the SSC-FDM-OR0035 conversion issue.

CREATE OR REPLACE PROCEDURE schema1.procedure1
AS
BEGIN
  DBMS_OUTPUT.PUT_LINE('hello world');
END;
Copy
CREATE OR REPLACE PROCEDURE schema1.procedure1 ()
RETURNS VARCHAR
LANGUAGE SQL
COMMENT = '{"origin":"sf_sc","name":"snowconvert","version":{"major":1, "minor":0},{"attributes":{"component":"oracle"}}'
EXECUTE AS CALLER
AS
$$
  BEGIN
    --** SSC-FDM-OR0035 - CHECK UDF IMPLEMENTATION FOR DBMS_OUTPUT.PUT_LINE_UDF. **
    CALL DBMS_OUTPUT.PUT_LINE_UDF('hello world');
  END;
$$;
Copy

The row in the issues report for the SSC-FDM-OR0035 conversion issue will have the following information:

Column

Value

Session ID

Not available

Severity

Low

Code

SSC-FDM-OR0035

Name

Custom UDF inserted

Description

CUSTOM UDF ‘DBMS_OUTPUT.PUT_LINE_UDF’ INSERTED.

Parent File

sample.sql

Line

4

Column

3

Code Unit Database

N/A

Code Unit Schema

schema1

Code Unit Package

N/A

Code Unit Name

procedure1

Code Unit Id

schema1.procedure1

Code Unit

CREATE PROCEDURE

Code Unit Size

XS
Language: English