XMA: Safeguard mover gets error 45 on AUDSEIND index.

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> edit newtbls  -- SQL commands to rebuild all tables and indexes.
*LB/CREATE UNIQUE INDEX =XMA_AUDSESSIONIND ON =XMA_AUDSESSIONTBL/
*TEdit;DI <Line Number from Above>
 
Tedit will display the following lines, the extent sizes should match your own installation, change the extent sizes to 500,500.
 
  CREATE UNIQUE INDEX =XMA_AUDSESSIONIND ON =XMA_AUDSESSIONTBL
               ( RECORDINSTALLKEY,SESSIONID )
       CATALOG =XMA_CAT
       EXTENT (500,500) format 2 MAXEXTENTS 900;
                  
Take a copy of the lines so that it can be used later.            
                   
Exit Tedit and save.
*EXIT
 
TACL> SQLCI
>DROP INDEX =XMA_AUDSESSIONIND;
Using the create index command from above, re-create the index on the session table.
>CREATE UNIQUE INDEX =XMA_AUDSESSIONIND ON =XMA_AUDSESSIONTBL
               ( RECORDINSTALLKEY,SESSIONID )
       CATALOG =XMA_CAT
       EXTENT (500,500) format 2 MAXEXTENTS 900;
>Exit;
TACL> fup info  =XMA_AUDSESSIONIND, DETAIL
 
Re-Start XMA

    • Related Articles

    • XMA: Safeguard mover is opening $ZNET.#ZSPI on remote nodes

      This is normal behavior. There is a field on some Safeguard records indicating the terminal id and some of those records do not include a TCP/IP address. In those cases, the Safeguard mover attempts to find the TCP/IP address associated with the ...

    • XMA: Measure Mover Keeps Abending

      Is XYPRO SecurityOne installed? The Measure mover is not designed to collect system performance metrics. It is designed to only capture process information for the XYGATE SecurityOne WHO Resolver. The MEASURE mover collects information regarding ...

    • XSR: Safeguard mover abends with PROCESS_CREATE_ error on XYGATESR.

      FIX: Restart the CMON process, and start the Safeguard mover. If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.

    • XMA: How to Change the Safeguard Mover's IGNORE READ RECORDS parameter

      By default the Safeguard mover ignores the extraneous secondary READ records for file access attempts. If you wish to change the setting: XMA_MANAGER / Mover Menu / Option 12 / Parameters Menu /Option 12: Show Read Details If set to TRUE, the ...

    • XMA: Saveabend files are not being created by mover abends

      1. Does the security of the XYGATEMA (XMA) installation disk volume or subvolume allow CREATE access to the XMA installation owner? Check for any Safeguard volume or subvolume ACLs or XYGATEOS rules that prevent WRITE or CREATE access for the XMA ...