XMA: Error 73

XMA: Error 73

This is a known issue that has been addressed in our current XMA Version 2.65. We therefore recommend upgrading to XMA 2.65 in order to address this error.

Softdoc entry for this issue:

* XMA-1329 Addresses a latency issue when retrieving messages 
  over 1k characters. The SYSLOGQ table index is 
  restructured, and the program is modified to always use the 
  index for a more efficient access path to decrease the 
  message retrieval time. 
  SOLN: 10-221102-6436, 10-221122-6501 



If you have additional questions or if you need installation assistance please Click Here to open a case from our Customer Care Portal.


    • Related Articles

    • XMA: XMA_MANAGER macro fails with [Check_SQLCompileNeeded] error

      The XMA SQL database needs to be recompiled for this error to be resolved. 1) stop XMA XMA_PWSTOP 2) Update the database statistics and re SQLCOMPILE all the XMA programs XMA_SQLCOMPALL 3) Start XMA XMA_PWCOOL If you are unable to locate the solution ...

    • XMA: Error compiling CNVRTIP when upgrading to XMA 2.41

      Purging CNVRTIP from the XYGATEMA subvol and running XMA_MANAGER again will allow the upgrade to proceed as expected. TACL> VOLUME <XMA INSTALLATION VOLUME/SUBVOLUME> TACL> XMA INSTALL TACL> XMA_VOLUME TACL> FUP PURGE CNVRTIP TACL> XMA_MANAGER Note: ...

    • 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:Update all statistics abends with error 1120

      Use the =_SQL_CAT_HEAP_LIMIT, FILE M<nnnn> define to enlarge the default amount of memory (16 MB) that SQLCAT reserves for these kinds of structures. For example, the following DEFINE allows the heap to grow to 128MB: TACL> ADD DEFINE ...

    • 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 ...