cancel
Showing results for 
Search instead for 
Did you mean: 

Log file is growing too big and too quick on ECC6 EHP4 system

Former Member
0 Kudos

Hello there,

i have ECC6EHP6 system based on NW 7.01 and MSSQL as back-end.

My log file is growing very fast. i seen a number of threads but does not got some perfect idea what to do. Please see DEV_RFC0 and DEV_W0 log file excerpt below. Please help

DEV_RFC0

        • Trace file opened at 20100618 065308 Eastern Daylight Time, SAP-REL 701,0,14 RFC-VER U 3 1016574 MT-SL

======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

ABAP Programm: SAPLSADC (Transaction: )

User: DDIC (Client: 000)

Destination: SAPDB_DBM_DAEMON (handle: 2, , )

SERVER> RFC Server Session (handle: 1, 59356166, {ADC77ADF-C575-F1CC-B797-0019B9E204CC})

SERVER> Caller host:

SERVER> Caller transaction code: (Caller Program: SAPLSADC)

SERVER> Called function module: DBM_CONNECT_PUR

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501

CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

DEST =SAPDB_DBM_DAEMON

HOST =%%RFCSERVER%%

PROG =dbmrfc@sapdb

        • Trace file opened at 20100618 065634 Eastern Daylight Time, SAP-REL 701,0,14 RFC-VER U 3 1016574 MT-SL

======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

ABAP Programm: SAPLSADC (Transaction: )

User: DDIC (Client: 000)

Destination: SAPDB_DBM_DAEMON (handle: 2, , )

SERVER> RFC Server Session (handle: 1, 59587535, {28C87ADF-4577-F16D-B797-0019B9E204CC})

SERVER> Caller host:

SERVER> Caller transaction code: (Caller Program: SAPLSADC)

SERVER> Called function module: DBM_CONNECT_PUR

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501

CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Transaction program not registered

DEST =SAPDB_DBM_DAEMON

HOST =%%RFCSERVER%%

PROG =dbmrfc@sapdb

DEV_W0

X

X Fri Jun 18 18:05:15 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

N

N Fri Jun 18 18:05:25 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

X

X Fri Jun 18 18:05:39 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X

X Fri Jun 18 18:05:46 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X

X Fri Jun 18 18:05:52 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X

N Sun Jun 20 10:55:32 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

X

X Sun Jun 20 11:00:02 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

N

N Sun Jun 20 11:00:32 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

C

C Sun Jun 20 11:03:34 2010

C Thread ID:1956

C dbmssslib.dll patch info

C patchlevel 0

C patchno 13

C patchcomment Errors when running with par_stmt_prepare set to zero (1253696)

C Local connection used on SAPFIVE to named instance: np:SAPFIVE\ECT

C

C Sun Jun 20 11:03:49 2010

C OpenOledbConnection: line 23839. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C

C Sun Jun 20 11:04:04 2010

C OpenOledbConnection: line 23839. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C

C Sun Jun 20 11:04:19 2010

C OpenOledbConnection: line 23839. hr: 0x8000ffff Login timeout expired

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Login timeout expired

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err -1, sev 0), SQL Network Interfaces: Server doesn't support requested protocol [xFFFFFFFF].

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23839]: Error/Message: (err 0, sev 0), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C failed to establish conn to np:SAPFIVE\ECT.

C Retrying without protocol specifier: SAPFIVE\ECT

C Connected to db server : [SAPFIVE\ECT] server_used : [SAPFIVE\ECT], dbname: ECT, dbuser: ect

C pn_id:SAPFIVE_ECT_ECTECT_ECT

B Connection 4 opened (DBSL handle 2)

B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE YES YES NO 000 255 255 20100618 061458 SAPFIVE\ECT

B 000 001 +DBO+0050 000002156 INACTIVE NO NO NO 004 255 255 20100618 101017 SAPFIVE\ECT

B 000 002 +DBO+0050 000001981 DISCONNECTED NO NO NO 000 255 255 20100620 070023 SAPFIVE\ECT

B 000 003 +DBO+0050 000001982 DISCONNECTED NO NO NO 000 255 255 20100620 070023 SAPFIVE\ECT

B 000 004 R/3*INACT_PACK 000002157 ACTIVE NO NO NO 004 255 255 20100620 110334 SAPFIVE\ECT

...

N Sun Jun 20 17:35:35 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

M

M Sun Jun 20 17:47:29 2010

M ThAlarmHandler (1)

M ThAlarmHandler (1)

M ThAlarmHandler: set CONTROL_TIMEOUT/DP_CONTROL_JAVA_EXIT and break sql

C

C Sun Jun 20 17:47:33 2010

