When I schedule a Job, the job is executed twice.

Post Author: sachinddalal
CA Forum: Data Integration
Hello,
I am using Data Integrator Ver 11.0.2.22. I have scheduled the job through Admin Console. When the job is executed it seems that the job is executed twice.
On the Status tab onDI Administrator, it shows that both the jobs started at same time. The end time of bot the job is different.
Any one have any idea how this happens?
Also any way to ensure that the job are not executed twice.
Thanks,
Regards
Sachin Dalal

Post Author: bhofmans
CA Forum: Data Integration
If you get this issue for a scheduled job only, I might be that the schedule is created twice in the OS scheduler. You could check the windows task scheduler (or cron on UNIX) to check for duplicate schedules.
If you see this issue also for jobs you execute manually (via webadmin or Designer), you can have this kind of problems if the same jobserver is registered multiple times in a repository. You can check the AL_MACHINE_INFO in your repository. It should have one line for each jobserver and one line for each administrator the repo is connected too. I suspect you have some duplicates there (you can just remove them - this table gets populated when adding a repo in the web admin and when adding a repo to a jobserver in the server manager).

Similar Messages

How to schedule a job to run twice within a request set?

How to schedule a job to run twice within a request set?

Create one more stage for the same concurrent program.
Thanks
Nagamohan

Why is the last script executed twice?

Here is my problem. I have two files, file1.sql and file2.sql that are called in a third file test.sql. The output from test.sql show that file2.sql was called twice
--file1.sql
select 'file1' as str from dual;
--file2.sql
select 'file2' as str from dual;
--test.sql
@file1.sql
@file2.sql
The output shows:
STR
file1
STR
file2
STR
file2
Why is the last file execute twice. If I change the order of files in test.sql, then file1 is displayed twice

I found my problem. In test.sql I had '/' in the last line
--test.sql
@file1.sql
@file2.sql
/

C# Script to copy an Excel File working locally but not on the server when I schedule a job

So I have these couple C# commands to copy an Excel File which works fine and dandy on my local client when I test and run this SSIS Package but when I tried scheduling the job on the server, it failed.
These are the couple C# commands...
// This Opens the Source .xlsx File from Emdeon ePaySmart
Workbook workbook = excelApplication.Workbooks.Open(StringSourceFile, XlUpdateLinks.xlUpdateLinksNever, true, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing);
// This will Save the Source .xlsx Emdeon ePaySmart File as a .xls File...note xlFileFormat.xlExcel5
workbook.SaveAs(StringDestinationFile, XlFileFormat.xlExcel8, Type.Missing, Type.Missing, Type.Missing, Type.Missing, XlSaveAsAccessMode.xlExclusive, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing);
Is this because I'm using xlFileFormat.xlExcel8 and locally it is running fine but when I schedule via SQL Server Management Studio as a SQL Server Agent Job it seems to be failing??
I sure hope I don't have to change this so it will run as a SQL Server Agent Job and/or run this locally every blessed week.
Can someone clear this up for me and provide a potential solution?
Thanks for your review and am hopeful for a reply.
ITBobbyP85

That is Excel automation, which requires Excel to be installed on the computer where the code runs, and is not supported on a server without an interactive user logged in.
David
David http://blogs.msdn.com/b/dbrowne/

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

How to schedule a Job in SAP DS ?

AFAIK, a SAP data services job is an ATL (i.e XML) file/code. How do we schedule this code to run automatically ? What runs it ?
In SSIS, Job = Package and it can be scheduled as a *job* in SQL server Agent. The agent runs it as per your schedule. So,
is there some kind of server which executes the code in the ATL file ?

Hi Terry,
There are three ways you can manage batch job schedules
1. Using the job scheduler
When you schedule batch jobs using the SAP Business Objects Data Services job scheduler, it creates an entry in the operating system's scheduling utility on the Job Server computer. Windows uses the Task Scheduler and UNIX systems use the CRON utility. (Note that if you make changes to a schedule directly through these utilities, the job scheduler will not reflect those changes.)
2. Scheduling jobs in SAP Business Objects Business Intelligence platform
If you are using SAP Business Objects Business Intelligence platform and you want to manage your
SAP Business Objects Data Services job schedules in that application, first create a connection to a
Central Management Server (CMS), then configure the schedule to use that server.
3. Using a third-party scheduler
When you schedule jobs using third-party software:
• The job initiates outside of SAP Business Objects Data Services.
• The job runs from an executable batch file (or shell script for UNIX) exported from SAP Business Objects Data Services.
Note:
When a third-party scheduler invokes a job, the corresponding Job Server must be running.
Regards
M Ramesh

