Starting Scheduled JOB by OMBPLUS

Hi all,
Can OMB+ start a scheduled job ?
I can't find the scripts....
I would promoting to production only using OMB+ !
I'm using OWB 10gr2 on DB 10gr2 and OWF 2.6.4 on UNIX.
Thanks,
Marco

Hi Marco,
in 10.2 and asuming you are using DBMS_SCHEDULER, then scheduled jobs are started by the scheduler process itself, which is always running as long as the database is up.
OMB+ is used for object administration, if you will, while the WF Server and Scheduler processes are used for object execution.
Cheers,
Donna

Similar Messages

Deploy Scheduled JOB by OMBPLUS

Hi,
I need to deploy a scheduling by OMB+ Script.
My scheduling is correctly created.
Then, I send this instruction :
OMBCC '/$project_name/SCH'
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'SCHEDULING_PACKAGE'
ADD ACTION 'SCH'
SET PROPERTIES (OPERATION) VALUES ('CREATE')
SET REFERENCE SCHEDULABLE'SCH_DELTA'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'SCHEDULING_PACKAGE'
OMBDROP DEPLOYMENT_ACTION_PLAN 'SCHEDULING_PACKAGE'
OMBCOMMIT
but I obtain this error :
OMB01073 : SCHEDULABLE SCH_DELTA not found
Can someone help me?
Thank you
Julie

Hi Nigel,
I will try to explain on the best how I have created my objects :
I created a process flow PRC_DELTA which needs to run every day.
This process flow is created in the 'Process Flow Modules' like this :
Process Flow Modules
     PFL_PROCESS
          PPK_DMT
               PRC_DELTA
Then by OMB Script I created a scheduling in the 'Schedules Module' like this :
Schedules
     SCH
     SCH_DELTA
Still by OMB script, I have combined PRC_DELTA with SCH_DELTA (ie SCH_DELTA is the referred calendar of PRC_DELTA)
Then, I have deployed my process flow. But, it doesn't run every day.
So I try to understand why.
In the Control center my objects are presented like this :
SCH_LOCATION
     Scheduled jobs
          PRC_DELTA_JOB
OWF_LOCATION
     PFL_PROCESS
          PPK_DMT
               PRC_DELTA
And I need to deploy the PRC_DELTA_JOB object and start it. But I don't know how to do this by OMB+ script.
Thank you for your help
Julie.

How to create schedule job and event trigger in XI to start a ABAP program?

Dear All:
Here are what i need to do:
1.To run a ABAP program to start an XI scenario per hour.
2.To run a ABAP program to start an XI scenario per day at 6 PM.
3.To run a ABAP program used event trigger to make sure that XI scenario has finished the process and after that wait for 10 min later and run again.
only i know is used sm36 & sm37 to set up a schedule job.
but what i don't know is how to do it step by step.
especially point 3.
are there any step by step example can show me how?
it better be simple and details...
thanks you all
Regards
Jack Lee

Hi,
If you want to trigger the event manually from within SAP, use transaction
SM64
in SAP this is done by scheduling a job
once a new customer is entered
your scheduled report sends customer master data
you can schedule your report (TCODE - BD12 I think) to one day or every 5 minutes... it depend on your needs and the system performence
Regards,
Surya

BI Publisher (Obiee 11g) Scheduled jobs start randomly after services restarting

Hi everybody,
I've a problem with scheduled jobs on BI Publisher that start randomly after server restarting.
For example if there's a job scheduled every day at 8.00 am it works fine until the server is not restarted but when I restart it next job running start at 9.28 am (it is an example because the real start time is very unpredictable).
In my case bi publisher is integrated with obiee 11g (11.1.1.6.2) and I've scheduled jobs with administrative user (weblogic). For this user I've set the Bi Publisher Preferences (report locale = Italiano-Italia, Report Time Zone = GMT +1:00) from obiee analytics user account preferencies.
Can anyone have this problem too and help me?
Thanks
Annalisa

These are not helpful. The first link is to OBIEE 10g and the second is just an install guide. I am having the same issue with BI Publisher returning java.lang.NullPointerException in OBIEE 11g. Any help would be appreciated. Thanks,
Paul
Edited by: pneedleman on Nov 17, 2010 10:15 AM

Request vs Actual Start Date in Scheduler Jobs

Hi, I want to run a PL/SQL block, all days, at 1:00 AM
I've defined the following scheduler job, in a new (and empty) Job Class:

SQL> select job_name, repeat_interval, job_class, job_priority from dba_scheduler_jobs where job_class = 'MY_NOCHE_JOB_CLASS';
JOB_NAME...........: UNIFICA_CLIENTES
REPEAT_INTERVAL....: FREQ=DAILY;BYHOUR=1;BYMINUTE=0;BYSECOND=0
JOB_CLASS..........: MY_NOCHE_JOB_CLASS
JOB_PRIORITY.......: 1

