Agent Unavailable after second job run

We're having an issue with the Tidal_Agent_1 service stopping after running a job a second time. The first time the job completes normally. When I perform a rerun the tidal service gets shut down and the job outputs "Agent Unavailable".
I have tested this with a few different simple jobs, reinstalled a stable tidal version (3.0.1.14), and still the same behavior.
We are using TES 5.2.2 and the agent uses Windows Server 2008 R2 Enterprise for OS.
Any ideas? Working with tidal for years and first time seeing this.
Thanks

Hi,
Check the agent logs and look for "out of memory" errors. You may want to tweak the config file and set the basic heap sizes to 2x or 4x basic depending on your system physical resources.
Cheers

Similar Messages

SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege. I have a SQL server 2012 instance whose Agent service is configured to run
under an AD user account named 'SQLServices'. The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'. The jobs are set up to execute SSIS packages which read and
write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server). The jobs are currently executing without error and are reading writing data correctly. Upon close examination, it turns out the
SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server. How are these jobs working? I verified in profiler that the login name indeed is 'SqlServices'. I also verified
that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected. According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
some cases where that is not necessarily the case. So this is not so concerning. What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does.
The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access. What am I missing here? Any input would be helpful.

After 2 days on this forum I found the answer to my own question. In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed. This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
role. This is the login that Agent uses to connect to the local instance of SQL server. If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

SSIS job runs in designer but fails in SQL Agent - timeout error

