Sysdate in Schedule

Hello!
I have a problem scheduling my reports. I need YTD and other time comparisons, and use simple DECODE function like this one to achive this:
SUM(DECODE(TO_CHAR(sales_date,'YYYY'),TO_CHAR(CURRENT_DATE,'YYYY'),sales_amount,0))
If I don't Schedule the report, it turns out OK. Whenever I schedule the report using DECODE function with current_date(sysdate), results in scheduled report (like there exists some special SCHEDULE SYSDATE) are one year behind. Where can I configure this date in Discoverer or what is the solution?
Thx Gorazd

I'm adding some new conclusions, if this helps to clear my problem.
I have made some new tests, and I found out that the sysdate in mentioned calculation is not a problem:
I have 3 similar calculations in report using DECODE for time comparisions and planned sales.
sales_current_year:
SUM(DECODE(TO_CHAR(sales_date,'YYYY'),TO_CHAR(CURRENT_DATE,'YYYY'),sales_amount,0))
sales_previous_year:
SUM(DECODE(SIGN(Datum Racuna-ADD_MONTHS(TRUNC(SYSDATE,'YYYY'),-12)),-1,0,DECODE(SIGN(Datum Racuna-ADD_MONTHS(LAST_DAY(SYSDATE),-12)),1,0,sales_amount)))
sales_plan:
SUM(DECODE(TO_CHAR(sales_date,'YYYY'),TO_CHAR(CURRENT_DATE,'YYYY'),planned_amount,0))
And I found out that in Scheduled report Discoverer somehow ''mix-up'' names of the columns with coresponding results. So under label for calculation1 I get results of calculation2.
Have anybody else found anything similar using Discoverer? Should I upgrade or what is the solution?
The same happen in Desktop and Plus:
Discoverer Desktop version: 9.0.4.00.00
Oracle Application Server Discoverer 10g (9.0.4.00.00)
Oracle Application Server Discoverer Plus 10g (9.0.4.43.15)
Thx Gorazd Firm

Similar Messages

Simple Scheduling Question

I have a report that takes always Sunday date parameter. If I schedule the report to run every Wednesday with the previous Sunday date parameter, will the date parameter automatically update every week? I am hoping it does. If it does not, how does one go about getting the date parameter to update automatically?
Thanks in advance.

HareshM,
To answer your question, I don't think BI Pub can do this.
I have 2 ideas for you:
1) Modify your SQL so that you can either pass in a date or not. This way the users can pass in a date they choose from the calendar popup window. In the scheduled screen, schedule the report without any date value.
Example SQL:
SELECT *
FROM table x
WHERE ((:p_date IS NOT NULL AND
TRUNC(x.date) = TRUNC(:p_date)) OR
(:p_date IS NULL AND
TRUNC(x.date) = TRUNC(SYSDATE, 'DAY')))
2) If you want the flexibility for your users to pick any date from the popup calendar, then have this date passed to your SQL so that your SQL will use the previous Sunday from this passed in date and the ability to have this same exact report run atuomatically every Wednesday, then this is my idea:
Create 2 reports that are exactly the same. Allow the users to "see" 1 of the 2 reports so they can pass in any date they want. Do not allow the users to "see" the other report. Modify the WHERE clause in the SQL in this 2nd report to programmically select Sunday based off of SYSDATE. Schedule this report to run every Wednesday.
Personally, I like idea #1 above. "Simple is best".
Good luck,
James

Time Estimate for creating a new Discoverer Report

Hi,
Can anyone tell me how to estimate time required to create a new Discoverer Report?
It would be great if anyone give me a template / tool for calculating the time estimate..I know, its a manager's job, but I am supposed to give this time estimate for a report.
The requirement is, to convert Apps standard Invoice Aging Report into Discoverer Report. As far as I know, this is much complex report in Apps.
Thanks!
Yogini

