"BBP_SC_TRANSFER_GROUPED" to run as a scheduled job

Hi,
I need to make the program BBP_SC_TRANSFER_GROUPED, run as a scheduled job. please guide me the steps to do that. Thanks in advance.

Hi Krishna Vardhan,
You can schedule this report using SA38txn.
Input the report name and click on Background tab on the menu bar and in the next screen click on Variants tab on the menu bar and in the next screen click on create tab next to the variant field and create a variant.
Enter the criteria for the variant and click on attributes and enter the short description for variant and also choose the preferences for various attributes and clcik the save icon to save the variant.
Then goto SA38 txn again and input the report name and clcik on the with variant tab on the menu bar and click background tab and enter the required variant name in the next screen and click on Schedule tab and schedule the job periodically based on your requirement.
Hope this makes you more clear and helps in resolving your issue. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Similar Messages

OIM11g: Error while running AD Reconcilliation Schedule Job

Hi All,
I am using OIM 11g BP05 and have deployed AD connector 11.1.1.5.0 using connector server. While running the AD Group/Organization/User Reconcilliation schedule job, I am getting below error in connector logs:
11/8/2012 4:25:59 PM <ERROR>: Class-> ActiveDirectoryUtils Method -> GetDirectoryEntry, Message -> Exception Stack Trace : at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_NativeObject()
at Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryUtils.GetDirectoryEntry(String path, ActiveDirectoryConfiguration configuration) in c:\ADE\aime_oimcp\idc\bundles\dotnet\ActiveDirectory\ActiveDirectoryConnector\ActiveDirectoryUtils.cs:line 1423
11/8/2012 4:25:59 PM <ERROR>: Class-> ActiveDirectoryConnector Method -> ExecuteQuery, Message -> Caught Exception: Unable to get the Directory Entry11/8/2012 4:25:59 PM <ERROR>: Class-> ActiveDirectoryConnector Method -> ExecuteQuery, Message -> Stack Trace: at Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryUtils.GetDirectoryEntry(String path, ActiveDirectoryConfiguration configuration) in c:\ADE\aime_oimcp\idc\bundles\dotnet\ActiveDirectory\ActiveDirectoryConnector\ActiveDirectoryUtils.cs:line 1456
at Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options, Boolean includeDeleted, SortOption sortOption, String serverName, String searchRoot, SearchScope searchScope, OperationOptions otherOptions) in c:\ADE\aime_oimcp\idc\bundles\dotnet\ActiveDirectory\ActiveDirectoryConnector\ActiveDirectoryConnector.cs:line 1048
at Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options) in c:\ADE\aime_oimcp\idc\bundles\dotnet\ActiveDirectory\ActiveDirectoryConnector\ActiveDirectoryConnector.cs:line 814
ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Unable to get the Directory Entry
Also, I am seeing this error in log too:
*11/8/2012 4:25:59 PM <ERROR>: Class-> ActiveDirectoryUtils Method -> GetDirectoryEntry, Message -> Exception occured during the creation of directory entry.*
*11/8/2012 4:25:59 PM <ERROR>: Class-> ActiveDirectoryUtils Method -> GetDirectoryEntry, Message -> Exception Message : An invalid dn syntax has been specified.*
11/8/2012 4:25:59 PM <ERROR>: Class-> ActiveDirectoryUtils Method -> GetDirectoryEntry, Message -> Exception Stack Trace : at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_NativeObject()
at Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryUtils.GetDirectoryEntry(String path, ActiveDirectoryConfiguration configuration) in
Any pointers for resolving this issue?
Regards,
Sunny
Edited by: ajmerasunny on Nov 8, 2012 4:32 PM

Hi All,
My bad, I gave wrong search base. Issue resolved.
However, I need to run the a trusted source recon for only active
Users. I gave filter as useraccountcontrol=512 but got casting exception.
Any pointers on how to specify the filter to get only active accounts from AD?
Regards,
Sunny

DS run longer with scheduled job as compare to manual run

