HotNews correction for Y2010 spool request error available

[Former Member]

Dear gurus,

I became aware of [SAP Note 1422843|https://service.sap.com/sap/support/notes/1422843] which has affected all my systems's spool request reorg jobs.

It is currently release and patch level independent, so you will all be affected by it as well.

You can verify this via entries in table SP01 field RQDELTIME = 2099*

As a kernel patch might take a while (also to download, install, test, etc...) there is a workaround attached to the note until you get there.

Cheers and best wishes for the new years until 2099..

Julius

[Former Member · Accepted solution]

Hello,

We're having this problem in some systems and the variant provided in this note 1422843 doesn't clean at all....

Does anyone have the same problem?

best regards,

Filipe Vasconcelos

[Former Member · Accepted solution]

There have been updates to the note and an additional related note of symptoms added.

Our kernel releases are available and the patches worked, also for the additional symptoms which we reported.

Which release are you on?

Please also see the related [SAP Note 48284|https://service.sap.com/sap/support/notes/48284] for the limitations. You might have reached a spool overflow already...!

Cheers,

Julius

[Former Member · Accepted solution]

> ...and the variant provided in this note 1422843 doesn't clean at all....

Yes, it does not "clean" the spool requests out of the system - it corrects the deletion date symptom so that your reorg job will pick them up again. Dependent on your config, this might take a few days to become "cleaned", as they were before as well.

Another option is to reorg the spool requests based on the creation date alone. This works fine for "smaller" systems and will protect the spool overflow and number range problem. It will however not correct the other less critical symptoms, so applying the kernel patch at some stage soon is recommended anyway.

Cheers,

Julius

[Former Member · Accepted solution]

The above kernel patches now have subsequent patch levels which solve side-affects.

Rather go straight to the newest kernel, before your spool range runs out.

If you reorg based on creation date then this is less of an issue for you initially.

Cheers,

Julius

[Former Member]

What is the Kernel Patch Level that solve this problem if you not implement as per note: 1422843?

Currently I'm at kernel release 640, patch level 274