CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer on Documentation - V2

CMS Snapshot Analysis - Run Analyser - Fatal Error - Universal Analyzer - Invalid type name xxx not declared in metamodel

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution to error message - Invalid type name: ‘xxx’ (not declared in metamodel) which occurs during running Universal Analysis

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	✅
CSS2	✅
CSS1	✅

Step by Step Scenario

Configure UA analysis
Run Analysis

Action Plan

Check if the object type for which the error occurs is present on the Knowledge base
Run the below query for each object type

CMS Snapshot Analysis - Run Analyser - Fatal Error - Universal Analyzer - PeopleSoft - function psoft metrics update does not exist

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page is a troubleshooting guide for the below error:

Error while executing batch : Select <Knowledge_Base>.psoft_metrics_update()
Query failed because :
Error : function <Knowledge_Base>.psoft_metrics_update() does not exist.

This error occurs while running peoplesoft analysis during the step of running tools after analysis - “PeopleSoft Metrics Update”

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - An exception occurred while searching for the substring

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page is a troubleshooting guide for Universal analysis failing with error An exception occurred while searching for the substring using a regular expression.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	❌

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	✅
CSS2	✅
CSS1	❌

Step by Step scenario

Configure UA job
Run analysis and analysis fails with error

Action Plan

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - Code only checksum calculation for object failed because the code is not well formed

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page gives a solution to the error - Code only checksum calculation for object failed because the code is not well formed. After the occurrence of this error the analysis fails at the Universal Importer job step as seen in the below screenshot.

This issue is planned to be fixed in PeopleSoft package 5.0.2

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x	✅
7.2.x	✅
7.0.x	✅

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - Error retrieving language pattern file for language PowerCenter

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

UI job fails quickly with Error Code 2

with message error retrieving language pattern file for language PowerCenter

Any UI language pack was required to have a language pattern to be defined since 7.0.x, x = 20,21

Error free logs - CMS Snapshot Analysis - Run Universal Analyzer - Custom UA profile - Error Free Logs - CAST AIP 8 - CAST Internal

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x	❌
7.2.x	❌
7.0.x	✅

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - Failed to parse xml file File cannot be opened

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page gives solution to the below error which occurred while running a UI analysis:

Failed to parse xml file: (File cannot be opened (pos l: 0 col: 0))

Error free logs - CMS Snapshot Analysis - Run Universal Analyzer - Custom UA profile - Error Free Logs - CAST AIP 8 - CAST Internal

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.2	✅ x = 2
7.2.x	❌
7.0.x	❌

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - Invalid Category Failed to process job

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Between CAST versions 6.0 and 6.4, changes were made to the way in which Universal Analyzer profiles are interpreted and as a result, some of the existing categories and properties are now deprecated.

If the error “Invalid catergory … failed to process job” is displayed during a Universal Analyzer analysis, check the Universal Analyzer profile for any unsupported categories used in the xxxMetaModel.xml file.

Error free logs - CMS Snapshot Analysis - Run Universal Analyzer - Custom UA profile - Error Free Logs - CAST AIP 8 - CAST Internal

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - PeopleSoft Analyzer - Copy file error There is not enough space on the disk

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page describes the rule to estimate the space needed by the PeopleSoft analyzer during the Completion Process

Applicable in CAST Version

Release	Yes/No
8.3.x	❓
8.2.x	❓
8.1.x	❓
8.0.x	❓
7.3.x	❓
7.2.x	?
7.0.x	✅

Action Plan

Here is the rule to estimate the space needed by the PeopleSoft analyzer during the Completion Process:
1. At the end of the process, when all the steps have been performed, the final size is (.UAX + .SRC) files size in the delivery folder = .CastExtraction file size x 3,5 then Final size = .CastExtraction file size x 4,5.
2. During the completion step, the process needs to copy the .UAX and .SRC files in tmp and working folders, then Estimated size during the completion steps is:
  (.UAX + .SRC) files size in the delivery folder + (.UAX + .SRC) files sizein the tmp folder + (.UAX + .SRC) files sizein the working folder + .CastExtraction file size = (.CastExtraction file size x 3,5 ) x 3 + .CastExtraction file size
  Estimated file size ~= .CastExtraction file size x 12
Create space in hard disk
If you are facing this issue on supported version of CAST AIP then contact CAST Technical Support with relevant input.

Notes

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - PeopleSoft - Failed to parse xml file invalid document structure pos 1 col 1

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page gives solution to the below error occurring while running a PeopleSoft analysis

Failed to parse xml file: S:\Source_Code\Vanilla\PeopleSoftPackage\3\78.1233.uax (invalid document structure (pos l: 1 col: 1))

Observed in CAST AIP

Release	Yes/No
8.3.x	❌
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x (x < 3)	✅
7.2.x	✅
7.0.x	❌

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	❌
CSS3	❌
CSS2	✅
CSS1	❌

Step by Step Scenario

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - PHP or FLEX language

Mon, 01 Jan 0001 00:00:00 +0000

Panel Description

Introduction

For UA languages using a plugin such as PHP or FLEX from CoE, there is a known bug in UA that can lead to a crash in Anaman in 7.0.X (from 7.0.9 to at least 7.0.19). It occurs when the plugin computes some violations in a file which is unknown from the analyzer.

Explanation of the process

During the UA processing, once the objects have been successfully analyzed, the analyzer checks whether or not an external plugin exists for the current techno. Usually, this plugin can be found in the folder “%ALLUSERSPROFILE%\CAST\CAST\<CAST_VERSION>\configuration\Languages\<TECHNO_NAME>\plugin” where <CAST_VERSION> with the version of CAIP (i.e. “7.0”, “7.1”, “7.2”) and with the name of the techno (i.e. “PHP, “FLEX”, etc.).
If a plugin is found, it is launched with the base folder of the sources to analyze as parameter.
Then, the UA loads the xml file(s) generated by this plugin and containing the results of its computation.
All the violations extracted from the results file(s) are posted to the KB.

Description of the crash

During this process, a crash occurs if the xml results file(s) refers to sources files that does not exists in the KB (see CAST-32265).

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - Siebel - PLS 00306 - wrong argument number or types when calling SIEBEL TECHNICAL

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

The “Siebel Content Enrichment Init” job is failing with the following error :

Error SQL Error: ORA-06550: line 7, column 12
Error SQL Error: PLS-00306: wrong argument number or types when calling “SIEBEL_TECHNICAL”
Error SQL Error: ORA-06550: line 7, column 2:.
Error SQL Error: PL/SQL: Statement ignored (Severity 1, Msg No 6550).
Error Failed to launch SQL Queries

Info

This error was observed in CAST 7.0.12 with Siebel Package 4.0.5 on RDBMS Oracle 11g

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Universal Analyzer - Siebel - ProcessPropertiesImport on instance uaxFile

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Using CAST 7.0.9 version and Siebel version 4.0.2 configure a UI job for a Siebel application.
UI Analysis runs out of memory. Crashes with the following error/warning message in the log file:
Internal exception occurred during processing listener CUIDataReaderAction[UniversalActionsImpl::CUaxFileReaderAction]::ProcessPropertiesImport on instance uaxFile #59986 of path ‘S:...…uax’

The generated source code in UAX files have an instance id, a parentLink and an isInProjectLink. Hence if there are more than 1000000 instances; the total would be number of objects multiplied by 3 (number of instances * 3).