CMS Application - Universal Importer - Performance Issue

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

For more information, refer to:

• Official documentation: Universal Importer - Advanced configuration

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

1. If you are using the Universal Importer with the option Import from set to Database:
   Figure 1
   
   1. Check if the performance issue is linked with the queries that have been implemented to populate the tables UAX_IMPORT_INSTANCES and UAX_IMPORT_PROPERTIES.
   2. Execute these queries in your SGBD tools (PGADMIN for CSS / Postgresql, Toad-Aquastudio for Oracle, SQL Server Studio for SQL Server).
   3. If there is performance issues during the SQL Execution, you must improve these queries.
      
      
2. If the above steps do not explain the performance issue, then it could be due to SQL statement that are run during the Universal Importer Process.
   1. Stop the Run Universal Importer.
   2. Activate SQL traces at Database Server level :
      1. For CSS, see the page:  RDBMS Information - PostgreSQL - How to log Postgres SQL queries
   3. Run the Universal Importer.
   4. After a long time (1 hour or more), send the Universal Importer log file that is Universal Importer log along with the CAST Storage Service log file that is in Getting the CSS Log File to CAST Technical Support to identify the longest querie
   5. If you cannot add SQL Traces on your Database Server (because you cannot stop the Cast Storage Service), you can add the SQL traces on the Universal Importer log file :
      1. Open the CAST-MS log file that is in CAST Management Studio (CMS) log file
      2. Search the statement Starting Task Run Universal Importer in the CAST MS log file.
      3. Just above the starting statement, there is the command line to run the Universal Importer tool :
         

      4. Copy this command line, and add the statement -SHOW(SQL) just after anarun.exe. The command you will have will look to :

         C:\Program Files\CAST\8.0/ anarun.exe -SHOW(SQL) -CONNECT_PROFILE('<SERVER>:2280 on CastStorageService.prod800_local') -RUN_AU(301,110551,'C:\Users\JMC~1.CAS\AppData\Local\Temp\CAST\CAST\8.0\LISA\bd1c4a0b868f4e9cabae9c7378ab898f\Scr14050\JobSettings.xml') -MANAGED(301) -SESSION_ID(110551) -LOG('C:\Users\JMC~1.CAS\AppData\Local\Temp\CAST\CAST\8.0\bd1c4a0b868f4e9cabae9c7378ab898f\My Universal Importer-20160824163958.castlog',TRUNCATE) -LARGESTORAGE('C:\Users\JMC~1.CAS\AppData\Local\Temp\CAST\CAST\8.0','C:\Users\JMC~1.CAS\AppData\Local\Temp\CAST\CAST\8.0','bd1c4a0b868f4e9cabae9c7378ab898f/Scr14050') -LOGIN(,CASTCORP\JMC,) -APP(-NOGUI) -FINAL_UPDATE -NOPROGRESS -EXIT

      5. Execute this command line in a command prompt.

      6. After a long time (1 hour or more), retrieve the log file that is defined in the command line with the option -LOG(<PATH>\My Universal Importer-[date].castlog', TRUNCATE)
      7. Send this log to CAST Technical Support to Identify the longest query.
         
         
3. If the problem you are facing does not match any case listed in this page, contact CAST Technical Support with the below relevant input in order to reproduce the issue.

Relevant input 

1. Sherlock (CAST Support Tool (CST) - alias Sherlock). Option to select : Export CAST Database, Export Logs, Export Configuration Files.
   
2. Source Code : Required to reproduce the problem IF the universal importer is run with option Import from set to Files.
3. Explanation about the problem and supporting screenshots