Hi Yogini,
I’ve just looked at the ‘Invoice Aging Report’, and it shouldn’t be too difficult to convert into a Discoverer Report.
The time scales really depend on the following:
-whether the Discoverer Report has been fully spec’d out by the customer.
Sometimes it’s not a matter of just copying a standard Apps report into Discoverer, as they can always be improved on. It’s best to get the customer to specify exactly what they want on paper first, such as any additional columns, sorts, what parameters etc. Creating a ‘Discoverer Business Requirement Form’ could come in handy, to capture all of this information from the customer, hopefully avoiding them giving you the run around.
-if the EUL has all the required items for the report
An item required in the report might not exist in the EUL. If this is the case, do you need to go through Change Control to get it put in? How long would this take?
-how quickly can get the report into a TEST instance for the customer to test before signing off the change to go in LIVE. Sometimes Customers can hold this process up, so give yourself a couple of days.
So the time you give really depends on how comfortable you feel with the module (AP) and the actual creation of Discoverer Reports. It obviously also depends on your business processes which can always slow things down.
As for the report, I’ve actually made a report very similar for the Transactions Age Debt (AR). It could help you a bit.
To calculate the Days Overdue you could use a Calculation below:
SYSDATE-Payment Schedules.Due Date
To calculate the 1 - 30 Days you could use a Calculation with a case statement below.
CASE WHEN Days Overdue BETWEEN 0 AND 30 THEN Balance Due ELSE TO_NUMBER(NULL) END
Otherwise no Time Estimated Calculation form… But hope the info will help.
Cheers,
Lance

SYSDATE is not getting incremented in the parameter - Scheduler

Hi All
I have used the query 'SELECT SYSDATE FROM DUAL' for a parameter in concurrent request. If I execute this concurrent as a single request, then it returns exact sysdate (current date) in a parameter.
If i schedule this program for daily execution using scheduler, then the sysdate is always giving value of the date when i have configured the scheduler (even I have enabled the check box increment date parameters each run).
For example,
My Requirement :The scheduler configured such a way that it should run everyday.Whenever it runs my query has to return the current date.
Current Issue: I schedule the scheduler on 23-Dec-2008. If it runs on 24-DEC-2008,it returns as '23-DEC-2008', If it runs on 28-DEC-2008 also,it returns as '23-DEC-2008.However If I execute this as a single request, it works fine.
Can anyone help me please,,It is very urgent.
Thanks in Advance

Hi,
This forum is dedicated to the Oracle Scheduler which uses the dbms_scheduler package.
It looks like you might be using a different scheduler since the Oracle Scheduler does not allow using a query as a parameter and does not have an "increment date parameters" checkbox.
If you are using the Oracle Applications Scheduler, you should ask this question on the Applications forum here
http://forums.oracle.com/forums/category.jspa?categoryID=3
If you are using the Enterprise Manager Scheduler you should ask on the Grid Control forum here
Enterprise Manager
If you are using the Oracle Scheduler you should post the code being used to create your job which may be found by using the "Show SQL" button on the create job webpage. This should include a call to dbms_scheduler.create_job .
Thanks,
Ravi.

How to set a parameter to sysdate() - 1 in the scheduler?

Hi,
I have a report with two parameters. One is the date and in the parameter's definition I have set it to {$SYSDATE()-1$} which works perfectly.
However, when I try to schedule the report, it does not accept the default above.
How can I schedule a report with one parameter defined and the other defaulting to sysdate() or sysdate() - 1?
Thanks for the help.

The easiest way would be to include sysdate (or sysdate - 1) in your data def. and then pass it in the xml data to the format template.
I try to keep all my data def (even sysdate) out of the format templates.
Scott

(Urgent) Sysdate issue in Oracle applications scheduler.

