Detailed technology support
|Supported||Supported by reference||Deprecated||Comments|
Oracle 8i (8.1.6.x, 8.1.7.x)
Please note that the extraction of schemas on Oracle 8i via the CAST Delivery Manager Tool and via the standalone CAST Database Extractor is now unsupported. However, it is still possible to analyze Oracle 8i if you have output from an older version of the standalone CAST Database Extractor.
Oracle 9i R1 (184.108.40.206.x)
Oracle 9i R2 (220.127.116.11.x)
Oracle 10g R1 (10.1.0.x) with x ≥ 2
Oracle 10g R2 (10.2.0.x) with x ≥ 2
Oracle 11g R1 (18.104.22.168 - 22.214.171.124)
|Oracle 11g R2 (11.2)|
|Oracle 12c R1 (12.1)||Supported with limitations: New syntax introduced in Oracle 12c is not supported.|
Required third-party software
To successfully deliver and analyze Oracle Server PL/SQL code, the following third-party software is required:
Install on workstation running the DMT (for extraction)
Install on workstation running CMS (for analysis)
All that is required is network access to the live database/schema to be packaged.
Specific connection configuration for Oracle "pluggable" database servers in the CAST Delivery Manager Tool
Please ensure that you use the Service option (rather than the SID option) when configuring the CAST Delivery Manager Tool connection parameters to a schema hosted in a pluggable database.
Oracle Server objects and links
The following section lists the objects and links between objects that the SQL Analyzer is capable of detecting and storing in the CAST Analysis Service:
Collection Nested Table Type
Index, Foreign Key Constraint, Primary Key Constraint, Check Constraint and Unique Key Constraint
Object Type (Incomplete, Body and Header)
View (Normal and Materialized)
Object properties that are supported by the current release of the SQL Analyzer are described in the attached Excel file:
Links detected by the SQL Analyzer are listed in the attached Excel file:
Technology support notes
This section provides more detail about the support for specific Oracle Server syntax and the way in which CAST handles them.
Oracle 11G R1
The following syntax introduced in Oracle 11g R1 is supported (other new syntax is not supported):
- New dataypes:
- BINARY XML
- PL/SQL CONTINUE statement
- Compound trigger type
- REGEXP Built-ins
- NON ANSI JOIN relations between tables
OPEN FOR statement
The OPEN FOR statement for CURSORS (available since version 10G) is not supported.
Conditional compilation directives
Conditional compilation directives (i.e. directives starting with $$ or $, such as $$PLSQL_UNIT, $if, $else, $end etc.) are ignored during an analysis and therefore syntax errors do occur, and the object (function, procedure, trigger,..) is not saved in the CAST Analysis Service.
Links between objects belonging to different schemas not in the same Oracle instance
"Public DB links" are extracted and saved in the Analysis Service, but remote object resolution is not performed by a standard analysis. For instance, a PL/SQL procedure using a remote table through a DB Link on a remote Oracle instance, will have a missing link to this table. A custom workaround is possible that will create this missing link in some situations. Please contact CAST Support for more information.
A syntax error is reported by the analyzer when analyzing syntactically correct code containing superfluous parentheses. A superfluous parenthesis is a parenthesis that can be omitted without changing the result of the query. The following cases have been identified causing the issue:
Case 1: SELECT statement between parentheses followed by another SELECT statement between parentheses:
Case 2: FROM clause containing an ORDER BY clause or a WITH clause followed by parentheses:
The following section lists technical and functional aspects with regard to analysis of Oracle Server source code:
Wrapped PL/SQL source code
Wrapping is the Oracle process of hiding PL/SQL source code. The CAST Database Extractor (either embedded in the CAST Delivery Manager Tool or standalone) cannot access the wrapped item's source code, and instead generates a generic body for these objects. These objects can be analyzed by the CAST PL/SQL Analyzer, but with limitations:
- All "fan-out" Quality Rules/metrics (for example "Avoid Artifacts with High Fan-Out - 7778") will not be taken into account
- All Quality Rules/metric based on properties (for example "Number of Code Lines - 10151") will not be taken into account
- For wrapped package/type headers and bodies, the sub-object declaration is not available, therefore the analyzer cannot create these objects
As wrapped objects have no fan-out, they will have no direct or indirect link to End Points and Data Functions. Therefore, you may consider them as Transaction End Points
Please note that currently inter-Application links (i.e. links between source code in separate Applications) between the following combinations of technologies is not supported:
- Between Oracle Server PL/SQL Analysis Units in different Applications
- Between Oracle Forms Analysis Units and Oracle Server PL/SQL Analysis Units in different Applications
If you do require link resolution, then all Analysis Units must belong to the same Application.
Invalid Oracle Server objects
The analyzer does not analyze objects that are marked as invalid in the Oracle Server system catalogue. Invalid objects are still visible in CAST Enlighten (with the property "Object is invalid") but no links will be created from or to these objects. An entry in the analysis log will be created as follows:
Oracle objects containing the word LOG as an alias
When the word "LOG" is used as an alias, the SQL analyzer will raise a syntax error during the attempted analysis of the object. The object that contains the alias will not be analyzed once the syntax error has been raised. To workaround this issue, edit the object and replace the alias "LOG" with another alias name.
Fine Grain Impact Analysis
The functionality known in previous releases of CAST AIP as the Fine Grain Impact Analysis (FGIA) for participating Oracle schemas is no longer available (and has not been since CAST AIP 7.2.x). There is no workaround for this feature.