Purpose (problem description)

This guide gives the general approach to troubleshoot syntax error warnings in a PL/SQL analysis

The warning message in the analysis log file is : Syntax error found in %.%.src'

You can also refer to the following Official Documentation :

For 8.3 : Oracle Server , Microsoft SQL Server and Sybase ASE

For 8.2 : Oracle Server , Microsoft SQL Server and Sybase ASE , IBM DB2

For 8.1 : Oracle Server , Microsoft SQL Server and Sybase ASE , IBM DB2

For 8.0 : Oracle Server , Microsoft SQL Server and Sybase ASE , IBM DB2

Observed in CAST AIP
Release
Yes/No
8.3.x (tick)
8.2.x(tick) 
8.1.x(tick) 
8.0.x (tick) 
7.3.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
CSS1(tick)
Step by Step scenario
  1. Package and deliver the Oracle extraction
  2. Run analysis
  3. Open the analysis log file
Action Plan

Proceed with the below steps:

  1. Validate customer expectation
    Validating customer expectation means identifying the unsupported syntax, and checking in official documentation if it is supported or not
    1. Open the Analysis Log and detect the line with the syntax error message. Open the detailed view of the log and detect the source code file location, the source line and source column:
      Figure 1

    2. Open source code file  in a text editor(for example notepad++) and detect the corresponding source line:
      Figure 2

      The column corresponds to the character number of the invalid syntax, but it is not 100% accurate due to whitespaces. In the above example it the error is the  double $$

    3.  According to the PL/SQL analyzed you can check in the official doc if this is a documented supported or unsupported syntax: Oracle Server , Microsoft SQL Server and Sybase ASE , IBM DB2

      If Official Documentation states that the syntax is not supported, then this is expected behavior : explain it to customer, referring to the Official Documentation

    4. Check on the Internet in which version of Oracle the syntax was introduced. If the syntax was introduced in a version of Oracle that is not supported, then this is expected behavior. For Support : Explain this to the user, referring the Official Documentation

    5. If the syntax is supported, then you can you go to Step 2 and check if the syntax error is part of the known cases

  2. Check for known cases.
    Here is a list of known cases of syntax error warnings :
    CMS Snapshot Analysis - Run Analyzer - Warnings - Oracle Server PL SQL with Core CAST AIP - Syntax errors - XML Extensions ,
    CMS Snapshot Analysis - Run Analyzer - Warnings - PL SQL - Syntax error - "AS OF"
  3. If you do not find the information you are looking for a solution for your problem in this page,  contact CAST Technical Support, with the below Relevant Input

Relevant Input

  1. CAST Support Tool (CST) - alias Sherlock with the options export Logs, export CAST Databases (for Management Base only)
  2. The DatabaseExtraction.uaxdirectory file, the instance UAX file I.x.uax, the schema UAX and SRC files, the SRC file containing the syntax error and the corresponding UAX file
Impact of syntax errors

If the analyzer encounters a syntax error, it skips the file.

So, the .src file is not analyzed and no objects or link in this file will be created.

Notes/comments

 Tickets # 9720, 9409, 9408, 9150 

Related Pages