[sap-basis] Runtime Errors: RAISE_EXCEPTION
Posted by
Admin at
Share this post:
|
on 07/27/2009 02:57:00 PM
Hi group,
Every time when I check the abap runtime error using st22, there is always a
dump "runtime error: RAISE_EXCEPTION" I checked for the sap notes. But i
didnt find any result. Could you please help me out with this problem.
ECC6.0 ,win 2003 oracle10g
I have pasted the abap dump log:
Runtime Errors RAISE_EXCEPTION
Date and Time 11.07.2009 06:10:23
Short text
Exception condition "TID_NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
Error analysis
A RAISE statement in the program "/ISDFPS/SAPLSYNC_MONITORING" raised
the
exception
condition "TID_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
-
Last error logged in SAP kernel
Component............ "NI (network interface)"
Place................ "SAP-Gateway on host sapserver / sapgw01"
Version.............. 38
Error code........... "-2"
Error text........... "hostname 'XXXXXX' unknown"
Description.......... "NiHsLGetNodeAddr: hostname cached as unknown"
System call.......... " "
Module............... "nixxhsl.cpp"
Line................. 223
The error reported by the operating system is:
Error number..... " "
Error text....... " "
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
please use the following search criteria:
"/ISDFPS/SAPLSYNC_MONITORING" "RAISE_EXCEPTION"
or
"/ISDFPS/SAPLSYNC_MONITORING" "TID_NOT_FOUND"
or
"SAPMSSY8 " "TID_NOT_FOUND"
System environment
SAP-Release 700
Application server... "sapserver"
Network address...... "122.169.248.218"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPSERVER"
Database type..... "ORACLE"
Database name..... "DM0"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10103_SHARE "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE
10.2.0.*.*"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 8361792
Heap.... 0
Page.... 16384
MM Used. 4762088
MM Free. 2552400
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language key........ "E"
Transaction......... " "
Program............. "/ISDFPS/SAPLSYNC_MONITORING"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "/ISDFPS/SAPLSYNC_MONITORING" -
in
"/ISDFPS/REPORT_SYSTEM_SYNC".
The main program was "SAPMSSY8 ".
In the source code you have the termination point in line 47
of the (Include) program "/ISDFPS/LSYNC_MONITORINGU03".
The program "/ISDFPS/SAPLSYNC_MONITORING" was started as a background
job.
Job Name....... " "
Job Initiator.. " "
Job Number..... " "
Regards,
Satish __.____._
Toolbox.com
4343 N. Scottsdale Road
Suite 280
Scottsdale, AZ 85251
In the Spotlight
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion