Skip to Content
0

Package folders don't allow to run jobs

Apr 12, 2017 at 02:34 PM

67

avatar image

Hey,

has anybody the same problem, that if you create a tree structure within Eclipse with package folders, that you cannot run jobs within this folder? After clicking on run, nothing happens. Exactly the same job in a package which is on first-Level of the structure runs perfectly (same dispatcher etc.). Seems like a bug, but for now we don't have a workaround.

We recently ugraded the System 7.2 => 8.0 SP 4. AS Java Netweaver 7.4 and Oracle DB on the same Windows Server 2008 R2.


KR Marcel

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

C Kumar Apr 12, 2017 at 07:44 PM
0

Hello Marcel,

Could you please share the corresponding error screenshot. Please also ensure that the Job must be enabled.

Regards,

C Kumar

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hey Kumar,

the problem ist, there ist no error. The job is not running, if he is within a package structure. You click on run and nothing happens. Excatly the same constellation like outside the package structure (When it runs). Enabled: Yes. Dispatcher for job: yes. Dispatcher running: yes.

You can switch the corresponding package between the package folder and on the first-level again and again. It works (1stLevel) and it doesn't work (in a folder).

By the way, we are using Eclipse Mars (4.5.2).

I think the mistake is coming in this Prelog.log:

13.04.2017 09:31:27 :E: Error code 6502 SQL state:65000(!) - 
java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: 
character string buffer too small
ORA-06512: at "MXMC_OPER.MC_LOCATE_PACKAGE", line 22
ORA-06512: at "MXMC_OPER.MC_LOCATE_OBJECT", line 111
ORA-06512: at "MXMC_OPER.MC_JOB_GETINFO", line 69
ORA-06512: at line 1<br><strong></strong>

13.04.2017 09:31:27 :E: - java.lang.RuntimeException: Package information not found for jobid:1007052

As soon as IdM has to go in the "MXMC_OPER.MC_LOCATE_PACKAGE" the string buffer is to small. How can I increase it? Maybe there is a variable which was declared with a small data type. And (because there is an additional package name) there is a too big value.

In another log it also says so. That the db function didnt't return a value:

13.04.2017
09:23:27: com.sap.idm.ic.MCHandler :D: BEGIN mc_getx_job(:1 ,:2 ,:3 ,:4 ,:5 ,:6
,:7 ,:8 ); END;,1=idmdispatcher,2=2,3=10.117.81.231,4=8.0.4.3 -
227834
13.04.2017
09:23:27: com.sap.idm.ic.DBStatement :D: execute:{call
mc_getx_job('idmdispatcher',2,'10.117.81.231','8.0.4.3 -
227834',@PAR5 OUTPUT(INTEGER),@PAR6 OUTPUT(VARCHAR),@PAR7 OUTPUT(INTEGER),@PAR8
OUTPUT(VARCHAR))} - time used: 4 ms
13.04.2017
09:23:27: com.sap.idm.ic.MCHandler :X: MCGetJob(idmdispatcher,2) did
not return a job!Status=No
scheduled jobs for idmdispatcher (1)
13.04.2017
09:23:27: com.sap.idm.ic.DSERunTime :X: No job returned from IdentityCenter
<br>

Thanks!

KR Marcel

0
Deva Prakash B Apr 13, 2017 at 10:17 PM
0

Hi Marcel,

I have also face the same issue with repository based jobs in idm sp00.

When we try to run from identity center it doesnt get triggered at all.

try to run it form admin ui or else disable and enable the job, change dispatcher and check. for me enabling & disabling the job after changing dispatcher worked. Try to check the mc_jobs tables the state whether it is 1.

Regards,

DP

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hey DP,

thanks for your hints. I think it is the easiest way to avoid a package structure and only use packages on first level.

Regards, Marcel

0