USMM - System measurement

[Former Member]

Hi,

I´m trying to run the system measurement in tcode USMM on SAP ECC 6.0 \ SQL \ WIN x64.

When i start the measurement i receive the error "56 measurement job(s) is/are not yet started or still running".

I already check the "RSUV*" jobs and they´re with status "releasead".

Does anyone knows how to solve this error?

Thanks,

Hugo

[mamartins · Accepted solution]

Hi,

I do the system measurement for more than 5 years on about 10 systems and never saw something like that.

Do you have enough background jobs dispatchers (BTC) on that system? Provably they are all occupied and "RSUV*" jobs have low priority.

Regards,

MM

[Former Member · Accepted solution]

Hi Manuel,

Yes i have background jobs.

Thanks,

Hugo

[former_member182657]

Hi Hugo,

Could you share system logs from SM21 & share the job log for RSUV * ? With this please confirm for any dumps under ST22,if yes you could share these too for analysis.

If possible try to patch the System components with the latest available,as this could be resolved only by patching the latest components(e.g SAP_BASIS,SAP_ABA) .

Addition to it suggest you to raise SAP Support ticket in parallel with thread.

Hope this will help you.

Good luck !!

[Former Member]

Hi Gaurav,

There´s no registed dumps in ST22, the "RSUV*" jobs are with released status but they don´t get active when i start the measure.

Thanks,

Hugo

[Former Member]

Hello,

The issue was resolved.

Like you said Manuel Martins there wasn´t enough BTC processes.

Initialy, when i ran the measurement i still had 1 BTC process free. Today i checked tried again the measurement and the 4 BTC processes were busy with another process.

When they were free i ran the measurments without problems and get the report.

Thanks very much for all your support!

Regards

Hugo

[mamartins]

Hi,

Glad that I helped.

Please mark the question as solved.

Regards,

MM

[Former Member]

Hi Hugo..Check this note...

1901069 - System measurement: User measurement extremely long runtime

regards,

Syed

[former_member225699]

HI ,

Please

a)goto transaction se16

b) open table TUJOB

c)delete all entries related to failed jobs in SM37 for USMM

d)re-run meaurement.

if this does not work:

then change job status to A

kindly, let me know if this resolves your issue.

Thanks,

Avadhesh

[former_member225699]

Correction not to A but to P

[Former Member]

Hi Basis,

I checked the TUJOB table and didn´t see any failed jobs.

Thanks,

Hugo

[Former Member]

Hello Syed,

I checked too this note, it cannot be implemented. The system has SAP_BASIS 740 (level 5).

Thanks again for your reply.

Regards,

Hugo

[Former Member]

Hi... pls refer this thread..Hope it helps...

Thanks,

Raz

[Former Member]

Hi Syed,

I´ve already read and tried the mencioned notes (1150840 | 1150840), i tried too the "%UNLOCK" command in tcode field but didn´t worked.

I´m still searching for notes.

Thanks very much.

Regards,

Hugo

[Former Member]

You just need to wait. They will finish eventually. Mine can sometimes take 10 or 15 minutes, depending on the other load on the system. On a busy production system I've had to wait over an hour once or twice.

Leave it alone and come back to check later.

Steve.

[Former Member]

Hello Steve,

I waited more than 3 days and nothing.

Thanks for your replay.

Hugo

[Former Member]

Yes, three days is probably too long a wait! I've never had to wait more than a few hours. I'd probably search OSS at this point, to see if it is a know problem, and if you don't find anything create an OSS incident for it.

Steve.

[Former Member]

Yes it is.

I´m still searching for oss notes to solve this problem.

Thanks,

Hugo