CMS Application - Universal Importer - Fatal Error

 This page will help you to troubleshoot the problems you may face while running the Universal Importer tool.

Refer to Official documentation :

• CAST AIP 8.3.x Documentation : Universal Importer - Advanced configuration

CAST MS help Online : CAST Management Studio - Help > Infrastructure > Editors > Application Editor> Content Enrichment tab

1. Check if the error is due to a custom procedure that has been added to the CAST databases.

   1. Do this by checking if the function or stored procedure which is resulting in the error exists in a standard CAST database.
      For example, if the following is the error seen in the CAST-MS log

      ERR: 2016-10-31 18:14:52: Error while executing Batch: select UI_FILL_TABLES_PROC();                             
       
      Query failed because: 
                                  
      ERROR: null value in column "instance_id" violates not-null constraint
      Detail: Failing row contains (CLASS2BOT_LINKS, null, inheritImplementLink).
      Where: SQL statement "insert into UAX_IMPORT_INSTANCES values
      (c_groupname, v_instance_id, 'inheritImplementLink')"                             
      PL/pgSQL function ui_fill_tables_proc() line 37 at SQL statement                             
       
      com.castsoftware.java.InternalException:Error while executing Batch: select UI_FILL_TABLES_PROC(); 
       
      Query failed because: 
       
      ERROR: null value in column "instance_id" violates not-null constraint   
      Detail: Failing row contains (CLASS2BOT_LINKS, null, inheritImplementLink).   
      Where: SQL statement "insert into UAX_IMPORT_INSTANCES values       
      (c_groupname, v_instance_id, 'inheritImplementLink')" 
      PL/pgSQL function ui_fill_tables_proc() line 37 at SQL statement

      The failing function - UI__FILL_TABLES_PROC() - is not found in a standard CAST knowledge base, so the error is due to a custom stored procedure.

      Custom code added to the CAST databases is outside the scope of support and should be handled by the people who have created the custom stored procedures, which is usually CAST consulting or the local CAST Administrator.

2. If the issue is not because of the above check the following sections to see if any of the below are applicable to your issue
   
3. If the problem you are facing does not match any case listed in this page, contact CAST Technical Support with below relevant input.

Relevant input

1. Sherlock (CAST Support Tool (CST) - alias Sherlock) : This will provide us the logs and the bases to understand the environment and the information about the problem. 
2. Source Code : Required to reproduce the problem on our side to investigate further.
3. Explanation about the problem and supporting screenshots