However, the process is starting later, for example:

Request Start Date....: Nov 10, 2010 1:00:00 AM -02:00
Actual Start Date.....: Nov 10, 2010 4:06:33 AM -02:00

Why is the difference between Request Start Date and Actual Start Date ?
Is there any way to enforce the start of the Job at any time ?
OS: Solaris 10 8/07 s10s_u4wos_12b SPARC
DB: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
Thanks in advance

The database is not down since at least 2 months

SQL> select LAST_START_DATE from DBA_SCHEDULER_JOBS where job_class = 'MY_NOCHE_JOB_CLASS';
LAST_START_DATE
────────────────────────────────────
17-NOV-10 04.21.00.447083 AM -02:00

Any advice ?

Schedule job don't start

Hi Gurus, for last 2 days, no Jobs are being started in my BI system.
Whenever I schedule or start any job.. it says job started..
But when I check in SM37, I find the start column empty. And the delay(secs) column has the number of seconds increasing.
It goes 500 or even more.. The job actually never get started.
What might be the problem ??
Is it regarding any space issue ?
Have anyone of you faced this problem ?
Please help, Akash

Not sure what those jobs are
You can actually do "Cancel Without Core" but better talk to BASIS and figure out whats happening.

All scheduled jobs started suddenly to fail with ORA-01031: insufficient pr

I have a setup of gridcontrol 11g on windows 2008. I've been running successful for weeks until the other day when all my scheduled jobs started to fail with
ORA-01031: insufficient privileges (rman jobs)
ERROR: Invalid username and/or password (sql scripts).
I verified for the accounts being locked, pw correct, expired / grace period, etc.
all good when I try from the command line. running an rman backup from the command line works great, but the same one through the job scheduler fails with ORA-01031.
I've dropped the jobs completely, recreated them again. same thing.
I'm using preferred credentials and dropped and recreated them. same thing.
I don't know where else to look. Only grid control scheduled jobs fail, but all of them do.
I'm using SQLNET.AUTHENTICATION_SERVICES= (NTS) in my sql.ne (always have).
we use a windows domain server / domain authentication for logging into boxes. I haven't changed any of my passwords.
I am probably looking in the wrong places. Anybody able to help?

Hi,
ERROR: Invalid username and/or password (sql scripts).This error message clearly tells that password is incorrect and "insufficient privileges" shows that perhaps you are using SYS user for running the jobs and password for user SYS is incorrect.
If you are specifying passwords in your scripts, i don't think you need to set preferred credentials.
Try following
1) Remove preferred credentials
2) Don't check password of user sys by locally logging in (because if Os authentication is on, even wrong password will allow you loging into the database and you will think that password is correct). Try connecting database using SYS user from a remote machine and check whether it accepts your password and make sure you have same password for your jobs and in sql scripts
3) If still problem, just for test, remove SQLNET.AUTHENTICATION_SERVICES= (NTS) and try
Salman

Unable to start scheduler in OIM 9.1.0.2bp11 Weblo10.3.2

