This error occurs when the Migration Workbench has failed to understand the T-SQL code. This is likely to be caused by an incomplete representation of the T-SQL syntax by the Migration Workbench parser.
Some identifiers such as ERROR, DATETIME, and OUTPUT are not official T-SQL reserved words but have meaning in T-SQL syntax. If your T-SQL code uses these words as object names, you must select the "Allow 'Reserved Words' in table names" check box in the Parse Options tab of the Source Model property sheet for the particular object and then reparse the object. The parser then recognises that these words are object names. If you do not select this check box, you will encounter a ParseException. This functionality is still in development and is, therefore, currently offered as an option instead of as the default.
When you are reporting problems, please include at least the couple of lines around the ParseException if it is not feasible to send the entire stored procedure. The reason for this is that the error may occur up to six words ahead of the indicated location.
Examples and brief explanations of <STRING values that may present this error are outlined below.
CONSTRAINT
CONSTRAINT is not parsed
in CREATE TABLE statements. You should remove CONSTRAINT and add it
manually. This is e
=
Subselect, SUM, or CASE
in queries.
(
Can be complicated INNER
JOIN, or CREATE TABLE statement issue.
WITH
WITH may be associated
with DBCC. DBCC is a hands-on maintenence command in T-SQL. DBCC is
not required in Oracle.
&
Bit-wise operations are
not automatically converted. However, there is a BITAND function in Oracle.
PRIMARY
CREATE TABLE statements
issue, complete CREATE TABLE syntax is not covered.
INNER
Some INNER JOIN complication.
DBCC
DBCC is a hands-on
maintenence command in T-SQL. DBCC is not required in Oracle.
WHEN
Complicated CASE statement.
CLUSTERED
CREATE TABLE statement
issue, complete CREATE TABLE syntax is not covered.
CASE
Complicated CASE
statement, for example one that includes SUBSELECT.