Hi All
I have used the query 'SELECT SYSDATE FROM DUAL' for a parameter in concurrent request. If I execute this concurrent as a single request, then it returns exact sysdate (current date) in a parameter.
If i schedule this program for daily execution using scheduler, then the sysdate is always giving value of the date when i have configured the scheduler.
For example,
My Requirement :The scheduler configured such a way that it should run everyday.Whenever it runs my query has to return the current date.
Current Issue: I schedule the scheduler on 23-Dec-2008. If it runs on 24-DEC-2008,it returns as '23-DEC-2008', If it runs on 28-DEC-2008 also,it returns as '23-DEC-2008.However If I execute this as a single request, it works fine.
Can anyone help me please,,It is very urgent.
Thanks in Advance

Hi,
I can confirm that this does work properly on 11.1.0.6 . Here is the code I used
-- create a table for output
create table job_output (log_date timestamp with time zone,
        output varchar2(4000));
begin
dbms_scheduler.create_job (
    job_name => 'myjob',job_type => 'plsql_block',
    job_action =>
'insert into job_output values(systimestamp, ''myjob runs'');',
    repeat_interval=>'freq=minutely',
    number_of_arguments => 0, enabled => true);
end;
exec dbms_lock.sleep(130);
select * from job_output order by log_date ;The table job_output clearly shows dates increasing by one minute every run. If you use "freq=daily" instead then the job will run once a day instead of once a minute.
Does this example work for you ? If not could you post output from the job_output table and tell us what version database you are using.
Thanks,
Ravi.

How to stop scheduled ship date and scheduled arrival date from defaulting to sysdate

Hello,
We have a business scenario where we are deriving scheduled ship date and scheduled arrival date outside and then imported in the instance with the order. However we find that the scheduled ship date and scheduled arrival date are defaulting to sysdate. The atp flag is set to N for these items. I have checked the defaulting rules, there is no such defaulting rule set for scheduled ship date or arrival date ( screenshot attached) Please share your thoughts on how can I stop scheduled ship date and arrival date date from defaulting to sysdate ?
Thanks
Rajesh

Hi
Please visit following link. It may be useful.
How to prevent auto default of schedule ship date in sales order form
HTH
sd

(Sysdate-1) in filename using scheduler and ftp

Hello,
I'm having a little problem with BI Publisher.
What i am trying to do is use the sysdate-1 in the filename when using the scheduler in BIP.
I found out that for using the regular date there are functions like %d %m %y, so obviously the first thing i tried was using the %d-1 but that didn't work :(
Then i went looking on the internet and found the following article:
http://obiee-bip.blogspot.com/2010/05/dynamic-delivery-file-naming-in-bi.html
This mentions things like:
dd : CAST( DAYOFMONTH(NOW()) AS CHAR) ( ex, 01 - 31)
mon : CAST( SUBSTRING(MONTHNAME(NOW()) FROM 1 FOR 3) AS CHAR) (ex, Jan - Dec)
yyyy : CAST( YEAR(NOW()) AS CHAR) (ex, 2006,2010)
But when i use those in the same filename field then it just displays the string as text in the filename.
Could someone tell me what i am doing wrong, or what i need to do to make this work?
Thanks in advance
BIP version : Oracle BI Publisher 10.1.3.4.1
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
"CORE 10.2.0.4.0 Production"
TNS for HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production

