cancel
Showing results for 
Search instead for 
Did you mean: 

STMS getting slow

Former Member
0 Kudos

Dear Guru,

While i am trying to move a single request to production system stms taking too much time. Please help me to sort out the problem.

Thanks,

Samrat Chakraborty

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Once you import the transport in QAS it gets added into /usr/sap/trans/buffer/PRD. Check the size of file /usr/sap/trans/buffer/PRD is continuously increasing.

Also check if background work processes are available.

Regards,

Venkata S Pagolu.

rupali_karbhari3
Active Contributor
0 Kudos

Hi Samrat,

You mean to say same transport request , takes less time while importing into Quality system but in production system all transport request imports taking time...

Check which is the transport host ? and is it located remotely to different location? if yes , might be to access respective cofiles/datafiles it is taking time to import

Best Regards,

nirmal_konchada
Active Contributor
0 Kudos

Hi,

You can use the close the import queue from STMS transaction (Import Queue--> Menu Queue --> Close) so as to close the queue for buffering. This may speed up your buffering during import.

Regards,

Nirmal.K

Former Member
0 Kudos

Hi,

Could u please tell me the system is getting slow at the time of transport's only,  how is the overall response of the system....???

Regards,

Anil

Former Member
0 Kudos

Hi,

System is getting slow at the time of transport's only

Former Member
0 Kudos

Samrat,

Try these things

1. Clear old requests from buffer queue in production system

2. Check the number of files in /usr/sap/trans/  cofiles, datafiles and log. If you have too many files, it can slowdown on read (co and data files), and write (log files)

3.Check if there is a network issue between storage system and server. For this, try to read and/or write a file from production server to /usr/sap/trans/log directory

4. Are you importing an index with a table which has large value? If yes, it may be trying to create index in the activation phase (and it takes time based on table size, index fields)

Ajith