September 22, 2011 at 1:22 am
I need to check performance issues when a TWS job is running for one of my server for 15 mins time duration .
I have added few required counters like sql server : wait statistics in my perfmon , but i am not able to schedule it for tommorow ( say , 5 am )
Application team has asked me to check from DB side as recently , they have been recieving the warning 05:00:30.683-04:00 Invalid argument though the job completes ( with some extra time now )
September 22, 2011 at 1:52 am
your message is confusing.
Are u running it from correct user and with permissions.
Thanks
September 22, 2011 at 4:30 am
Waits stats will show you what processes are waiting on, but you won't see what's up with that single request. Instead, I'd suggest using Dynamic Management Objects (DMOs). You can see what's actively running by querying sys.dm_exec_requests. If a process is running for a long time, this would be how you manage it. Further, you can combine it with sys.dm_exec_sql_text using statement offsets in order to see specifically which statement is running at any one time. You can also combine these with sys.dm_exec_sql_plan in order to get the execution plan to understand why things are running slow.
If you want to see how queries have performed previously, assuming they're still in cache, you can use sys.dm_exec_query_stats or sys.dm_exec_procedure_stats.These also can be combined with other DMOs to get text & exec plans.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 22, 2011 at 4:37 am
Nice Grant...But this is giving the error of invalid arguments...means some invalid...how does it related with plan...
Thanks
September 22, 2011 at 4:43 am
forsqlserver (9/22/2011)
Nice Grant...But this is giving the error of invalid arguments...means some invalid...how does it related with plan...
Sorry, you have to be more clear what "this" is.
This works fine on a machine 2005 or better:
SELECT * FROM
sys.dm_exec_requests AS der
CROSS APPLY sys.dm_exec_query_plan(der.plan_handle) AS deqp
CROSS APPLY sys.dm_exec_sql_text(der.sql_handle) AS dest
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 26, 2011 at 9:42 pm
Hi All,
I am also getting this kind of error in TWS logs but its going to success.
Mon Sep 26 22:40:59 2011
2011-09-26 22:40:59.069-04:00 Invalid argument
2011-09-26 22:40:59.069-04:00 Invalid argument
2011-09-26 22:40:59.069-04:00 Invalid argument
2011-09-26 22:40:59.069-04:00 Invalid argument
2011-09-26 22:40:59.069-04:00 Invalid argument
2011-09-26 22:40:59.069-04:00 Invalid argument
Can any one please tell how was this issue fixed ? and soln for this.
Please drop an email to shivammax12345@gmail.com
September 26, 2011 at 11:35 pm
what is tws...?what are you going to do?complete thequestion?
Thanks
September 27, 2011 at 3:42 am
I don't know what TWS is either. I tried looking it up online but I'm getting crazy stuff like Texas World Speedway. You have to help us. We're not sitting at your desk and seeing what you see.
That looks like a fairly straight forward error on the application side of things. It doesn't look like a standard database error.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
September 27, 2011 at 3:50 am
Tivoli Workload Scheduler I believe.
If so, then this error needs to be taken up with the Tivoli support, it's not a SQL Server error.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 27, 2011 at 8:50 pm
Hi All,
Yes TWS is IBM's Tivoli work load scheduler tool.
The jobs is run on production windows server with SAP as application.
I am getting this error in prod system and not able to replicate in DEV system.
Any pointers in fixing this error in logs will be very helpful.
Thanks
Shivam
September 28, 2011 at 1:09 am
Call Tivoli support.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 2, 2011 at 8:12 pm
Issue still persists...
Following up with IBM Tivoli Support team ....
will keep you all posted on the same...
thanks for pointers and help
Viewing 12 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply