Stop Job scheduler

We have set up some jobs to run through the job scheduler in OEM. We still have jobs running though the old job scheduler. To stop the old jobs we issue the command
alter session set job_queue_processes=0
This does not stop the jobs we have running through the new job scheduler. How can we stop them? Is there a parameter that we can easily set to stop and start them like the old job_queue_processes or do we have to go to each job to do it?
We clone our production DB to our test environments and when they come up we need things to be shut off until we make changes to some of the production data. Is there an easy way to shut off the job scheduler?

Hi, JOB_QUEUE_PROCESSES specifies the maximum number of processes that can be created for the execution of jobs, if you need disable all jobs you must execute
alter system set job_queue_processes=0;
If you need stop the any job when they are runnning you must the stop manually with dbms_job.stop(jobid);.
Luck.
Have a good day.
Regards,

Similar Messages

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"*

How to stop a scheduled job using OMB*Plus ?

Hello everyone,
I use a OMB*Plus script to deploy a project in various environments. This includes scheduled jobs.
In this context, I need to stop the schedules of the previous versions to avoid a script crash.
I found the OMBSTOP command thad could do, but I need to retrieve the job ID of the schedule I want to stop. And I don't know how to get the Job ID.
I could get it from a previous launch and save it somewhere, but it wouldn't work if the schedule was manually stopped and restarted. Maybe is there a command that lists the running / scheduled jobs and their IDs? I didn't find it.
Thanks in advance for your help.
Cedric.

