Comparion Index for SPL and Partner - Message log full

[Former Member]

Hi Guys

Was recently going through the forums and found a lot on this error 'Message number 999999 reached. Log is full'

But i was not able to found one on the Comparsion terms, i am trying to create the Index for SPL and Business Partners and it stops midway because of this.

Can you advise on the below.

1) Can this number be extended?

2) Anyway to delete logs - then what is the Object and Subobject

3) How do you guys build the Comparison index, since this must be a common error

Would be very appreciative if the experts can provide an pointers on this.

Thanks

Carl

[former_member215181]

Hi Carl,

I don't know all of the answers, but you could start with Transaction SLG2 - delete logs. There aren't so many /SAPSLL/ objects, and they are described, so you could try deleting logs for some of them and see if you hit the one that's a problem. Perhaps that helps with your Q2?

The code that generates the error message has the number hard-coded at '999999'. It's not a variable that you can play with, so I don't think it's worth trying to extend any number ranges. Perhaps that answers your Q1?

Regards,

Dave

[Former Member]

Hi Dave

Thanks for coming back on this.

Not much help in SLG2, as if i selected my user name and tried to delete every log under that, it did not delete much, Plus no object corrosponds to Indexing also.

Also if i do delete the logs, eventually it will build up when i am building the index.

Hence am stuck in this.

How do you guys manage this anyway, with such a short log limit.

Any tips on this.

Cheers

Carl

[christin_angus]

Dear Carl,

There are a number of options that can solve this issue.

1.) Obsolete applogs can be deleted using TA SLG2. Please

try this possibility.

2.) Setup of control profiles

Check the definition of control profiles. In field Log Backup you

have two choices:

- Save current log and delete old log

- Save current log and retain old log

to avoid an overflow I recommend to use the or option.

Path: SAP GTS Customizing > General settings > Define control

profile for logging

3.) It is not advisable to run search term generation for a high number of

BP's at one go. Please restrict the selection further.

This is true both for search terms generation and B1,C1 scenario.

The ideal number of BP is 30-40K. Please create

multiple jobs and run these jobs serially. This will not only

prevent memory problems, but also improve overall performance.

Best regards,

Christin

[Former Member]

Thanks guys for all the answers.

Am not very much worried for the initial as during BP creation search terms are generated automatically, only thing is the restriction which is pretty limiting and cumnbersome, as there have to be multiple batch jobs going on in case of huge amount of Partners.

Cheers

Carl

[Former Member]

Hi Carl,

I dont recollect the object name handy, but you should take a look at the table NRIV and search for records wherein the number status is 99999999 ( the value you are getting in the error message).

You can then check if the object has a number range that can be further stretched or not..

Let me know if this works with you.

Regards,

Jasmit