Executing Scheduled jobs via Control Centre

Hello Forum,
We have a question on the scheduled jobs in OWB. We have some process flows that are attached to some (corresponding) schedules. Now in the Control Centre, we have two options to get the scheduled jobs executed:
1. We can have the scheduled jobs deployed, but not started, in which case the scheduled jobs would run as our Repository Owner (say OWB).
2. We can have the scheduled jobs deployed AND started, in which case the scheduled jobs would run as OWF (Oracle Workflow User).
(Just to clarify - by "starting" a scheduled job we mean that we make use of the "Start" option available in the right-click menu for every scheduled job that appears under the "Scheduled Jobs" node in the Control Centre.)
We would like to understand what is the advantage/disadvantage of setting up the scheduled jobs (for execution) for the two cases described above.
Any help is much appreciated.
Best Regards,
Piyush
For reference, following is our environment info:
OWB Client Version - 10.2.0.1.31
Repository Version - 10.2.0.1.0
Database Version - 10.2.0.3.0
OWF Version - 2.6.4
-----------------------------------------------------------------------------------------

Hi Sam,
Thanks a lot for your kind inputs. Well the situation that I have at hand is that when I don't "start" the schedules (as in Case 1. described in my earlier post), everything goes fine. However, if I "start" the schedules jobs (as in Case 2. described in my earlier post), the scheduled jobs failed to execute after DB restart. So I feel we are better off by not starting the scheduled jobs so as to make them run as our target workflow user.
Do you think this is the right approach for executing the scheduled jobs?
Best Regards,
Piyush

Similar Messages

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

Executing a Job via Web Services using a Server Group?

When executing a job from Designer or from the Management Console you have the option to select a specific job server or a server group.
But when executing a job via Web Services it uses the first job server with which the repository was associated (i.e. the first job server listed in AL_MACHINE_INFO).
Is there a way to get the job to execute using a server group instead simply choosing the first job server in the list?
Note: We are using FIM to execute the jobs via web services and don't have access to additional parameters.

Joe
Here is the where you can change the server group/job server.
- After you add the Batch/real Time job as a webservice.
- Go to the Webservice Batch Job Attribute and from the drop down choose the "Enable job Attributes" and hit apply.
- After this if you use the WSDL URL http://<Data Services Web Server>:<Web server Port>/DataServices/servlet/webservices?ver=2.0&wsdlxml
- You will see the job attributes that you can change based on the allowed parameters mentioned in the documentation.
The batch job or real time job is published without the job parameters by default. Once you enable the job attributes, remove and re publish the batch job as a web service. The application making the call to this webservice should be able to read the WSDL generated by Data services and pickup all the input and output parameters of the method.
Refer to the Data Services Integrator guide (Chapter 3 : pages 25 - 33 ) to get the exact parameter values permitted via Data Services jobs called via web services.
Hope this helps!
Thanks & Regards
Tiji

TS1559 i can turn on wifi via control centre but not via wifi menu (greyed out)as ive restored my phone i cant now enter my wifi password

wifi greyed out but can turn on via control centre but now cant entre wifi passwords as i restored my phone

I would try a restore, but more than likely this is hardware.
I would call apple, and i hope you're covered under warranty because it sounds like your wifi module is no good.

Scheduling jobs via DBMS_JOB

Hi,
Can anyone please help me to schedule a job via DBMS_JOB.
I have to execute a procedure p_upload_data from Tuesday to saturday at 1:00 AM.
Please provide me the code that i can use.
Thanks