Hello,
After doing a REINIT using the scheduler web interface : http://xxxxx:7511/xlScheduler/ with xelsysadm account
Then, STOP the scheduler and trying to START it without success.
I have restarted my server, same issue.
Bellow are my log file details when starting my OIM and after the ############################################# section, the logs when clicking the START button of the scheduler interface :
Thanks for your help !
JAVA Memory arguments: -Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m
WLS Start Mode=Development
CLASSPATH=:/appl/oim/middleware/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/appl/oim/middleware/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/appl/oim/middleware/jdk160_14_R27.6.5-32/lib/tools.jar:/appl/oim/middleware/utils/config/10.3/config-launch.jar:/appl/oim/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/appl/oim/middleware/wlserver_10.3/server/lib/weblogic.jar:/appl/oim/middleware/modules/features/weblogic.server.modules_10.3.2.0.jar:/appl/oim/middleware/wlserver_10.3/server/lib/webservices.jar:/appl/oim/middleware/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/appl/oim/middleware/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/appl/oim/middleware/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/appl/oim/middleware/wlserver_10.3/server/lib/xqrl.jar:/appl/oim/product/9.1.0.2/xellerate/ext/jdbcpool-0.99.jar:/appl/oim/product/9.1.0.2/xellerate/ext/xerces.jar:/appl/oim/product/9.1.0.2/xellerate/lib/xlLogger.jar:/appl/oim/product/9.1.0.2/xellerate/ext/log4j-1.2.8.jar:/appl/oim/product/9.1.0.2/xellerate/lib/xlUtils.jar:/appl/oim/product/9.1.0.2/xellerate/lib/xlCrypto.jar:::
PATH=/appl/oim/middleware/wlserver_10.3/server/bin:/appl/oim/middleware/modules/org.apache.ant_1.7.0/bin:/appl/oim/middleware/jdk160_14_R27.6.5-32/jre/bin:/appl/oim/middleware/jdk160_14_R27.6.5-32/bin:/appl/oim/middleware/wlserver_10.3/server/bin:/appl/oim/middleware/modules/org.apache.ant_1.7.0/bin:/appl/oim/middleware/jdk160_14_R27.6.5-32/jre/bin:/appl/oim/middleware/jdk160_14_R27.6.5-32/bin:/sbin:/usr/sbin:/bin:/usr/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode)
Starting WLS with line:
/appl/oim/middleware/jdk160_14_R27.6.5-32/bin/java -client -Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.security.SSL.trustedCAKeyStore=/appl/oim/middleware/wlserver_10.3/server/lib/cacerts -DXL.HomeDir=/appl/oim/product/9.1.0.2/xellerate -Djava.security.auth.login.config=/appl/oim/product/9.1.0.2/xellerate/config/authwl.conf -Dlog4j.configuration=file:/appl/oim/product/9.1.0.2/xellerate/config/log.properties -Djava.awt.headless=true -Xverify:none -da -Dplatform.home=/appl/oim/middleware/wlserver_10.3 -Dwls.home=/appl/oim/middleware/wlserver_10.3/server -Dweblogic.home=/appl/oim/middleware/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://mrs-px-00050:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/appl/oim/middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/appl/oim/middleware/patch_wls1030/profiles/default/sysext_manifest_classpath -Dweblogic.Name=px50 -Djava.security.policy=/appl/oim/middleware/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
<Dec 16, 2010 9:27:44 AM UTC> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/appl/oim/user_projects/domains/OIM_PREPROD/lib/log4j-1.2.8.jar:/appl/oim/user_projects/domains/OIM_PREPROD/lib/mbeantypes/XL10SecurityProviders.jar:/appl/oim/user_projects/domains/OIM_PREPROD/lib/nexaweb-common.jar>
<Dec 16, 2010 9:27:44 AM UTC> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 14.0-b16 from Sun Microsystems Inc.>
<Dec 16, 2010 9:27:45 AM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
<Dec 16, 2010 9:27:46 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 16, 2010 9:27:46 AM UTC> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 16, 2010 9:27:47 AM UTC> <Notice> <LoggingService> <BEA-320400> <The log file /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/px50.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Dec 16, 2010 9:27:47 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/px50.log00054. Log messages will continue to be logged in /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/px50.log.>
<Dec 16, 2010 9:27:47 AM UTC> <Notice> <Log Management> <BEA-170019> <The server log file /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/px50.log is opened. All server side log events will be written to this file.>
log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.DailyRollingFileAppender.
DEBUG,16 Dec 2010 09:28:38,604,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateAuthenticationProviderImpl/initialize entered.
DEBUG,16 Dec 2010 09:28:38,605,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateAuthenticationProviderImpl/initialize left.
<Dec 16, 2010 9:28:39 AM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 16, 2010 9:28:40 AM UTC> <Notice> <LoggingService> <BEA-320400> <The log file /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Dec 16, 2010 9:28:40 AM UTC> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/access.log00172. Log messages will continue to be logged in /appl/oim/user_projects/domains/OIM_PREPROD/servers/px50/logs/access.log.>
<Dec 16, 2010 9:28:41 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 16, 2010 9:28:41 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 16, 2010 9:29:05 AM UTC> <Warning> <HTTP> <BEA-101369> <ServletContext@404977[app:Xellerate module:/xlWebApp path:/xlWebApp spec-version:null]: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.>
Loading xalan.jar for XPathAPI.
 Nexaweb Technologies Inc.(C)2000-2004. All Rights Reserved.
 Nexaweb Technologies Inc.
 10 Canal Park
 Cambridge, MA 02141
 Tel: 617.577.8100. Email: [email protected]