C SQLBREAK: DBSL_CMD_SQLBREAK: CbOnCancel was not set. rc: 15

M program canceled

M reason = max run time exceeded

M user = SAPSYS

M client = 000

M terminal =

M report = SAPMSSY2

M ThAlarmHandler: return from signal handler

A

A Sun Jun 20 17:48:33 2010

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK completed.

A ** RABAX: level LEV_RX_DB_ALIVE entered.

A ** RABAX: level LEV_RX_DB_ALIVE completed.

A ** RABAX: level LEV_RX_HOOKS entered.

A ** RABAX: level LEV_RX_HOOKS completed.

A ** RABAX: level LEV_RX_STANDARD entered.

A ** RABAX: level LEV_RX_STANDARD completed.

A ** RABAX: level LEV_RX_STOR_VALUES entered.

A ** RABAX: level LEV_RX_STOR_VALUES completed.

A ** RABAX: level LEV_RX_C_STACK entered.

A

A Sun Jun 20 17:48:42 2010

A ** RABAX: level LEV_RX_C_STACK completed.

A ** RABAX: level LEV_RX_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A ** RABAX: level LEV_RX_INTERFACES entered.

A ** RABAX: level LEV_RX_INTERFACES completed.

A ** RABAX: level LEV_RX_GET_MESS entered.

A ** RABAX: level LEV_RX_GET_MESS completed.

A ** RABAX: level LEV_RX_INIT_SNAP entered.

A ** RABAX: level LEV_RX_INIT_SNAP completed.

A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A ** RABAX: level LEV_RX_WRITE_SNAP entered.

A

A Sun Jun 20 17:48:48 2010

A ** RABAX: level LEV_SN_END completed.

A ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A ** RABAX: level LEV_RX_SET_ALERT entered.

A ** RABAX: level LEV_RX_SET_ALERT completed.

A ** RABAX: level LEV_RX_COMMIT entered.

A ** RABAX: level LEV_RX_COMMIT completed.

A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A ** RABAX: level LEV_RX_RESET_PROGS entered.

A ** RABAX: level LEV_RX_RESET_PROGS completed.

A ** RABAX: level LEV_RX_STDERR entered.

A Sun Jun 20 17:48:48 2010

A

A ABAP Program SAPMSSY2 .

A Source RSBTCTRC Line 131.

A Error Code TIME_OUT.

A Module $Id: //bas/701_REL/src/krn/runt/abinit.c#1 $ SAP.

A Function ab_chstat Line 1941.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end no http/smtp

A ** RABAX: end RX_BTCHLOG|RX_VBLOG

A Time limit exceeded..

A

X

X Sun Jun 20 17:49:03 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

...

...

...

N Sun Jun 20 18:35:40 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

N

N Sun Jun 20 18:50:35 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

N

N Sun Jun 20 18:55:31 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

N

N Sun Jun 20 19:00:31 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

X

X Sun Jun 20 19:01:59 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

X

X Sun Jun 20 19:02:05 2010

X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]

M

M Sun Jun 20 19:04:02 2010

M ***LOG R49=> ThReceive, CPIC-Error (020223) [thxxhead.c 7488]

M ***LOG R5A=> ThReceive, CPIC-Error (76495728) [thxxhead.c 7493]

M ***LOG R64=> ThReceive, CPIC-Error ( CMSEND(SAP)) [thxxhead.c 7498]

N

N Sun Jun 20 19:05:31 2010

N RSEC: The entry with identifier /RFC/DIICLNT800

N was encrypted by a system

N with different SID and cannot be decrypted here.

N RSEC: The entry with identifier /RFC/T90CLNT090

N was encrypted by a system

N with different SID and cannot be decrypted here.

Thanks

Mani

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

See if you have any background job running which might be the reason for increase in log file. Check system log and dumps for additional information if any

Regards,

Anand

Former Member
0 Kudos

i have few BG jobs running at backend, but i dont think that could be a problem. I have these jobs running

ESH_IX_PROCESS_CP_20100621051308

EU_PUT

EU_REORG

RPTMC_CREATE_CHANGEPOINT_AUTH

i cancelled the last one and first job is for trex indexing for changed object i SAP hR master data. middle two i dont know the purpose.

do you think these could be problem?

Mani

Former Member
0 Kudos

Can you provide more information from your post i'm really can't understand what log file growing to big , only one log file or not ? The file name ? Post last 50 lines from this log, are you see any messages in sm21 about it or dumps in st22 ?

Regards.

Former Member
0 Kudos

Hello,

Stop the currently active job to ensure that they dont have any effect on the log file growth. Any information on system log SM21 or Dumps ST22? Check that as well

Check the database logs also to find any errors(didnt remember the exact path)

Regards,

Anand