I have scheduled a job through Management Console (MC) to run everyday once at
certain time. After some time, maybe after 15 days of running, the execution
time has increased to double from 17 mins to 67 mins by one time jump. After
that, the job kept running and spent 67 mins to complete.
The nature of the job is to generate around 400 output flat files from a
source db2 table. Under efficient running time, 1 file took around 2 seconds to
generate. But now it became taking 8 seconds to generate one file. The data
volume and nature of the source table didn't change, so that was not the root
cause of increasing time.
I have done several investigations and the results as such:
1) I scheduled again this job at MC to run for testing, it would take 67 mins
to complete. However, if I manually run this job thorough MC, it would take
17 mins efficient time to run.
2) I replicated this job to a second job as a copy. Then I scheduled this
copied job at MC to run, it would take 67 mins to run. But if I manually run
this job through MC, it will take 17 mins to run.
3) I created another test repo and load this job in. I scheduled the job to
run at this new repo, it would take 67 mins to run. If I manually run the job
through MC, it only took 17 mins to run.
4) Finally, I manually executed the job through unix job scripts command,
which is one of the scheduled job entry in the cron file, such as
./DI__4c553b0d_6fe5_4083_8655_11cb0fe230f4_2_r_3_w_n_6_40.sh, the job also would take 17
mins to run to finish.
5) I have recreated the repo to make it clean and reload back the jobs and
recreated again the schedule. Yet it still took 67 mins to run scheduled job.
Therefore, the conclusion is why it takes longer time to run by scheduling
method as compare to manually running method?
Please provide me a way to troubleshoot this problem. Thank you.
OS : HPUX 11.31
DS : BusinessObjects Data Services 12.1.1.0
databasee : DB2 9.1

Yesterday we had done another test and indirectly made the problem to go
away. We changed the generated output flat file directory from current directory
of /fdminst/cmbc/fdm_d/bds/gl to /fdminst/cmbc/fdm_d/bds/config directory to
run, to see any difference would make. We changed the directory pointing
inside Substitution Parameter Configurations windows. Surprisingly, job had
started to run fast and completed in 15 minutes and not 67 minutes anymore.
Then we shifted back and pointed the output directory back to original
/fdminst/cmbc/fdm_d/bds/gl and the job has started to run fast ever since and all
completed in 15 minutes. Even we created ad hoc schedule to run and it was
still running fast.
We not sure why it was solved by shifting directory away and shifting back,
and whether this had to do with BODS problem or HP Unix system environment
problem. Nonetheless, the job is started to run normally and fast now as we
test.

OIM 11 - Error while running scheduled job "Evaluate User Policies"