Scheduling a job in BI Publisher

Hi All,
Is there any configuration file in BI Publisher which I can use to schedule a job. if not can insert the scheduled job directly into database. I noticed that when I schedule a job it is inserted into QRTZ_JOB_DETAILS and also goes to XMLP_SCHED_JOB and XMLP_SCHED_SUBSCRIPTION
table. If I can directly update database, do I need to update the other two tables also or it is done through trigger ?
If I can update databse directly, what value is stored in the field JOB_DATA of the table 'QRTZ_JOB_DETAILS'.
I have another issue with scheduling as below:
I do not see the table 'QRTZ_JOB_LISTENERS' is populated when i schedule a job. What is the reason of this? Am I missing any configuration?
Thanks and Regards
Angshuman

Hi,
Any one can help me on this please?
Angshuman

Schedule a job(execute a procedure periodically)

as I explained in subject I want to schedule a job which executes a procedure without parameters on oracle managment system. Then,I schedule job as "on interval" and "1 minutes". But when I monitor the job status, there is no change. it says submitted. what is wrong, could you explain how it is with an example.
thanks.
Message was edited by:
user554973

You need to be a bit clearer on what you're monitoring. What "status" stays unchanged?
Some basics. When a job is submitted an entry is made into the Job Queue (a data dictionary table). The views DBA_JOBS, USER_JOBS and ALL_JOBS are views on this table.
When the job is to be executed, it is executed by a job queue process. There is a pool of these Job Processes that checks the job queue and execute jobs in the queue. Such a Job Process will have an entry in the V$SESSION virtual view.
To monitor the status of the actual executing job, requires you to look at the active sessions on the database and not at the job queue. Looking at the Job Queue is not looking at the actual process running and executing the job.
So what status is being looked at here? What status do you want, or do you expect to see?

Scheduled Background jobs after Client Copy

Hello,
I've been doing some searching online and I don't seem to be able to find a definitive answer to this question:
Are background jobs client specific?
I've seen some discussions on here say some are and some are not. I've also seen a discussion that says ALL background jobs are client specific.
It's really related to non-SAP background jobs after a client copy.
If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
Thanks

Hello All
If I have a client 100 in QA with half a dozen non-SAP standard jobs configured, and I create client 110 in QA and perform a remote client copy from PROD into client 110 on QA, will my non-SAP standard backgrounds run in Client 110, or do I need to set them all up again?
Yes. You will need to set those non standard jobs in the new client. When you schedule a job there will be a reference to the client where the job will be executed is stored under AUTHCKMAN in the table TBTCO. If the job is scheduled periodically then the job is executed only on the client where it is scheduled.
I used SAP_ALL profile when performing the client copy. So my scheduled jobs WILL have been copied along with everything else? Is that correct?
In SAP_ALL profile the background jobs will be coming from source client not from QA client 100.
No. Background jobs are not transportable and will not be copied during a client copy. Job definitions are client independent.
Read these SAP notes.
31503 - FAQ: Background jobs
51135 - Why are bkgd processing jobs not generally transportable?
If you want to schedule those jobs in the new client the follow the suggestion in the SAP note 3150 point 6.
Regards
RB

Schedule background jobs which run only on Thursdays.

Dear Friends,
We are using ECC6.00. I have a requirement whereby a specific job (background) should be executed only on Thursdays. I searched in this forum but couldn't get anything related to my question. I tried the options present in the SM36 transactions (scheduling options).
Is there any way of achieving my requirement.? Experts help required.
Regards,
M.M

Hi Magesh,
I am not sure if this would be the right approach. But if you are really sure that there is no way to do this using SM36 settings,
you can schedule a job to execute daily, which would be a custom abap program.
This program would check the day and if it is a thursday ,will schedule another job for the day(programatically).
This can be a way around to solve this problem.
Regards,
Sagar

Permissions needed for sql server job to execute stored procedure on linked server?

