cancel
Showing results for 
Search instead for 
Did you mean: 

SAP IDM doesn't trigger Initial Load Job

ravi_paul
Participant
0 Kudos
105

Facing very strange issue:

We have imported AD package from Development to Quality IDM system, added AD repository details and while I run the initial load for AD, it doesn't trigger anything in Job Log. I confirm, dispatcher is running and SF Job & Process are running fine with same dispatcher.

Later I imported ABAP Package from Dev to QA IDM and there as well facing same issue with running Initial Load.

Then we created another dispatcher in QA IDM to match the name with Dev IDM and then re-imported both packages, unfortunately same issue.

In mc_jobs table, Jobdefinition is NOT NULL (some b64 encoded value) and statustext says - 'Error retrieving job definition'

Whereas under Initial Load Job properties, each time I try to run the job, it add Number of Errors -

ravi_paul_0-1729859648513.png

Any help will be greatly appreciated?

-RP

View Entire Topic
ravi_paul
Participant
0 Kudos

In interest of all specialist. We got the issue resolved.

Found the following error while troubleshooting in Oracle DB -

31.10.2024 14:27:39 :D: 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

31.10.2024 14:27:39: com.sap.idm.ic.DBStatement :D: execute:{call mc_job_getinfo(0,1006145,@PAR3 OUTPUT(INTEGER),@PAR4 OUTPUT(UNKNOWN))} - time used: 9 ms
31.10.2024 14:27:39 :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

 

Found an error at database level relating to mentioned three procedures. These are SAP procedures. We increased value and recompiled procedure and working now. Interestingly it was correct in Dev environment but not in Quality.