Hello,
We are trying to run the OOTB scheduled job " EValuate User Policies" with the default parameters. Job history shows the execution status success but diagnostic logs throw the following error. And the users donot get provisioned to their resources based on the access policies.
We are on OIM 11 BP05.
[2013-01-30T10:11:47.072-05:00] [oim_server1] [NOTIFICATION] [IAM-0080006] [oracle.iam.platform.kernel.impl] [tid: Thread-1033] [userId: oiminternal] [ecid: 3f3dc64898fb7625:-13c8cd5d:13c88a6943c:-8000-0000000000000002,1:26684] [APP: oim#11.1.1.3.0] Orchestration process moved to failed stage, and the corresponding error is - {0}[[
oracle.iam.platform.kernel.EventFailedException: Operation - EVALUATE_POLICIES that is submitted as part of the orchestration is not supported.
at oracle.iam.platform.kernel.impl.EntityDefaultActionHandler.execute(EntityDefaultActionHandler.java:53)
at oracle.iam.platform.kernel.impl.DefaultActionHandler.execute(DefaultActionHandler.java:41)
at sun.reflect.GeneratedMethodAccessor5717.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.iam.platform.kernel.impl.EventHandlerDynamicProxy.invoke(EventHandlerDynamicProxy.java:30)
at $Proxy254.execute(Unknown Source)
at oracle.iam.platform.kernel.impl.OrchProcessData.runActionEvents(OrchProcessData.java:1036)
at oracle.iam.platform.kernel.impl.OrchProcessData.runEvents(OrchProcessData.java:644)
at oracle.iam.platform.kernel.impl.OrchProcessData.executeEvents(OrchProcessData.java:227)
at oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.resumeProcess(OrchestrationEngineImpl.java:764)
at oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.process(OrchestrationEngineImpl.java:519)
at oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.orchestrate(OrchestrationEngineImpl.java:459)
at oracle.iam.platform.kernel.impl.OrchestrationEngineImpl.orchestrate(OrchestrationEngineImpl.java:378)
at oracle.iam.accesspolicy.impl.AccessPolicyServiceInternalImpl.evaluatePoliciesForUser(AccessPolicyServiceInternalImpl.java:78)
at oracle.iam.accesspolicy.api.AccessPolicyServiceInternalEJB.evaluatePoliciesForUserx(Unknown Source)
at sun.reflect.GeneratedMethodAccessor5730.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy574.evaluatePoliciesForUserx(Unknown Source)
at oracle.iam.accesspolicy.api.AccessPolicyServiceInternalEJB_bgsblp_AccessPolicyServiceInternalRemoteImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at oracle.iam.accesspolicy.api.AccessPolicyServiceInternalEJB_bgsblp_AccessPolicyServiceInternalRemoteImpl.evaluatePoliciesForUserx(Unknown Source)
at sun.reflect.GeneratedMethodAccessor5727.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
at $Proxy164.evaluatePoliciesForUserx(Unknown Source)
at sun.reflect.GeneratedMethodAccessor5726.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
at $Proxy421.evaluatePoliciesForUserx(Unknown Source)
at oracle.iam.accesspolicy.api.AccessPolicyServiceInternalDelegate.evaluatePoliciesForUser(Unknown Source)
at com.thortech.xl.schedule.tasks.tcTskUsrEvaluatePolicies$PolicyEvalWorker.run(tcTskUsrEvaluatePolicies.java:319)
at java.lang.Thread.run(Thread.java:662)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask$XLSchedulerThread.run(SchedulerBaseTask.java:157)
[2013-01-30T10:11:47.081-05:00] [oim_server1] [NOTIFICATION] [IAM-0080046] [oracle.iam.platform.kernel.impl] [tid: Thread-1030] [userId: oiminternal] [ecid: 3f3dc64898fb7625:-13c8cd5d:13c88a6943c:-8al.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
        at oracle.iam.accesspolicy.api.AccessPolicyServiceInternalEJB_bgsblp_AccessPolicyServiceInternalRemoteImpl.evaluatePoliciesForUserx(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor5727.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
        at $Proxy164.evaluatePoliciesForUserx(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor5726.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
        at $Proxy421.evaluatePoliciesForUserx(Unknown Source)
        at oracle.iam.accesspolicy.api.AccessPolicyServiceInternalDelegate.evaluatePoliciesForUser(Unknown Source)
        at com.thortech.xl.schedule.tasks.tcTskUsrEvaluatePolicies$PolicyEvalWorker.run(tcTskUsrEvaluatePolicies.java:319)
        at java.lang.Thread.run(Thread.java:662)
        at com.thortech.xl.scheduler.tasks.SchedulerBaseTask$XLSchedulerThread.run(SchedulerBaseTask.java:157)
Any answer is highly appreciated.
Thanks,
MBiswal

Ok, did you reimported the /metadata/iam-features-accesspolicy/event-definition/EventHandlers.xml from the BundlePatch folder?
Have you followed Addendum to OIM 11.1.1.5.6 Bundle Patch 06 Readme (Doc ID 1543504.1)?

How to Schedule Jobs to only run during a time window

I have a long running task that needs to schedule jobs to process data.
I only want these scheduled jobs to start during a specific window of time each day, probably 10:00 PM to 6:00 AM.
If the scheduled jobs do not begin during the specified time frame, they must wait until the next day to start running.
Each scheduled job will only be executed once and then auto dropped.
How should I go about creating these scheduled jobs?

Hi Jeff,
I agree that the documentation isn't clear enough about the purpose of windows.
You can indeed use windows for changing the resource plan, but you can also use them for scheduling your jobs.
I did a simple test in real-time to illustrate the latter.
At around 10.30 am today I created a table that will populated by a job:
CREATE TABLE TEST_WINDOW_TABLE(EVENT_DATE DATE);
Then, I created a window whose start_date is today at 10.40 am :
dbms_scheduler.create_window(
                             window_name     =>'TEST_WINDOW',
                             resource_plan   => NULL,
                             start_date      => to_date('10/04/2014 10:40:00', 'dd/mm/yyyy hh24:mi:ss'),
                             repeat_interval => NULL,
                             duration        =>interval '5' minute
You can see that this window doesn't have a resource plan, and its repeat interval is NULL (so it will be opened only once).
The window will stay open for 5 minutes.
Finally, I created a one-off job whose schedule is the previously created window:
DBMS_SCHEDULER.create_job (
                           job_name      => 'TEST_WINDOW_JOB',
                           job_type      => 'PLSQL_BLOCK',
                           job_action    => 'BEGIN insert into test_window_table values (sysdate); COMMIT; END;',
                           schedule_name => 'SYS.TEST_WINDOW',
                           enabled       => true,
                           auto_drop     => true
Checking the user_scheduler_job_log before 10.40 would return no rows, which mean the job hasn't started yet since the window was not open.
Now, from 10.40, it shows one entry:
SQL> select log_date, status from user_scheduler_job_log where job_name = 'TEST_WINDOW_JOB';
LOG_DATE                                                                         STATUS
10/04/14 10:40:02,106000 +02:00                                                  SUCCEEDED
The TEST_WINDOW_TABLE has also got the row:
SQL> select * from TEST_WINDOW_TABLE;
EVENT_DATE
10/04/2014 10:40:02
Voilà.
In your case, since you want to run the jobs daily between 10 pm and 6 am (duration of 8 hours), the window would look like this:
dbms_scheduler.create_window(
                             window_name     =>'YOUR_WINDOW',
                             resource_plan   => NULL,
                             repeat_interval => 'freq=daily;byhour=22;byminute=0;bysecond=0',
                             duration        =>interval '8' hour
For your jobs, you may need to specify an end_date if you want to make sure the job gets dropped if it couldn't run in its window.

Problem with variable in scheduled job

I'm trying to get the following scheduled job to run:
switch(config)# scheduler job name backup_job
switch(config-job)# cli var name timestamp $(TIMESTAMP) ; copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp) ; copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4/
switch(config-job)# exit
switch(config)# scheduler schedule name backup_timetable
switch(config-schedule)# job name backup_job
switch(config-schedule)# time daily 1:23
switch(config-schedule)# exit
switch(config)# exit
This job is taken directly from multiple Cisco MDS and Nexus documents. From what I can tell, the purpose of this job is to save the running configuration to a file on bootflash with date & time in the file name and then to copy the file from bootflash to tftp server.
I can create the job and schedule successfully:
switch(config)#show scheduler job name backup_job
Job Name: backup_job
cli var name timestamp $(TIMESTAMP)
copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp)
copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4
==============================================================================
switch(config)#show scheduler schedule name backup_timetable
Schedule Name       : backup_timetable
User Name           : admin
Schedule Type       : Run every day at 10 Hrs 48 Mins
Last Execution Time : Tue Mar 6 10:48:00 2012
Last Completion Time: Tue Mar 6 10:48:00 2012
Execution count     : 1
     Job Name            Last Execution Status
backup_job                        Success (0)
==============================================================================
The scheduled job runs successfully but the files that are created have the variable $(TIMESTAMP) in the file name instead of the actual date and time e.g. switch-cfg.$(TIMESTAMP)
The logfile contains the following:
Schedule Name : backup_timetable                  User Name : admin
Completion time: Tue Mar 6 10:59:26 2012
--------------------------------- Job Output ---------------------------------
`cli var name timestamp $(TIMESTAMP)`
`copy running-config bootflash:/PEN-9509-2-cfg.$(TIMESTAMP) `
Copy complete, now saving to disk (please wait)...
`copy bootflash:/PEN-9509-2-cfg.$(TIMESTAMP) tftp://1.2.3.4 `
Trying to connect to tftp server......
Connection to server Established. Copying Started.....
It looks to me that the $(timestamp) variable is being created successfully and is being replaced with the $(TIMESTAMP) variable but this is not being replaced with the actual date and time.
The thing I don't get is that this looks to me that we're trying to nest variables and the same Cisco documents from which I get this configuration also state that nested variables are not allowed.
I have tried this on different hardware - MDS9500, MDS9100, Nexus 5000, Nexus 7000 and different software - SAN-OS 3.3, NX-OS 4.1, NX-OS 5.2 but cannot get it to work. I have also tried to put the commands in a script and run with the run-script command but it still does not work.
There is probably another method to achieve what this configuration is trying to achieve (and I would like to know if there is) but I want to know if this particular configuration will work.
Can anyone tell me if they have got this working or can see what I'm doing wrong or can try running this in a lab please?

I managed to get this resolved with a bit of a workaround. If I put the copy commands in a script and pass the variable to the run-script command as part of the scheduled job then it works ok. Trying to create the variable within the script (or as a separate scheduled job command) still doesn’t work.
So, creating a script file (script) as follows:
copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp)
copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4
and creating a scheduled job with the following command:
run-script bootflash:script timestamp=”$(TIMESTAMP)”
achieves the desired result.

Scheduling jobs in OWB 10.2

I'm busy with a migration of OWB 10.1 to 10.2 and I had almost everything up and running
except
the scheduled jobs.
In 10.1 my predecessors made scheduled jobs which started in their turn a procedure which then started the process flow with wb_rt_api_exec.
After migration I could not get those jobs going anymore.
After investigation I could see that the procedures (starting the proess flows) ran when started with the runtime rrepository owner as launcher.
Even te jobs ran when they were started with the session credentials (iow the credentials from the logged on user being the runtime repository owner).
I've seen the atricles telling that you need to set the preferred credentials to the runtime repository owner in oem if you want to get it running from there.
Anyhow I could start it by recreating the jobs with the runtime repository owner as the creator.
Doens anybody know why it could run in owb 10.1 with sys as creator and why it nn longer works in 10.2.
I checked the 10.1 installation and I haven't found any priviileges granted to sys that where not granted in the 10.2 installation, so there is no diff.
Any help would be welcome.

Hi,
You cannot schedule direct mapping. You need create Process flow then u need to attach calendar for that. Go to Control Centre Deploy process flow and schedule and further click on start.
Regards,
Ava

Troubled to get scheduler job to run?

Hi all friends:
I'm having trouble getting any scheduler jobs (here, troubled job name is CUSTMASTER_CHANGES_01) to actually run.
when
sql>select job_name,state,enabled,retry_count,failure_count,run_count,restartable,start_date,repeat_interval,job_class
from all_scheduler_jobs;
JOB_NAME STATE ENABL RETRY_COUNT FAILURE_COUNT RUN_COUNT RESTA START_DATE REPEAT_INTERVAL JOB_CLASS
CUSTMASTER_CHANGES_01 SCHEDULED TRUE 0 0 0 FALSE 14-JAN-08 09.46.14.6 FREQ=SECONDLY;I SCANNER_JO
72965 AM AMERICA/NEW NTERVAL=5 B_CLASS
_YORK
for job 'CUSTMASTER_CHANGES_01'
we can see RUN_COUNT 0 and restartable false.
I upped slave processes to 5. dbms_scheduler.run_job('CUSTMASTER_CHANGES_01') works, but it's still not executing on the schedule
when run as sysdba
SQL> exec dbms_scheduler.run_job('CUSTMASTER_CHANGES_01');
ERROR at line 1:
ORA-27475: "SYS.CUSTMASTER_CHANGES_01" must be a job
ORA-06512: at "SYS.DBMS_ISCHED", line 150
ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
ORA-06512: at line 1
to resolve that,
we found
When you create your job by using dbsm_scheduler, it has a parameter called ‘auto_drop’, is by default, =’true’, like, auto_drop => TRUE
see below;
dbms_scheduler.create_job(
job_name IN VARCHAR2,
job_type IN VARCHAR2,
job_action IN VARCHAR2,
number_of_arguments IN PLS_INTEGER DEFAULT 0,
start_date IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
repeat_interval IN VARCHAR2 DEFAULT NULL,
end_date IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
job_class IN VARCHAR2 DEFAULT 'DEFAULT_JOB_CLASS',
enabled IN BOOLEAN DEFAULT FALSE,
auto_drop IN BOOLEAN DEFAULT TRUE,
comments IN VARCHAR2 DEFAULT NULL);
The job you manually run once and then it drops itself when you test.
so I am specifiying auto_drop to be false, but it is showing it has true as the attribute.
DBMS_SCHEDULER.CREATE_JOB(
job_name => scanner.scanner_name,
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN IF EEG_SCAN.GET_RUNNING_JOBS_COUNT('
||''''||UPPER(scanner.scanner_name)||''''
||') < 2 THEN '||scanner.scanner_proc_name||'; END IF; END;',
repeat_interval => 'FREQ=SECONDLY;INTERVAL=5',
job_class => c_job_class_name,
auto_drop => FALSE,
enabled => true
scheduler job is still not working as expected.....?
Can you help me for this??
thanks a lot in advance.
Message was edited by:
jerrygreat
Message was edited by:
jerrygreat

Hi,
There are a few other limits you could check .
Make sure that you have not exceeded the maximum number of sessions or the maximum number of processes or the maximum number of scheduler jobs
select * from dba_scheduler_global_attribute;
and
select name,value from v$parameter where name like '%process%';
select name,value from v$parameter where name like '%session%';
Also check how many jobs are currently running
select count(*) from dba_scheduler_running_jobs;
select count(*) from dba_jobs_running ;
select count(*) from v$session ;
One of these limits may need to be increased.
The run_job succeeds because it runs in the current session by default, if you use use_current_session=>false, does it still work ?
Also auto_drop only drops the job when it has completed e.g. past its end_date or exceeded its max_runs.
Finally note that there is a dedicated forum for dbms_scheduler located here
Scheduler
Hope this helps,
Ravi.

Error while running schedule jobs in oim 11 gr2

Hello,
         I have create the custom schedule job.for which i have create the java call and the plugin.xml file and i have successfully register it to oim
             ,then i have create the metadata scheduler xml and import it to mds using wlst.
          then i have cretae the schedule job in oim advance tab.but when i run that task the console propmt the error
<Jun 13, 2013 5:47:19 PM IST> <Warning> <oracle.iam.scheduler.impl> <BEA-000000> <XSD Validation Exception: org.xml.sax.SAXParseException: cvc-elt.1: Cannot f
ind the declaration of element 'scheduledTasks'.>
<Jun 13, 2013 5:48:51 PM IST> <Error> <oracle.iam.transUI.impl> <BEA-000000> <ADP ClassLoader failed to load: com.oracle.demo.oim.scheduled.NotificationDemoSc
heduledTask>
please help how to resolve this error
regards,
Tushar

Check your scheduler xml. I hope XSD validation exception points to invalid scheduler xml file. It should look something like this sample
<scheduledTasks xmlns="http://xmlns.oracle.com/oim/scheduler">
   <task>
      <name>Lookup Recon Scheduled Task</name>
<class>oracle.iam.samples.schtasks.LookupReconScheduledTask</class>
      <description>Lookup recon Scheduled Task</description>
      <retry>5</retry>
      <parameters>
          <string-param required="true" helpText="Name of the Lookup code">Lookup Code Name</string-param>
</parameters>
   </task>
</scheduledTasks>

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

DBMS_SCHEDULER.RUN_JOB causes scheduled job not to run again

Environment: 10.2.0.2 Linux 64-bit
Hi,
I have some DBMS_SCHEDULER chain jobs scheduled to run every hour which has been running fine with no issues for a while now.
I needed to run a couple of jobs manually in-between scheduled times so I ran the job using DBMS_SCHEDULER.RUN_JOB, and that worked as expected as it has done in the past.
This issue is that the jobs I ran manually haven't run at their scheduled time since I did that. The only way around it was to recreate the job completely.
Any idea if this is normal functionality, or should I be raising this as a possible issue through Oracle Metalink?
Any help or ideas would be much appreciated.
Thanks
Tim

Hi Tim,
This is a known bug which is tracked internally by bug #5705385. It will be fixed in the next patchsets for 10.2 and 11.1 (i.e. 10.2.0.5 and 11.1.0.7) . If you urgently need a fix, an official patch seems to be available for 10.2.0.3 .
There does seem to be a workaround - using run_job again after the first run_job has completed will not do anything but the chain job should again run on schedule.
Hope this helps,
Ravi.

Scheduled jobs are not running DPM 2012 R2

Hi,
Recently upgraded my dpm 2012 sp1 to 2012 R2 and upgrade went well but i got 'Connection to the DPM service has been lost.(event id:917 and other event ids in the eventlog errors ike '999,997)'. Few dpm backups are success and most of the dpm backups consistenancy
checks are failed.
After investigating the log files and found two SQL server services running in the dpm 2012 r2 server those are 'sql server 2010 & sql server 2012 'service. Then i stopped sql 2010 server service and started only sql server 2012 service using (.\MICROSOFT$DPM$Acct).
Now 'dpm console issue has gone (event id:917) but new issue ocurred 'all the scheduled job are not running' but manully i can able to run all backup without any issues. i am getting below mentioned event log errors
Log Name: Application
Source: SQLAgent$MSDPM2012
Date: 7/20/2014 4:00:01 AM
Event ID: 208
Task Category: Job Engine
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
SQL Server Scheduled Job '7531f5a5-96a9-4f75-97fe-4008ad3c70a8' (0xD873C2CCAF984A4BB6C18484169007A6) - Status: Failed - Invoked on: 2014-07-20 04:00:00 - Message: The job failed. The Job was invoked by Schedule 443 (Schedule 1). The last step to
run was step 1 (Default JobStep).
Description:
Fault bucket , type 0
Event Name: DPMException
Response: Not available
Cab Id: 0
Problem signature:
P1: TriggerJob
P2: 4.2.1205.0
P3: TriggerJob.exe
P4: 4.2.1205.0
P5: System.UnauthorizedAccessException
P6: System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal
P7: 33431035
P8:
P9:
P10:
Log Name: Application
Source: MSDPM
Date: 7/20/2014 4:00:01 AM
Event ID: 976
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
The description for Event ID 976 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The DPM job failed because it could not contact the DPM engine.
Problem Details:
<JobTriggerFailed><__System><ID>9</ID><Seq>0</Seq><TimeCreated>7/20/2014 8:00:01 AM</TimeCreated><Source>TriggerJob.cs</Source><Line>76</Line><HasError>True</HasError></__System><Tags><JobSchedule
/></Tags></JobTriggerFailed>
the message resource is present but the message is not found in the string/message table
plz help me to resolve this error.
jacob

Hi,
i would try to reinstall DPM
Backup DB
uninstall DPM
Install DPM same Version like before
restore DPM DB
run dpmsync.exe -sync
finished
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

Scheduled jobs do not run as expected after upgrading to 10.2.0.3 or 4

FYI, we've had a ticket open for several days because our scheduled jobs (dbms_scheduler) would no longer run as scheduled after an upgrade to 10.2.0.4 on HPUX, couldn't find the solution by searching in metalink, nor did I find it here or using Google - obviously I wasn't searching correctly. There is a note id that references a set of steps that appears to have resolved our problem. I am putting this note out here so that if you encountered the same difficulty you may come across this note earlier in your troubleshooting efforts rather than later. The full title of the note is: 'Scheduled jobs do not run as expected after upgrading to either 10.2.0.3 or 10.2.0.4'. The Doc ID is: 731678.1.

Thanks - our ticket should be getting closed out on it (our dba will be updating it), the scheduler has been running reliably since we took the steps in the doc mentioned.

F110 APP run - Payment run has been scheduled, but job was not released

Dear Friends,
We have made payment parameters, payment proposal, edit payment proposal and it was working fine upto that stage.
Parameters have been entered
Payment proposal has been created
Payment proposal has been edited
But when we selected payment run, immediately it showed the below status:
Payment run has been scheduled 17.01.08 12:59:55
Job was not released
Also I'm not able to delete the Payment run made, fields are in disabled mode.
Please guide me how to resolve this issue.
Thanks in advance for your help.
Regards,
Dwarak.

Dear Supriya,
Thanks a lot for your immediate response.
Still the same problem is existing even after one and half hours.
ie.,
Payment run has been scheduled 17.01.08 12:59:55
Job was not released
Could you please let me know which Tcode we have to go to release this inorder to solve this issue.
As it is in the production client, it would be really helpful if you could let me know the details at the earliest.
Thanks again.
Regards,
Dwarak.

Event based scheduler job - 2 events at the same time only 1 run

Hi,
i converted our dbms_job - jobs to the newer package dbms_scheduler.
It is a 10.2.0.4 patch 23(8609347) database on an windows server 2003 R2 Enterprise x64 Edition SP2.
The Jobs(about 130) are nothing special ... only some statistics, matview-refreshes and so on.
For the notification of failed jobs and jobs which run over the max_run_duration i downloaded and installed the job notification package.
The jobs are assigned to different departments and the corresponding developer teams in our company.
I created a notification job for each department and if a job fails we (the database administrators) and the corresponding deverlopers will be informed.
Now i ascertained that only 1 email will be send if 2 jobs of the same department fails at the same time.
The emailer-jobs are auto-generated by the job notification package. I only modified them to look after all jobs of special department and not only after one job. (--> event_condition ... object_name LIKE 'XXX%')
example for dba-jobs(copy of the script output of TOAD):
SYS.DBMS_SCHEDULER.CREATE_JOB
       job_name        => 'DBA_JOBS_EMAILER'
      ,start_date      => NULL
      ,event_condition => tab.user_data.object_name LIKE ''DBA%'' AND tab.user_data.event_type in (''JOB_FAILED'',''JOB_OVER_MAX_DUR'')'
      ,queue_spec      => 'SYS.SCHEDULER$_EVENT_QUEUE, JOB_FAILED_AGENT'
      ,end_date        => NULL
      ,program_name    => 'SYS.EMAIL_NOTIFICATION_PROGRAM'
      ,comments        => 'Auto-generated job to send email alerts for jobs "DBA%"'
    );I thought that a queue is used to manage all events from the scheduler jobs. So i made a test with 2 dba jobs and simulated a failure at the same time but i received only one mail.
So what is happend with the second event? I looked for the events in the qtab(SCHEDULER$_EVENT_QTAB) which belongs to the event queue(SYS.SCHEDULER$_EVENT_QUEUE) and no event was missing.
So i think the emailer job has to run 2 times.
Is anyone able to explain or to find my mistake?
I know that the easiest way is to create one emailer job for each normal job but i think this is a little bit costly because all the arguments are the same for one department.
Thanks & Regards

Thanks for your fast answer.
You are right with the "enabled => TRUE;" part and i only forgot to post it.
So the Job is enabled (otherwise it would not send any mail). Because it is sending one mail i think it is also not necessary to hand over a job_type.
Additionally the job starts a program ... so it is right to set the job_type='STORED_PROCEDURE' isn't it?
And also right ... i already added the agent as subscriber to the queue.
Anyway i think the whole thing do what it have to do. So in my oppinion there are no big mistakes in creating the job or at adding the subscriber.
There are also no problem in raising the events by itself and enqueue them in the scheduler event queue.
There is only a problem when 2 jobs fails (or run out ouf max duration) at exactly the same time.
If i understand it right:
The agent/subscriber will find the "JOB_FAILED"-event for the first Job in the queue and starts the emailer Job.
The agent will also find the "JOB_FAILED"-event for the second Job and wants to start the emailer Job again.
I don't know if this is really the problem but perhaps the emailer-job can not be started in consequence of the second event because ist is already running.
I also don't know if this is a mistake of the agent or of the emailer-job by itself.
I only want that it runs two times (one run for each event). I my case it also doesn't matter which email is send at first.

"BBP_SC_TRANSFER_GROUPED" to run as a scheduled job

Similar Messages

Maybe you are looking for