Job is in ready status in ECC

[Former Member]

HI All,

I

am using ECC 6.0 with SQL 2008 Windows NT server 2003.

We are releasing jobs from tivoli and run in SAP, Jobs are successfully released from tivoli and work process is not allocated for the job and it hungs in ready state for long time. im attaching the error log from SM21 during the which the job is in ready state.It is frequently happening and most of the critical jobs is getting stuck. kindly advice.

******************************************************************************************

*GENER Trace switched off ***

C ERROR: -1 in function StartSelect (execute) [line 10756]

C (10054) [08S01] [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host.

C

C native_db_err 10054 severity 0 errclass set to DBSL_EC_RESTART

C sl_glob.dbsl_ca.errclass set to DBSL_EC_RESTART

C ERROR: -1 in function StartSelect (execute) [line 10756]

C (10054) [08S01] [Microsoft][SQL Server Native Client 10.0]Communication link failure

B ***LOG BYM=> severe DB error 10054 ; work process in reconnect status [dbsh#3 @ 1127] [dbsh 1127 ]

B ***LOG BY4=> sql error 10054 performing SEL on table TST01 [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

B ***LOG BY0=> [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host.

[dbtrtab#7 @ 3914] [dbtrtab 3914 ]

M ***LOG GZZ=> retry creation JOBLGX [btctlgow.c 216]

C ERROR: -1 in function StartSelect (execute) [line 10756]

C (0) [08S01] [Microsoft][SQL Server Native Client 10.0]Communication link failure

C 1 times error (0,0) or (-1,0) in sequence

B ***LOG BY4=> sql error 0 performing SEL on table TST01 [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

B ***LOG BY0=> [Microsoft][SQL Server Native Client 10.0]Communication link failure [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

M ***LOG GZZ=> retry creation JOBLGX [btctlgow.c 216]

C ERROR: -1 in function StartSelect (execute) [line 10756]

C (0) [08S01] [Microsoft][SQL Server Native Client 10.0]Communication link failure

C 2 times error (0,0) or (-1,0) in sequence

B ***LOG BY4=> sql error 0 performing SEL on table TST01 [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

B ***LOG BY0=> [Microsoft][SQL Server Native Client 10.0]Communication link failure [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

M ***LOG GZZ=> retry creation JOBLGX [btctlgow.c 216]

C ERROR: -1 in function StartSelect (execute) [line 10756]

C (0) [08S01] [Microsoft][SQL Server Native Client 10.0]Communication link failure

C 3 times error (0,0) or (-1,0) in sequence

B ***LOG BY4=> sql error 0 performing SEL on table TST01 [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

B ***LOG BY0=> [Microsoft][SQL Server Native Client 10.0]Communication link failure [dbtrtab#7 @ 3914] [dbtrtab 3914 ]

L *** ERROR => BtcEnvPrep: BtcLgOw failed: jobname=SAPSD_SEV2NA-ECC-A-D-DLYCRT , jobcount=01153600, rc=4 [btcjcntl.c 1555]

M ThShortCommit: db unusable

M ThICommit3: db unusable

C

C Mon Jun 20 01:18:24 2011

C ERROR: -1 in function DoPing (SQLExecDirect failed) [line 11243]

C (10054) [08S02] [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host.

C

C native_db_err 10054 severity 0 errclass set to DBSL_EC_RESTART

C sl_glob.dbsl_ca.errclass set to DBSL_EC_RESTART

C ERROR: -1 in function DoPing (SQLExecDirect failed) [line 11243]

C (10054) [08S02] [Microsoft][SQL Server Native Client 10.0]Unable to open a logical session

B Reconnect state is entered by connection:

B 000: name = R/3, con_id = 000000000, state = ACTIVE , tx = YES, hc = NO , perm = YES,

B reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

B RECONNECT: rsdb/reco_trials: 3

B RECONNECT: rsdb/reco_sleep_time: 5

B RECONNECT: rsdb/reco_sync_all_server: OFF

B db_con_reconnect: reconnecting to connection 0:

B 000: name = R/3, con_id = 000000000, state = ACTIVE , tx = YES, hc = NO , perm = YES,

B reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

B disconnecting from connection 0 ...

B disconnected from connection 0

B opening connection 0 ...

C Thread ID:4680

C Thank You for using the SLODBC-interface

C Using dynamic link library 'E:\usr\sap\ECP\D19\exe\dbmssslib.dll'

C dbmssslib.dll patch info

C SAP patchlevel 0

C SAP patchno 289

C Last MSSQL DBSL patchlevel 0

C Last MSSQL DBSL patchno 289

C Last MSSQL DBSL patchcomment Syntax error caused by SQL hints (1555289)

C Network connection used from USLEXECP11 to ECPDSQL01 using tcp:ECPDSQL01

C Network connection used from USLEXECP11 to ECPDSQL01 using tcp:ECPDSQL01

C Driver: sqlncli10.dll Driver release: 10.00.2531

C GetDbRelease: 10.00.4000

C GetDbRelease: Got DB release numbers (10,0,4000)

B Connection 0 opened (DBSL handle 0)

B successfully reconnected to connection 0

B

B Mon Jun 20 02:02:04 2011

B dbtran INFO (init_connection '<DEFAULT>' [MSSQL:700.08]):

B max_blocking_factor = 50, max_in_blocking_factor = 255,

B min_blocking_factor = 5, min_in_blocking_factor = 10,

B prefer_union_all = 1, prefer_join = 1,

B prefer_fix_blocking = 0, prefer_in_itab_opt = 0,

B convert AVG = 1, alias table FUPD = 0,

B escape_as_literal = 0, opt GE LE to BETWEEN = 0,

B select * =0x00, character encoding = STD / []:X,

B use_hints = abap->1, dbif->0x1, upto->0, rule_in->0,

B rule_fae->0, concat_fae->0, concat_fae_or->0

M SecAudit(RsauShmInit): WP attached to existing shared memory.

M SecAudit(RsauShmInit): addr of SCSA........... = 000000000B5E0050

M SecAudit(RsauShmInit): addr of RSAUSHM........ = 000000000B5E07C0

M SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 000000000B5E0800

M SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 000000000B5E080C

S handle memory type is RSTSPROMMM

B

B Mon Jun 20 02:07:40 2011

B dbmyclu : info : my major identification is 3719880788, minor one 3219.

B dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.

B dbmyclu : info : my initial uuid is E09AE2135FE82CF19ECF005056B816B2.

B dbmyclu : info : current optimistic cluster level: 3

B dbmyclu : info : pessimistic reads set to 2.

Edited by: Rajendran Vijayashree on Jun 30, 2011 4:40 AM

Edited by: Rajendran Vijayashree on Jun 30, 2011 4:42 AM

[Former Member]

Hi,

We're facing the exactly the same issue on 2 out of 6 application servers.

We're you ever able to resolve the problem?

A restart solves the problem temporary.

Thanks in advance

Ron

[Former Member]

Hello,

As per the attached SM21 log, there is a "Communication link failure". The following error is there as well:

"sql error 0 performing SEL on table TST01"

The error is from networking failures which can be resolved by alteration of one of the networking components.

Can you please post the corresponding ST22 log as well.

[Former Member]

Hi,

We could not find any ST22 dump at the time when the job is in ready state, could you please tell me which network component needs to be changed. could you suggest few notes or any links useful for this issue

[Former Member]

Hello,

Please try and adjust the network packet size to 4096 as follows:

Inside Query Analyzer, being logged on as sa, execute the following script:

EXEC sp_configure 'show advanced options', 1

EXEC sp_configure 'allow updates', 1

GO

RECONFIGURE WITH OVERRIDE

GO

EXEC sp_configure 'set working set size', 0

EXEC sp_configure 'priority boost', 0

EXEC sp_configure 'network packet size', 4096

GO

RECONFIGURE WITH OVERRIDE

GO

EXEC sp_configure 'allow updates', 0

GO

RECONFIGURE WITH OVERRIDE

GO

EXEC sp_configure

GO

Following this, shutdown the entire R/3 system. Then stop and restart the SQL Server Service.

Adjust the profile parameter packet_size (per OSS Note 28667) and set the Application Server network packet size to 4096 for each AS connecting to SQL Server.

And finally restart the R/3 system.

Kindly inform if this helps.

[Former Member]

HI Rikidas,

Thanks for your reply.

Our Network Packet size is already set to 4096.

Is it recommended to increase the value further? ,if so what is the recommended value.

Kindly advice me.

Issue i am having with ECC server.

ECC 6.0

SQL 2008

Do you need any more details about my landscape ?

Thanks

[Former Member]

Hello,

If the issue is persisting please go through the following article:

http://wiki.sdn.sap.com/wiki/x/XwGDDg

[Former Member]

Hi,

We are facing this issue, not only in ECC production server, also in ECC quality server. We are also facing this issue in BI system ( SAP NetWeaver 7.0 with kernel 701 support pack level 136), so this issue occurs not only for ECC but also for BI system, so this might me an network issue. could you please suggest on this.