WBS Scheduling procedure --

Good Morning Experts ..
Please explain me all the steps to be required in WBS scheduling at user end ..
as per me in our scenario - we are doing-
1.first of all we assign the activitis to WBS then we make the relationship between them then we scheduled them from planning board.
whenever activity is completed we confirm that from Project builder ..
is this right procedure ?
if you have some document with screen shot please provide me .
Regards

Hi Robert,
Please check the link below.
http://help.sap.com/saphelp_47x200/helpdata/en/4c/2276a246e611d189470000e829fbbd/frameset.htm
It will give you more idea on the said subject.
Regards
Tushar Vhora
P.S. Reward points for useful answer

Similar Messages

Issue with WBS scheduling

Hello everybody,
Our project structures consist of WBS elements only -no networks-. I configured the WBS scheduling profile with "scheduling type = Forwards", and "Schedul. method = WBS determines dates". I configured the project profile with "sched. scenario = Top-down scenario", "planning methods = top-down"
When I create a project, I enter a start and finish date in the project definition area. The project structure consists of 1 WBS element in the first level, and various WBS elements in the second level.
When I try to schedule this project (from the project definition area), the following message is displayed: "
There is no operation for scheduling
Message no. C71462"
I even entered the basic start and finish date in the first level WBS element and perfomed scheduling; I expected to see the start and finish date in all WBS elements, but this didn´t happen.
I appreciate your collaboration,
Nat.

Hi RAJ.
The data object J_OBJNR is a CHAR22 field and would leave open many othe possibilities. I have never seen a system with more than 1 Billion (!!!) projects though.
What happens at creation of a project or a WBS element is that an internal object number is triggered and stored in SAP memory. Especially when you do validations or substitutions at time of creation you have to read out this internal number.
Best regards.
Jens Schmid

How to schedule procedure in DBMS_JOBS?

Hi,
i have one stored procedure .. i want to schedule that procedure to run every 15 of the month at 2AM... plz help

Oracle recommends (from 10.1 onwards?) that you use DBMS_SCHEDULER instead of DBMS_JOB. DBMS_SCHEDULER provides a much richer set of features then the old DBMS_JOB does.
user2017273 wrote:
it will run every month 15th 2AM like 15-oct-2010 2AM,15-Nov-2010 2AM,....? plz confirmFor example if you were using DBMS_SCHEDULER there is a procedure called EVALUATE_CALENDAR_STRING which you can use to undeniably confirm the schedule does what you expect. For example in your case:
SQL> DECLARE
2 start_date        TIMESTAMP;
3 return_date_after TIMESTAMP;
4 next_run_date     TIMESTAMP;
5 BEGIN
6 start_date := SYSTIMESTAMP;
7 return_date_after := start_date;
8 FOR i IN 1..5 LOOP
9    DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING(
10      'FREQ=MONTHLY;BYMONTHDAY=15;BYHOUR=2;BYMINUTE=0;BYSECOND=0;',
11      start_date, return_date_after, next_run_date);
12 DBMS_OUTPUT.PUT_LINE('next_run_date: ' || next_run_date);
13 return_date_after := next_run_date;
14 END LOOP;
15 END;
16 /
next_run_date: 10/15/2010 02:00:00.100000 AM
next_run_date: 11/15/2010 02:00:00.100000 AM
next_run_date: 12/15/2010 02:00:00.100000 AM
next_run_date: 01/15/2011 02:00:00.100000 AM
next_run_date: 02/15/2011 02:00:00.100000 AM
PL/SQL procedure successfully completed.So in your case your DBMS_SCHEDULER job would look like this:
DBMS_SCHEDULER.create_job (
    job_name        => 'test_job',
    job_type        => 'PLSQL_BLOCK',
    job_action      => 'BEGIN your_procedure; END;',
    start_date      => SYSTIMESTAMP,
    repeat_interval => 'FREQ=MONTHLY;BYMONTHDAY=15;BYHOUR=2;BYMINUTE=0;BYSECOND=0;',
    end_date        => NULL,
    enabled         => TRUE,
    comments        => 'Some job to run on the 15th of every month at 2am');Hope this helps!
