Critical scheduled job disapears abnormally

[former_member211576]

Hi experts,

one critical scheduled job disapeared. Please

check SM21 for TemSe->XRTAB(0)->1 and ST22 for DBIF_RSQL_SQL_ERROR. I

have found 2 notes 43369, 48400, and run SP12 consistency check online.

Is this a right solution? Is there a permanent solution, ex: scheduled

job of housekeeping? (PS: I have scheduled RSPO1043 on a daily basis.

Should I schedule RSTS0020 as a daily basis, but as per note 48400 it

does not remove inconsistent automatically)

--

Database error: TemSe->XRTAB(0)->1 for table TST01 key DBIF_RSQL_SQL_ERROR

> retry creation JOBLGX btctlgow216#

---

Runtime Errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Date and Time 2009/09/27 12:10:26

Short text

SQL error in the database when accessing a table.

How to correct the error

Database error text........: "[Microsoft][SQL Server Native Client 10.0]TCP

Provider: An existing connection was forcibly closed by the remote host.##"

Internal call code.........: "[RSQL/RDUP/VBHDR ]"

Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

"RSM13000" or "RSM13000"

"VB_V1_NORMAL"

[former_member211576]

note 1159521

[former_member211576]

Hi Markus,

I really appriciate for you support. I have created a customer message: https://service.sap.com/sap/support/message/1/002007974700009159692009, FYI. I have also open service connnection if you need.

--

And here is last reply from SAP support:

Dear skip,

Right, 27.9. Yes, the only affected job. So it is just an unknown

accidence created by MSSQL and I supposed it would NEVER happen again?

28.09.2009 - 11:49:26 CET - by SAP

DEar Mr. Lee,

it seems that this happened on 27.9. not 28.9., correct?

The syslog entreis have nothing to do with that:

they are from server 14 but job was executed on server 12.

There is no errormessage in syslog or tracefile or joblog.

So it will be difficult to tell why the job was not scheduled.

Is it the only affected job?

Yours sincerely,

skip

SAP Active Global Support - Netweaver Web Application Server

[markus_doehr2]

Hi Dennis,

I'm not working @ SAP so I can't see your call.

I'm sure the support will find the cause for this.

Markus

[markus_doehr2]

Check the SQL Server event log on your database server.

Markus

[former_member211576]

Hi Markus,

I did, but there is no error in errorlog.

[markus_doehr2]

Well - this would be then a case for the support. I'd open an OSS call (BC-DB-MSS) and let the support have a look on the system.

Markus