I have several SSIS packages that have been running without issue for well over a year. These jobs were imported into SQL Server and run on a schedule with SQL Agent.
Over the weekend these jobs failed with the message:
Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. Source: .Net SqlClient Data Provider Started: 8:13:01 AM
Finished: 8:13:31 AM Elapsed: 30.155 seconds. The package execution failed. The step failed.
When I look at the package history it doesn't even show that the job attempted to run over the weekend. As such I assume that the error is related to SQL Agent attempting to connect to the SSIS job.
As stated in the title, the jobs run without issue in the designer.
I did stop and restart SQL to see if that would have an effect - sadly it did not.
I attempted to reload one of the packages. More specifically I re-imported it and allowed it to overwrite the existing project, This step completed ok and moved to the next step - deploy the project. It fails to deploy the project with the following error
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2218&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
Server Name: XXXXXXX
Error Number: -2
Severity: 11
State: 0
Program Location:
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.IntegrationServices.Common.ObjectModel.SqlHelper.ExecuteSQLCommand(SqlStoreConnection storeConnection, CommandType cmdType, String cmdText, SqlParameter[] parameters, ExecuteType execType, Int32 commandTimeout)
   at Microsoft.SqlServer.Management.IntegrationServices.CatalogFolder.DeployProject(String projectName, Byte[] projectStream)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeployExportProjectHelper.DeployProject(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.Deploy(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.DeployProject()
   at Microsoft.SqlServer.IntegrationServices.Deployment.DeployProjectPage.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
===================================
The wait operation timed out
It would seem to me that there is an environmental error, though I know of nothing that has changed. I don't know where to look. If you have seen this behavior before or have an idea, I welcome your input.
Thanks
Mike

Hi Mike,
Based on the error message, we can infer that the issue is caused by connection or command timeout.
To work around this issue, we can increase the connection timeout and command timeout, buffer size and create two indexes in the SSISDB catalog to improve the performance. For more details, please see:
http://capstonebi.blogspot.com/2012/09/ssis-2012-deployment-frustrations.html
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/804901/ssis-2012-deploying-new-versions-of-large-projects-runs-into-a-timeout-during-deployment-into-ssis-catalog
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

After trying to run the iTunes automatic update, I got this "The feature you are trying to use is on a network resource that is unavailable." Click OK to try again,or enter an alternate path to a folder containing the installation package 'itunes.msi"

After trying to run the iTunes automatic update, I got this box on my pc "The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'iTunes.msi" in the box below.. I ran a search for the file, and entered that into the box, to no avail. Then I launched iTunes and clicked on 'check for updates', and was told I had the latest version 11.0.1 I think it is. So, any clue on what to do? Thanks for any and all help.

(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?

How to get the SQL Signon that Agent Jobs "Run As" or "Executed as User"

How to get the SQL Signon that Agent Jobs "Run As" or "Executed as User"?
I have an install SQL scripts that creates a Linked Server. I want to put some security on the Linked Server and only grant the Agent Job Signon (the "Run As" or "Executed as User") access to the linked server. I need to retrieve the
Agent Job Signon (something like "NT SERVICE\SQLAgent$FIDEV360BI02").
I could query certain jobs and SUBSTRING the Message column - using some form of the query below, which would return "Executed as user: NT SERVICE\SQLAgent$SSDEVBI02. The step succeeded." But that is pretty imprecise.
use msdb
SELECT [JobName] = JOB.name,
[Step] = HIST.step_id,
[StepName] = HIST.step_name,
[Message] = HIST.message,
[Status] = CASE WHEN HIST.run_status = 0 THEN 'Failed'
WHEN HIST.run_status = 1 THEN 'Succeeded'
WHEN HIST.run_status = 2 THEN 'Retry'
WHEN HIST.run_status = 3 THEN 'Canceled'
END,
[RunDate] = HIST.run_date,
[RunTime] = HIST.run_time,
[Duration] = HIST.run_duration,
[Retries] = HIST.retries_attempted
FROM sysjobs JOB
INNER JOIN sysjobhistory HIST ON HIST.job_id = JOB.job_id
-- CHANGE THIS
-- WHERE JOB.name like '%GroupMaster%' or Job.name like '%etlv%'
ORDER BY HIST.run_date, HIST.run_time

by default all sql jobs are executed as sql server agent account, unless otherwise a proxy is setup.
you can get the proxy information as Olaf mentioned, if the proxy_id is null for the step, it implies that the job step was executed as sql server service account and in such case it will be null
so, if it is null, it ran as sql server agent account.
so, one work around is get the sql server agent service account and if the proxy is null, that means it ran as sql server agent account, so, use isnull function. the disadvantage would be if the sql server agent account was switched, you might not get the
accurate information as the new account will show up though the job really ran as old account, to get this information, you need to get this from the logmessage column as you mentioned above.
try this code...
/*from sql 2008r2 sp1, you get the service accounts using tsql,otherwise you have to query the registry keys*/
declare @sqlserveragentaccount varchar(2000)
select @sqlserveragentaccount= service_account
from sys.dm_server_services
where servicename like '%sql%server%agent%'
select message,isnull(name,@sqlserveragentaccount) as AccountName
from sysjobhistory a inner join sysjobsteps b
on a.step_id=b.step_id and a.job_id=b.job_id
left outer join sysproxies c on c.proxy_id=b.proxy_id
Hope it Helps!!

Contact is available when i sign in,then changes to unavailable after a few seconds

When I sign in to Skype,one of my contacts appears available,but then changes to unavailable after a few seconds,although this time varies too. What makes this happen?

This page explains the method for restoring from a backup without having the sync process delete your calendars:
http://www.wilmut.webspace.virginmedia.com/notes/icloudtm.html

SQL Agent job running DTS package running in SQL 2005 is unable to run if job onwer is not logged onto server

I am currently working on a SQL Server upgrade project for a a client where I am converting old dts packages to SSIS. However for a few of the packages no conversion is allowed to be done. For these few packages I have to use dts legacy components in SQL
2005 on a windows 2003 server to run them.
These packages use CAPICOM via an Active X script in the package to envelope connection string data for security within the package. Consequently I have to register the capicom.dll for the job owner (which will execute the job via proxy) and install private
and public key files via internet explorer. I also do this when I am logged in with my account so i can test the package.
I have created a SQL Server Agent Job which is used to execute the package. We have a schedule account which is local admin on the server and sysadmin within SQL Server. This account is used to create a credential and then a proxy for the CmdExec subsystem
is then created based on this credential. A CmdExec job step is then added to the job. The directory of cmd file which calls the dts package is then entered in the command window.
Finally a recurring schedule is added to execute the job every 5 minutes.
If i am logged in to the server using the scheduled account the schedule runs successfully. I am also able to run the command file manually by double clicking on it. The DTS package is run successfully. However once the schedule is set up and I log off the
machine and log onto my development machine with my normal account and fire up SQL Server. I connect to that instance with the schedule and see that the job is failing with and Active X error in the package. From experience with this package this Active
X error occurs when the user executing the package has not registered the capicom.dll. This has already been done for the scheduler account because the job runs when the scheduler account is logged in on the server.
It almost seems as though the job will only run if the Scheduler account is logged on. If i log directly on to the server with own user account I am able to manually execute the package via the cmd file which indicates that the capciom.dll is registered
under my account. Yet if I try an run the job in SQL Server when I am logged in under my account (using the scheduler account proxy) then the job fails.
Does anybody have any idea why this may be happening? Any ideas would be much appreciated

Run the job SSIS step under a proxy account that is derived from the domain account, non-expiring password and has been set to have all the necessary rights.
How to is here: http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Arthur
MyBlog
Twitter

Email Notification after Job run

Hi everybody,
I want to setup an email notification at the end of a job run.
The job is an update run from our Activate Directory and checks if there are some changes to do.
At the end or after this job I would like to send an email to the admin that the job successfully run and what the job did.
How could I setup this?
At the moment I tried to use a SQL statement to table MC_LOGS within a script called in the last pass of the job.
But I only get the information what to job do from the last run of the job and not from the current run.
Best regards & a happy new year, Anja

Hi Anja
Your last pass can only fetch information from the last run and not the current one because the Job is still running and the respective log is not yet written to the table.
But maybe you could use the LogFile created then the Job finishes.
I suppose you use the "LDAP (ADS) - Update All"- Job for LDAP-to-IC updates. This job writes a logfile to %$ddm.ddmpath% which you could send as mail attachment. Use the UpdateJob-"Event scheduling" button to run your SendMail-Job after every UpdateJob-completion.
Another idea would be to use the SQL-View MCMV_JOBLOG which I think is the datasource of IC-JobLog. I suppose column "mcmv_data" stores the details.
Hope I could help.
BR
Michael

Job group does not go red when agent unavailable

Hi,
We noticed that if you have a job that completes abnormally due to the Agent being unavailable, then parent job groups more than one level up do not turn red. This seems to be different behavior to tes5 and makes identifying failed jobs difficult.
Is there a setting that governs this somewhere. ?
Sent from Cisco Technical Support Android App

I think the issue lies with your device software. If wiping the handled doesn't work then try wiping the device software and loading them again with Application Loader with Desktop Manager.
tanzim
If your query is resolved then please click on “Accept as Solution”
Click on the LIKE on the bottom right if the post deserves credit

Crystal Reports 2013 freezes after 22 seconds of running report

I'm running a report that includes 5 linked subreports. I have parameters for start and end dates for the the data I'm running, and if the report takes longer than 22 seconds to run, the program locks up and I have to manually kill the crw.32 process. At the bottom of the report I can see where text is constantly overlayed where it says "Subreport: Reading Records" which almost makes me wonder if it's a graphics issue vs. a Crystal issue. I can see where it began to write "Generating Page 1" over "Subreport: Reading Records". Any help would be greatly appreciated. A screenshot of what's happening at the bottom of the program is attached. I'm running CR Developer 14.1.1.1036. Thank you very much!

Hi Drew,
Remember that each time a subreport is called, it's querying the database again. If you have 5 linked subreports in a group header or footer that means all 5 of those subreports are hitting the database for each group.
The screenshot you attached tells me Crystal is busy trying to process the report and is dedicating all of its resources to that. My guess is if you click on Crystal you the window says it's busy.
This could be a resource issue on your database server or your client machine. So it could be a matter of giving it more time to complete. It sounds like the problem can be reproduced. Remove a subreport and see if the report still hangs. If it does remove another and repeat the process until it doesn't hang.
If possible, can you filter the data going into the subreports so they process less records? The less data it has to play with the better the performance.
Good luck,
Brian

Dbms_scheduler - dbms_aq - dbms_aqadm - event driven job runs only once/sec

hi, i tried here to process events with 2 jobs... surprisingly i had to call dbms_lock.sleep(1) to be able to enqueue events
at inserts in a row ... even more surprisingly the enqueuing doesn't function if the processing (prc_evsched) lasts some seconds...
how must the code be changed to be able to enqueue all events after the inserts without any sleep()?
and how must the code be changed to be able to enqueue all events with a proc (prc_evsched) running longer?
thanx in advance for your help!
--evsched
h4.
--to remove all test-objects
h4.
--test table
h4.
--define the object type to act as the payload for the queue
h4.
--creating the event queue
h4.
--creating the proc for the prog/job
h4.
--creating the proc for the prog/job
h4.
--creating the program
h4.
--creating the first job (for parallel execution)
h4.
--creating the second job (for parallel execution)
h4.
--test block
h4.
--test scenarios/results
h4.
--to remove all test-objects
DECLARE
exc_ora_27475 EXCEPTION; --ora-27475: <job_name> muss job sein
PRAGMA EXCEPTION_INIT (exc_ora_27475, -27475);
exc_ora_27476 EXCEPTION; --ora-27476: <program_name> ist nicht vorhanden
PRAGMA EXCEPTION_INIT (exc_ora_27476, -27476);
exc_ora_24010 EXCEPTION; --ORA-24010: QUEUE SYSGIS.EVENT_QUEUE ist nicht vorhanden
PRAGMA EXCEPTION_INIT (exc_ora_24010, -24010);
exc_ora_24002 EXCEPTION; --ORA-24002: QUEUE_TABLE SYSGIS.EVENT_QUEUE_TAB ist nicht vorhanden
PRAGMA EXCEPTION_INIT (exc_ora_24002, -24002);
exc_ora_4043 EXCEPTION; --ORA-04043: Objekt T_EVENT_QUEUE_PAYLOAD ist nicht vorhanden
PRAGMA EXCEPTION_INIT (exc_ora_4043, -4043);
exc_ora_942 EXCEPTION; --ORA-00942: Tabelle oder View nicht vorhanden
PRAGMA EXCEPTION_INIT (exc_ora_942, -942);
exc_ora_2289 EXCEPTION; --ORA-02289: Sequence ist nicht vorhanden.
PRAGMA EXCEPTION_INIT (exc_ora_2289, -2289);
v_fpos PLS_INTEGER := 1;
BEGIN
v_fpos := 10;
BEGIN
--remove job
SYS.DBMS_SCHEDULER.DROP_JOB(job_name=> 'job_evsched', FORCE=>TRUE);
EXCEPTION WHEN exc_ora_27475 THEN NULL;
END;
v_fpos := 12;
BEGIN
--remove job
SYS.DBMS_SCHEDULER.DROP_JOB(job_name=> 'job_evsched_2', FORCE=>TRUE);
EXCEPTION WHEN exc_ora_27475 THEN NULL;
END;
v_fpos := 20;
BEGIN
--remove program
SYS.DBMS_SCHEDULER.DROP_PROGRAM(program_name=>'prg_evsched',FORCE=>TRUE);
EXCEPTION WHEN exc_ora_27476 THEN NULL;
END;
v_fpos := 30;
BEGIN
-- stop the event queue.
DBMS_AQADM.stop_queue (queue_name => 'evsched_event_queue');
EXCEPTION WHEN exc_ora_24010 THEN NULL;
END;
v_fpos := 40;
BEGIN
-- drop the event queue.
DBMS_AQADM.drop_queue (queue_name => 'evsched_event_queue');
EXCEPTION WHEN exc_ora_24010 THEN NULL;
END;
v_fpos := 50;
BEGIN
-- Remove the queue table.
DBMS_AQADM.drop_queue_table(queue_table => 'tab_evsched_event_queue');
EXCEPTION WHEN exc_ora_24002 THEN NULL;
END;
v_fpos := 60;
BEGIN
-- remove type
EXECUTE IMMEDIATE 'DROP TYPE typ_evsched_payload';
EXCEPTION WHEN exc_ora_4043 THEN NULL;
END;
v_fpos := 70;
BEGIN
-- remove table
EXECUTE IMMEDIATE 'DROP TABLE tab_evsched';
EXCEPTION WHEN exc_ora_942 THEN NULL;
END;
v_fpos := 80;
BEGIN
-- remove sequence
EXECUTE IMMEDIATE 'DROP SEQUENCE seq_evsched';
EXCEPTION WHEN exc_ora_2289 THEN NULL;
END;
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('v_fpos='||v_fpos);
END;
h4.
--test table
CREATE TABLE tab_evsched
( id NUMBER
, sys_date DATE
, status VARCHAR2(1)
, processed VARCHAR2(1) DEFAULT 'N'
, processed_by varchar2(128)
GRANT DELETE, INSERT, SELECT, UPDATE ON tab_evsched TO PUBLIC
CREATE SEQUENCE seq_evsched
h4.
--define the object type to act as the payload for the queue
CREATE OR REPLACE TYPE typ_evsched_payload AS OBJECT
( event_name VARCHAR2(30)
, tab_evsched_id NUMBER
, daterf DATE
h4.
--creating the event queue
BEGIN
-- Create a queue table to hold the event queue.
DBMS_AQADM.create_queue_table
( queue_table => 'tab_evsched_event_queue'
, queue_payload_type => 'typ_evsched_payload'
, multiple_consumers => TRUE
, COMMENT => 'Queue Table For Event Messages'
-- Create the event queue.
DBMS_AQADM.create_queue
( queue_name => 'evsched_event_queue'
, queue_table => 'tab_evsched_event_queue'
, queue_type => DBMS_AQADM.NORMAL_QUEUE
, max_retries => 0
, retry_delay => 0
, dependency_tracking => FALSE
, comment => 'Test Object Type Queue'
, auto_commit => FALSE
-- Start the event queue.
DBMS_AQADM.start_queue
( queue_name => 'evsched_event_queue'
END;
h4.
--creating the proc for the prog/job
CREATE OR REPLACE PROCEDURE prc_evsched
( p_message IN typ_evsched_payload
, p_job_name IN VARCHAR2
IS
BEGIN
UPDATE tab_evsched
SET processed = 'J'
, processed_by = p_job_name
, sys_date = p_message.daterf
WHERE 1=1
AND id = p_message.tab_evsched_id
dbms_lock.sleep(5); --#sleep-1#
COMMIT;
END prc_evsched;
h4.
--creating the program
DECLARE
exc_ora_27476 EXCEPTION; --ora-27476: <program_name> ist nicht vorhanden
PRAGMA EXCEPTION_INIT (exc_ora_27476, -27476);
BEGIN
BEGIN
SYS.DBMS_SCHEDULER.DROP_PROGRAM(program_name=>'prg_evsched',FORCE=>TRUE);
EXCEPTION
WHEN exc_ora_27476 THEN
NULL;
END;
SYS.DBMS_SCHEDULER.CREATE_PROGRAM
( program_name => 'prg_evsched'
, program_type => 'STORED_PROCEDURE'
, program_action => '"SYSGIS"."PRC_EVSCHED"'
, number_of_arguments => 2
, enabled => FALSE
, comments => 'Program-Komponent für den Test von DBMS_SCHEDULER'
--event message as the first param to prc_evsched
DBMS_SCHEDULER.DEFINE_METADATA_ARGUMENT
( program_name => 'prg_evsched'
, argument_position => 1
, metadata_attribute => 'EVENT_MESSAGE'
--name of the job as the second param to prc_evsched
SYS.DBMS_SCHEDULER.define_program_argument
( program_name => 'prg_evsched'
, argument_name => 'p_job_name'
, argument_position => 2
, argument_type => 'VARCHAR2'
, default_value => 'dummy'
--enable program
SYS.DBMS_SCHEDULER.ENABLE(NAME=>'prg_evsched');
END;
h4.
--creating the first job (for parallel execution)
DECLARE
exc_ora_27475 EXCEPTION; --ora-27475: <job_name> muss job sein
PRAGMA EXCEPTION_INIT (exc_ora_27475, -27475);
BEGIN
BEGIN
--remove job
SYS.DBMS_SCHEDULER.DROP_JOB(job_name=> 'job_evsched', FORCE=>TRUE);
EXCEPTION WHEN exc_ora_27475 THEN NULL;
END;
DBMS_SCHEDULER.create_job
( job_name => 'job_evsched'
, program_name => 'prg_evsched'
, start_date => SYSTIMESTAMP
, event_condition => 'tab.user_data.event_name = ''MYEVENT'''
, queue_spec => 'evsched_event_queue'
, auto_drop => FALSE
, enabled => FALSE
SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE
( job_name => 'job_evsched'
, argument_name => 'p_job_name'
, argument_value => 'job_evsched'
SYS.DBMS_SCHEDULER.ENABLE(NAME=>'job_evsched');
END;
h4.
--creating the second job (for parallel execution)
DECLARE
exc_ora_27475 EXCEPTION; --ora-27475: <job_name> muss job sein
PRAGMA EXCEPTION_INIT (exc_ora_27475, -27475);
BEGIN
BEGIN
--remove job
SYS.DBMS_SCHEDULER.DROP_JOB(job_name=> 'job_evsched_2', FORCE=>TRUE);
EXCEPTION WHEN exc_ora_27475 THEN NULL;
END;
DBMS_SCHEDULER.create_job
( job_name => 'job_evsched_2'
, program_name => 'prg_evsched'
, start_date => SYSTIMESTAMP
, event_condition => 'tab.user_data.event_name = ''MYEVENT'''
, queue_spec => 'evsched_event_queue'
, auto_drop => FALSE
, enabled => FALSE
SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE
( job_name => 'job_evsched_2'
, argument_name => 'p_job_name'
, argument_value => 'job_evsched_2'
SYS.DBMS_SCHEDULER.ENABLE(NAME=>'job_evsched_2');
END;
h4.
--test block
DECLARE
PROCEDURE pr_ins_tab_evsched
( p_id IN NUMBER
, p_status IN VARCHAR2
IS
BEGIN
INSERT INTO tab_evsched(id,status) VALUES (p_id, p_status);
COMMIT;
--enqueue the MYEVENT-event
IF p_status = 'M' THEN
--enqueue works in 1sekunden-taktung.... !?
dbms_lock.sleep(1); --#sleep-2#
DECLARE
v_enqueue_options DBMS_AQ.enqueue_options_t;
v_message_properties DBMS_AQ.message_properties_t;
v_message_handle RAW(16);
v_queue_msg typ_evsched_payload;
BEGIN
v_queue_msg := typ_evsched_payload
( event_name => 'MYEVENT'
, tab_evsched_id => p_id
, daterf => SYSDATE
v_enqueue_options.VISIBILITY := DBMS_AQ.ON_COMMIT;
v_enqueue_options.delivery_mode := DBMS_AQ.PERSISTENT;
v_message_properties.PRIORITY := 1;
v_message_properties.DELAY := DBMS_AQ.NO_DELAY;
v_message_properties.EXPIRATION := DBMS_AQ.NEVER;
v_message_properties.CORRELATION := 'TEST MESSAGE';
DBMS_AQ.enqueue
( queue_name => 'evsched_event_queue'
, enqueue_options => v_enqueue_options
, message_properties => v_message_properties
, payload => v_queue_msg
, msgid => v_message_handle
END;
END IF;
COMMIT;
END pr_ins_tab_evsched;
BEGIN
DELETE tab_evsched;
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
pr_ins_tab_evsched (seq_evsched.NEXTVAL,'M');
END;
SELECT * FROM tab_evsched ORDER BY id;
SELECT * FROM sysgis.tab_evsched_event_queue;
h4.
--test scenarios/resultsh
h5.
--test results #sleep-1#=5, #sleep-2#=0
--job (job_evsched) runs only once, only the first event is enqued/processed
ID SYS_DATE STATUS PROCESSED PROCESSED_BY
9 22.03.2012 17:00:41 M J job_evsched
10 (Null) M N (Null)
11 (Null) M N (Null)
12 (Null) M N (Null)
13 (Null) M N (Null)
14 (Null) M N (Null)
15 (Null) M N (Null)
16 (Null) M N (Null)
h5.
--test results #sleep-1#=0, #sleep-2#=1
--jobs (job_evsched/job_evsched2) run alternately, every events are enqued/processed
ID SYS_DATE STATUS PROCESSED PROCESSED_BY
25 22.03.2012 17:04:31 M J job_evsched_2
26 22.03.2012 17:04:32 M J job_evsched_2
27 22.03.2012 17:04:33 M J job_evsched
28 22.03.2012 17:04:34 M J job_evsched_2
29 22.03.2012 17:04:35 M J job_evsched_2
30 22.03.2012 17:04:36 M J job_evsched_2
31 22.03.2012 17:04:37 M J job_evsched
32 22.03.2012 17:04:38 M J job_evsched_2
h5.
--test results #sleep-1#=5, #sleep-2#=1
--jobs (job_evsched/job_evsched2) run alternately, only two events are enqued/processed
ID SYS_DATE STATUS PROCESSED PROCESSED_BY
41 22.03.2012 17:07:42 M J job_evsched_2
42 (Null) M N (Null)
43 (Null) M N (Null)
44 (Null) M N (Null)
45 (Null) M N (Null)
46 (Null) M N (Null)
47 22.03.2012 17:07:48 M J job_evsched
48 (Null) M N (Null)
*/

hi, thank you for your (fast) answer! that is the solution to my problem!
now i have a follow-up question:
i've got a procedure, that runs between 1 and 2 minutes long. unlimited running lightweight jobs
would freeze the db...
how can the count of the parallel running lightweight-jobs be limited?
according to the documentation it is not possible:
There is no explicit limit to the number of lightweight jobs that can run simultaneously to process multiple instances of the event.
However, limitations may be imposed by available system resources.
could you explain to me, what it (...available system recources...) means?
eventually what i would like to have: max. two parallel running (lightweight) jobs....
thank you in advance, bye, á
ps: can i attach a file to the post anyway?
Edited by: user4786904 on 23.03.2012 07:22

Periodic Background Jobs after another Job finishes

Hi
I have to schedule a job 'B' to run after job 'A' finishes.
When i schedule job 'B' to run after job A , it runs only once , while i need the job B to run periodically after job A finishes.
1) I cannt make job B as step 2 of job A , because job A is not scheduled by me and i cannt change that.
Can anyone tell me how to i trigger the job B periodicaly after job A finishes .
Any solution or hint would be appreciated.
Looking forward to some helpful replies from the gurus of SAP.
Regards
Purva

Dear Team,
Job ES_RPTMC_CREATE_CHANGEPOINT_AUTH ran only once where as SEC:INDX_UPDATE_FOR_STRUCT_AUTHS ran daily.
CAUSE:
“The start condition "Start after job" is internally mapped by means of "Start after event SAP_END_OF_JOB with the parameter <Jobname><Jobcount> of the predecessor". The pair <Jobname><Jobcount> is the unique key for a job.
If a job is executed periodically, the SAP_END_OF_JOB event is always triggered with different parameters.
The successor in turn waits for SAP_END_OF_JOB with just one particular parameter (this is the parameter with <Jobname><Jobcount> from the first predecessor). When the successor is rescheduled, the key fields from the next predecessor must therefore always be known in advance, something which is not always technically possible.”
SOLUTION:
This task can be completed with the new ABAP program Program BTC_EVENT_RAISE.
The program is delivered by Support Package for Basis Releases 640 and 700, and is included in the standard system in all subsequent releases.
The program is used to trigger a batch event. Existing programs do not therefore have to be changed. The BTC_EVENT_RAISE program has several parameters in the selection screen, including the event (and parameters) that is to be triggered.
PROCESS:
 Go To SM64
 Click on Create
 Create two events.
Our Case:
We created Z_ES_CP_AUTH and Z_SEC_AUTHS
 Go to SE38
 Give the event name as BTC_EVENT_RAISE
 Select Variants and click on Display
 Give the variant name as the one you created.
Our Case:
Z_ES_CP_AUTH
 Click on Create
 Give in the details for variants
 Click on attributes and give the details for attributes
 Go to the job which needs to be run first
• Select the job in released status
• Job->Change
• Step
• Add BTC_EVENT_RAISE as the last step of the job with the parameter as the variant created
Our Case:
Step: BTC_EVENT_RAISE, Parameter: Z_ES_CP_AUTH
 Go to the job which needs to be run next
• Select the job in released status
• Job->Change
• Start Condition -> After Event.
• Give the BTC_EVENT_RAISE parameter of the first job as the event of the second job.
Our Case:
After Event: Z_ES_CP_AUTH
 Save the changes.
 The jobs will start running one after the other with the given frequency.
Thanks
Joginadham U

EIMAdaptiveProcessingService is unreponsive and Dataservice job run slow down

Hi all,
I have a BO DS 4.0 SP3 installed on Win SQL Server 2008 R2 and IPS 4.0.
The CPU is Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz 2.19 GHz(4 processors) with 16GB RAM.
Since several weeks, the new DS job run in the production. the job run sometimes during 1hour and sometimes during 5hours.
when it run more than 2 hours, we find BODS service do nothing during serval hours. I found there is some errors "WebIntelligenceProcessingServer' is being marked as down because it is unresponsive" in the event viewer.
The AdaptiveProcessingService as below:
GC: [4612] 03:39:34 Suspiciously long running GC (turn this off via -XX:-DumpGCStatisticForLongGCs or change the time threshold via -XX:LongGCTime=<time in seconds>):
GC: [4612] 03:39:34 GC Nr. : 58
GC started : Tue May 20 03:37:35 2014
Nr. of full GCs : 5
GC algorithm : -XX:+UseParallelGC
Reason : Allocation Failure
Type : partial
Forced SoftRef clearing : no
Duration : 119471.03 ms
Cumulative duration : 123392.10 ms
CPU time : 78.00 ms
Cumulative CPU time : 7878.03 ms
Page faults during GC : 15
Cumulative page faults during GCs : 94406
Allocation goal : 48 B (48)
Used in Java heap before GC : 223.57 MB (234431584)
Used in Java heap after GC : 110.65 MB (116024464)
Bytes freed in Java heap during GC : 112.92 MB (118407120)
Committed in Java heap before GC : 336.31 MB (352649216)
Committed in Java heap after GC : 313.56 MB (328794112)
Bytes decommitted in Java heap : 22.75 MB (23855104)
Nr. of unloaded classes : 0
Nr. of non-array classes before GC : 8580
Nr. of non-array classes after GC : 8580
Nr. of array classes before GC : 574
Nr. of array classes after GC : 574
Cumulative unloaded non-array classes : 32
Cumulative unloaded array classes : 0
Used in eden before GC : 113.13 MB (118620160), 100.00% of committed, 33.14% of young gen max
Used in eden after GC : 48 B (48), 0.00% of committed, 0.00% of young gen max
Bytes freed in eden : 113.12 MB (118620112), 33.14% of young gen max
Committed in eden before GC : 113.13 MB (118620160), 33.14% of young gen max
Committed in eden after GC : 113.13 MB (118620160), 33.14% of young gen max
TLAB waste in eden space before GC : 15.48 MB (16228992), 13.68% of used in eden
Used in 'from' space before GC : 2.31 MB (2424880), 9.74% of committed, 0.68% of young gen max
Used in 'from' space after GC : 2.41 MB (2523184), 98.72% of committed, 0.71% of young gen max
Bytes freed in 'from' space : -96.00 kB (-98304), -0.03% of young gen max
Committed in 'from' space before GC : 23.75 MB (24903680), 6.96% of young gen max
Committed in 'from' space after GC : 2.44 MB (2555904), 0.71% of young gen max
Used in 'to' space before GC : 0 B (0), 0.00% of committed, 0.00% of young gen max
Used in 'to' space after GC : 0 B (0), 0.00% of committed, 0.00% of young gen max
Bytes added in 'to' space : 0 B (0), 0.00% of young gen max
Committed in 'to' space before GC : 25.31 MB (26542080), 7.42% of young gen max
Committed in 'to' space after GC : 23.88 MB (25034752), 7.00% of young gen max
Max in young gen : 341.31 MB (357892096)
Used in young gen before GC : 115.44 MB (121045040), 33.82% of max
Used in young gen after GC : 2.41 MB (2523232), 0.71% of max
Bytes freed in young gen : 113.03 MB (118521808), 33.12% of max
Committed in young gen before GC : 136.88 MB (143523840), 40.10% of max
Committed in young gen after GC : 115.56 MB (121176064), 33.86% of max
Tenuring threshold : 15
Max in old gen : 682.69 MB (715849728)
Used in old gen before GC : 108.13 MB (113386544), 62.10% of committed, 15.84% of max
Used in old gen after GC : 108.24 MB (113501232), 62.16% of committed, 15.86% of max
Bytes freed in old gen : -112.00 kB (-114688), -0.02% of max
Committed in old gen before GC : 174.13 MB (182583296), 25.51% of max
Committed in old gen after GC : 174.13 MB (182583296), 25.51% of max
Max in perm gen : 256.00 MB (268435456)
Used in perm gen before GC : 60.30 MB (63226432), 65.14% of committed, 23.55% of max
Used in perm gen after GC : 60.30 MB (63226432), 65.14% of committed, 23.55% of max
Bytes freed in perm gen : 0 B (0), 0.00% of max
Committed in perm gen before GC : 92.56 MB (97058816), 36.16% of max
Committed in perm gen after GC : 92.56 MB (97058816), 36.16% of max
Bytes allocated in non-perm until now : 6.77 GB (7273341072)
Bytes freed in non-perm until now : 6.67 GB (7160953417)
Bytes allocated in perm until now : 60.45 MB (63388408)
Bytes freed in perm until now : 176.66 kB (180899)
Nr. of soft refs cleared until now : 1754
Nr. of soft refs enqueued until now : 61
Nr. of weak refs cleared until now : 48369
Nr. of weak refs enqueued until now : 47736
Nr. of final refs enqueued until now : 52559
Nr. of phantom refs enqueued until now: 0
Number of parallel scavenge threads : 4
Nr. of GC events : 3
GC Event Nr. : 1
GC event name : Young generation reference handling
Event start time : Tue May 20 03:39:34 2014
Duration : 12.36 ms
CPU time : 15.60 ms
Page faults during event : 0
Max last used time (ms) of SoftRefs : 70000
Nr. of SoftRefs found : 35
Nr. of SoftRefs kept alive by policy : 20
Nr. of dead SoftRefs cleared : 15
Nr. of dead SoftRefs not cleared : 0
Nr. of live SoftRefs : 20
Nr. of SoftRefs newly enqueued : 1
Nr. of new alive SoftRefs found : 0
 during SoftRef handling
Nr. of new alive WeakRefs found : 0
 during SoftRef handling
Nr. of new alive FinalRefs found : 0
 during SoftRef handling
Nr. of new alive PhantomRefs found : 0
 during SoftRef handling
Nr. of WeakRefs found : 1193
Nr. of dead WeakRefs : 1192
Nr. of live WeakRefs : 1
Nr. of WeakRefs newly enqueued : 1185
Nr. of FinalRefs found : 1121
Nr. of live FinalRefs : 21
Nr. of FinalRefs newly enqueued : 1100
Nr. of new alive SoftRefs found : 0
 during FinalRef handling
Nr. of new alive WeakRefs found : 0
 during FinalRef handling
Nr. of new alive FinalRefs found : 0
 during FinalRef handling
Nr. of new alive PhantomRefs found : 0
 during FinalRef handling
Nr. of PhantomRefs found : 1
Nr. of live PhantomRefs : 1
Nr. of PhantomRefs newly enqueued : 0
Nr. of new alive SoftRefs found : 0
 during PhantomRef handling
Nr. of new alive WeakRefs found : 0
 during PhantomRef handling
Nr. of new alive FinalRefs found : 0
 during PhantomRef handling
Nr. of new alive PhantomRefs found : 0
 during PhantomRef handling
Soft reference handling duration : 0.01 ms
Soft reference handling CPU time : 0.00 ms
Weak reference handling duration : 0.47 ms
Weak reference handling CPU time : 0.00 ms
Final reference handling duration : 11.67 ms
Final reference handling CPU time : 15.60 ms
Phantom reference handling duration : 0.01 ms
Phantom reference handling CPU time : 0.00 ms
JNI weak reference handling duration : 0.16 ms
JNI weak reference handling CPU time : 0.00 ms
GC Event Nr. : 2
GC event name : Parallel scavenge (young generation GC)
Event start time : Tue May 20 03:37:35 2014
Duration : 119470.94 ms
CPU time : 78.00 ms
Page faults during event : 15
Used in eden before event : 113.13 MB (118620160)
Used in eden after event : 0 B (0)
Freed in eden : 113.13 MB (118620160)
Used in 'from' space before event : 2.31 MB (2424880)
Used in 'from' space after event : 2.41 MB (2523184)
Freed in 'from' space : -96.00 kB (-98304)
Used in 'to' space before event : 0 B (0)
Used in 'to' space after event : 0 B (0)
Added in 'to' space : 0 B (0)
Used in young generation before event : 115.44 MB (121045040)
Used in young generation after event : 2.41 MB (2523184)
Freed in young generation : 113.03 MB (118521856)
Used in old generation before event : 108.13 MB (113386544)
Used in old generation after event : 108.24 MB (113501232)
Freed in old generation : -112.00 kB (-114688)
Used in perm generation before event : 60.30 MB (63226432)
Used in perm generation after event : 60.30 MB (63226432)
Freed in perm generation : 0 B (0)
System load average : 0.03, 0.03, 0.64
Promotion failed : no
Number of successful steal operations : 123
Number of failed steal operations : 4
Number of failed steals and yields : 0
Size of 'to' space PLAB (per thread) : 32.00 kB (32768 bytes)
Objects of age 0 : 22228, 1.02 MB (1071744 bytes)
Objects of age 1 : 4917, 188.57 kB (193096 bytes)
Objects of age 2 : 3006, 100.47 kB (102880 bytes)
Objects of age 3 : 1775, 147.48 kB (151016 bytes)
Objects of age 4 : 2384, 71.31 kB (73024 bytes)
Objects of age 5 : 2362, 65.82 kB (67400 bytes)
Objects of age 6 : 3254, 107.34 kB (109912 bytes)
Objects of age 7 : 1972, 56.80 kB (58168 bytes)
Objects of age 8 : 2720, 83.50 kB (85504 bytes)
Objects of age 9 : 2210, 62.80 kB (64312 bytes)
Objects of age 10 : 2646, 81.98 kB (83944 bytes)
Objects of age 11 : 1863, 59.31 kB (60736 bytes)
Objects of age 12 : 2751, 110.47 kB (113120 bytes)
Objects of age 13 : 2419, 67.50 kB (69120 bytes)
Objects of age 14 : 2872, 92.19 kB (94400 bytes)
Objects of age 15 : 2766, 95.27 kB (97552 bytes)
Objects of age 16 : 0, 0 B (0 bytes)
Objects of age 17 : 0, 0 B (0 bytes)
Objects of age 18 : 0, 0 B (0 bytes)
Objects of age 19 : 0, 0 B (0 bytes)
Objects of age 20 : 0, 0 B (0 bytes)
Objects of age 21 : 0, 0 B (0 bytes)
Objects of age 22 : 0, 0 B (0 bytes)
Objects of age 23 : 0, 0 B (0 bytes)
Objects of age 24 : 0, 0 B (0 bytes)
Objects of age 25 : 0, 0 B (0 bytes)
Objects of age 26 : 0, 0 B (0 bytes)
Objects of age 27 : 0, 0 B (0 bytes)
Objects of age 28 : 0, 0 B (0 bytes)
Objects of age 29 : 0, 0 B (0 bytes)
Objects of age 30 : 0, 0 B (0 bytes)
Objects of age 31 : 0, 0 B (0 bytes)
GC Event Nr. : 3
GC event name : Skipped parallel scavenge (young generation GC)
Event start time : Tue May 20 03:39:34 2014
Reason to skip GC : Too much time spend in GC
Thanks for your help
Xin

Hello Xin SUN,
Try checking whether any other database application running at the back end.
when that particular job is running see the CPU usage, if it is high try to find which process takes lot of memory.

Xgrid agents fail Maya rendering jobs

Hello,
We are a college and have setup an xGrid for students to submit Autodesk Maya 2008
rendering jobs to the xGrid for processing Maya .mb animation projects.
Our xGrid runs perfectly we can submit simple jobs and it works perfectly.
We are using the GUI Xgrid Feeder Sample app included in the Xcode SDK to submit jobs using a Autodesk Maya command called "Render" (plus some options for the command added using the Feeder app GUI)
Xgrid is correctly feeding the agents, but all the agents immediately fail the jobs. I have included the xGrid console output for one of the agents below:
The first job fails (maya command)
The second one works (simple bash command)
Thu Apr 2 15:36:45 W87301MXXAH.local xgridagentd[23064] <Notice>: Notice: agent task "23109" failed for user "nobody" executable "/Applications/Autodesk/maya2008/Maya.app/Contents/bin/Render" arguments (
"/Volumes/Courses/anm1303dAnimation_maya/xgrid_test/big_zwalk",
"big_z.mb"
Thu Apr 2 15:49:14 W87301MXXAH.local xgridagentd[23064] <Notice>: Notice: agent task "23121" started for user "nobody" executable "/usr/bin/cal" arguments (
Thu Apr 2 15:49:14 W87301MXXAH.local xgridagentd[23064] <Notice>: Notice: agent task "23121" finished for user "nobody" executable "/usr/bin/cal" arguments (
Does anyone have any idea why the maya jobs are failing?
Could it be permissions problems for the nobody user, and how would I change those?
Cheers

Are you using an AFP, SMB, or NFS network share? Logged on as which user?
I've had good success with AFP shares logged in as the local admin, and using RUSH for maya rendering (set to render as local admin). NFS should work better for permissions if you need to render as different users.

How define background job, after a job, daily

Hi Gurus!
i need to create several Jobs, one after another. i'm working with R/3 enterprise.
I can create a Job after another, but I can't put it daily.
anyone knows how I can define job, after a specific job, daily???
THANKS!!!!

Hi Oscar,
If you want to execute the Background jobs one by one(sequence order),
Goto SM36 and create a Background job, then create another job then press Start condition, in this one there is a tab after JOB, here give the job name, os the will be run after this job complets
another way is there, if you want to run the jobs in a sequence, there is a TAB called STEP, create a Job name then press the tab STEP, here give the first job name then press the create button then create the second job name.. like this you can give N number of background Programs one by one
hope you got the answer
Thanks
Sudheer

Agent Unavailable after second job run

Similar Messages

Maybe you are looking for