Edited by: Centinul on Sep 30, 2010 10:54 AM
I know you haven't identified your version, but I wanted to make the comment just in case you are on more recent versions of Oracle.

Scheduling procedure with remote db = logon denied

I´m having two DBs (db1 and db2) which are connected by a database link and a non-dba user "xyz" in both DBs.
I´m starting a procedure in db1, which catches data from a table in db2 and combines it with data from db1 - it works perfectly fine.
Now I want to automate this procedure with the scheduler, so I´m getting the privileges (GRANT CREATE JOB TO user xyz) => works perfectly fine, too.
Whats the problem?
The procedure runs in the given time interval, but I´m always getting a ORA-01017 error invalid username /password; logon denied.
If the procedure runs manuel (outside the scheduler) it works perfectly.
Do I need additional privileges or is there something wrong with the db link? (e.g. the username and pw will not be committed).
Sorry to bother you with these questions - if you need additional info, please let me know.
Regards!
forget to mention: If I´m running the scheduler with a procedure, that accesses only local table, it works...but if I try to access a remote table (which is normally outside the scheduler no problem) it doesn´t work.
Edited by: user10537960 on 08.02.2011 06:17

The mystery has been solved: the DB link was created by another user, thats why the remote connect didn´t work - now I´ve created a fully qualified link and it works :)

Troubleshooting a scheduled Procedure

Dear All,
If I schedule a procedure from my sqlplus client, I would be able to know if there were any problems the procedure has encountered while it is running ex. any runtime errors or any network issues that cause the procedure to fail...
But is there any way to know where and why a procedure got failed when I schedule it on the server? (The server is Oracle8i)
Regards
RK Veluvali
Message was edited by:
RK Veluvali

You want to run a procedure from SQLPLUS through a schedule (say crontab?) and want to know (email? logfile?) if there were any errors?
You could spool to a file before executing the procedure and check (grep?) it for errors (ORA-, TNS-, etc) for errors and email the logfile to yourself and/or write a wrapper script that calls SQLPLUS that does the same and catches any problems running SQLPLUS.
You may be better off scheduling the procedure through an anonymous PL/SQL through database control (10g) and checking errors, notifications if it fails this way. More of an out-of-the-box solution.

Problem scheduling procedure to run at 3 different times

I created the following statement to have a simple procedure to run at 3 different time.
repeat_interval => 'freq=DAILY; BYHOUR=12,13,14;',
The job runs the moment I schedule it but I did not see it kick off at the other times.
What did I do wrong and I check the time of the db
The complete scheduling statement.
begin
Dbms_Scheduler.create_job(
job_name => 'DEMO_HALL_TEST_SCHEDULE',
job_type => 'STORED_PROCEDURE',
job_action => 'HR.a_simple_subprogram',
start_date      => SYSTIMESTAMP,
repeat_interval => 'freq=DAILY; BYHOUR=12,13,14;',
enabled => TRUE,
comments => 'Demo for job schedule.');
END;
/PROCEDURE
create or replace
procedure a_simple_subprogram
is
begin
null;
end;

Hi,
you didn't set the minutes. So they are derived from the start date. Probably the job will start at some time between 12 and 13
SQL> select job_name, start_date, next_run_date, repeat_interval from user_scheduler_jobs;
JOB_NAME                       START_DATE                       NEXT_RUN_DATE                    REPEAT_INTERVAL
DEMO_HALL_TEST_SCHEDULE        03.01.13 13:09:06,873025 +01:00 03.01.13 14:09:06,600000 +01:00 freq=DAILY; BYHOUR=12,13,14;
DEMO_HALL_TEST_SCHEDULE_2      03.01.13 13:09:09,384254 +01:00 03.01.13 14:00:09,400000 +01:00 freq=DAILY; BYHOUR=12,13,14; byminute=0;Excerpt from Oracle® Database PL/SQL Packages and Types Reference, DBMS_SCHEDULER
>
Start Dates and Repeat Intervals The Scheduler retrieves the date and time from the job or schedule start date and incorporates them as defaults into the repeat_interval. For example, if the specified frequency is yearly and there is no BYMONTH or BYMONTHDAY clause in the repeat interval, then the month and day that the job runs on are retrieved from the start date. Similarly, if frequency is monthly but there is no BYMONTHDAY clause in the repeat interval, then the day of the month that the job runs on is retrieved from the start date. If present, BYHOUR, BYMINUTE, and BYSECOND defaults are also retrieved from the start date, and used if those clauses are not specified.