Hi Raafje,
Like I've already discussed in my Blog ,Using Date Expressions on Filenames of Burst Query has its own limitations. This date expression that you have tried for sysdate-1 (%d-1%m%y) will not hold good to the requirement. Anyways you can resolve the issue using other work arounds.
Method I (Using CAST and DATE Functions)
1.Previous Day -> CAST(DAYOFMONTH(TIMESTAMPADD(SQL_TSI_DAY, -1, CURRENT_DATE)) AS CHAR)
2.Month of Previous Day -> CAST(MONTH(TIMESTAMPADD(SQL_TSI_DAY, -1, CURRENT_DATE ) ) AS CHAR)
3.Year of Previous Day -> CAST(YEAR(TIMESTAMPADD(SQL_TSI_DAY, -1, CURRENT_DATE)) AS CHAR)
Sample Code
+'ReportName'||'-'||CAST( DAYOFMONTH(TIMESTAMPADD(SQL_TSI_DAY, -1, CURRENT_DATE)) AS CHAR)||'-'||CAST(MONTH(TIMESTAMPADD(SQL_TSI_DAY, -1, CURRENT_DATE ) ) AS CHAR)||'-'||CAST( YEAR(TIMESTAMPADD(SQL_TSI_DAY, -1, CURRENT_DATE)) AS CHAR)||'.pdf'+
Method II (Using Server Variables)
1. Create a Dynamic Repository Variable like Previous_Date(Non-System Session variables can also be used)
2. Create a Initialization blocks
In Data Source Section - Edit Data Source and place the below query
Select TO_CHAR(SYSDATE-1,'MM/DD/YYYY')
FROM Dual (you can use any date format as required)
3. In Variable Target Section
Edit Target -
Give the Name as Previous_Date (as you created in Step1) and Enable the Radio Button as Dynamic
Place date in Default Value like '9/22/2010'
4. Now use this Repository Variable in the filename parameter of the burst query as VALUEOF("Previous_Date") for Repository Variable
and VALUEOF(NQ_SESSION.Previous_Date) in case you have created a session variable for the query
Thanks & Regards,
Goushalya
http://obiee-bip.blogspot.com/2010/05/dynamic-delivery-file-naming-in-bi.html
Edited by: Goushalya on Sep 29, 2011 7:09 AM

Schedule Process Flow with sysdate input parameter

Hi experts,
I'm facing a problem trying to run a schedule in a job,
The schedule is defined to run daily at 3am, and the job receive a sysdate parameter, when I start the schedule in the control center I put
TO_CHAR (TRUNC (SYSDATE), 'DD / MM / YYYY') , and the JOB runs fine with the correct date, but the next day the schedule runs with the date from yesterday, i.e the sysdate is not working.
Maybe I missing something here ?, or is there another way to pass a dinamyc parameter to a scheduled job.
I´m using OWB 11.2.0.1
Thanks.

Chino -
Once you start the job, do you have to leave the "Job Details" window open in order for teh scheduled task to run?
thanks for the help ....
txb

Difference between sy-datm and sysdate in a variant of a report

hi,
I am working on a report which fills the database and i had assigned variant called SYSDATE -1 bcoz it will update the database table for all the plants for the previous date. can anybody guide me that whether i should use the variable SYSDATE- 1 or the sy-datum-1 ,so that uploading the data can be performed.

These are few options you may try
1. Create a wrapper program which will first modify date in variant and save it again. FM RS_VARIANT_CONTENTS, RS_CHANGE_CREATED_VARIANT and
RS_CREATE_VARIANT, RS_VARIANT_DELETE will be useful.
Submit program with this changed variant.
2. Same as above except variant change program can be scheduled and dependent step can be created to run from that variant.
3. While saving the variant you may assign "Selection Variable". This will fetch data from table TVARVC. You will need to periodically update value of your date field in this table.
Regards,
Mohaiyuddin

Scheduled job in oracle database 10g release 2

I have scheduled a batch job job to run once a day at 8.30 in the morning
but the program runs twice a day, onca at acheduled time and once in the evening 18.30.
I am unable to find any reference to the batch program in the job any where.
Database version: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
Operating system version: HP-UX B.11.11

This job is scheduled through dba_jobs.
JOB LOG_USER PRIV_USER SCHEMA_USER LAST_DATE LAST_SEC THIS_DATE THIS_SEC NEXT_DATE NEXT_SEC TOTAL_TIME BROKEN INTERVAL FAILURES WHAT
7353 FPCDBA FPCDBA FPCDBA 01/03/11 08:31:08 08:31:08 02/03/11 08:31:08 08:31:08 29118 N SYSDATE+ 1 0 FRB05101;

Oracle Discoverer report pulls incorrect result when scheduled.

