on 02-21-2008 10:56 AM
Hello,
I have NW4 running on FC5.
When I try to create a webservice in SE80 the whizard dumps:
Runtime Errors GEN_NO_GENINFO_FOR_DATID
Occurred on 21.02.2008 at 10:08:16
-
No generation information for DATID "%_#D18404".
-
What happened?
-
Processing had to be terminated because an internal error
occurred when generating the ABAP/4 program "CL_SWF_CNT_FACTORY============CP".
-
What can you do?
-
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
-
Error analysis
-
There is no generation information for the internal ID "%_#D18404".
This is most probably due to an
invalid DATID or an object type for which there is usually
no generation information.
Possible causes for the error are:
- an RSYN programming error
- the following internal constants were used
%_ENDIAN, %_CHARSIZE, %_MINCHAR, %_MAXCHAR, %_HORIZONTAL_TAB,
%_VERTICAL_TAB, %_NEWLINE, %_CR_LF, %_FORMFEED, or %_BACKSPACE
For optimization reasons, no generation information is created for these
constants. Therefore these constants can generally only be used with
the VALUE specification of DATA, CONSTANTS etc.
-
How to correct the error
-
Use the Transaction SYNT to search for the error.
-
System environment
-
SAP Release.............. "640"
Application server....... "BLN787"
Network address.......... "192.168.100.2"
Operating system......... "Linux"
Release.................. "2.4.22-1.2129.nptlsm"
Hardware type............ "i686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "BLN787"
Database type............ "ADABAS D"
Database name............ "NW4"
Database owner........... "SAPNW4"
Character set............ "en_US.ISO-8859-1"
SAP kernel............... "640"
Created on............... "Jan 13 2004 20:13:34"
Created in............... "Linux 2.4.18-64GB-SMP
#1_SMP_Wed_May_15_13:27:16_GMT_2002 i686"
Database version......... "SAPDB 7.4.3.029 "
Patch level.............. "1"
Patch text............... " "
Supported environment....
Database................. "SAP DB 7.4.3, MySQL MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.2, Linux 2.4"
Memory usage.............
Roll..................... 8112
EM....................... 15679560
Heap..................... 0
Page..................... 49152
MM Used.................. 6768560
MM Free.................. 546564
SAP Release.............. "640"
-
User, transaction...
-
Client.............. 000
User................ "DEVELOPER"
Language key........ "E"
Transaction......... " "
Program............. "CL_SWF_CNT_FACTORY============CP"
Screen.............. " "
Screen line......... " "
-
Information on where terminated
-
The termination occurred during generation of the ABAP program
"CL_SWF_CNT_FACTORY============CP".
The point of termination was in line 64 of the ABAP source code of the
(Include) program "CL_SWF_CNT_FACTORY============CCIMP".
of the program "CL_SWF_CNT_FACTORY============CCIMP" (when calling the editor
640).
-
Source code extract
-
000340
000350 **** Test methods. Use TA SE80 or RS_AU_LIGHT for complete test.
000360
000370
000380 **** Test METHOD test_instance_manager_state
000390 METHOD test_instance_manager_state.
000400 DATA:
000410 l_abap_rh1 TYPE swfrcntref, "cont IF reference
000420 l_abap_rh2 LIKE l_abap_rh1,
000430
000440 l_inst_manager_state TYPE xfeld,
000450 l_num_requests TYPE i,
000460 l_num_hits TYPE i,
000470 l_num_misses TYPE i,
000480 l_cache_size TYPE i,
000490 l_last_reset TYPE timestamp,
000500 l_non_expected_ifs_cx TYPE REF TO cx_swf_ifs_exception.
000510 **** container manager is expected to be active
000520 CONSTANTS l_expected_inst_manager_state TYPE xflag VALUE 'X'.
000530 **** is the container instance manager currently active ?
000540 TRY.
000550 CALL METHOD cl_swf_cnt_factory=>create_method_container
000560 EXPORTING
000570 im_objtype = 'CL_SWF_CNT_FACTORY'
000580 im_catid = 'CL'
000590 im_method = 'CREATE'
000600 IMPORTING
000610 ex_method_container = l_abap_rh1.
000620 CATCH cx_swf_ifs_exception INTO l_non_expected_ifs_cx.
000630 ENDTRY.
-
> cl_aunit_assert=>assert_not_bound( l_non_expected_ifs_cx ).
000650
000660 TRY.
000670 CALL METHOD cl_swf_cnt_factory=>query_create_buffer
000680 IMPORTING
000690 ex_inst_manager_state = l_inst_manager_state
000700 ex_num_requests = l_num_requests
000710 ex_num_hits = l_num_hits
000720 ex_num_misses = l_num_misses
000730 ex_last_reset = l_last_reset
000740 ex_num_cache_entries = l_cache_size.
000750 CATCH cx_swf_ifs_exception INTO l_non_expected_ifs_cx.
000760 ENDTRY.
000770 cl_aunit_assert=>assert_not_bound( l_non_expected_ifs_cx ).
000780
000790 **** check status of instance manager
000800 cl_aunit_assert=>assert_equals( act = l_inst_manager_state
000810 exp = l_expected_inst_manager_state
000820 msg = 'METHOD' & "#EC NOTEXT
000830 'test_instance_manager_state:' & 'check instance manager state' ).
-
Contents of system fields
-
SY field contents..................... SY field contents.....................
-
-
-
-
-
Active calls / events
-
No dump information available
-
Chosen variables
-
No dump information available
-
Application Calls
-
No dump information available
-
Application Information
-
No dump information available
-
Internal notes
-
The termination occurred in the function "cg_GetSdatPtr" of the SAP
Basis System, specifically in line 2918 of the module
"//bas/640_REL/src/krn/gen/cgen.c#6".
The internal operation just processed is " ".
The internal session was started at 20080221100749.
-
Active calls in SAP kernel
-
(LinStack+0x3e)[0x81ed7ce]
(CTrcStack2+0x59)[0x81ed439]
(CTrcStack+0x21)[0x81ed3d1]
(rabax_CStackSave__Fv+0x9f)[0x857ac4f]
(ab_rabax+0x400)[0x8571db0]
(cg_GetSdatPtr__FPc+0x7e)[0x87523de]
(cg_cbindex__FPc+0x18)[0x8752408]
(sc_scont_short+0x86)[0x874d996]
(rs_expan_abap+0x51cff)[0x886210f]
(sc_expan__FUi+0xcf)[0x872e23f]
(parse__FUiPi+0x479)[0x8726fc9]
(sc_check+0x1bd)[0x872573d]
(ProcessText__FUi+0x6a)[0x872556a]
(sc_check+0x15c)[0x87256dc]
(sc_inclu+0x6e2)[0x871f142]
(rs_oper_abap2129+0x8e)[0x894d79e]
(rs_expan_abap+0x8f618)[0x889fa28]
(sc_expan__FUi+0xcf)[0x872e23f]
(parse__FUiPi+0x479)[0x8726fc9]
(sc_check+0x1bd)[0x872573d]
(cg_generate+0x9df)[0x8757c2f]
(ab_gabap+0x9f)[0x850c85f]
(dy_gen+0x45c)[0x82473ac]
(ab_genprog__FPcPvUii+0x487)[0x850c187]
(newload__FPcP13TmpSubpoolDirUi+0x29e)[0x8355b2e]
(ab_LoadProg__FPcUi+0x152)[0x8355752]
(LoadGlobalClass__FPCcUiUiUi9ClasState+0xcd)[0x83a06dd]
(FillCfixInt__FPC4CREFP4CFIXUiUi9ClasState+0x19f)[0x83a1bff]
(ab_FillCfix__FUsUi+0x23c)[0x83a263c]
(ab_CrefToCladId_ActivateOK__FUsPUc+0x4c)[0x83a26fc]
(ab_jclcc__Fv+0x26)[0x84190c6]
(ab_extri__Fv+0x9c9)[0x831e9b9]
(ab_xevent__FPCc+0x20)[0x8457f10]
(ab_dstep+0x775)[0x8582d55]
(dynpmcal+0x89b)[0x823e83b]
(dynppbo0+0x2a8)[0x823bb88]
(dynprctl+0x62e)[0x823b5fe]
(dynpen00+0x2db0)[0x8239160]
(Thdynpen00+0x6f6)[0x80d1916]
(TskhLoop+0x3bdf)[0x80d0c6f]
(tskhstart+0x27b)[0x80c964b]
(DpMain+0x26c)[0x805af9c]
(main+0x16)[0x80595a6]
/lib/libc.so.6(__libc_start_main+0xbf)[0x41dbbbaf]
-
List of ABAP programs affected
-
-
No dump information available
-
List of internal tables
-
No dump information available
-
Directory of Application Tables
-
No dump information available
-
Directory of Application Tables (Administrative Information)
-
No dump information available
-
ABAP control blocks CONT
-
No dump information available
-
End of runtime analysis
-
Has anyone come across this and knows how to fix it?
Thanks
Matthias
Hi,
upgrade you kernel.
A kernel patch is available for kernel release 6.40 (patch text: "runtime error GEN_NO_GENINFO_FOR_DATID", patch number 57)
regards,
kaushal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks,
where can I get this patch?
I have currently no access to servive marketplace.
Matthias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.