IDM Job Not Executing

Hi All,
I have created a regular job to create a "Entry Type" Jasper Report using the templates that come along with SAP IDM 7.1 installation. The job keeps idle indefinitely and times out. Earlier it used to get rescheduled again and again. The following JARs are being made use of. Using "Force Restart" option hasn't paid off either. Can anything be done to execute the job?
1. commons-beanutils-1.8.0
2. commons-collections-3.2.1
3. commons-digester-1.7
4. commons-javaflow-20060411
5. commons-logging-1.1
6. itext-2.0.8
7. jasperreports-1.3.0
8. jcommon-1.0.15
9. jfreechart-1.0.12
10. js_jaxrpc
11. jxl-2.6
12. xercesImpl
Thanks & Regards,
Vijayakumar Ganesan

What is the value of init. parameter job_queue_processes ?
job_queue_processes=10Do you have any error message related to this job in the db alert.log ?
Not a single error message. When I issued EXEC proc_name; the following lines were added in the alert.log:kupprdp: master process DM00 started with pid=20, OS id=5225
to execute - SYS.KUPM$MCP.MAIN('TIMS_EXP_FULL15Jan2007_1434', 'SYS', 'KUPC$C_1_20070115143431', 'KUPC$S_1_20070115143431', 0);
kupprdp: worker process DW01 started with worker id=1, pid=21, OS id=5227
to execute - SYS.KUPW$WORKER.MAIN('TIMS_EXP_FULL15Jan2007_1434', 'SYS');
select * from dba_jobs;
This important info is given below:JOB = 22
LOG_USER=SYS
PRIV_USER=SYS
SCHEMA_USER=SYS
LAST_DATE=
LAST_SEC=
THIS_DATE=
THIS_SEC=
NEXT_DATE=16-JAN-07
NEXT_SEC=00:00:00
TOTAL_TIME=0
BROKEN=N
INTERVAL=TRUNC(SYSDATE)+1
FAILURES=
WHAT=PROC_NAME;
As you can see that in the NEXT_DATE it was scheduled to run on 16-JAN-07 but it didn't run on that date and time and it is still showing the backdate in the NEXT_DATE.
Just to clerify:
SELECT TO_CHAR(NEXT_DATE, 'DD-MON-YYYY HH24:MI:SS') FROM DBA_JOBS;
TO_CHAR(NEXT_DATE,'D
16-JAN-2007 00:00:00

Similar Messages

Scheduled SAP Job not executed as per restrictions

Hi All,
A job was scheduled to execute every Saturday (Job Frequency - weekly). Also in the Start time - Restrictions, the check box for "Execute only on Workdays" is checked.
Last saturday 27/08 was a holiday (displayed properly in the factory calendar), So the job should not have got executed.
But it got executed. I cannot find any reason for this.
Is there any other conditions that need to be provided so that it don't get executed on non-working days?

- Check in job definition if the factory calendar of the job is the good one (TBTCO-CALENDARID for the job that executed saturday), check also if job definition was changed (TBTCO-LASTCHDATE, LASTCHTIME and LASTCHNAME for next scheduled job) (or "Job details" on SM37)
- Check in the factory calendat, if the holiday was changed after saterday (SCAL, Extras, Display change docs.)
Regards,
Raymond

Job not executing through database link

hello all,
we have a database server with oracle 10g enterprise edition on RHEL 5.3 64-bit , we have created a procedure which pulls data from a remote server using a procedure. that procedure collect data in cursor ..both server are connected using RF connectivity..
but after every 2 or 3 days i saw that data is not pulled and job is marked as broken .... and when i mark that job as unbroken and try to rexecute that procedure it hangs for long.....
i don't understand whats going on....i have also seen large number of sessions in my database..is possible that huge number of session are consuming resources and that's why oracle is unable to execute the job??? i have check network also but it is fine...i can access that remote server using VNC or team viewer..so network is definitely not an issue...
i also set SQLNET.EXPIRE_TIME=10 in sqlnet.ora file and also created a profile for idle_time to get rid of excess inactive sessions....what might be issue??? any suggestion is appreciable...
thanks and regards
VD

hello sir,
actually it is not about the job, i am sure that procedure is causing problem..... because when i try to execute that procedure , it also hangs, i check all requirements need to be checked..... i think lots of inactive sessions causing this issue, but even after adding sqlnet and profile i is not removing those sesions and hence i think that procedure is not executing....
coz the database i am connecting is having already connections and doing lots of transactions...so i it possible that it might be an issue.??
sometime i also got timeout error while connection to that remote server but it is not issue because at the same time i am connected to it from another machine..
thanks and regards
VD

Background job not executing... pls help

I want to schedule and execute a batch job with the start date and time with another program.
In program1 im doing the below.
job_open
   getting job_count
CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
      no_dialog              = abap_true
    IMPORTING
      out_parameters         = ls_params
      valid                  = lv_valid
    EXCEPTIONS
      archive_info_not_found = 1
      invalid_print_params   = 2
      invalid_archive_params = 3
      OTHERS                 = 4.
SUBMIT (c_test)                 VIA JOB lv_jobname
                                  NUMBER lv_jobcount
                               TO SAP-SPOOL WITHOUT SPOOL DYNPRO
                                   SPOOL PARAMETERS ls_params
                                   AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
      JOBCOUNT             = lv_jobcount
      JOBNAME              = lv_jobname
      LASTSTRTDT           = p_sdate
      LASTSTRTTM           = p_stime
     targetserver         = lv_targetserver
    EXCEPTIONS
      CANT_START_IMMEDIATE = 1
      INVALID_STARTDATE    = 2
      JOBNAME_MISSING      = 3
      JOB_CLOSE_FAILED     = 4
      JOB_NOSTEPS          = 5
      JOB_NOTEX            = 6
      LOCK_FAILED          = 7
      INVALID_TARGET       = 8
      OTHERS               = 9.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
in the job_closei gave start date and time, but the job is getting scheduled but not to released/cancelled status.
I want the job to happen at that given time and date,
is there anything im missing,
pls help

Rajan,
In the same documentation it says : Note:  if a user does not have the authorization to release a job, then the job is scheduled with the status planned.
Now after i run this program , and check SM37, the status is scheduled. so this tells not an authorization issue.
Also i can go and schedule on a given time from SM36.
Now after reading that i also passed the parameter JOB_WAS_RELEASED importing it is geting blank value.
but documentation says, it shud be X if Job is released.
any idea pls....
Niraja

Scheduled job not getting executed on a logical standby

Hello,
We have created a job(through dbms_scheduler API). The job is enabled and shows up in the SCHEDULERJOBS view also.
However the job does not get executed. I looked into the following tables there was no relevant entry found for the aforesaid job:
select * from all_scheduler_job_log
select * from dba_scheduler_running_jobs
select * from DBA_SCHEDULER_JOB_RUN_DETAILS order by log_date desc
Is there any limitation that we cannot execute scheduled jobs on a logical standby database. If i execute the relevant program (that is configured to be run as job in this scenario) as an individual procedure from SQL plus, it gets executed successfully implying there is no errors/problem in the subprogram that the job is going to invoke.
Appreciate your thoughts in this regard.
Thanks.

Hi Justin,
Thanks for your response.
As per the app design, the job invokes a stored program(that maps to a stored procedure present in standby db itself) that reads the data from standby and populates the relevant tables/entities in another database(third db, not primary or standby) which acts as a repository. No write operations are to be performed on standby.
So, i have two doubts:
-- Can scheduled jobs execute on logical standby db[Oracle release 10g(R2)]
I was going through few of the oracle docs and it is mentioned that this is a known limitation in 10g
R2 release and has been corrected in 11g. Now we have something called database_role
attribute that needs to be set to 'LOGICAL STANDBY' if you need to execute a job on
standby. However it is available in 11g onwards.
-- If there is no workaround for the above mentioned problem in 10g-R2 release.
Then we may have to schedule a job from third db instance that shall invoke the program(residing on the standby db). Can we have a scheduled job which executes a program that maps to a remote stored procedure instead of local stored procedure?
Appreciate your thoughts.
Thanks

Oracle Jobs not getting executed

Hi all,
I am using oracle release 10.2.0.4.0. I have two similar databases and I am trying to run same jobs in two different databases. one is running successfully however when i m trying to submit the same jobs in another database the jobs are getting stuck in DBA_JOBS with below values:
next_date next_sec total_time broken interval failures
15-07-2009 00:00:00 0 N NULL NULL
and jobs are not giving desired result. in fact they are not doing any thing which i am expecting.
there is no change in program level. same program unit is able to submit the job in another database. I have checked the job_queue_processes and value is 10.
I don't have any clue were to check at oracle level. i am pl/sql dev so i don't have much hand on oracle.
here is the program block which is submitting jobs:
Job := 'batch_run.Pr_Process_dup
( ' || chr(39) || CurBranch || chr(39) || '
,' || chr(39) || CurUser || chr(39) || '
sys.dbms_job.submit(jno, job, StartTime, Interval);
commit;
This is the part of function were job is getting submitted.
I don't think there is any issue at program level as it was working fine before and there is no change aswell. also same functions are being used in other database. in fact we are using these objects in front end which is working fine in rest of databases.
We have two databases at same server.I compared all parameters in both instances.
Please help me.

hi
here are the steps which I did.
1. I submitted job using below code.
declare
job1 integer :=0;
begin
sys.dbms_job.submit(job1,'Begin null; end;',sysdate,'');
commit;
end;
here are the values i was getting in DBA_jobs:
next_date 16-07-2009 15:35:20
next_sec 15:35:20
total_time 0
broken N
interval null
failures (no value)
what Begin null; end;
I don't think it was running.
2. After running ur statement:
set serveroutput on;
exec dbms_job.run(9623);
output: PL/SQL procedure successfully completed.
Job was not present in DBA_JOBS so i think Job got executed.
I am clueless what is happening.What should be the cause?why is it not getting executingwhile running inside the pl/sql block?
Thanks
Edited by: sameer wani on Jul 16, 2009 8:52 AM

Not executing the job automatically scheduled in dba_scheduler_jobs

Hi Friends,
I have scheduled a job in dba_scheduler_jobs ,it should run on every 15 mins intervel , But it is not happening.If I trigger the job by manually .. like exec dbms_scheduler.run_job('SNAP15MIN_JOB') , executing successfully.
please fiind the below info...
Oracle s/w : Oracle Standared Edition 10.2.0.4
Used cript to create the job :
begin
dbms_scheduler.create_job(
job_name => 'snap15min_JOB',
START_DATE => SYSDATE ,
job_type => 'PLSQL_BLOCK',
job_action => 'begin statspack.snap;end;',
repeat_interval => 'SYSDATE + 10/1440',
enabled => true,
comments => 'statspack 15mins job');
end;
SQL> select JOB_NAME,REPEAT_INTERVAL,STATE from dba_scheduler_jobs;
JOB_NAME REPEAT_INTERVAL STATE
SNAP15MIN_JOB SYSDATE + 10/1440 SCHEDULED
please help on this .
Thanks
Mahesh

Hi,
Please select start_date, LAST_START_DATE, next_run_date for the job.
Also see this post for more tips
Answers to "Why are my jobs not running?"
Hope this helps,
Ravi.

Could not execute the job

Hi,
when i execute the job a a window appear with the massage" ERROR: could not execute the job .Error returned was 1
     MESSAGE is : Could not open command file...
And i can't find from where it comes any suggestion?

When today i execute the job i had this list of error
13860    15384    REP-100109        27/05/2014 08:22:10       |Session TF_SGFA
13860    15384    REP-100109        27/05/2014 08:22:10       Cannot save <History info> into the repository. Additional database information: <SQL submitted to ODBC data source
13860    15384    REP-100109        27/05/2014 08:22:10       <SIGSIRDDB01\SQLSIRDBD> resulted in error <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object
13860    15384    REP-100109        27/05/2014 08:22:10       'dbo.AL_HISTORY_INFO' in database 'DS_REP' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded
13860    15384    REP-100109        27/05/2014 08:22:10       files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files
13860    15384    REP-100109        27/05/2014 08:22:10       in the filegroup.>. The SQL submitted is <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME",
13860    15384    REP-100109        27/05/2014 08:22:10       "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
13860    15384    REP-100109        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
13860    15384    REP-100109        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
13860    15384    REP-100109        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
13860    15384    REP-100109        27/05/2014 08:22:10       TXT') >.>.
13860    15384    REP-100112        27/05/2014 08:22:10       |Session TF_SGFA
13860    15384    REP-100112        27/05/2014 08:22:10       Cannot save <History info> for repository object <>. Additional database information: <Cannot save <History info> into the
13860    15384    REP-100112        27/05/2014 08:22:10       repository. Additional database information: <SQL submitted to ODBC data source <SIGSIRDDB01\SQLSIRDBD> resulted in error
13860    15384    REP-100112        27/05/2014 08:22:10       <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.AL_HISTORY_INFO' in database 'DS_REP'
13860    15384    REP-100112        27/05/2014 08:22:10       because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
13860    15384    REP-100112        27/05/2014 08:22:10       adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.>. The SQL submitted is
13860    15384    REP-100112        27/05/2014 08:22:10       <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME", "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
13860    15384    REP-100112        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
13860    15384    REP-100112        27/05/2014 08:22:10       TXT') >.>.>.
13860    15384    REP-100112        27/05/2014 08:22:10       |Session TF_SGFA
13860    15384    REP-100112        27/05/2014 08:22:10       Cannot save <History info> for repository object <>. Additional database information: <Cannot save <History info> into the
13860    15384    REP-100112        27/05/2014 08:22:10       repository. Additional database information: <SQL submitted to ODBC data source <SIGSIRDDB01\SQLSIRDBD> resulted in error
13860    15384    REP-100112        27/05/2014 08:22:10       <[Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.AL_HISTORY_INFO' in database 'DS_REP'
13860    15384    REP-100112        27/05/2014 08:22:10       because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup,
13860    15384    REP-100112        27/05/2014 08:22:10       adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.>. The SQL submitted is
13860    15384    REP-100112        27/05/2014 08:22:10       <INSERT INTO "AL_HISTORY_INFO" ("OBJECT_KEY", "NAME", "VALUE", "NORM_NAME", "NORM_VALUE") VALUES (430, N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/log/JobServDS/sigsirddb01_sqlsirdbd_ds_rep_dsuser/trace_05_27_2014_08_22_09_10__3a4327b0_92c8_4abe_ac24_96d49123242a.
13860    15384    REP-100112        27/05/2014 08:22:10       txt', N'TRACE_LOG_INFO',
13860    15384    REP-100112        27/05/2014 08:22:10                N'F:\SAPDS/LOG/JOBSERVDS/SIGSIRDDB01_SQLSIRDBD_DS_REP_DSUSER/TRACE_05_27_2014_08_22_09_10__3A4327B0_92C8_4ABE_AC24_96D49123242A.
13860    15384    REP-100112        27/05/2014 08:22:10       TXT') >.>.>.
and thank u.
Sincerly

Why Are My EM Jobs Not Editable After They Execute?

hi experts,
I'm using 10g's Database Control tool to create some Export jobs - using the "Export to Export Files" wizard
When I create the job, it executes at the scheduled time. But then I cannot modify the schedule after that. When I attempt to edit the job, I get error
"Edit is not supported for *this job type*, only general information about the job can be updated No scheduled executions - this job can not be modified."
I want to be able to modify the schedule or change anything else I may need to change. What is different about this job type that makes it uneditable?
Sorry I'm new to Oracle jobs, still learning.
Thanks, John

3.6.0 Editing Finished Jobs
When attempting to edit a job, a user might see this error message: "No scheduled executions - this job cannot be modified". This means that based on the job's schedule, Enterprise Manager has determined that there are no future job executions scheduled for this job. Hence editing the parameters of the job does not make sense and thus will be prevented. However, the access page of the job can always be modified by the job owner, even after the job finishes, in order to share job output with others.
Please see more detailed documentation here:
http://www.coppertop.org.uk/doc/readmes/README_EM.htm#Jobs

Job scheduled in background but not executed

Dear Expert, above is section of code through which i am scheduling a program to run in background. through this a job is created and is schedule(it show schedule using sm37) but it's not executed (generate output ).
Edited by: shekharamit on Jul 14, 2010 1:09 PM

See what is the status now it is showing ,
if it is canceeled see why it got cancelled?it can be because of job closed or like.
it can aslo be like there are more jobs in queue , so giver it as high priority .
Try withthis
Rajendra

Job is not executing

Hi,
I scheduled one package in test server but when I am scheduling that package on Live server it is not executing
job is showing in user_jobs table but it is not executing. could any body suggest what is the problem?
Regards
Gagan

could you give the commit a try. In my server, the total time is 0 for my job and i know that it completed. Maybe your test server is just slower.
drop table testi;
Create Table Testi(I Int);
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
    ( Job       => X
     ,What      => 'insert into testi values (1); commit;'
     ,Next_Date => sysdate+10/86400
     ,interval=>null
     ,no_parse => TRUE
Sys.Dbms_Output.Put_Line('Job Number is: ' || To_Char(X));
End;
Select * From Testi;
select total_time from user_jobs;
I
1
1 rows selected
TOTAL_TIME
0
1 rows selected
Dave

Jobs not getting displayed in ECC

Hi
We implemented Redwood 8.0 and scheduled some jobs using that.
The jobs ran successfully in ECC server, but since then there is no jobs that we can view in SM37
All jobs are executing successfully, but there is no log in sm37.
Alos the JOBLOG files are there at OS
Can someone tell what happenned
Thanks and Regards
Tushar

Hi Tushar,
Usually most of the third party Background job scheduler just keeps "header" type information. The job logs history is not retained for x number of days. Please check with your backup team they might provide you a ztable name in which you can look at the history of the background jobs.
SAP_REORG_JOBS and the main report it runs that controls which jobs get rolled off is RSBTCDEL2.
Thanks.
Adil

Cron job not running - script uses rsync, ssh (with id_rsa)

Does anyone know how to get cron to run a rsync/ssh script which uses id_rsa for passwordless logins?
I have a backup script I have slaved for months over that works wonderfully when running it from the command line.
It uses rsync and connects with SSH (passwordless using ssh keys). I have setup id_rsa and id_rsa.pub for passwordless logins (this is my user account, and connects using root@ to the server)
As stated all works find when run from the command line. But when I setup a cron job to run this file (exact same line I run from the command line) it does not execute. Actually, it does run, as I have an email notifiction which sends to me. It is just the rsync/ssh part that does not run.
I have spent days and days trying to figure it out. No error messages occur, nothing. Took me a while to find out cron is emailing the user account on Lion the messages (not to a proper email address).
The error shows a permission denied, which I believe to be the cron user cannot use the id_rsa/ssh connection.
Cron is running the script as my user, the same I use on the command line. I even tried copying the id_rsa to the root user .ssh folder in case cron is running as root but that does not work either.
So does anyone know how to get cron to run this rsync/ssh script which used id_rsa for passwordless logins?
Thanks a lot

YES! Got it working, finally!
So the issue is indeed cron/launchd not being able to access the ssh-agent which holds the key.
So this is the solution...
Download keychain for Mac:
http://www.funtoo.org/wiki/Keychain
Then once its installed and configured, the script to run needs this added to the top:
eval `keychain --noask --eval id_rsa` || exit 1
Note I am using id_rsa whereas keychains instructions refer to id_dsa so I just changed it and it works OK.
When the script runs the first time it asks for the key password. Then it works from then on.
What I do not know yet is will I need to re-enter the password when I logoff/logon again. That will cause an issue as I auto restart the Mac every day which means if I am off for a few days backup will stop (can you see the madness in this issue!).

Background job not updating data for some steps of program

We have created a custom program and submitting the standard program RPRCCC_READ_KR1025
which is used for conversion of AMEX credit card files.
Since this program can update data for 1 company id at a time,we have created a background job
for that program with 10 steps and 10 variants of data related to 10 different company codes.
when this job is executed it is not updating data for all the 10 files , sometimes it updates 5,7,etc...
If we execute the other files which didnt update in job manually they are getting updated.
All the files executed with that program can be seen in PRTA transaction.
Regards,
Gautham.
Edit: Solved.
Since the standard program updates the database every time with commit work
there should be some time until the next database update,so we can use wait command
after the submit statement which will do the trick.
Edited by: Gautham Vangaveti on Aug 5, 2010 7:20 PM

Hi,
I mean B(Sub Assembly)
Item Rollup Flag
A No
--B Yes
---B1 No
---B2 No
---B3 No
--C Yes
In this case when we run cost rollup by giving item A, Oracle will consider below structure.
A
--C
Regards,
Sarvottam.

Background job not run properly

Hi,
When an infopackage is triggred through process chain in BI a background job will be exeuted at R/3 to fetch data from R/3.
But the bakground job did not execute properly hat is it did not fetch any data but ot finished.
But when the infopackage is executed manually the background job fetches the data from R/3.
Why the job is not fetching data when triggered through process chain.
Please help me to sole this issue.
Regards,
Indhu

Hi Induja,
In your case, you will have to debug the background job that is activated through BI. Check if proper data is coming from BI.
You can only debug a background job if it is created under your user id. Thus, to debug the job you first have to own it and then debug by selecting it and either typing 'JDBG' in the command field or through menus available on the top.
Job overview transaction code - SM37.
Hopefully the issue is in Development/Test/Quality system and not in Production.
Hope that helps!.
Regards,
Saba

IDM Job Not Executing

Similar Messages

Maybe you are looking for