GMS: address is mrs-px-00050:56555
DEBUG,16 Dec 2010 09:29:14,307,[XELLERATE.SCHEDULER],trigger Misfire instruction : MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT
DEBUG,16 Dec 2010 09:29:14,307,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzTrigger left.
DEBUG,16 Dec 2010 09:29:14,316,[XELLERATE.SCHEDULER],Loading Scheduled task class com.thortech.xl.scheduler.core.quartz.QuartzWrapperusing ADP classloader
DEBUG,16 Dec 2010 09:29:14,323,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/scheduleJob left.
DEBUG,16 Dec 2010 09:29:14,323,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent entered.
DEBUG,16 Dec 2010 09:29:14,325,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/scheduleJob entered.
DEBUG,16 Dec 2010 09:29:14,325,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzJobDetail entered.
DEBUG,16 Dec 2010 09:29:14,325,[XELLERATE.SCHEDULER],Creating Quartz Job with job name Manage Reconciliation Events
DEBUG,16 Dec 2010 09:29:14,325,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getJobClass entered.
FATAL,16 Dec 2010 09:29:14,353,[SCHEDULER.WEBSTARTUP],Unable to start scheduler : SchedulerBaseTask
<Dec 16, 2010 9:29:14 AM UTC> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 16, 2010 9:29:14 AM UTC> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 16, 2010 9:29:14 AM UTC> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of OIM_PREPROD_CLUSTER.>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.0.141.40:7511 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:250:56ff:fea2:6063:7511 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:7511 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7511 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 16, 2010 9:29:46 AM UTC> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "px50" for domain "OIM_PREPROD" running in Development Mode>
<Dec 16, 2010 9:29:49 AM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 16, 2010 9:29:49 AM UTC> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
DEBUG,16 Dec 2010 15:00:32,106,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/initialize entered.
DEBUG,16 Dec 2010 15:00:32,106,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/initialize left.
DEBUG,16 Dec 2010 15:00:32,106,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/login entered.
DEBUG,16 Dec 2010 15:00:32,106,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/getCallbacks entered.
DEBUG,16 Dec 2010 15:00:32,106,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/getCallbacks left.
DEBUG,16 Dec 2010 15:00:32,106,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/getUserName - Data: userName - Value: xelsysadm
DEBUG,16 Dec 2010 15:00:32,107,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/getPasswordHave entered.
DEBUG,16 Dec 2010 15:00:32,107,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/getPasswordHave left.
INFO,16 Dec 2010 15:00:32,107,[XELLERATE.ACCOUNTMANAGEMENT],Info Data: userName - Value: xelsysadm
DEBUG,16 Dec 2010 15:00:32,107,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/login: Calling Authenticate [Without Java:]
DEBUG,16 Dec 2010 15:00:32,107,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/connect entered.
DEBUG,16 Dec 2010 15:00:32,107,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/getPropertyValue entered.
DEBUG,16 Dec 2010 15:00:32,110,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection entered.
DEBUG,16 Dec 2010 15:00:32,111,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection left.
DEBUG,16 Dec 2010 15:00:32,111,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/getPropertyValue left.
DEBUG,16 Dec 2010 15:00:32,111,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/getPropertyValue entered.
DEBUG,16 Dec 2010 15:00:32,113,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection entered.
DEBUG,16 Dec 2010 15:00:32,113,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection left.
DEBUG,16 Dec 2010 15:00:32,113,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/getPropertyValue left.
DEBUG,16 Dec 2010 15:00:32,115,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection entered.
DEBUG,16 Dec 2010 15:00:32,116,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection left.
DEBUG,16 Dec 2010 15:00:32,116,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/isPasswordExpired entered.
DEBUG,16 Dec 2010 15:00:32,117,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection entered.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/closeConnection left.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: Authenticate/connect left.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XLDBRegistry/getUsersForGroup - Data: userName - Value: xelsysadm
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/login left.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/commit entered.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.ACCOUNTMANAGEMENT],Class/Method: XellerateLoginModuleImpl/commit left.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.SCHEDULER],Class/Method: SchedulerUtil/getSchedulerUsers entered.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.SCHEDULER],Class/Method: SchedulerUtil/getSchedulerUsers left.
DEBUG,16 Dec 2010 15:00:32,118,[XELLERATE.SCHEDULER],Class/Method: SchedulerUtil/getSchedulerProperties entered.
DEBUG,16 Dec 2010 15:00:32,119,[XELLERATE.SCHEDULER],Class/Method: SchedulerUtil/getSchedulerProperties left.
DEBUG,16 Dec 2010 15:00:32,119,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getSchedulerInstance entered.
DEBUG,16 Dec 2010 15:00:32,119,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getSchedulerInstance left.
DEBUG,16 Dec 2010 15:00:32,119,[XELLERATE.SCHEDULER],Class/Method: SchedulerUtil/getUserTrasaction entered.
DEBUG,16 Dec 2010 15:00:32,132,[XELLERATE.SCHEDULER],Class/Method: SchedulerUtil/getUserTrasaction left.
DEBUG,16 Dec 2010 15:00:32,142,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent entered.
ERROR,16 Dec 2010 15:00:32,142,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent encounter some problems: The Scheduler has been shutdown.
org.quartz.SchedulerException: The Scheduler has been shutdown.
 at org.quartz.core.QuartzScheduler.validateState(QuartzScheduler.java:498)
 at org.quartz.core.QuartzScheduler.getJobDetail(QuartzScheduler.java:1063)
 at org.quartz.impl.StdScheduler.getJobDetail(StdScheduler.java:485)
 at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.isTaskAlreadyPresent(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.initializeScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.startScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.service(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
DEBUG,16 Dec 2010 15:00:32,144,[XELLERATE.SCHEDULER],LefMethodDebug
DEBUG,16 Dec 2010 15:00:32,144,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/scheduleJob entered.
DEBUG,16 Dec 2010 15:00:32,144,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzJobDetail entered.
DEBUG,16 Dec 2010 15:00:32,144,[XELLERATE.SCHEDULER],Creating Quartz Job with job name ADMINISTRATORS
DEBUG,16 Dec 2010 15:00:32,144,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getJobClass entered.
DEBUG,16 Dec 2010 15:00:32,239,[XELLERATE.SCHEDULER],LefMethodDebug
DEBUG,16 Dec 2010 15:00:32,239,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzJobDetail left.
DEBUG,16 Dec 2010 15:00:32,239,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzTrigger entered.
DEBUG,16 Dec 2010 15:00:32,239,[XELLERATE.SCHEDULER],Creating Daily Trigger with StartTime 2009-08-22 15:46:49.0
DEBUG,16 Dec 2010 15:00:32,243,[XELLERATE.SCHEDULER],triggerFreq : DAILY
DEBUG,16 Dec 2010 15:00:32,244,[XELLERATE.SCHEDULER],triggerImpl : Trigger 'DEFAULT.ADMINISTRATORS': triggerClass: 'org.quartz.SimpleTrigger isVolatile: false calendar: 'null' misfireInstruction: 0
DEBUG,16 Dec 2010 15:00:32,244,[XELLERATE.SCHEDULER],trigger Misfire instruction : MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT
DEBUG,16 Dec 2010 15:00:32,244,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzTrigger left.
DEBUG,16 Dec 2010 15:00:32,244,[XELLERATE.SCHEDULER],QuartzSchedulerImpl scheduleJob Exception
org.quartz.SchedulerException: The Scheduler has been shutdown.
 at org.quartz.core.QuartzScheduler.validateState(QuartzScheduler.java:498)
 at org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:635)
 at org.quartz.impl.StdScheduler.addJob(StdScheduler.java:243)
 at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.scheduleJob(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.initializeScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.startScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.service(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
DEBUG,16 Dec 2010 15:00:32,244,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent entered.
ERROR,16 Dec 2010 15:00:32,244,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent encounter some problems: The Scheduler has been shutdown.
org.quartz.SchedulerException: The Scheduler has been shutdown.
 at org.quartz.core.QuartzScheduler.validateState(QuartzScheduler.java:498)
 at org.quartz.core.QuartzScheduler.getJobDetail(QuartzScheduler.java:1063)
 at org.quartz.impl.StdScheduler.getJobDetail(StdScheduler.java:485)
 at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.isTaskAlreadyPresent(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.initializeScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.startScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.service(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
DEBUG,16 Dec 2010 15:00:32,245,[XELLERATE.SCHEDULER],LefMethodDebug
DEBUG,16 Dec 2010 15:00:32,245,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/scheduleJob entered.
DEBUG,16 Dec 2010 15:00:32,245,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzJobDetail entered.
DEBUG,16 Dec 2010 15:00:32,245,[XELLERATE.SCHEDULER],Creating Quartz Job with job name RPM Reconciliation
DEBUG,16 Dec 2010 15:00:32,245,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getJobClass entered.
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],LefMethodDebug
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzJobDetail left.
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzTrigger entered.
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],Creating Once Trigger with StartTime 2010-12-03 15:30:55.0
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],triggerFreq : ONCE
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],triggerImpl : Trigger 'DEFAULT.RPM Reconciliation': triggerClass: 'org.quartz.SimpleTrigger isVolatile: false calendar: 'null' misfireInstruction: 0
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],trigger Misfire instruction : MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzTrigger left.
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],QuartzSchedulerImpl scheduleJob Exception
org.quartz.SchedulerException: The Scheduler has been shutdown.
 at org.quartz.core.QuartzScheduler.validateState(QuartzScheduler.java:498)
 at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:542)
 at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:220)
 at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.scheduleJob(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.initializeScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.startScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.service(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
DEBUG,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent entered.
ERROR,16 Dec 2010 15:00:32,246,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/isTaskAlreadyPresent encounter some problems: The Scheduler has been shutdown.
org.quartz.SchedulerException: The Scheduler has been shutdown.
 at org.quartz.core.QuartzScheduler.validateState(QuartzScheduler.java:498)
 at org.quartz.core.QuartzScheduler.getJobDetail(QuartzScheduler.java:1063)
 at org.quartz.impl.StdScheduler.getJobDetail(StdScheduler.java:485)
 at com.thortech.xl.scheduler.core.quartz.QuartzSchedulerImpl.isTaskAlreadyPresent(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.initializeScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.startScheduler(Unknown Source)
 at com.thortech.xl.scheduler.deployment.webapp.SchedulerInitServlet.service(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
DEBUG,16 Dec 2010 15:15:17,617,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/scheduleJob entered.
DEBUG,16 Dec 2010 15:15:17,617,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getQuartzJobDetail entered.
DEBUG,16 Dec 2010 15:15:17,618,[XELLERATE.SCHEDULER],Creating Quartz Job with job name Manage Reconciliation Events
DEBUG,16 Dec 2010 15:15:17,618,[XELLERATE.SCHEDULER],Class/Method: QuartzSchedulerImpl/getJobClass entered.
DEBUG,16 Dec 2010 15:15:17,618,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/getClassLoader entered.
DEBUG,16 Dec 2010 15:15:17,618,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/getClassLoader left.
DEBUG,16 Dec 2010 15:15:17,619,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
DEBUG,16 Dec 2010 15:15:17,620,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: com.oracle.oim.dictao.cmacgm.utils.tasks.ReconcialiationTask
DEBUG,16 Dec 2010 15:15:17,622,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
DEBUG,16 Dec 2010 15:15:17,622,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: SchedulerBaseTask
FATAL,16 Dec 2010 15:15:17,625,[SCHEDULER.WEBSTARTUP],Unable to start scheduler : SchedulerBaseTask

Here is the result and we can see the SchedulerBaseTask class
(px50) [iam10g] /appl/oim/product/9.1.0.2/xellerate/lib > jar tvf xlScheduler.jar
0 Wed Dec 15 10:13:54 UTC 2010 META-INF/
925 Wed Dec 15 10:13:52 UTC 2010 META-INF/MANIFEST.MF
8776 Wed Dec 15 10:13:52 UTC 2010 META-INF/ejb-jar.xml
2002 Wed Dec 15 10:13:52 UTC 2010 META-INF/weblogic-ejb-jar.xml
0 Wed Dec 15 10:13:54 UTC 2010 com/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/schedule/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/schedule/tasks/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/beans/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/cluster/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/common/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/core/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/core/quartz/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/data/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/deployment/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/deployment/webapp/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/ejb/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/exception/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/interfaces/
0 Wed Dec 15 10:13:54 UTC 2010 com/thortech/xl/scheduler/tasks/
777 Mon Aug 09 22:34:00 UTC 2010 META-INF/ibm-ejb-jar-bnd.xmi
581 Mon Aug 09 22:34:00 UTC 2010 META-INF/ibm-ejb-jar-ext.xmi
9887 Mon Aug 09 22:34:00 UTC 2010 META-INF/jboss.xml
1019 Mon Aug 09 22:34:00 UTC 2010 META-INF/orion-ejb-jar.xml
2400 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/DeleteOfflineMessages.class
1163 Mon Aug 09 22:35:00 UTC 2010 com/thortech/xl/schedule/tasks/EntitlementsConstants.class
22973 Mon Aug 09 22:34:24 UTC 2010 com/thortech/xl/schedule/tasks/GetSODCheckResults.class
3657 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/InitiateRequestApprovalTask.class
5229 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/ProcessDeferredReconEvents.class
3814 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/ProcessOldAuditMessages.class
4629 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/ReIssueAuditMessage.class
7221 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/ReSubmitTask.class
26190 Mon Aug 09 22:34:24 UTC 2010 com/thortech/xl/schedule/tasks/ResubmitUninitiatedApprovalSODChecks.class
27284 Mon Aug 09 22:34:24 UTC 2010 com/thortech/xl/schedule/tasks/ResubmitUninitiatedProvisioningSODChecks.class
2330 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcBaseTask.class
5432 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcEnableDisableEntitlement.class
12003 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcEntitlementDeltaLoad.class
15885 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcEntitlementListLoad.class
23282 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcEntitlementsAssignmentTask.class
4576 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcLDAPOperations.class
6053 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcLDAPRecon.class
2985 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcLDAPUpdate.class
2205 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcLookupFieldReconciliation.class
2876 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcRSAImport.class
4572 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskAttestation.class
3720 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskBaseReconEvent.class
2372 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskDeleteOpenTasks.class
5287 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskDisableRequest.class
4947 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskEnableRequest.class
3203 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskEscalation.class
6799 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskGenRecon.class
6596 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskGroupPriorityNoGap.class
4239 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskPasswordExpiration.class
4246 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskPasswordWarning.class
5555 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskResubmitReconEvent.class
2974 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskScheduledDaemon.class
3346 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskScheduledProvision.class
5077 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskSubmitAttestationRequets.class
3953 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskTimedRetry.class
4345 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUserOperations.class
3857 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrDeprovision.class
5951 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrDisable.class
3722 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrEnable.class
896 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrEvaluatePolicies$BucketData.class
2607 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrEvaluatePolicies$PolicyEvalWorker.class
5777 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrEvaluatePolicies.class
3924 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrProvision.class
3480 Mon Aug 09 22:35:06 UTC 2010 com/thortech/xl/schedule/tasks/tcTskUsrTriggerProvision.class
5514 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/beans/SchedulerControllerSession.class
327 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/cluster/ScheduleTaskEventInfo.class
1331 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/cluster/ScheduleTaskEventListener.class
5008 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/cluster/SchedulerClusterService.class
1570 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/cluster/SchedulerTaskLocater.class
772 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/common/SchedulerConstants.class
7349 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/common/SchedulerUtil.class
1225 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/Scheduler.class
635 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/SchedulerFactory.class
1245 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/QuartzSchedulerClassLoaderHelper.class
19644 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/QuartzSchedulerImpl.class
1456 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/QuartzTaskListener.class
1369 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/QuartzTriggerListener.class
7927 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/QuartzWrapper$TaskExecutionAction.class
8049 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/QuartzWrapper.class
1671 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/core/quartz/XLJobStoreCTM.class
2093 Mon Aug 09 22:34:56 UTC 2010 com/thortech/xl/scheduler/data/TaskDetail.class
1224 Mon Aug 09 22:34:56 UTC 2010 com/thortech/xl/scheduler/data/TriggerDetail.class
13200 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/deployment/webapp/SchedulerInitServlet.class
2500 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/ejb/SchedulerControllerBean.class
482 Mon Aug 09 22:34:24 UTC 2010 com/thortech/xl/scheduler/exception/SchedulerGenericException.class
246 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/exception/TaskAlreadyExistsException.class
344 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/exception/UnableToStopException.class
1162 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/interfaces/SchedulerController.class
458 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/interfaces/SchedulerControllerHome.class
1110 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/interfaces/SchedulerControllerLocal.class
457 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/interfaces/SchedulerControllerLocalHome.class
4193 Mon Aug 09 22:34:58 UTC 2010 com/thortech/xl/scheduler/interfaces/SchedulerControllerUtil.class
1252 Mon Aug 09 22:34:24 UTC 2010 com/thortech/xl/scheduler/tasks/SchedulerBaseTask$XLSchedulerThread.class
6661 Mon Aug 09 22:34:24 UTC 2010 com/thortech/xl/scheduler/tasks/SchedulerBaseTask.class

Schedule job with JOB_CLOSE until a certain time

Hello all,
I'd like to schedule a background job with JOB_CLOSE until a certain time, i.e. first start time at 10 a.m., repitition period 15 min., last start time 1 p.m.
I tried this using parameter LASTSTRTTM, e.g.:
i_startdate = sy-datum.
i_starttime = '100000'.
i_prdmins = '15'.
i_laststrtdt = sy-datum.
i_laststrttm = '130000'.
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
      jobcount             = l_jobcount
      jobname              = 'MY_JOB'
      sdlstrtdt            = i_startdate
      sdlstrttm            = i_starttime
      laststrtdt           = i_laststrtdt
      laststrttm           = i_laststrttm
      prdmins              = i_prdmins
    EXCEPTIONS
      cant_start_immediate = 1
      invalid_startdate    = 2
      jobname_missing      = 3
      job_close_failed     = 4
      job_nosteps          = 5
      job_notex            = 6
      lock_failed          = 7
      OTHERS               = 8.
but I didn't succeed - the job didn't stop at 1 p.m. Any hints?
Best regards
Martin Lehmann

Hi Martin,
i_startdate = sy-datum. " 1st time Job Start Date
i_starttime = '100000'.
i_prdmins = '15'.
i_laststrtdt = sy-datum. " If Job is not started by this date, then it wont be started once this date is completed
i_laststrttm = '130000'.
What it means is, if i want to start a job by 10th Oct.. & expect that it should be started maximum by 20th Oct.. If its 20th Oct & still the job is not started,... then terminate the job & do not start it..
If the job is already started, then it wont stop.
Hope its clear.
Best regards,
Prashant

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

How to schedule Job for data uploading from source to BI

Hi to all,
How to schedule Job for data uploading from source to BI,
Why we required and how we do it.
As I am fresher in BI, I need to know from bottom.
Regards
Pavneet Rana

Hi.
You can create [process chain |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502b2998-1017-2d10-1c8a-a57a35d52bc8?quicklink=index&overridelayout=true]for data loading pocess and schedule start process to any time/date etc ...
Regadrs.

How to stop a Scheduler Job in Oracle BI Publisher 10g

Hello!
Can someone tell me how can I stop a scheduler job in Oracle BI Publisher 10g?
I scheduled a bursting job to run a report but is running during two days.
I would like to stop it.
Thanks.
Edited by: SFONS on 19-Jan-2012 07:16

Unfortunately there is no way to stop a job once it is being executed. Yes as you read, it is not possible once job has started.
Same thing applies for running queries.
Once queries are sent to the DB BIP loses control over them. The message you see (if any) "Click Here to Cancel" does not stop any query
it is just a message.
I guess you will have to stop/kill the process in your DB
regards
Jorge
p.s If you consider your question answered then please mark my answer as *"Correct"* or *"Helpful"*

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

Scheduled Job to gather stats for multiple tables - Oracle 11.2.0.1.0

Hi,
My Oracle DB Version is:
BANNER Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
In our application, we have users uploading files resulting in insert of records into a table. file could contain records ranging from 10000 to 1 million records.
I have written a procedure to bulk insert these records into this table using limit clause. After the insert, i noticed my queries run slow against these tables if huge files are uploaded simultaneously. After gathering stats, the cost reduces and the queries executed faster.
We have 2 such tables which grow based on user file uploads. I would like to schedule a job to gather stats during a non peak hour apart from the nightly automated oracle job for these two tables.
Is there a better way to do this?
I plan to execute the below procedure as a scheduled job using DBMS_SCHEDULER.
--Procedure
create or replace
PROCEDURE p_manual_gather_table_stats AS
TYPE ttab
IS
    TABLE OF VARCHAR2(30) INDEX BY PLS_INTEGER;
    ltab ttab;
BEGIN
    ltab(1) := 'TAB1';
    ltab(2) := 'TAB2';
    FOR i IN ltab.first .. ltab.last
    LOOP
        dbms_stats.gather_table_stats(ownname => USER, tabname => ltab(i) , estimate_percent => dbms_stats.auto_sample_size,
        method_opt => 'for all indexed columns size auto', degree =>
        dbms_stats.auto_degree ,CASCADE => TRUE );
    END LOOP;
END p_manual_gather_table_stats;
--Scheduled Job
BEGIN
    -- Job defined entirely by the CREATE JOB procedure.
    DBMS_SCHEDULER.create_job ( job_name => 'MANUAL_GATHER_TABLE_STATS',
    job_type => 'PLSQL_BLOCK',
    job_action => 'BEGIN p_manual_gather_table_stats; END;',
    start_date => SYSTIMESTAMP,
    repeat_interval => 'FREQ=DAILY; BYHOUR=12;BYMINUTE=45;BYSECOND=0',
    end_date => NULL,
    enabled => TRUE,
    comments => 'Job to manually gather stats for tables: TAB1,TAB2. Runs at 12:45 Daily.');
END;Thanks,
Somiya

The question was, is there a better way, and you partly answered it.
Somiya, you have to be sure the queries have appropriate statistics when the queries are being run. In addition, if the queries are being run while data is being loaded, that is going to slow things down regardless, for several possible reasons, such as resource contention, inappropriate statistics, and having to maintain a read consistent view for each query.
The default collection job decides for each table based on changes it perceives in the data. You probably don't want the default collection job to deal with those tables. You probably do want to do what Dan suggested with the statistics. But it's hard to tell from your description. Is the data volume and distribution volatile? You surely want representative statistics available when each query is started. You may want to use all the plan stability features available to tell the optimizer to do the right thing (see for example http://jonathanlewis.wordpress.com/2011/01/12/fake-baselines/ ). You may want to just give up and use dynamic sampling, I don't know, entire books, blogs and papers have been written on the subject. It's sufficiently advanced technology to appear as magic.

Need to write a procedure for Log files (scheduled jobs)

Hi,
We have around 50 scheduled jobs.Jobs will run parallelly. In these jobs, some jobs will repeat at different timings.in these some jobs are daily jobs and some are weekly and some are monthly and some will run first and second working day of the month and some will run on some particular days.
Now I want to write a procedure like, For every job it should create a log file like "
<Job_Name> started on <Date> at <start_Time(timestamp)> and completed on <Date> at <End_Time(Timestamp)> successfully.
<Job_Name> started on <Date> at <start_Time(timestamp)> and completed on <Date> at <End_Time(Timestamp)> abnormally.
If all jobs complted successfully it should send an email to the mailgroup with attached log file (which contains the details of all the jobs) with format as follows.
Jobname Start_date Start_time End_Date End_Time Status
SALES 21-May-2011 12:00:00 21-May-2011 12:01:00 Completed Successfully
21-May-2011 12:15:00 21-May-2011 12:16:00 Completed successfully
Proudcts 21-May-2011 23:00:00 21-May-2011 23:16:00 Completed successfully
ITEMS 21-May-2011 23:00:00 21-May-2011 23:16:00 Completed successfully
If the status ="Completed abnormally" for any particular job
immediately it should send an mail to the group like " FATAL_MESG_JOBANAME_Date_Time(timestamp)"
for example if SALES job was failed at 15:00:00 then immediately it should send a mail.
if ITEMS got failed then it should mail ( in between any job got failed it should send an email).
if every thing is going cool then need send a final success mail to the group.
so Please let me know how to write a program for this requiremnt.
Thanks in advance.

832581 wrote:
Hi,
Thanks for giving valuable link to gain the knowledge on DBMS_SCHEDULER.
But here I didn't get clear idea to write a program which I need to schedule the job for every 1hr.
Please suggest me to write the program..
ThanksYou'll have to read the link i sent. Or google for an example.

Starting Scheduled JOB by OMBPLUS

Similar Messages

Maybe you are looking for