Hi all
I have a job step which attempts to call a stored procedure on a linked server.
This step is failing with a permission denied error. How can I debug or resolve this?
The job owner is sysadmin on both servers so should have execute permission to the database/proc I'm calling, right?
The error is:
The EXECUTE permission was denied on the object 'myProc', database 'myDatabase', schema 'dbo'. [SQLSTATE 42000] (Error 229). The step failed.
My code is:
EXEC [LinkedServer].myDatabase.dbo.myProc
Also tried:
SELECT * FROM OPENQUERY([LinkedServer], 'SET FMTONLY OFF EXEC myDatabase.dbo.myProc')
With the same result.
Any help appreciated.

The job owner may be sysadmin on the remote server. The service account for SQL Server Agent may not. And it is the latter that counts, since the it the service accounts that logs in and impersonates the job owner. But the impersonation inside SQL Server
does not count much in Windows, and it is through Windows connection is made to the other site.
One way to resolve this is to set up a login mapping for the job owner. The login mapping must be for an SQL login on the remote server.
You can verify the theory, but running this query from the job:
SELECT * FROM OPENQUERY([LinkedServer], 'SELECT SYSTEM_USER')
By the way, putting SET FMTONLY OFF in OPENQUERY is a terrible idea. This has the effect that the procedure is executed twice. (Unless both servers are SQL 2012 or higher in which case FMTONLY has no effect at all.)
Erland Sommarskog, SQL Server MVP, [email protected]

After Update Trigger executes twice when single row is uptd thro proc

We have the below trigger in our db. When a single record is updated using a procedure the trigger is executed twice and it inserts two records in other table.
But when i issue an update statement using any sql client tool it is executing only once and inserts only one record in other table.
Can any one please help me to find the reason?
Trigger:*
create or replace TRIGGER CX_HEADER_ESCL_T1 AFTER UPDATE OF STATUS ON CX_HEADER
FOR EACH ROW
DECLARE
"b1-CTRIYJ" boolean := FALSE;
BEGIN
IF UPDATING('STATUS') AND(:NEW.status = 'SUCCESS') THEN
"b1-CTRIYJ" := TRUE;
END IF;
IF "b1-CTRIYJ" = TRUE THEN
INSERT
INTO siebel.s_escl_req(req_id, created, bt_row_id, rule_id, tbl_name, created_by, group_id)
VALUES('11111111', CURRENT_DATE, :NEW.row_id, '1-CTRIYJ', 'CX_HEADER', :NEW.last_upd_by, '1-2CU3');
"b1-CTRIYJ" := FALSE;
END IF;
END;
Procedure:
CREATE OR REPLACE
PROCEDURE CLOSE_BATCH
(ChildRecordCount IN NUMBER, HeaderId IN VARCHAR2, CompletionStatus OUT VARCHAR2) AS
CafeChildCount NUMBER;
BEGIN
select count(*) into CafeChildCount from SIEBEL.CX_CHILD where HEADER_ID=HeaderId;
IF ChildRecordCount = CafeChildCount THEN
update SIEBEL.CX_HEADER set STATUS ='SUCCESS', MODIFICATION_NUM = MODIFICATION_NUM+1 where HEADER_ID=HeaderId;
CompletionStatus := 'SUCCESS';
ELSE
update SIEBEL.CX_CHILD set STATUS='FAILED' where HEADER_ID=HeaderId;
update SIEBEL.CX_HEADER set STATUS='FAILED' where HEADER_ID=HeaderId;
CompletionStatus := 'FAILED';
END IF;
commit;
/*CompletionStatus := 'SUCCESS';*/
EXCEPTION
WHEN OTHERS THEN
CompletionStatus := SQLCODE;
rollback;
END;

Your problem seems not be related to the trigger restart issue I have already mentioned because you are using a AFTER UPDATE trigger and not a BEFORE UPDATE trigger:
>
BEFORE Triggers Fired Multiple Times
If an UPDATE or DELETE statement detects a conflict with a concurrent UPDATE, then Oracle Database performs a transparent ROLLBACK to SAVEPOINT and restarts the update. This can occur many times before the statement completes successfully. Each time the statement is restarted, the BEFORE statement trigger is fired again. The rollback to savepoint does not undo changes to any package variables referenced in the trigger. Your package should include a counter variable to detect this situation.
>
If you are sure that you update a single row and that your trigger fires twice and if you can easiily reproduce the issue, I recommend that you contact Oracle Support and create a Service Request for your issue that could be an Oracle bug.

Job scheduling failed because the user has no permission to access this rep

