Description

This page explains the impact of the below Resolution error message you can see in the PL/SQL Extraction 

Resolution error type in: XXXXX for identification group: DT on value: ***.PLS_INTEGER

or

Resolution error type in: XXXXX for identification group: DT on value: ***.ODCIINDEXCTX

or

Resolution error type in: XXXXX for identification group: DT on value: ***.STRING

or

Resolution error type in: XXXXX for identification group: DT on value: ***.XMLFORMAT


This page can be used only if the 4 types ODCIINDEXCTX, PLS_INTEGER, STRING, XMLFORMAT appear in the Resolution error message.

Observed in CAST AIP
Release
Yes/No
8.3.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
CSS(tick)
Step by Step Scenario
 Run the DB extractor
Action Plan

This Resolution error message means that the Extractor is not able to identify the types ODCIINDEXCTX, PLS_INTEGER, STRING, XMLFORMAT when they are defined in an Oracle table, stored procedure, function or index.

This error does not block the extraction. However the objects that are involved in the error message will be extracted.

The impact of these Resolution error will appear during analysis that will raise warning such as :

Warning  unresolved reference 'DT.-1' used in property 'CAST_AST_WithResolutionSymbolReference.resolutionSymbol'

This Resolution errors are appearing when using PL/SQL extractor older than the PL/SQL extractor version 2.7.

The PL/SQL extractor version 2.7 is used by the DMT starting from CAST AIP 8.1.0. Then, these warning messages will not appear in the extraction, using the PL/SQL Online Extraction (CAST Extractor for Oracle) and no warning related to these types will appear during analysis.

Nevertheless, to avoid Added/Deleted objects in the dashboard, if you have extracted the PL/SQL schema using PL/SQL extractor older than PL/SQL extractor version 2.7, and having the Resolution error messages, you must use the same PL/SQL extractor than the previous extraction.

Related Pages


Notes

Ticket # 9389