Schedule/procedure

Hello guys,
I´m having some trouble by running a job:
BEGIN
dbms_scheduler.create_job (
job_name=>'test_minuto', job_type => 'PLSQL_BLOCK', job_action => 'exec tempo2', start_date=> SYSTIMESTAMP, repeat_interval=> 'freq=minutely', end_date=>null, comments => 'testando 123');
END;
and the procedure tempo2 :
create procedure tempo2 as
begin
insert into armazena values ((select to_char(sysdate, 'fmDD/MM/YYYY - HH24:MI:SS ' ) horario from dual), system.seq_test.nextval);
commit;
end;
I checked the table USER_SCHEDULER_JOB_RUN_DETAILS and noticed that the job is running but its status shows 'FAILED' and its ADDITIONAL_INFO shows:
ORA-06550: line ORA-06550: line 1, column 475:
PLS-00103: Encountered the symbol "TEMPO2" when expecting one of the following:
:= . ( @ % ;
Does anyone knows what i am doing wrong ?
Thanks
Edited by: BrunoSales on 12/04/2012 09:23

BrunoSales wrote:
Hello guys,
I´m having some trouble by running a job:
BEGIN
dbms_scheduler.create_job (
job_name=>'test_minuto', job_type => 'PLSQL_BLOCK', job_action => 'exec tempo2', start_date=> SYSTIMESTAMP, repeat_interval=> 'freq=minutely', end_date=>null, comments => 'testando 123');
END;
and the procedure tempo2 :
create procedure tempo2 as
begin
insert into armazena values ((select to_char(sysdate, 'fmDD/MM/YYYY - HH24:MI:SS ' ) horario from dual), system.seq_test.nextval);
commit;
end;
Not part of your immediate problem, but why are you converting sysdate to a character string and inserting that into your table? If you want that first column of table ARMAZENA to have a date, then it should be declared a DATE and you just insert sysdate:
insert into armazena values (sysdate horario, system.seq_test.nextval);And it is pointless to put a column alias on that, so we can reduce it even further
insert into armazena values (sysdate, system.seq_test.nextval);And you should NEVER put user defined objects into the SYSTEM schema, so should be
insert into armazena values (sysdate, appschema.seq_test.nextval);>
I checked the table USER_SCHEDULER_JOB_RUN_DETAILS and noticed that the job is running but its status shows 'FAILED' and its ADDITIONAL_INFO shows:
ORA-06550: line ORA-06550: line 1, column 475:
PLS-00103: Encountered the symbol "TEMPO2" when expecting one of the following:
:= . ( @ % ;
Does anyone knows what i am doing wrong ?
Thanks
Edited by: BrunoSales on 12/04/2012 09:23

WBS Forecast dates disappears during scheduling after final confirmation

Hi dear Experts.I faced a problem with WBS dates.
The system overwrites forecast and basic dates on WBS after final confirmation of attached activities. And start to schedule wbs dates from dates of activities with no confirmation. Is there any way to solve this prolem?
In other words i need my WBS to take into scheduling ALL the operations forecast date. Moreover how the system can overwrite the forecast dates wich were entered manually by user?
Green - actual dates
Yellow (orange) - forecast dates
Bue - Basic dates
Please help.

Hi Kirill,
Please check the control parameters for WBS Scheduling. Check if the scheduling method over here is WBS Determines Dates. If this is the case, irrespective of the scheduling that was carried out at the activity level, the system overwrites the basic and forecast dates present at the WBS level. May be in your case the scheduling method that had been used was "Network determines dates".
. Please change this and let me know if this helps.
Regards
Varun

Script to schedule a procedure

hii,
i want the script to execute a procedure on daily basis at a particular time(at 10pm daily).my data base version is 9.2.0.6.0.
How i can check wheather my scheduled procedure is executed or not

Hi,
In addition, pay attention about possible job execution failures.
Scheduled jobs
SELECT job, next_date, next_sec, failures, broken FROM dba_jobs;
JOB   NEXT_DATE NEXT_SEC FAILURES B
14144 24-OCT-02 16:35:35 0        N
41762 01-JAN-00 00:00:00 16 Y
2 rows selected.
Jobs currently in execution
SELECT sid, r.job, log_user, r.this_date, r.this_sec
FROM dba_jobs_running r, dba_jobs j
WHERE r.job = j.job;
SID   JOB        LOG_USER      THIS_DATE THIS_SEC
25    341        SCOTT         24/04/03 16:45:12
1 rows selected.Cheers

How to schedule macros to open a report , refresh and update database?

Hi,
We have the below set of steps that work on a deski environment. It works fine on XI R3.1 Fix pack 1.5, but I am unable to schedule and get the macros to run although i've included the entire macros code in - Private Sub DocumentAfterRefresh()
Refresh of report
Step 1 : Report is Refreshed. Refreshed data contains 10 Report Names to be opened by the Macros and the prompt values that these reports need to be refreshed with.
Macros Functionality:
Step 1 : Opens 1st report of the 10 reports from the repository in deski thick client, updates the database by setting a flag on the processing to Y or N for the report being processed.
Step 2 : Refreshes the report with the prompt values obtained from the first refresh in the report, saves the refreshed data to a CSV or PDF at a location.
Step 3 : Updates the database if the report has been genrated or not and then deletes the local copy of the output csv and pdf.
The above steps repeat over and over again until all 10 reports open up, get refreshed and update the database.
Now all of this works on Deski thick client/refresh and macros.
However, when i schedule it, the macros doesnot seem to be running.
Is the above scenario even possible to replicate via a schedule process..?
Note : The reports need to be retained in Deski itself.
PLz help...!

Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
Call Transaction SM36 or choose CCMS ® Jobs ® Definition .
Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
Set the jobs priority, or "Job Class":
High priority: Class A
Medium priority: Class B
Low priority: Class C
In the Target server field, indicate whether to use system load balancing.
For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
To use a particular application server to run the job, enter a specific target server.
If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
Save the fully defined job to submit it to the background processing system.
When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
For a simple job scheduling procedure, see the R/3 Getting Started Guide.

DBMS scheduler jobs running twice

Hi,
I have 4 DBMS scheduler jobs , which checks for a specific job status in DB and sends an email , when i started the schedule for the first week the jobs executed fine from next week I am getting two emails from each job , when i check the logs USER_SCHEDULER_JOB_RUN_DETAILS I see only one run , which seems weird to me so i disabled one job and left the three jobs in schedule , next time i got two emails from 3 jobs and one from disabled job . After checking logs i see that there is no entry of the disabled job execution . I am not sure where is the problem i can't find any log from where the disabled job executing. Please help me
Job schedule is to run every Saturday
Interval setup :
start_date => trunc(SYSDATE)+ 8.5/24,
repeat_interval => 'TRUNC(LEAST(NEXT_DAY(SYSDATE,''SATURDAY'') )) + 8.5/24'
Suresh

Hi,
I tried to schedule the same jobs using DBMS_JOB but i still get the same problem , I created the procedure with all code in and scheduled it using dbms job , first day it run once second day it run twice ( sending two emails) Inow i am not sure if issue is with my code or scheduler
Procedure
Declare
v_count number;
v_Recipient VARCHAR2(400) := '[email protected]';
v_Subject VARCHAR2(80) := 'TEST_Email';
v_Mail_Host VARCHAR2(30) := 'localhost';
v_Mail_Conn utl_smtp.Connection;
crlf VARCHAR2(2) := chr(13)||chr(10);
BEGIN
select count(*) into v_count from TEC_CODERETURN@RPRD where interface like 'FOR002B' and trunc(rundate) =trunc(sysdate);
if v_count = 0
then
v_Mail_Conn := utl_smtp.Open_Connection(v_Mail_Host, 25);
utl_smtp.Rcpt(v_Mail_Conn, '[email protected]');
UTL_SMTP.OPEN_DATA(v_Mail_Conn);
utl_smtp.WRITE_RAW_DATA(v_Mail_Conn, UTL_RAW.CAST_TO_RAW(
'Date: ' || to_char(sysdate, 'Dy, DD Mon YYYY hh24:mi:ss') || UTL_TCP.CRLF ||
'From: ' || '[email protected]' || UTL_TCP.CRLF ||
'Subject: '|| v_Subject || UTL_TCP.CRLF ||
'To: ' || v_Recipient || UTL_TCP.CRLF ||
'This is a test Alert'|| UTL_TCP.CRLF
UTL_SMTP.CLOSE_DATA(v_mail_conn);
utl_smtp.Quit(v_mail_conn);
end if;
EXCEPTION
WHEN utl_smtp.Transient_Error OR utl_smtp.Permanent_Error then
raise_application_error(-20000, 'Unable to send mail: '||sqlerrm);
END;
DBMS job creation
DECLARE
jobno NUMBER;
BEGIN
DBMS_JOB.submit
(job => jobno,
what => 'TEST_ALERT;',
next_date => trunc(sysdate)+0.1/24,
interval => 'SYSDATE + 1',
no_parse => TRUE );
DBMS_OUTPUT.put_line ('Created Job - the job number is:' || TO_CHAR (jobno));
COMMIT;
END;
Suresh

Calculation of start date with backward scheduling

Dear all,
I am facing an issue related to backward scheduling. I have requirement in which whenever backward scheduling is used, system should calculate from last activity to first for calculation of schedules which is fine. But when running scheduling i am giving finish date as input and system is always using start date as current date and not calculation last date from last. For example if i input finish date as 15 feb 2015, and there is only one activity of 15 days, system should count start date from 1 feb 2015. Please help me how i can achieve this, currently its always putting start date as current date.
My current settings are--
Project definition- WBS Scheduling profile- Backward scheduling
                              scheduling scenario- Free scheduling
Network-      Planning type- basic dates
                    Scheduling type- Backward
Please help.
Thanks

Dear all, this issue is resloved. Reason was that by default i am using forward scheduling for all project but in case of backward scheduling, user change schedule type at project definition and network. I was removing start date and putting finish date and running scheduling. Missing step from my side was i need to first copy date from top to down than run scheduling again.
Thanks.

Discoverer 3.1.25: getting error ORA-06550 when scheduling report

Hello,
we are still using the Discoverer version 3 (release 3.1.25). I know that this version is out of support, but that doesn't harm use from using it...
The Discoverer has been working fine for the last couple years. At the beginning of every month the same already defined reports are getting generated. But with the beginning of the year 2010 we are getting the error:
ORA-06550: line 1, column 93:
PLS-00201: identifier 'EUL$BATCH_PACKAGE0100112082923.RUN' must be declared
ORA-06550: line 1, column 93:
PL/SQL: Statement ignored
ORA-06512: at "SYS.DBMS_JOB" line 79
The numbers "0100112082923" after the identifier "EUL$BATCH_PACKAGE" specify the date and time:
082923: 08 hour, 29 minutes, 23 seconds
0100112: 010 year, 01 month, 12 day
The reason of that error is that the mentioned Package/Packagebody EUL$BATCH_PACKAGE*0*100112082923 doesn't exist in the database. But as a matter of fact the Package/Packagebody 'EUL$BATCH_PACKAGE100112082923 does exist. The Discoverer creates the Package/Packagebody without the "0" after the identifier "EUL$BATCH_PACKAGE" in the database, but wants to use the Package/Packagebody with the "0" after the identifier "EUL$BATCH_PACKAGE". Seems like a bug to me - does anybody have the same problem?
Until the year 2009 the year was specified with just two digits (09) - now the year seems to get specified with 3 digits (010) - but in the database just two digits are used. Is there any property table or button where this gets defined?
Any help will be appreciated!

Seems like if I have found the bug by myself...
In the procedure SubmitJob(...) of the package EUL$BATCH_REPOSITORY the name of the scheduled procedure gets generated with the hardcoded string
"EUL$BATCH_PACKAGE0". The zero after "PACKAGE" is only correct when the year ends with one digit (e.g. 2001, 2002, ..., 2009). When shortening the
string to "EUL$BATCH_PACKAGE" everything works fine again...
Rgds

How to schedule another program by giving report name and variant name?

I want to create a program for Scheduling another program using function 'FASU_V_CREATE_VARIANT_RFC'
(FASU_V_CREATE_VARIANT_RFC : This function used for creating the variant ) by giving
1) Report name
2) varaint name
Could anybody please help me.??

Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
Call Transaction SM36 or choose CCMS ® Jobs ® Definition .
Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
Set the jobs priority, or "Job Class":
High priority: Class A
Medium priority: Class B
Low priority: Class C
In the Target server field, indicate whether to use system load balancing.
For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
To use a particular application server to run the job, enter a specific target server.
If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
Save the fully defined job to submit it to the background processing system.
When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
For a simple job scheduling procedure, see the R/3 Getting Started Guide.

DBMS_schedular.create_job procedure

HI ,
I am trying write a scheduler for one of the Pl/SQL package...
Here is the package i m trying to schedule...This works absolutely fine
--- Spec
create or replace package my_pack
as
begin
procedure common_proc(var_num number);
end;
--- Body
create or replace package body my_pack
as
procedure insert_tbl1(v_num number)
   is
    begin
       insert into tbl1 values (....)
          select ....from src_tbl where col1 = v_num and ...and...;
   end;
   procedure insert_tbl2(v_num number)
    is
    begin
       insert into tbl2 values (....)
          select ....from src_tb1 where col1 = v_num and ...and...;
   end;
   procedure insert_tbl3(v_num number)
    is
    begin
       insert into tbl3 values (....)
          select ....from src_tb1 where col1 = v_num and ...and...;
   end;
   procedure insert_tbl4(v_num number)
    is
    begin
       insert into tbl4 values (....)
          select ....from src_tb1 where col1 = v_num and ...and...;
   end;
procedure common_proc(var_num number )
as
   begin
        insert_tbl1(var_num);
        insert_tbl2(var_num);
        insert_tbl3(var_num);
        insert_tbl4(var_num);
   end;
end my_pack;
Here is the procedure for scheduling the above package...
create or replace procedure schedule(s_num in number )
     as
   var_1 varchar2; -- sqlstr
   var_2 varchar2; -- v_jobn
   begin
     var_1 := 'my_pack.common_proc('''||s_num||''');';
     dbms_output.put_line(var_1);
     var_2 := 'my_pack_'||to_char(s_num);
     dbms_output.put_line('job name :'||var_2);
     dbms_schedular.create_job(
                                   job_name => var_2
                                  ,job_type => 'PLSQL_BLOCK'
                                  ,job_action => 'begin '||var_1||' end; '
                                  ,start_date => NULL
                                  ,repeat_interval => NULL
                                  ,enabled => TRUE
                                  ,comments => null
                                  ,auto_drop => TRUE
   exception
     when others then
     raise;
   end schedule;
When i compile the above schedule procedure, i get the following error
   PLS-00201: identifier 'DBMS_SCHEDULER' must be declared
ANy idea why ???Next question,
- how would i test this scheduler?? do i need to run the procedure with passing the parameter or how would i know whether schedular is kicked off or running or any place i can i see the logs ???
- If you have any idea of making this procedure schedule to write in a efficient way, please feel free to suggest me
last thing, i m tottally new to schedular, this is the first time i m using it..
Your suggestions or advice or help is greatly appriciated!!!
thank you so much !!!

I think you are missing the privileges.
GRANT CREATE JOB,MANAGE SCHEDULER to <user>;
They have explained scheduler here : http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#i1000363
Since you are setting the start_date to null, the job will be executed as soon as it gets created.
You can check the status of the run by:
SELECT * FROM USER_SCHEDULER_JOB_RUN_DETAILS
WHERE job_name = <>
ORDER BY log_Date DESC;
You can see the running jobs by:
select job_name
, session_id
, running_instance
, elapsed_time
, cpu_used
from USER_SCHEDULER_RUNNING_JOBS;
Note that there are "DBA" counterparts of these tables too.

WBS Scheduling procedure --

Similar Messages

Maybe you are looking for