Description

When you run the JEE analysis some of the JEE objects are not saved in local base.

Observed in CAST AIP
Release
Yes/No
8.3.x(error)
8.2.x(tick) x<5
8.1.x (tick) 
8.0.x (tick)
7.3.x(error)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)

Step by Step scenario

  1. Create a user defined analysis unit with some application root path.
  2. Create another user defined analysis unit with other application root path.
  3. Annotate the analysis units.
  4. Run the analysis, in the Keys table you will see the objects on the analysis unit which has run last.
Action Plan

To troubleshoot this issue, you need the following Relevant input

Perform the below actions:

  1. Check if you have two user defined analysis units which share the same name, their resulting KB projects are shared (that is, only one project is created),such as in the below scenarios then check these solutions:
    the two analysis units are in two different applications, or separated into two execution units, the last executed one replaces the content of the other one.
    the two analysis units are in the same execution unit, the two contents are merged, in this merge case, this may lead to problems (e.g., when defining UDMs per analysis unit, this will generate an empty module).
  2. If this is the case then follow the below steps to perform the analysis:
    1. Take the backup of your management base first, because we have to run a query and if that does not work you should have a backup to restore it.
    2. Run the below query in your management base:

      UPDATE CMS_J2EE_Analysis cja
      SET    Object_Name = cja.Object_Name
                    || '_'
                    || CAST(cja.Object_Id AS VARCHAR),
             AnalyzerProjectName  = NULL
      WHERE  cja.Project_Id IS NULL
      AND    cja.Object_Name IN
             (SELECT  cja.Object_Name
             FROM     CMS_J2EE_Analysis cja
             GROUP BY cja.Object_Name
             HAVING   COUNT(1) > 1
             );
    3. Run the full analysis.
  3. If the issue is not about the above scenario, then contact CAST Technical Support with Relevant input.

Relevant Input

CAST Support Tool (CST) - alias Sherlock by checking Export bases, Export logs, Export Configuration files and export source code. 

Impact on Analysis and Snapshot

Impact : J2EE objects will not be created

After applying the work around : There is no impact after applying the work around.

Notes/comments

Ticket # 9196

The issue is fixed in CAST 8.2.5

Related Pages