cancel
Showing results for 
Search instead for 
Did you mean: 

Archive Delete job taking too much time - STXH Sequential Read

Former Member
0 Kudos

Hello,

We have been running Archive sessions in our production system in last couple of months. We use SARA and selecting the appropriate variants for WRITE, DELETE and STORAGE options.

Currently we use the Archive object FI_DOCUMNT and the write job is finished as per the normal time (5 hrs based on the selection criteria). After that normally the delete job is used to complete in 1hr or less than 2hrs always (in last 3 months).

But in last few days the delete job is taking too much to complete (around 8 - 10hrs) when I monitor the system found that the Sequential Read for table STXH is taking too much time to read and it seems this is the cause.

Could you please provide a solution for the same, so that the job will run faster as earlier.

Thanks for your time

Shyl

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor
0 Kudos

You can try 2 things, first you can check the read statement and create an secondary index to minimize the sequential reads on STXH, also make sure that you stats are updated.

Regards

Juan

Former Member
0 Kudos

Hi Juan,

After the statistics run the performance is quite good. Now the job getting finished as expected.

Thanks. Problem solved

Shyl

Answers (1)

Answers (1)

Former Member
0 Kudos

Check the statistics for the table and update if neccessary.

Regards,

Srinivas Chapa.