How to Work With Parser Errors
Parser errors may occur during conversion. To make it convenient to view error messages, the Ispirer toolkit provides an opportunity to view a full report with the results of the conversion. You can also see error messages in the sqlways.log file located in the export directory.
To open the report, go to the Completing Page and click on the Review Full Report button.
On the page that opens, you can see information about objects and errors. To see the errors for a specific object type, please click on the object type in the “Information Table” (for example “Views”).
This page will display the object names and error messages. If in the Error Message column you see that there are Parser Error, it means that tool was not able to read and analyze the source code of the object and parser failed.
You can also click on Erors Summary on the Migration Report page. On this page you will see the entire list of errors, including parser errors.
So that we can fix this error, you should send the source code of the object(s) or the statement on which the error occurs to email@example.com. The source code can be found in the source database, or you can open the export directory, find the SQL file with the object name and open it. It will contain the source code, which you can send us. We will analyze the code and prepare a version of the Ispirer toolkit that will parse the source code.
If you have any additional questions please contact us.