cofusracle wrote:
Can anyone please help me to schedule a job via DBMS_JOB.Have a look at the Oracle® Database PL/SQL Packages and Types Reference manual
I have to execute a procedure p_upload_data from Tuesday to saturday at 1:00 AM.
Please provide me the code that i can use.Scheduling a job is as easy as follows:
declare
j number;
begin
DBMS_JOB.Sumbit(
    job => j, --// job id created for the job in USER_JOBS
    what => 'P_Upload_Data;', --// PL/SQL code block scheduled for execution
    next_date => sysdate, --// when to start executing the job (e.g. immediate)
    interval => 'trunc(sysdate+1)' --// function to use to calculate when next to execute the job (midnight each day)
commit; --// the DBMS_JOB package updates the SYS.JOB$ table and changes need to be comitted
end;I leave the interval calculation up to you to figure out.

How to remove scheduled jobs from Control Center?

Hi,
My control center shows a bunch of jobs in the "scheduled" tab that no longer exist.
They do not exist in Control Center and they also do not exist in the Design Center anymore.
Is there a way I can delete entries from the list of schedule jobs?
I am on OWB 10gR2
Thanks,
Sam
PS, I saw this thread that talks about my problem. However the solution provided seems to only work if the jobs still exist
in your control and design centers.
OWB 11g Control Centre, Want to Remove Schedule Jobs list

Could it be that some process flows are still attached to a schedule? Perhaps you've made a copy of a Process Flow?

Error while executing a job via dbacockpit

Hi,
I encountered the below errores while trying to execute a dba job (cleanup log, backup redo log...)
What could be the cause ? Could it be the SAPPROD_00 windows service that's not working ?
Please advise. TIA !
SAP-Basis System: Operating system call        connect failed (error no. 10061)
SAP-Basis System: Communication error, CPIC return code 017, SAP return code 236
SAP-Basis System: > CPI-C function: CMINIT(SAP)
Background processing: Error1005 when executing external command brconnect on SAPXPG_DBDEST_BELLSERVER (in=R,out=M,err=M,trc=0,trm=C. strtstat=,xpgid=0,convid=. msg:Error when openi                                               )

Hi,
If CI & DB are on different host this error normally occures.SAP return codes 236 means no connection to gateway, can you check it?
Also check whether TCP/IP RFC connection SAPXPG_DBDEST_* is working fine or not.If it is not working fine then please check whether you have mentioned below details
Program              sapxpg
Target Host          DB Host name
Gateway Host    DB host/gateway host
Gateway service sapgw##
Also refer SAP Note 108777 - CCMS: Message 'SAPXPG failed for BRTOOLS' & Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13
Hope this helps.
Thanks,
Sushil

Who should schedule jobs via DBMS_SCHEDULER; Sys or Apps user ?

Oracle Version: 11.2.0.3 on RHEL 5.4
We need to schedule running few Stored Procs in an Apps schema using DBMS_SCHEDULER.
Should this be scheduled by Sys or Apps user ? If its Apps user I need to grant execute privilege on DBMS_SCHEDULER to the apps user and I want to know if this is a good practise ?

Yes, you should use the apps account with execute on DBMS_SCHEDULER.
SYS should not be used unless it is absolutely required -- e.g. makes use of SYS calls that are not available to other database accounts.
Hemant K Chitale

OWB 11g Control Centre, Want to Remove Schedule Jobs list

I am having a problem to deleting the list of Schedule Jobs in Control Centre which are not required any more. The Schedule has been disabled but unable to remove them from control centre, How we can achieve that.
Thanks

Hi,
the first remove sheduled records from target database via deployment with Deploy Action = Drop.
Then clear (unset) configuration property Referred Calendar on mapping/processflow (corresponding to scheduled job) - click on checkbos None.
Usually job has name in format <object name>_JOB (where <object name> - name of scheduled mapping or processflow)
Regards,
Oleg

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

Empty "scheduled jobs" list in control center

Hi all,
due to a move to a new data warehouse environment i added a new configuration
to my OWB project with new locations, control center etc.
I was able to deploy and run all of the owb stuff into the new environment except all
the scheduled jobs to deploy into OEM,
which owb generates for all the process flows that have a schedule assigned ("Referred Calendar" in Configuration).
The list of "Scheduled Jobs" in control center for the target location just appears empty.
Are there any additional settings or privileges missings,
i.e. for target location, owb repository owner, configuration, location, ...?
Old env is Oracle DB 10.2.0.2 on Win Server 2003 32 bit, Workflow Server 2.6.4, OWB Client 10.2.0.1.31, OWB-Repository 10.2.0.1.0.
New env is Oracle DB 10.2.0.2 on Redhat 64 bit, Workflow Server 2.6.4, OWB Client 10.2.0.1.31, OWB-Repository 10.2.0.1.0.
Any hints would be appreciated.
Thanks,
Matthias

Hi,
I found out that I have to create a new schedule module.
In the create module wizard you'll have to define a location where schedules
are deployed to and there I defined the new target location.
It is not possible to assign different deployment locations for same schedule
module in each configuration.
I don't know if it is a bug or a feature, but with the new seperate schedule module
it works.
Just to let you know,
Matthias

DBMS SCHEDULER JOB failed

Hi,
I have created a dbms job as shown below for export backup, It was running fine on 10g. Recently I upgraded my database to 11g. since then that job is failing. Below is the error i am receiving while executing the job via toad as it is not getting triggered on time. If any 1 faced such issue kidly suggest.
BEGIN
SYS.DBMS_SCHEDULER.RUN_JOB
(job_name => 'SYS.EXPORT_DATAPUMP_JOB1'
,use_current_session => TRUE);
END;
Error at line 2
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
ORA-06512: at "SYS.DBMS_ISCHED", line 185
ORA-06512: at "SYS.DBMS_SCHEDULER", line 486
ORA-06512: at line 2

Hi,
Please find the output
SQL> SELECT additional_info FROM DBA_SCHEDULER_JOB_RUN_DETAILS WHERE job_name='EXPORT
ADDITIONAL_INFO
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ADDITIONAL_INFO
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
ADDITIONAL_INFO
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
ADDITIONAL_INFO
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ADDITIONAL_INFO
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ADDITIONAL_INFO
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
ADDITIONAL_INFO
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
ADDITIONAL_INFO
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ADDITIONAL_INFO
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ADDITIONAL_INFO
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
ADDITIONAL_INFO
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."
ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
ADDITIONAL_INFO
STANDARD_ERROR="'expdp' is not recognized as an internal or external command,
operable program or batch file."

How to Schedule Job using Database Control for SQLPLUS script?

Hi All,
I am using Database version 10.2. I would like to schedule a SQLPLUS script job using Database control (Not using Grid Control!). The following is the script.
========================================================
define OEM_FRIENDLY=1
define OWB_BACKGROUND=0
set serveroutput on
set verify off
whenever sqlerror exit failure;
define REPOS_OWNER='&1.'
define LOCATION_NAME='&2.'
define TASK_TYPE='&3.'
define TASK_NAME='&4.'
define SYSTEM_PARAMS='&5.'
define CUSTOM_PARAMS='&6.'
alter session set current_schema = &REPOS_OWNER.;
set role owb_d_&REPOS_OWNER., owb_o_&REPOS_OWNER.;
variable exec_return_code number;
begin
-- Initialize Return Code
:exec_return_code := wb_rt_api_exec.RESULT_FAILURE;
-- Run Task
:exec_return_code := wb_rt_api_exec.run_task('&LOCATION_NAME.',
'&TASK_TYPE.',
'&TASK_NAME.',
'&CUSTOM_PARAMS.',
'&SYSTEM_PARAMS.',
&OEM_FRIENDLY.,
&OWB_BACKGROUND.);
end;
exit :exec_return_code;
===========================================================
Is it possible to schedule SQLPLUS script with 6 different parameters? If yes then how can I schedule for monday to friday or only for Saturday and sundays.
Please provide brief steps.
Thanks for your help in advance.
- Mehul

Let me explain to you about scheduler.
You can schedule a pl/sql stored procedure TEST_S as follows...
Begin
dbms_scheduler.create_job(
job_name=>'MY_JOB',
Job_Type=>'STORED_PROCEDURE',
job_action=>'TEST_S',
start_date=>sysdate,
repeat_interval=>'freq=monthly;BYDAY=MON,TUE,WED,THU,FRI',
end_date=>null');
END;
You can also also execute o/s script like .bat or .sh. For this job type should be EXECUTABLE.
Example of converting a .sql script in .bat script...
insert.sql
insert into dept values(50,'IT','LONDON');
exit
insert.bat
sqlplus scott/tiger @insert.sql
Executing now...
C:\Documents and Settings>insert.bat
C:\Documents and Settings>sqlplus scott/tiger @insert.sql
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Mar 1 08:01:00 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
1 row created.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - P
oduction
With the Partitioning, OLAP and Data Mining options
C:\Documents and Settings>
So first read about DBMS_SCHEDULER and do the work in prompt. Then you can go and schedule it even by database control.
Scheduling by database control...
http://www.oracle.com/technology/oramag/oracle/04-jul/o44tech_dba.html
Scheduler
http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#CIHEHDHA
PS: By default each job you created is disable state. Please enable it by enable procedure of DBMS_SCHEDULER package.

Error when scheduling job (JOB_SUBMIT) when execute PC in WAD

Dear BIers,
I execute a Process Chain in commond button of WAD, however, I got the error message:
Job BI_PROCESS_DTP_LOAD could not be scheduled. Termination with returncode 8
Returncode '8' means ' Error when scheduling job (JOB_SUBMIT).
Any suggestions are appreciated.
B.R
Gerald

Dear Raju,
Have you checked SM21? Maybe you have a problem with your TemSe object. If this is the case a basis guy should know how to handle it.
Greetings,
Stefan

Control Center status running scheduled jobs stops when DB is shutdown

I have scheduled jobs in the Control Center of OWB, and the status is "Running" (Green Arrow ->), but everytime we stop and start the database I have to start the schedule job again under Status.
Is there any way to fix this so that when the database stops and restarts somebody does not have to go into the Control Center and restart the jobs that are scheduled?
Thanks

I'm been told that it's a bug in the current version of OWB and to fix this problem we should upgrade to 10.2.0.3.

Executing Scheduled jobs via Control Centre

Similar Messages

Maybe you are looking for