XMA Critical TMF message #222 from SLSENDER - TMF AutoAbort timeout duration error messages remedy

XMA Critical TMF message #222 from SLSENDER - TMF AutoAbort timeout duration error messages remedy

We have two potential solutions:
  1. Upgrade to XMA 2.60 where the SYSLOGQ index has been updated. This is the preferred 
  2. Implement the procedure below to update the current XMA SYSLOGI index in any XMA implementation prior to 2.60.
SYSLOGQI index update procedure:
  1. Start by navigating to the XYGATEMA subvolume and attaching the XMA segment.
  2. Shutdown XMA pathway from XMA manager. (1. Pathway > 3. Stop) then exiting the MANAGER.
  3.  Run the command: NEWDEFS to load the XMA defines
    1. then enter the command XMA_DBVOLUME. This will volume you to the XMA database subvolume.
  4. Enter the command:  SQLCI; drop index =XMA_SYSLOGQIND;
  5. Create the index:
(copy and paste the entire command at once. The numbers highlighted are suggestions, the numbers represent the primary and secondary extents of the file, these need to be the same size as the existing SYSLOGQ file)

CREATE INDEX =XMA_SYSLOGQIND ON =XMA_SYSLOGQ
(
ACTION ASC, ALERTEDGMT ASC, ACTIONGMT ASC, PART ASC
)
CATALOG =XMA_CAT
EXTENT (12000, 12000)
MAXEXTENTS 500
;

         6. enter the command: XMA_SQLCOMPALL
         7. Restart Pathway from XMA_Manager (1. Pathway > 1. Cold Start)

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: SLSENDER Error unable to send messages to host.

      The SYSLOGQ database table in the XMADAT subvolume has 2 columns that can be used to determine if messages are being sent to the SIEM. ENTRYGMT is the timestamp when the message was inserted into the queue by a mover. ALERTEDGMT is the timestamp when ...

    • XMA: Critical Msg:Syslog Sender SLSENDER Unable to send messages to host

      Wait for the HKEEPER to delete the records based on the maximum age of not sent messages to be retained or use the following SQL queries to identify and delete or change the relevant records. Show ?stuck? records and allow them to be deleted or ...

    • XMA: How to uninstall SLSENDER.

      As the SLSENDER is configured and added to the XMA pathway when the customer follows the installation process in the XMA manual. The following procedure can be used to manually stop the SLSENDER , remove any records that have been generated, and stop ...

    • SLSENDER getting error 1120. CPU spikes are also noticed

      A couple of things may help this issue: 1. Update statistics a. Logon as the XMA owner b. Attach to the XMA segment file RUN $<vol>.XYGATEMA.XMA INSTALL (where $<vol> is the disk where XMA is installed) d. XMA_MANAGER d. Option 3, Database e. Option ...

    • XMA: TMF is keeping active transactions open for SLSENDER after SLSENDER and XMA Pathway are stopped

      The reason for this behavior because is the XMA TACL routines are shutting down the pathway with the Pathmon command ?SHUTDOWN2, MODE IM, UNTIL DONE?. The ?MODE IM? means that it stops the servers immediately but does not close them. This allows them ...