XMA: Can't start iTP Webserver Mover - SQL Error

XMA: Can't start iTP Webserver Mover - SQL Error

Probable cause is that the iTP webserver mover is attempting to process a file type that is not yet supported.  Several file formats are not currently supported by the iTP mover:  
 
  • HTTPD log support. The format is not CLF format but a hybrid of access and error log data. Not currently supported by the iTP mover.
  • Error log support. The file is in CLF format from a column perspective but uses a non-standard date/time format for one of the columns. It's also missing the IP address at the start.  Not currently supported by the iTP mover.
  • Multiple access.log files and how to differentiate. Current implementation does not track location of the file being used and therefore the files cannot be differentiated files without running separate XMA instances.  Not currently supported by the iTP mover.
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.


    • Related Articles

    • XMA: XMA_MANAGER returns ERROR from SQL [-8025]: The SQL region was not SQL compiled

      To recompile the XMA SQL objects perform the following: TACL> VOLUME $<volume>.<XYGATEMA Installation Subvolume> TACL> RUN XMA INSTALL TACL> XMA_PWSTOP (Stop XYGATEMA Mover Processes) TACL> XMA_SQLCOMPALL (SQL Compile the Mover Objects) TACL> ...

    • XMA: The SQLXPress mover fails with error 48 (security Violation).

      Start SQLEXpress with the same user id that started XMA, or re-secure the object shown in the error message for access by the user id that started XMA. If this article did not provide a solution, please open a case with our support team by sending an ...

    • XMA: How to generate the SQL explain plan for movers.

      To produce an explain plan to show the SQL/MP cost and table usage for XMA movers. Using XMA_MANAGER stop the Mover Volume $<XUGATEMA Installation volume>.XYGATEMA RUN NEWDEFS SQLCOMP /IN <Object>/CATALOG =XMA_CAT,EXPLAIN Using XMA_MANAGER start the ...

    • XMA: Newly added EPS Mover abends and will not start

      If a newly added EPS mover is abending and will not start steps should be taken to ensure both the UALOGD and UALOGD0 can be accessed by Merged Audit. Please check both files have appropriate guardian security and that there is no safeguard ACL ...

    • XMA: Safeguard mover gets error 45 on AUDSEIND index.

      Resize AUDSEIND table using the following procedure. Shutdown XMA TACL> Volume <XMA Installation Subvolume> TACL> RUN NewDefs -- Loads defines for all the tables. TACL> info define =XMA_AUDSESSIONIND TACL> fup info =XMA_AUDSESSIONIND, DETAIL TACL> ...