Recently the database was migrated to 10.1.2 RAC from 9.2.0.6, so the discoverer EUL is now resides on new database.
after migration the report which pulls correct results when run interactively is pulling incorrect result when scheduled in Discoverer.
This report used sysdate and aggregate functions, i had ran the same report simultaneously( Directly in Discoverer Desktop/Plus and scheduled in discoverer), but the data retrieved in both case is not matching.
here is the query. any help is appreciated.
SELECT /*+ FIRST_ROWS */ A.SITE_ID as E175108,B."SYSTEM DESCRIPTION" as System_Prefix,
B."SYSTEM PREFIX" as System_Description,
COUNT(CASE WHEN ( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ) < 0 THEN 1 ELSE TO_NUMBER(NULL) END) as Less_than_0_Days,
COUNT(CASE WHEN ( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ) > 121 THEN 1 ELSE TO_NUMBER(NULL) END) as 0_to_14 Days,
COUNT(DECODE(TRUNC(( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) )/31),3,( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ),to_number(NULL))) as 14_to_30_Days,
COUNT(DECODE(TRUNC(( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) )/31),2,( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ),to_number(NULL))) as 31_to_60_Days,
COUNT(DECODE(TRUNC(( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) )/31),1,( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ),to_number(NULL))) as 61_to_90_Days,
COUNT(CASE WHEN ( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ) BETWEEN 15 AND 30 THEN 1 ELSE TO_NUMBER(NULL) END) as 91_to_120_Days,
COUNT(CASE WHEN ( TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE) ) BETWEEN 0 AND 14 THEN 1 ELSE TO_NUMBER(NULL) END) as 120_Days_Plus,
COUNT(TRUNC(SYSDATE)-DISCO10G.DATE_FORMAT_TEST(A.STATUS_DATE)) as Total
FROM PSTAGE.ALL_EQUIPMENT A,
( SELECT A.SITE "SYSTEM PREFIX", A.DESCRIPTION "SYSTEM DESCRIPTION", A.SITE_ID, B.SITE_DESCRIPTION, A.G2B_ID
FROM SITE_LIST A, ALL_CF_SITE_CONTROL B
WHERE A.SITE_ID = B.SITE_ID
ORDER BY 1, 3
) B
WHERE ( (B.SITE_ID = A.SITE_ID))
AND (A.EQUIPMENT_STATUS_CODE IN ('T','7'))
GROUP BY A.SITE_ID,B."SYSTEM DESCRIPTION",B."SYSTEM PREFIX"
ORDER BY B."SYSTEM DESCRIPTION" ASC ;
Thanks!

Hi sunil,
Rod is referencing the NLS parameters i.e.
Can you please let me know which NLS parameters you are referring toNLS parameters in this scenerio may be the date and language for that session.Do check out
SELECT * from NLS_SESSION_PARAMETERS
how i can check if there any differences in the NLS parameters when report is scheduled or run interactivelyI think you should run the trace file.Iam not sure about it.
It would be system_context.
Hope it helps you.
Kranthi.

How to let a prompt vary together with the systemdate when using scheduling

Hello,
If I schedule a report to run every month on the data of the previous month I would like to be able to change the prompt date automatically without me changing this prompt date every month. Does anyone know how I can do this?
thanks in advance
Thierry Renaer

Hi Thierry,
I could only achieve this by setting a condition in the universe to a default date. So if the date equalled the 1st January 1900 then use the system date otherwise use the date in the prompt
The code would look something like
test_date = case when @prompt('Enter date:', 'D', {MyClass\MyDate},mono,free,,,) = to_date('01/01/1900', 'DD/MM/YYY')
then sysdate
else @prompt('Enter date:', 'D', {MyClass\MyDate},mono,free,,,)
end
You can then schedule your report using 1st Jan 1900, but the user can also refresh with genuine dates
Regards
Alan

Error in schedule job

