on 12-31-2014 12:50 PM
HI Experts,
In our ECC development server we are gettin this error and also when we check system status it showing blank. I checked saposcol, its running. Please help me resolve this issue.
Runtime Errors | GEN_INCLUDE_NOT_EXEC |
Date and Time | 31.12.2014 18:05:27 |
Short Text
Program "CL_FB_PARAMETER_DB============CP" is type I and therefore cannot be |
What happened?
The current ABAP/4 program | |
attempts to call the program "CL_FB_PARAMETER_DB============CP", | |
but this program cannot be executed. | |
Therefore, the current program had to be terminated. |
What can you do?
Note down which actions and inputs caused the error. |
To process the problem further, contact you SAP system | |
administrator. |
Using Transaction ST22 for ABAP Dump Analysis, you can look | |
at and manage termination messages, and you can also | |
keep them for a long time. |
Error analysis
If the system determines at runtime that a program called with SUBMIT | |
or a routine accessed by an external PERFORM | |
cannot be executed (because the program is type I instead of 1 | |
or M), that program must be terminated. |
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: |
"GEN_INCLUDE_NOT_EXEC" " " | |
"CL_FB_PARAMETER_DB============CP" or | |
"????????????????????????????????????????" | |
" " Regards Manjappa H M |
I had the same issue in one of my programs at CALL FUNCTION or RECEIVE RESULTS FROM FUNCTION, the called function module belongs to a ZZZ function group whose SAPLZZZ was of type I (include) instead of type F (function pool), for unkwown reason (it was F for a long time, I don't know what suddenly happened). ABAP 7.52 system.
I solved as explained in note 2017410 - GEN_INCLUDE_NOT_EXEC for ABAP Program SAPLSEOP or SAPLSEDI_ACTIVATE (although this note concerned another function group, the procedure works on any function group: SE16 on table PROGDIR, change column SUBC of SAPLZZZ from I to F)
This one might also work: 592507 - Incorrect program type in PROGDIR/TRDIR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you please share complete dump details and current kernel release,if possible first patch your existing kernel with latest available and check again.
Additionally follow SAP note 1656703 - Short dump GEN_INCLUDE_NOT_EXEC
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Could you paste or attach the full dump
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Below is the dump
Runtime Errors GEN_INCLUDE_NOT_EXEC
Date and Time 02.01.2015 13:22:13
Short Text
Program "CL_FB_PARAMETER_DB============CP" is type I and therefore cannot be
What happened?
The current ABAP/4 program
attempts to call the program "CL_FB_PARAMETER_DB============CP",
but this program cannot be executed.
Therefore, the current program had to be terminated.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
If the system determines at runtime that a program called with SUBMIT
or a routine accessed by an external PERFORM
cannot be executed (because the program is type I instead of 1
or M), that program must be terminated.
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:
"GEN_INCLUDE_NOT_EXEC" " "
"CL_FB_PARAMETER_DB============CP" or
"????????????????????????????????????????"
" "
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
tem environment
SAP-Release 700
Application server... "eccdev"
Network address...... "confidential"
Operating system..... "Linux"
Release.............. "2.6.9-34.ELsmp"
Hardware type........ "i686"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "eccdev"
Database type..... "ORACLE"
Database name..... "DEV"
Database user ID.. "SAPSR3"
Terminal................. "AIPL-DT-BLR-107"
Char.set.... "en_US.ISO-8859-1"
SAP kernel....... 700
created (date)... "Dec 24 2011 07:24:32"
create on........ "Linux GNU SLES-9 i686 cc3.3.3"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 333
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, O
SAP database version. 700
Operating system..... "Linux 2.6, Linux 3"
Memory consumption
Roll.... 8112
EM...... 8362368
Heap.... 0
Page.... 65536
MM Used. 628856
MM Free. 415104
User and Transaction
Client.............. 200
User................ "BASISADM"
Language key........ "E"
Transaction......... " "
Transactions ID..... "54A6156935C93AC9E1000000C0A86407"
Program............. "CL_FB_PARAMETER_DB============CP"
Screen.............. " "
Screen line......... " "
Information on where terminated
The termination occurred during generation of the ABAP/4 program
"CL_FB_PARAMETER_DB============CP".
-
The termination occurred in line 0
of the source code of program "????????????????????????????????????????" (when
calling the editor 00).
Internal notes
The termination was triggered in function "cg_generate"
of the SAP kernel, in line 500 of the module
"//bas/700_REL/src/krn/gen/cgmain2.c#11".
The internal operation just processed is " ".
Internal mode was started at 20150102132213.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(CTrcStack2+0x78)[0x82a3f88]
(CTrcStack+0x23)[0x82a45b3]
(ab_rabax+0x3711)[0x8773b61]
(cg_generate+0xe8c)[0x8a2fe9c]
(ab_gabap+0x118)[0x86e89c8]
(dy_gen_abap+0x5dc)[0x831e29c]
(ab_genprog+0x14d8)[0x86eac48]
(_Z17ab_LoadProgOrTrfoPKcjPj+0xb69)[0x84da379]
(_Z11ab_LoadProgPKcj+0x1f)[0x84da5af]
(_Z15LoadGlobalClassPKcjjj9ClasState+0x257)[0x8538da7]
(_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x204)[0x85375d4]
(_Z11ab_FillCfixtj+0x5d)[0x8537c5d]
(_Z26ab_CrefToCladId_ActivateOKtPh+0x63)[0x8537cd3]
(_Z8ab_jaboov+0x5fb)[0x853980b]
(_Z8ab_extriv+0x528)[0x849dd08]
(_Z9ab_xeventPKc+0x26a)[0x85fb1ea]
(ab_dstep+0x1ac)[0x8787a7c]
(dynpmcal+0x4ea)[0x830d50a]
(dynppbo0+0x595)[0x83104b5]
(dynprctl+0x39b)[0x830e20b]
(dynpen00+0x45f)[0x83007cf]
(Thdynpen00+0x2bd)[0x8114e4d]
(TskhLoop+0xbaa)[0x812031a]
(ThStart+0x213)[0x812d253]
(DpMain+0x35c)[0x80903bc]
(main+0x1e)[0x8064efe]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0x12a8e23]
Regards
Manjappa
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.