The objective of this page is to give a detailed list of issues related to different Source Extractors and methodology to handle these issues.
This page will help you solve problems related to different Source Extractors provided by CAST i.e People Soft, Sibel, SQL PL/SQL or Sybase.
Source Extractor is a Component of CAST AIP that will help you Extract your Source code and help you analyze them using CAST.

For more information, refer to:

  • Official documentation: Please refer to the technology specific master pages mentioned in the Table of Content Section to find its related documentation
  • Online-help: Please refer to the technology specific pages to find the related Online-help
*Observed in CAST AIP
*Observed on RDBMS
Oracle Server(tick)
Microsoft SQL Server(tick)
Action plan

Proceed with the following steps:

  1. Other than the SAP extractor, check in the CAST AIP Extensions > CAST AIP Extensions Documentation > CAST AIP Extensions, in the Release note of the Extension, check in the "CAST AIP compatibility" that the Extension version is supported by CAST AIP.
  2. Select the section you are interested in:
  3. If the problem you are facing does not match any case listed in this page, contact CAST Technical Support with below relevant input in order to reproduce the issue and to investigate.

How to check the version of the source extractor used by the customer

  1. With the extension downloader, select the installed tab to list all the extension downloaded and istalled :
    Figure 1
  2. in the CAST Support Tool (Sherlock) what are the extractor installed in the DMT.
    1. To install an extractor in the DMT, user need to copy this extractor in the Plugins folder that is in the Delivery folder as shown in the below example :

      Figure 2
    2. The Plugins folder is not retrieved by the Sherlock, only the Data folder is retrieved:
      Figure 3
    3. In the Sherlock output, the Data Folder is in : <Sherlock Folder>\ConfigurationFiles\Delivery folder as shown above
    4. In the Data Folder, the Plugins are referenced in the *.entity.xml files as you can see below
      Figure 4
    5. If you are checking for a specific extractor, look into this file for the name of the extractor, the version is suffixed.

How to check the version of the source extractor used by the customer for Siebel Extractor

  1. Download the Siebel newest version using the extension downloader
  2. Get the Siebel plugin version of the downloaded version.
    1. To get the date, open the *mda file, unzip them and check the date of the JAR files
  3. Get the Siebel plugin version at the customer site
    1. To get the date, open the *mda file, unzip them and check the date of the JAR files
  4. If the JAR files date are different, replace the customer's with the newest.

For a Siebel packaging you always make sure to use a .castextraction file that satisfies the Siebel Recommendation.

If you provide an Oracle .castextraction file and use the Siebel discoverer in DMT, no package will be created by DMT.

To make sure, you have a Siebel castextraction file  used, you need to make sure to run the extraction always using the batch file located inside the Siebel Extension as mentioned here.

From Siebel 5.2.5 funcrel, there is a check introduced to make sure that only a Siebel castextraction file is identified by the Siebel discoverer. 

Extension Version Consistency to be checked - Siebel/Peoplesoft

We always need to make sure that Siebel/Peoplesoft extension used for Vanilla and Project schemas are the same. 

If there is a difference in the Siebel/Peoplesoft Extension installed on the Vanilla and Project, then we need to update the extension version on the triplet and re-run the analysis. 

But do note, if there is any change in the extractor part of extension (defined in release notes of extension), then packaging will also have to be re-run. 

From Siebel Extension version 5.2.3 funcrel, there is a check introduced to identify the version of CAST AIP as well as the Siebel extension. 

From Peoplesoft Extension version 5.1.10 funcrel, there is a check introduced to identify the version of CAST AIP as well as the Peoplesoft extension. 

Multithreaded Export Option - Cast Database Extractor

This option is mainly used to reduce the extraction run time. 

If you do observe performance issues during database extraction, we can suggest the customer to check this option. 

It can help to reduce the runtime from 3 days to 2 days. 

The option is located in the Expert Panel of the Cast Database extractor. 

If the PeopleSoft discrimination is not run, it can be because of 2 conditions - Either the Vanilla schema is not referenced in the Project schema or there are 2 projects present in the project schema.

To confirm this, you can run the below queries - 

select count(1) from Keys where ObjTyp = 1600003 and KeyNam = 'Project'

select var_value from cms_tool_variable where var_name = 'PSOFT_VANILLA_SCHEMA'

The first query should return 0 and the second query should return the name of your PeopleSoft vanilla schema.

If it returns any other value then we need to check the configurations in CAST-MS.

Relevant Input

  • If the extraction is done using a Standalone extractor (SQL Extractor, FORMS extractor, ABAP Extractor, ..), provide the version of the extractor, the extraction log file and screenshots from the standalone extractor showing the configuration settings.
  • If the extraction is an offline extraction (for PL/SQL - TSQL - ASE - DB2 z/OS), provide the source code.
  • If the discrimination for Siebel/Peoplesoft is not run, we specifically require the ApplicationExtensions-XXXXXXXX-XXXXX.castlog from the snapshot/analysis logs folder.

Related Pages