Hi. I've OBIP 10.1.3.4.1.
When I launch a print with the scheduler I see this error:
oracle.apps.xdo.servlet.scheduler.ProcessingException: Job scheduling failed because the user has no permission to access this report. [REPORT_URL]=[folderreport/report/report.xdo], [USERNAME]=[administrator]
     at oracle.apps.xdo.servlet.ui.scheduler.SchedulerServlet.scheduleJob(SchedulerServlet.java:1140)
     at oracle.apps.xdo.servlet.ui.scheduler.SchedulerServlet.doPost(SchedulerServlet.java:295)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:100)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
In this env. I've a LDAP Security Model and all the report and all the users work.

Please check whether you have assigned below responsibility to the user trying to schedule report.
XMLP_SCHEDULER

DBA COCKPIT error when scheduling a job

hi experts
Iam trying to schedule some jobs in DB13 when i try to add the action i get this error:
DBA Cockpit Error
Acces to system SID failed
Function Unit DB6_PLAN_DD_BATCH
Reason job error
iam able to run these jobs externally directly from DBM.
I have checked some notes 1072066,1057855,927642 and they are all refering to MS SQL Server as the database.Iam running ERP6 on Maxdb 7.6
Any help appreciated

hi
> dbmcli inst_enum
OK
7.6.00.35    /sapdb/BT1/db
dbmcli db_enum
OK
BT1     /sapdb/BT1/db                           7.6.00.35       fast    running
BT1     /sapdb/BT1/db                           7.6.00.35       quick   offline
BT1     /sapdb/BT1/db                           7.6.00.35       slow    offline
BT1     /sapdb/BT1/db                           7.6.00.35       test    offline
xinstinfo BT1-MAXDB
IndepData           : /sapdb/data
IndepPrograms       : /sapdb/programs
Installationpath of serverdb <BT1-MAXDB> not found!
ERR 20010 RTE      Could not open file /sapdb/data/config/BT1-MAXDB for read, rc = 2
sdbregview -l
DB Analyzer         /sapdb/programs    7.6.00.35     32 bit    valid
Server Utilities    /sapdb/programs    7.6.00.35     32 bit    valid
PCR 7300            /sapdb/programs    7.3.00.55               valid
PCR 7301            /sapdb/programs    7.3.01.18               valid
PCR 7500            /sapdb/programs    7.5.00.37     32 bit    valid
SAP Utilities       /sapdb/programs    7.6.00.35     32 bit    valid
Base                /sapdb/programs    7.6.00.35     32 bit    valid
Redist Python       /sapdb/programs    7.6.00.35     32 bit    valid
JDBC                /sapdb/programs    7.6.00.30               valid
Messages            /sapdb/programs    MSG 0.3951              valid
ODBC                /sapdb/programs    7.6.00.35     32 bit    valid
Database Kernel     /sapdb/BT1/db      7.6.00.35     32 bit    valid
Loader              /sapdb/programs    7.6.00.35     32 bit    valid
SQLDBC              /sapdb/programs    7.6.00.35     32 bit    valid
SQLDBC 76           /sapdb/programs    7.6.00.35     32 bit    valid
Fastload API        /sapdb/programs    7.6.00.35     32 bit    valid
PCR 7403            /sapdb/programs    7.4.03.44     32 bit    valid
SAP Basis component SAPKB70011
db59 there are no errors log says all 4 tests successfull.

What command will be executed when I schedule job via DB13

Hi all,
How do I get what command(full syntax) will be executed when I schedule jobs via DB13?
For example:
- Action: REORG of Tables in Tablespace(s)
- Tablespaces: "WI6#BTABD" is selected
- "Use Temporary Tablespaces" is selected
I think this is a really basic question...
Could you give me some advice?
Thanks in advance,
Ikue

Hi Ikue,
yes, you won't see, what the 'REORG for all tablespaces is doing. But it's not really necessary. Its's simply always the same call
REORG TABLE <tabname> INDEX <primary key> ALLOW NO ACCESS
and optionally the addition USE <tempspace>, if you have selected this option in DB13. And it is called for each table that is located in the tablespace(s) which you have specified.
The 'REORG for set of tables' is quite new. It is available with Basis Support Package 7.0 SP12. Before there was only a job to Reorg a single table.
The REORG for flagged tables is a deprecated job.
If you want to know more about the various REORG jobs and when and how to use them, then you should look at note 431430
Best regards
Ralf

When I schedule a Job, the job is executed twice.

Similar Messages

Maybe you are looking for