This page handle the following fatal error:

Error during set generation on local site

The model contains the following errors cannot generate set

DataSet 'Custom End Point Support' references DataSet 'Custom End Point Support'(GS)which do not exist



Release
Yes/No
8.3.x(tick)
8.2.x(tick)
8.1.x(tick)
8.0.x(tick)




RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS2(tick)



Step by Step scenario

  1. Generate Set


Perform the below actions

  1. From the left hand of TCC GUI, check if there are nodes highligted with red color, as shown below:


    In our example we can see that the Free definition node and the End point node are highligted with the red color
    1. If there are nodes highligted with red color:
      1. Go to the node that present this behavior, and check if there is an element from the DataSet of the node that reference a non existing Generic Set:


        In our example the DataSet of the node is the End points Set, we can see that the end point "Custom End Point Support" reference the generic Set "Custom End Point Support", but we can see also that the the generic Set "Custom End Point Support" does not exist in the Generic Sets definition.

        If there is no element from the DataSet of the node that reference an unexisting Generic Set, then it is expected to get the Fatal Error, you need to manage your configuration in order to overide the fatal Error.
        In our example and in order to overide the Fatal error, you need to either remove the End point Set "Custom End Point Support" from the End points Sets definition or to add the Generic Set "Custom End Point Support" to the Generic Sets definition.
    2. If there are no nodes highlithed with red color:
      1. Get the name of the DataSet of reference raised by the error, example:

      2. Search for the DataSet in all DataSet definitions: End point Entry point Data Function, Excluded Items(from more information refer to TCC - Data Entities, End points, Entry Points, Excluded Items nodes - Right hand panel)

      3. If you are not able to find the DataSet of reference, then check from the management schema if it is part of the list of rules used to select the DataSets for that refer to SQL Queries - CAST Management Base - Queries on Generic set - How to check if a referenced generic set does not exists

        1. If the query returns "f" then the DataSet of Reference is not a ghost DataSet, contact  CAST Technical Support. with the following  Relevant input

        2. Else If the query returns "t" then the DataSet of Reference is a ghost DataSet. In order to fix this perform the following:

          1. Export TCC configuration by following the page TCC - Import configuration / Export configuration

          2. Clean the configuration table cal_objsetdef located on the management schema as follows: 

            DELETE FROM cal_objsetdef 


          3. Import TCC configuration by following the page TCC - Import configuration / Export configuration 

          4. Generate the Set

  2. If the above steps do not solve your issue contact CAST Technical Support. with the following  Relevant input


Ticket # 11232


Transaction Configuration Center - AFP Calibration - Compute Application function points - Fatal Error - DataSet XXX references DataSet XXX which does not exist