Hi All,
I tried to create this job and encounter ORA-6550 which refers to a syntax error. However, I have checked the script and found no syntax errors.
Can anyone advise me on what's wrong with my sql statements?
ORA-06550: line 12, column 11:
PLS-00103: Encountered the symbol "TABLE" when expecting one of the following:
:= . ( @ % ;
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job       => X
   ,what      => 'LOOP
       DELETE W WHERE CREATED_DT < ADD_MONTHS(SYSDATE, -6) AND ROWNUM < 1000;
       EXIT WHEN SQL%ROWCOUNT=0;
       COMMIT;
     END LOOP;
     COMMIT;
     TRUNCATE TABLE X;
     ALTER TABLE Y ENABLE ROW MOVEMENT;
     ALTER TABLE Z SHRINK SPACE;
   ,next_date => to_date('30/05/2009 22:00:00','dd/mm/yyyy hh24:mi:ss')
   ,interval => 'NEXT_DAY(TRUNC(SYSDATE), ''SATURDAY'')+22/24'
   ,no_parse => FALSE
END;
/

Hi,
I have successfully scheduled this job to run on every saturday 10pm. Just to confirm, is the interval I have set correctly?
   ,next_date => SYSDATE
   ,interval => 'NEXT_DAY(TRUNC(SYSDATE), ''SATURDAY'')+22/24'
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job       => X
   ,what      => '
BEGIN
LOOP
    DELETE X WHERE CREATED_DATE < ADD_MONTHS(SYSDATE, -3) AND ROWNUM < 1000;
    EXIT WHEN SQL%ROWCOUNT=0;
    COMMIT;
END LOOP;
COMMIT;
EXECUTE IMMEDIATE ''TRUNCATE TABLE Y'';
EXECUTE IMMEDIATE ''ALTER TABLE W ENABLE ROW MOVEMENT'';
EXECUTE IMMEDIATE ''ALTER TABLE Z SHRINK SPACE'';
END;
   ,next_date => to_date('30/05/2009 22:00:00','dd/mm/yyyy hh24:mi:ss')
   ,interval => 'NEXT_DAY(TRUNC(SYSDATE), ''SATURDAY'')+22/24'
   ,no_parse => FALSE
END;
/

How to create a schedule to run once?

I am having some problems getting a schedule to run only once. If I leave the repeat_interval empty, the schedule does not run at all. The documentation explains all the options for setting the repeat frequency, but it does not explain how to run it only once at a set time/date. I have created a user interface to allow the users to create their own schedules and I'd rather not do something like a "yearly" interval with an end date of next week. I need the generic solution.
Any ideas?

Hi Ravi,
Thanks for your reply!
I have just discovered something very interesting! best explained by example:
(I might log an SR through metalink too. I'll be sure to update this thread with the outcome...)
I create 3 schedules and 3 simple jobs:
schedule 1 - start_date in 2 minutes time (eg. 11:30:00), repeat_interval => null
schedule 2 - start_date in 2 minutes, 20 seconds time (eg. 11:30:20), repeat_interval => 'FREQ=DAILY'
schedule 3 - start_date in 2 minutes, 40 seconds time (eg. 11:30:40), repeat_interval => null
jobs 1, 2 and 3 just insert a row into a table through a PL/SQL block.
My test results are as follows:
1. The first time these schedules are created only schedule 2 runs. Schedules 1 and 3 never run.
2. I drop and re-create all schedules and jobs, (adjusting the time to a few minutes in the future) and re-submit the schedules and jobs and they all run. I can continue this as many times as I like now and the repeat_interval of null will now work fine.
3. re-start the 10gR2 database.
4. re-create the schedules and jobs and only schedule 2 runs again. Schedules 1 and 3 never run. (I'm back at step 1!! I can reproduce this problem anytime by following these steps)
My script is below:
declare
start_datetime__w timestamp(3) with time zone;
repeat_interval__w varchar2(200);
begin
* REPEAT INTERVAL NULL TEST
* TIM_SCHED_2_1 - no repeat interval
* TIM_SCHED_2_2 - a repeat interval
* TIM_SCHED_2_3 - no repeat interval (identical to TIM_SCHED_2_1)
* Results on my 10gR2 database (Redhat Enterprise Linux 4.4) are:
* job 2 will always run
* jobs 1 and 3 will only run after the successful run of job2 AND jobs 1 and 3 have been re-created
* Why?
* It seems the scheduler needs a wakeup call!!!
* test table: create table tim (col1 varchar2(30), col2 date);
-- Cleanup previous jobs:
--dbms_scheduler.drop_job      (job_name      => 'TIM_JOB_2_1');
--dbms_scheduler.drop_schedule (schedule_name => 'TIM_SCHED_2_1');
--dbms_scheduler.drop_job      (job_name      => 'TIM_JOB_2_2');
--dbms_scheduler.drop_schedule (schedule_name => 'TIM_SCHED_2_2');
--dbms_scheduler.drop_job      (job_name      => 'TIM_JOB_2_3');
--dbms_scheduler.drop_schedule (schedule_name => 'TIM_SCHED_2_3');
repeat_interval__w := 'FREQ=DAILY';
-- create schedule TIM_SCHED_2_1, repeat_interval__w = null
start_datetime__w := '27-FEB-2007 11:34:00.000 AM +10:00';
dbms_scheduler.create_schedule (schedule_name => 'TIM_SCHED_2_1',
start_date => start_datetime__w,
repeat_interval => null,
end_date => null,
comments => 'schedule created at '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
-- create schedule TIM_SCHED_2_2, with a repeat_interval set
start_datetime__w := '27-FEB-2007 11:34:20.000 AM +10:00';
dbms_scheduler.create_schedule (schedule_name => 'TIM_SCHED_2_2',
start_date => start_datetime__w,
repeat_interval => repeat_interval__w,
end_date => null,
comments => 'schedule created at '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
-- create schedule TIM_SCHED_2_3, repeat_interval__w = null (SCHEDULE IDENTICAL TO TIM_SCHED_2_1)
start_datetime__w := '27-FEB-2007 11:34:40.000 AM +10:00';
dbms_scheduler.create_schedule (schedule_name => 'TIM_SCHED_2_3',
start_date => start_datetime__w,
repeat_interval => null,
end_date => null,
comments => 'schedule created at '||to_char(sysdate,'DD-MON-YYYY HH24:MI:SS'));
-- create jobs
dbms_scheduler.create_job (job_name => 'TIM_JOB_2_1',
schedule_name => 'TIM_SCHED_2_1',
job_type => 'PLSQL_BLOCK',
job_action => 'begin '||
'insert into tim values (''TIM_JOB_2_1'', sysdate); '||
'commit; '||
'end;',
number_of_arguments => 0,
enabled => TRUE,
comments => 'job created at '||to_char(sysdate,'DD-MON-YY HH24:MI:SS'));
dbms_scheduler.create_job (job_name => 'TIM_JOB_2_2',
schedule_name => 'TIM_SCHED_2_2',
job_type => 'PLSQL_BLOCK',
job_action => 'begin '||
'insert into tim values (''TIM_JOB_2_2'', sysdate); '||
'commit; '||
'end;',
number_of_arguments => 0,
enabled => TRUE,
comments => 'job created at '||to_char(sysdate,'DD-MON-YY HH24:MI:SS'));
dbms_scheduler.create_job (job_name => 'TIM_JOB_2_3',
schedule_name => 'TIM_SCHED_2_3',
job_type => 'PLSQL_BLOCK',
job_action => 'begin '||
'insert into tim values (''TIM_JOB_2_3'', sysdate); '||
'commit; '||
'end;',
number_of_arguments => 0,
enabled => TRUE,
comments => 'job created at '||to_char(sysdate,'DD-MON-YY HH24:MI:SS'));
end;
Cheers,
Tim.

Sysdate in Schedule

Similar Messages

Maybe you are looking for