Purpose (problem description)
This page provides information on the violation raised for the rule-“Avoid using deprecated objects” on Oracle connection objects:
Observed in CAST Version
Release | Yes/No |
---|---|
8.3 |
Observed in JEE Extension version
Release | Yes/No |
---|---|
>=1.0.x |
Observed in RDBMS
RDBMS | Yes/No |
---|---|
CSS |
Step by Step scenario
- Run analysis+snapshot
- Launch Dashboard
- Observe violation for rule- “Avoid using deprecated objects” on Oracle connection objects
Action Plan
If you observe the violations raised for the rule- “Avoid using deprecated objects” on Oracle connection objects then please note the below points:
- This is an expected behavior if these connection objects are coming from jar- Ojdbc14. Because they are actually deprecated.
- You can refer - http://www.microdeveloper.com/ojavadoc/deprecated-list.html where you will see all the deprecated class/method/fields.
- If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input
Relevant input
- CAST Support Tool (CST) - alias Sherlock export with the following options Export CAST Bases with Management Base, Knowledge Base, Central base, Measurement Base
- Violation screenshot
Notes/comments
Ticket #21595
Related Pages