on 11-29-2016 9:17 PM
Scheduling SQL Monitor collection jobs creates ABAP runtime errors.
GEN_INCLUDE_NOT_EXEC
Program "AL01100R" is type I and therefore cannot be generated.
The current ABAP/4 program
attempts to call the program "AL01100R",
but this program cannot be executed.
Therefore, the current program had to be terminated.
The program "AL01100R" was started as a background job.
Job Name....... "/SDF/ZQLM_UPDATE_DATA/SCHEDULE"
The program is type I - Include in production, but type 1 - Executable in QA system and does not exist at all in development. No version information exist either in any of the systems.
Jobs in QA and development environment run with out dumps.
Has anyone faced the same?
System details:
Oracle 11.2.0.4
SAP Basis 701 SP18
ST-PI 2008_1_700 SP14
SAP Kernel 721_EXT_REL patch 700
Reference notes:
1885926 - ABAP SQL monitor
1972328 - SQL Monitor - robustness and minimization of administrative efforts
have a look at => https://launchpad.support.sap.com/#/notes/0001634704
sapnote: 1634704 - ALLOCATION: Kurzdump GEN_INCLUDE_NOT_EXEC
==========================
sapnote: 2017410 https://launchpad.support.sap.com/#/notes/0002017410
use SE16N + edit the type from "I" to "F"
=====
You can check the SUBC type definition on:
In case program "SAPLSEOP" is defined as “I” or “K” instead of “F”, you should manually set SUBC value as “F”, by following below procedure:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
sapnote: 2017410 https://launchpad.support.sap.com/#/notes/0002017410
use SE16N + edit the type from "I" to "F"
=====
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.