SQL error 1-: Function sequence error

[Former Member]

Hi Team,

Database : MSSQL 2008R2

We have successfully done the SAP patching. We are getting below error in SM21

Database error -1 at FET

> Function sequence error

Database error -1

JOB : SAP_COLLECTOR_FOR_PERFMONITOR is failing with error

Job started

Step 001 started (program RSCOLL00, variant , user ID DDIC)

Clean_Plan:Cleanup of DB13 Plannings

Clean_Plan:started by RSDBPREV                       on server XXXXXXXXXXX

Clean_Plan:Cleaning up jobs of system PRD

Clean_Plan:finished

SQL error 1-:  Function sequence error

Job cancelled after system exception ERROR_MESSAGE

IN ST04 we are getting the error SQL error 1-: Function sequence error in the below status.

Kindly help us to resolve the issue

Regards

Raghu

[Former Member · Accepted solution]

Hi,

Have you check the below note.

1880067 - ST04 screen is missing some data

Thanks

Rishi Abrol

[Former Member · Accepted solution]

Hi Rishi,

The NOTE looks like the perfect solution. But before going into it, we need to clarify few things.

We have done SAP Patching and Kernel upgrade in DEV & TST too. But we didn't face this error.

We are having the issue only in PRD. This looks mystery. Could you know why this error will occur ?

Regards

Raghu

[Former Member · Accepted solution]

Hi,

The only reason that i think can be the cause of it is the user load and the value of the below parameters that sap talks about in the note .

There has been an overflow of SQL Server variables @@CPU_BUSY, @@IO_BUSY or @@IDLE.

Selecting the value of one of these variables results in an arithmetic overflow message, but the processing continues.

It might be that these parameters might have not overflow in Dev and Qua and that is the reason you would have not seen this error.

In the note it also says that the restart can also fix the issue. And usually dev and Qua go down more offen than production.

That i can think off if you say all things are same and no patch difference.

Thanks

Rishi abrol

[Former Member · Accepted solution]

Issue resolved.

We have upgraded the patch level to 519. Restarted the application & Database.

Thanks a lot

Regards

Raghu