Skip to Content

Critical scheduled job disapears abnormally

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"

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Posted on Sep 29, 2009 at 10:31 AM

    Check the SQL Server event log on your database server.

    Markus

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 30, 2009 at 08:53 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 05, 2009 at 01:18 AM

    note 1159521

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.