In NT the following is the cause :
The os user you login as should be a local user (i.e one who is
authenticated locally and NOT by the Primay Domain Controller) and the same
user should be existing in Oracle and should be used in the
credentials as the database user. This may probably help!
ramkumarg_at_hotmail.com
- Original Message -----
From: "Zhong Hong" <zhong_at_cantametrix.com>
To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com>
Sent: Wednesday, July 12, 2000 3:46 PM
Subject: RE: Scheduled Jobs in OEM not running
> Tried, none of the jobs in all job types ran. OEM console is running on
> win2000 workstation and jobs are submitted to Solaris 7 box. Any ideas?
>
> Zhong
> It's another beautiful day!
>
>
> -----Original Message-----
> Sent: Wednesday, July 12, 2000 8:35 AM
> To: Multiple recipients of list ORACLE-L
>
>
> Try to scheduling a job to run immediately, like ls -l, and see if it
runs.
> If it does then try one to run in 10 minutes. Try different types of
jobs,
> like a DB job, an OS jog, a Listener job and see what will and will not
> run.
>
> Let us know how it goes,
> Ruth
> ----- Original Message -----
> To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
> Sent: Tuesday, July 11, 2000 5:46 PM
>
>
> > Hi, all!
> > I have a scheduled a OS command job from OEM console, but it didn't run!
> > Pinged with intelligent agent, it's fine. Can anybody help?
> >
> > TIA,
> > Zhong
> >
> >
> > -----Original Message-----
> > Sent: Tuesday, July 11, 2000 12:56 PM
> > To: Multiple recipients of list ORACLE-L
> >
> >
> > I thought you could use a combination like:
> >
> > trunc(to_date(sysdate, 'format'))
> >
> > to get consistent scheduling (or a similiar combo of trunc and
sysdate)...
> >
> > From the 8i Administrator's Guide:
> > Job Execution Interval
> >
> > The INTERVAL date function is evaluated immediately before a job is
> > executed. If the job completes successfully, the date calculated from
> > INTERVAL becomes the new NEXT_DATE. If the INTERVAL date function
> evaluates
> > to NULL and the job completes successfully, the job is deleted from the
> > queue.
> >
> > If a job should be executed periodically at a set interval, use a date
> > expression similar to 'SYSDATE + 7' in the INTERVAL parameter. For
> example,
> > if you set the execution interval to 'SYSDATE + 7' on Monday, but for
some
> > reason (such as a network failure) the job is not executed until
Thursday,
> > 'SYSDATE + 7' then executes every Thursday, not Monday.
> >
> > If you always want to automatically execute a job at a specific time,
> > regardless of the last execution (for example, every Monday), the
INTERVAL
> > and NEXT_DATE parameters should specify a date expression similar to
> > 'NEXT_DAY(TRUNC(SYSDATE), "MONDAY")'.
> >
> > Table 8-5 lists some common date expressions used for job execution
> > intervals.
> >
> > Table 8-5 Common Job Execution Intervals
> >
> > Date Expression Evaluation
> > 'SYSDATE + 7' exactly seven days from the last
> execution
> > 'SYSDATE + 1/48' every half hour
> > 'NEXT_DAY(TRUNC(SYSDATE),
> > ''MONDAY'') + 15/24' every Monday at 3PM
> > 'NEXT_DAY(ADD_MONTHS
> > (TRUNC(SYSDATE, ''Q''), 3),
> > ''THURSDAY'')' first Thursday of each quarter
> >
> > Note:
> > When specifying NEXT_DATE or INTERVAL, remember that date literals and
> > strings must be enclosed in single quotation marks. Also, the value of
> > INTERVAL must be enclosed in single quotation marks.
> >
> > HTH,
> >
> > Scott Shafer
> > San Antonio, TX
> >
> >
> > ----- Original Message -----
> > To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com>
> > Sent: Tuesday, July 11, 2000 11:39 AM
> >
> >
> > > A week or so ago there was a brief discussion WRT to getting DBMS_JOB
> > > to successfully start a the same job every 5 minutes without having
> > > any schedule creep. I don't recall anyone posting a possible solution
> > > to this situation. Since I recently wanted to have such functionality
> > > on a couple of my instances, I have been working towards a solution.
> > >
> > > I'm not claiming my approach is the best, it does seem to be working.
> > > I have a PL/SQL task that I want to start running twelve times an
> > > hour; 00, 05, 10, ..., 50, 55 minutes after the hour. This procedure
> > > takes 1+ minutes to 3+ minutes to complete after being invoked.
> > >
> > > At the start of the PL/SQL procedure, a couple of "preparatory"
> > > tasks are completed. 1) DBMS_JOB.BROKEN is called to "break" the
> > > job. 2) a record within the database is updated with the "next"
> > > time this job is to be run. This "next" time is appropriately
> > > rounded to ALWAYS be an integer multiple(0-11) of FIVE minutes.
> > >
> > > As the last task of the procedure, a DBMS_JOB.NEXT_DATE call is
> > > made using the value that was stored in the database at the
> > > start of the procedure. All of the above are NECESSARY but are
> > > not sufficient to achive the desired scheduling.
> > >
> > > A key to accomplishing this scheduling goal seems to be to
> > > establish a sub-minute job_queue_interval in the initSID.ora
> > > file. After I went from job_queue_interval=60 to
> > > job_queue_interval=20, I started to get the scheduling desired!
> > >
> > > HTH & YMMV!
> > > --
> > > Charlie Mengler Maintenance Warehouse
> > > charliem_at_mwh.com 5505 Morehouse Drive
> > > 858-552-6229 San Diego, CA 92121
> > > Always be sincere about your enthusiasm, whether you mean it or not.
> > > --
> > > Author: Charlie Mengler
> > > INET: charliem_at_mwh.com
> > >
> >
> >
> > --
> > Author: Scott Shafer
> > INET: scott.shafer_at_ildmail.com
> >
> > Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> > San Diego, California -- Public Internet access / Mailing Lists
> > --------------------------------------------------------------------
> > To REMOVE yourself from this mailing list, send an E-Mail message
> > to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> > the message BODY, include a line containing: UNSUB ORACLE-L
> > (or the name of mailing list you want to be removed from). You may
> > also send the HELP command for other information (like subscribing).
> > --
> > Author: Zhong Hong
> > INET: zhong_at_cantametrix.com
> >
> > Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> > San Diego, California -- Public Internet access / Mailing Lists
> > --------------------------------------------------------------------
> > To REMOVE yourself from this mailing list, send an E-Mail message
> > to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> > the message BODY, include a line containing: UNSUB ORACLE-L
> > (or the name of mailing list you want to be removed from). You may
> > also send the HELP command for other information (like subscribing).
> >
>
> --
> Author: Ruth Gramolini
> INET: rgramolini_at_tax.state.vt.us
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
> --
> Author: Zhong Hong
> INET: zhong_at_cantametrix.com
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
Received on Thu Jul 13 2000 - 21:09:42 CDT
