on 09-29-2009 7:26 PM
Hi All...
===================================================================================================
SAP Early Watch Alert Report fail to generate suddenly. There was no changes made to the system.
It was generating periodically without any issues earlier. Suddenly got broke-down. The managed system is EP-Production Portal(WPP).
===================================================================================================
I happen to check SM:EXEC SERVICES - Job failed.
===================================================================================================
Here is the Job Log details:
===================================================================================================
Job started
Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant &0000000000744, user ID SMADMIN
RDSMOPBACK_AUTOSESSIONS : MemSize Begin = 1369184
Solution WCMC SAP Solutions is being edited (Operations)
Trying to perform session 1000000001457
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
===================================================================================================
In ST22 - Dump shows:
===================================================================================================
What happened?:
The current application program detected a situation which really should not occur. Therefore, a termination with a short dump was triggered on purpose by the key word MESSAGE (type X).
===================================================================================================
Error analysis :
Short text of error message:
A type conflict occurred when saving to check table (value= , type=G)
===================================================================================================
Long text of error message:
Diagnosis
You tried to save a value in the check table that could not be converted to the data type defined for that table column.
System Response
The transaction will be terminated.
Procedure
This was caused by an error in the check's programming. Look for an appropriate R/3 Note in SAPNet, or open a problem message. Procedure for System Administration
===================================================================================================
Technical information about the message:
Message class....... "DSVAS"
Number.............. 107
Variable 1.......... " "
Variable 2.......... "G"
Variable 3.......... " "
Variable 4.......... " "
===================================================================================================
How to correct the error:
Probably the only way to eliminate the error is to correct the program.
-
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:
"MESSAGE_TYPE_X" " "
"SAPLDSVAS_PROC" or "LDSVAS_PROCTAI"
"UNPACKED_SET"
===================================================================================================
System environment
SAP-Release 700
Operating system..... "Linux"
Release.............. "2.6.5-7.287.3-smp"
Hardware type........ "x86_64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database type..... "ORACLE"
Database name..... "WMP"
Database user ID.. "SAPDAT"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Feb 3 2008 20:24:53"
create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Linux 2.6"
===================================================================================================
Memory consumption
Roll.... 16192
EM...... 168125600
Heap.... 0
Page.... 163840
MM Used. 162885432
MM Free. 1030888
===================================================================================================
===================================================================================================
Source Code Extract:
2018 pf_type = <lfs_col>-col_typ
2019 pf_sign = abap_true " <lfs_col>-type_sign
2020 * IMPORTING
2021 * PF_DATA_INTERNAL = ls_column-field
2022 EXCEPTIONS
2023 DATA_TYPE_INVALID = 1
2024 DATA_INVALID = 2
2025 OTHERS = 3.
2026 if sy-subrc <> 0 and pf_force_dump = abap_true.
>>>> MESSAGE x107 WITH lf_field <lfs_col>-col_typ.
2028 endif.
2029 ENDIF.
2030 * Spalten
2031 INSERT ls_column INTO TABLE ls_row-columns.
2032 ENDIF.
2033 ENDDO.
===================================================================================================
===================================================================================================
System Status:
===================================================================================================
SAP_BASIS 700 0015 SAPKB70015 SAP Basis Component
-
SAP_ABA 700 0015 SAPKA70015 Cross-Application Component
-
PI_BASIS 2006_1_700 0005 SAPKIPYM05 Basis Plug-In (PI_BASIS) 2006_1_700
-
ST-PI 2005_1_700 0006 SAPKITLQI6 SAP Solution Tools Plug-In
-
SAP_BW 700 0017 SAPKW70017 SAP NetWeaver BI 7.0
-
SAP_AP 700 0011 SAPKNA7011 SAP Application Platform
-
BBPCRM 500 0011 SAPKU50011 BBPCRM
-
CPRXRPM 400 0011 SAPK-40011INCPRXRPM SAP xRPM/cProjects/cFolders 4.00
-
BI_CONT 703 0008 SAPKIBIIP8 Business Intelligence Content
-
ST 400 0016 SAPKITL426 SAP Solution Manager Tool
-
ST-A/PI 01K_CRM560 0000 - Application Servicetools for CRM 500 510
-
ST-ICO 150_700 0014 SAPK-1507EINSTPL SAP Solution Manager Implementation Cont
-
ST-SER 700_2008_1 0003 SAPKITLOO3 SAP Solution Manager Service Tools
-
===================================================================================================
===================================================================================================
Could you please provide the fix for this issue.
Appreicate your help and early solution.
Thanks/Rakesh
Hi Anjali,
I really appreciate for the quick reply.
Infact, I went through the note Note 1032269 - Creation of EarlyWatch Alert report ends with a short dump.
I did the Workaround suggested in the note:
Change the defaults of the user for the 'Decimal Notation' from 1,234,567.89 to 1.234.567,89 . The user needs to log on again.
This workaround was successful in all known cases. But it will not necessarily apply to all kind of similar short dumps which could occur in other checks (depends on the input data in the check table).
Goto SU01 of the User: SMADMIN(the same user ID used to configure EWA) --> change the decimal notation to 1.234.567,89 from 1,234,567.89
Then run the job again and I could see the job finished and generated the EWA Report and fixed the issue.
It worked for me...
Thanks/Rakesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok, As the dumps says, use the keywords "MESSAGE_TYPE_X" " " "SAPLDSVAS_PROC" or "LDSVAS_PROCTAI" "UNPACKED_SET to search for the SAP Notes
Note 768600 - RDSMOPBACK_AUTOSESSIONS termination with MESSAGE_TYPE_X
Note 764527 - RDSMOPBACK_AUTOSESSIONS termination w/ MESSAGE_TYPE_X
Note 700518 - SAP Service Sessions: How To Do Error Analysis
Note 890057 - MESSAGE_TYPE_X when you open service sessions
Note 1043161 - SL Reporting: MESSAGE_TYPE_X
Note 1343546 - EarlyWatch Alert: Short Dump Message_type_X with SLR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.