Frankly, I cannot see where this is available via pure OMB+, however you could back-door it if if you can figure out how to get these values from the public views (I would guess from the "Scheduling Views" section at http://download-east.oracle.com/docs/cd/B31080_01/doc/owb.102/b28225/toc.htm).
Then you could use my SQL library from OMB+ to get these values and stop the schedules before deploying. you can save this file as omb_sql_library.tcl and then just "source /path/to/omb_sql_library.tcl in your own script to make the functions available in your script.
{code}
package require java
# PVCS Version Information
#/* $Workfile: omb_sql_library.tcl $ $Revision: 1.0 $ */
#/* $Author: $
#/* $Date: 03 Apr 2008 13:43:34 $ */
proc oracleConnect { serverName databaseName portNumber username password } {
# import required classes
java::import java.sql.Connection
java::import java.sql.DriverManager
java::import java.sql.ResultSet
java::import java.sql.SQLWarning
java::import java.sql.Statement
java::import java.sql.CallableStatement
java::import java.sql.ResultSetMetaData
java::import java.sql.DatabaseMetaData
java::import java.sql.Types
java::import oracle.jdbc.OracleDatabaseMetaData
# load database driver .
java::call Class forName oracle.jdbc.OracleDriver
# set the connection url.
append url jdbc:oracle:thin
append url :
append url $username
append url /
append url $password
append url "@"
append url $serverName
append url :
append url $portNumber
append url :
append url $databaseName
set oraConnection [ java::call DriverManager getConnection $url ]
set oraDatabaseMetaData [ $oraConnection getMetaData ]
set oraDatabaseVersion [ $oraDatabaseMetaData getDatabaseProductVersion ]
puts "Connected to: $url"
puts "$oraDatabaseVersion"
return $oraConnection
proc oracleDisconnect { oraConnect } {
$oraConnect close
proc oraJDBCType { oraType } {
#translation of JDBC types as defined in XOPEN interface
set rv "NUMBER"
switch $oraType {
"0" {set rv "NULL"}
"1" {set rv "CHAR"}
"2" {set rv "NUMBER"}
"3" {set rv "DECIMAL"}
"4" {set rv "INTEGER"}
"5" {set rv "SMALLINT"}
"6" {set rv "FLOAT"}
"7" {set rv "REAL"}
"8" {set rv "DOUBLE"}
"12" {set rv "VARCHAR"}
"16" {set rv "BOOLEAN"}
"91" {set rv "DATE"}
"92" {set rv "TIME"}
"93" {set rv "TIMESTAMP"}
default {set rv "OBJECT"}
return $rv
proc oracleQuery { oraConnect oraQuery } {
set oraStatement [ $oraConnect createStatement ]
set oraResults [ $oraStatement executeQuery $oraQuery ]
# The following metadata dump is not required, but will be a helpfull sort of thing
# if ever want to really build an abstraction layer
set oraResultsMetaData [ $oraResults getMetaData ]
set columnCount [ $oraResultsMetaData getColumnCount ]
set i 1
#puts "ResultSet Metadata:"
while { $i <= $columnCount} {
set fname [ $oraResultsMetaData getColumnName $i]
set ftype [oraJDBCType [ $oraResultsMetaData getColumnType $i]]
#puts "Output Field $i Name: $fname Type: $ftype"
incr i
# end of metadata dump
return $oraResults
# SAMPLE CODE to run a quick query and dump the results. #
#set oraConn [ oracleConnect myserver orcl 1555 scott tiger ]
#set oraRs [ oracleQuery $oraConn "select name, count(*) numlines from user_source group by name" ]
#for each row in the result set
#while {[$oraRs next]} {
#grab the field values
# set procName [$oraRs getString name]
# set procCount [$oraRs getInt numlines]
# puts "Program unit $procName comprises $procCount lines"
#$oraRs close
#oracleDisconnect $oraConn
{code}
So you would want to connect to the control center, query for scheduled jobs, stop them, and then continue on with your deployment. I assume that you also need to pause and check that an scheduled job in mid-run has time to exit before moving ahead. You could do a sleep loop querying against system tables looking for active sessions running mappings and waiting until they are all done or something if you really want to bulletproof the process.
Hope this helps,
Mike

How do we stop the scheduled job ?

Hi all,
how do we stop the scheduled job if it is already been scheduled and running in the background.
please send your suggestions,
Rajesh.

Hi Rajesh
Each and every job is associated with a Job Number, you need to specify the exact number to extract the correct details.
Please check table: <b>TBTCO</b> for the same. For more details refer to tables of pattern TBTC*.
Kind Regards
Eswar

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

STOPPED JOBS with expdp and dbms_scheduler

Hello.
I am working with the 10g release 2 in a RAC enviroment, and i am trying to put an export job at the scheduler.
To launch the export i have make a shell script, then first exec the export process and after launch a bzip2 command to compress the resultant dmp file.
The problem is that the export process finish ok, but it don't compress the file, because the scheduler mark the job as STOPPED.
The log say:
REASON="Stop job with force called by user: 'SYS'"
and the expdp S.O process that launch the extjobo stay runing for ever, like if it was waiting for the expdp to exit and it can`t so the script never arrive to the part that compress the file.
I put the script that i make to export the schema:
#!/bin/bash
export ORACLE_HOME=/opt/oracle/product/10.2.0/db
export PATH=$PATH:$ORACLE_HOME/bin
export DIRBACK=/ORACLE/BACKUPS/BMR/Dumps
export dia=`date +%d_%m_%Y_%H_%M_%S`
export LOG=dump_backup_bmr_$dia.log
cd $DIRBACK
$ORACLE_HOME/bin/expdp userid=oracle_backup/orabck@BMR dumpfile="BMR_BMR_$dia.dmp" schemas=BMR directory=Dumps logfile=$LOG
cd $DIRBACK
/usr/bin/bzip2 -f --best ./BMR_BMR_$dia.dmp
cd $DIRBACK
/bin/mail -s "DUMP BACKUP BMR DIARIO [$dia]" [email protected] < ./dump_backup_bmr_$dia.log
I have put several cd $DIRBACK to see if it fail because the script don`t find the dmp file.
Any idea why it STOP after finish the script ?
PD: sorry for my poor english.
Regards

Hi,
A stop is only done in two cases - if the user calls dbms_scheduler.stop_job or if the database is shutdown while a job is running. Make sure the database is not being shutdown while the job is running or inside of the job.
If expdp is still running then this suggests that it is hanging. One possibility for that is that expdp is generating a lot of standard error messages and hanging the job (this is a known issue in 10gR2). You can try redirecting standard output and error to files to see if this helps.
e.g.
$ORACLE_HOME/bin/expdp > /tmp/output 2> /tmp/errors
Hope this helps,
Ravi.

Error occured while posting the job schedule for JDBCAdapter

Hi Experts,
In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:
#/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util
##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)
#J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0
#Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain
###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#
Frequently are created Lock's and I need remove them in Visual Admin.
Any idea about this error?
Tks in advance.

Hi,
After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.
But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.
Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.
I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.
Any ideas?
Thanks in advance.

NWA Job scheduler, how to change parameters?

Dear guys,
moving to AEX (java-only) the ABAP Stack is gone.
Regarding job scheduling there is no more transaction sm37, but Job scheduler within NWA to be used for scheduling jobs.
I configured a job for the predefined job definition AlertConsumerJob to get emails in case of alerts.
Doing this the questions arises how to change parameters once a job is scheduled e.g. add additional email receiver.
So far is seems you have to stop the configured job and define a NEW one from scratch by providing all job parameters. It seems not possible to adjust a job.
This is not very comfortable?
Is there an workaround / solution for this?
Best regards
Jochen

Hello Gaurav
thanks for your reply.
It's a pity, but shows that there is still some room of improvement regarding AEX functionality (java only)
Best regards
Jochen

To stop all scheduling in Business Objects 4.0

Hi
I just want to stop all the scheduled reports to run in Business Objects
Which process should i stop for it ?
Is it Adaptive Job Processor?
This is why i need it
We have migrated our BO from 3.1 to 4.0 in UNIX environment so its a prod parallel environment
and we are going to keep the old production environment running too for a week just to test the new one is fine or no.
But for 4.0 we have new prod environment and new CMS database
Next we are going to get all the data using BO Upgrade Tool
As Unix has complete upgrade it will get all the scheduling info too
Now i don't want the reports to run in our old production environment and new too
So which process should i stop which will only stop the Scheduling and wont impact other part.

Priyanka,
You need to STOP the Adaptive Job Server, this will STOP all scheduling jobs.
Regards,
Ajay

Jobs Scheduled But Never Run or EM jobs remain in 'running' status

Hi All,
Please I need help on this: I have job scheduled through Oracle Enterprise Manager (OEM) but each time our Windows server is shutdown for patches update the job I scheduled failed and in the status column it shows that the job is still running ( Note: I do know how to stop/delete this job) BUT I will like to know if there's anything I need to do so that each time our server is shutdown the scheduled job will not fail to run.
Thanks
Wale

Jobs Scheduled But Never Run or EM jobs remain in 'running' status what is the output of user_jobs and user_jobs_running views when this happens? especially last_date, last_sec, failures, broken columns.

Errors in job scheduled SSIS package

A job scheduled for SSIS package failed with the below errors:
Microsoft (R) SQL Server Execute Package Utility Version 10.50.4321.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 5:00:02 AM
Error: 2015-01-02 05:06:39.25
Code: 0xC0202009
Source: Data Flow Task OLE DB Destination [46]
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 10.0"
Hresult: 0x80004005
Description: "Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary
space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.". End Error Error: 2015-01-02 05:06:39.42
Code: 0xC0209029
Source: Data Flow Task OLE DB Destination [46]
Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (59)"
failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (59)" specifies failure on error. An error occurred on the specified object of the specified component. There may be
error messages posted before this with more information about the failure.
End Error Error: 2015-01-02 05:06:39.44
Code: 0xC0047022
Source: Data Flow Task SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Destination" (46) failed
with error code 0xC0209029 while processing input "OLE DB Destination Input" (59). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow
task to stop running. There may be error messages posted before this with more information about the failure.
End Error Error: 2015-01-02 05:06:39.48
Code: 0xC02020C4
Source: Data Flow Task Flat File Source [1]
Description: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
End Error Error: 2015-01-02 05:06:39.50
Code: 0xC0047038
Source: Data Flow Task SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Flat File Source" (1) returned
error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error
messages posted before this with more information about the failure.
End Error Error: 2015-01-02 05:16:23.49
Code: 0x00000000
Source: Execute SQL Task 1
Description: Could not allocate space for object 'bo.TLE'.'PK_new' in database because the 'PRIMARY' filegroup is full. Create disk space
by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
End Error Error: 2015-01-02 05:16:23.70
Code: 0xC002F210
Source: Execute SQL Task 1 Execute SQL Task
Description: Executing the query "Sp_load" failed with the following error: "Warning: Null value is eliminated by an aggregate
or other SET operation.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 5:00:02 AM
Finished: 5:16:27 AM
Elapsed: 984.928 seconds. The package execution failed. The step failed.
Please help!!!!

Hi,
Based on the error message” Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth
on for existing files in the filegroup”, we can know that the issue is caused by the there is no sufficient disk space in filegroup 'PRIMARY' for the database.
To fix this issue, we can add additional files to the filegroup by add a new file to the PRIMARY filegroup on Files page, or setting Autogrowth on for existing files in the filegroup to increase the necessary space.
As to the issue that the job executed successfully for the next run when executed, I think it can be caused by someone or something had made something to increase the space.
The following document about Add Data or Log Files to a Database is for your reference:
http://msdn.microsoft.com/en-us/library/ms189253.aspx
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SMW2 - Inbound , need to set STOP jobs to automatically delete

Hi
We set the system to receive data from ECC 6.0 system to SRM to inbound queue (SMQ2). There was specific data that we needed for processing and the other set to STOP in SMQ2. The ones that are in the QUEUE are holding back the the active one. We have to delete the STOP jobs to for the active one to process. Is there a way of setting a schedule for STOP job to automatically delete
Regards
Naziem Mahomed

usually a queue is stopped , if there is any problem.
You need to resolve the problem in the queue , and then once that is resolved... ,following queues will go through.
how ever it is not possible to automatially remove the stop queues , unless you have custom program to remove the stopped entries...

How to stop the schedule pakage

Hai Experts,
I have scheduled a package for print process at hourly basis and now i would like to stop the job.so how to do tht.i tried by going to scheduling tab but unable to find to delete the job schedule process .so how to do tht..?
Thanks in advance..
Suri

hai Roberto,
thnks fr u r reply .
but i sm37 i can stop the active jobs only only but my jb is not in active status.so how to proceed and one more thing is i would like to stop my job permanently not for temporary.
as we can see the scheduled /released / active /ready /finished jobs in sm37 but all this we can see when the job have started ..so i want my job to stop permanently.
hope u understand my problem..
Regards,
Suri

ASE 15.7 Job Scheduler won´t start again

Hi,
we encoutered the following problem in our ECC6.0 / EHP5 on ASE 15.7 PL 122 System:
DBACockpit / Collector Configuration shows the warning "The ASE-Job Scheduler is not active". The log SID_JSAGENT shows the following entries:
00:11704:12104:2014/09/01 08:00:35.78 jamain Opening jsagent connection.
00:11704:12104:2014/09/01 08:00:35.78 jamain Agent will listen on <IP>
00:11704:12104:2014/09/01 08:00:35.78 jamain SYB_JSAGENT waiting for connection
00:11704:12104:2014/09/01 08:00:36.72 jamain Job Scheduler Agent connected with Job Scheduler Task on port 4903
00:11704:12104:2014/09/01 08:00:36.72 jamain Initializing SYB_JSAGENT
00:11704:12104:2014/09/01 08:00:36.72 jamain Allocating list resources.
00:11704:12104:2014/09/01 08:00:36.72 jamain Allocating queue resources.
00:11704:12104:2014/09/01 08:00:36.72 jamain Allocating thread resources.
00:11704:12104:2014/09/01 08:00:36.72 jamain Initializing connection pool.
00:11704:12104:2014/09/01 08:00:36.99 jamain Client message: ct_connect(): user api layer: external error: The connection failed because of invalid or missing external configuration data.
00:11704:12104:2014/09/01 08:00:36.99 jamain ct_connect() failed.
00:11704:12104:2014/09/01 08:00:36.99 jamain jsj_AddConxs: jsd_MakeConnection() failed for user jstask to server SID
00:11704:12104:2014/09/01 08:00:36.99 jamain jsj_CreateConxPool: jsj_AddConxs() failed
00:11704:12104:2014/09/01 08:00:36.99 jamain Initialization failed initializing connection pool
00:11704:12104:2014/09/01 08:00:36.99 jamain Jsagent failed to handle INIT message.
00:11704:12104:2014/09/01 08:00:36.99 jamain JS Agent aborting. Cancel all running jobs.
00:11704:12104:2014/09/01 08:00:36.99 jamain Job Processing failed.
00:11704:12104:2014/09/01 08:00:36.99 jamain JS Agent exiting.
Restarting the scheduler on ISQL doesn´t seem to work. Any ideas?
Many thanks & greetings
Vierengel Stefan

Hi,
thank you. Problem was solved by performing the following steps
1.     deleting the following file: DRIVE:\sybase\SID\OCS-15_0\ini\ocs.cfg
2.     Stop / Start Job Scheduler
         exec sybmgmtdb..sp_sjobcontrol '','stop_js'
        go
         exec sybmgmtdb..sp_sjobcontrol '','start_js'
        go
3.     Refresh DBACockpit
Greetings
Vierengel Stefan

Window Server 2012 R2 Job Scheduler Failing.

Hi,
Currently, my company's Window Server 2012 R2 job scheduler having a problem.
Then i found out the solution at http://support.microsoft.com/kb/2617046, so i download the hotfix to fix the problem. However, i get another error as below.
Please, what can i do?
Thanks
Best Regard
Vincent.

Amy,
Thanks for the tips, I follow the settings. I checked the condition and troubleshoot according to the lists you provided.
The task was configured to run only when a specified network is available. (Not set this)
The configured expiration time for the task has passed. (no expired time set)
The task is configured to ignore or queue a new task instance if a previous instance is still running. (not set this)
The task is configured not to run when the computer is on battery power. (yes, will not run when computer on battery power. will not happen because is a server all the time running AC power).
The task is configured to run only if a specific user is logged on. (must select this, if not, the scheduler will not run at all)
The task was disabled by a user. (is enabled)
The previous task instance might have been running longer than expected because a component is busy processing data. If the task is normally expected to run for this length of time, consider modifying the task triggers to take this run-time length
into consideration, or configure the task to be terminated after a preset time. (already set "Stop the task if runs longer than 3 days" and "If the running task does not end when requested, force it to stop". and "Do not start
a new instance " had been set)
Frankly, for the moment it run normally, somehow, I don't know when the incident will happen again. It seem randomly happen, and not by default. That is why kinda need the fix to fix this bug. Cannot trigger email when this incident happen.
And the schedule we run is highly critical.
Thanks.

Stop Job scheduler

Similar Messages

Maybe you are looking for