|
|
Enron Mail |
Matt,=20
Each month, prior to bidweek, I pull up a monthly range in Path Manager to= =20 get a feel of how many of our swing customers operated in a prior month (or= a=20 month in a prior year). I have never had problem with this before, and I= =20 have done this task every month since Unify was put into production. When= =20 the problem occurred this month, I was attempting to view Apr 1-30, 2000 on= =20 Houston Pipe Line, with HPL as the shipper. This information is very=20 important for my bidweek preparation. So, I need to continue perfomorming= =20 this operation each month. If needed, I can wait until 5 pm top view the= =20 range. D From: Matt Pena/ENRON@enronXgate on 03/23/2001 02:30 PM To: Daren J Farmer/HOU/ECT@ECT cc: Chris Schomer/ENRON@enronXgate, Jaikishore Bharathi/ENRON@enronXgate, B= ob=20 Ward/ENRON@enronXgate, William Mallary/ENRON@enronXgate, Brian=20 Ripley/ENRON@enronXgate=20 Subject: RE: What happened: tempdb xact log Darren, Do you know if you were running pulling up the Path Manager for a date rang= e=20 around 10:51?=01; How do you normally pull up the Path Manager?=01; Please = let me=20 know as we're attempting to find out what caused this problem and if we=20 should restrict access on the date range functionality.=01; If you were onl= y=20 pulling it for a day, that would be okay. =01; Thanks -----Original Message----- From: Mallary, William=20 Sent: Friday, March 23, 2001 2:24 PM To: Ripley, Brian Cc: Schomer, Chris; Pena, Matt; Bharathi, Jaikishore; Ward, Bob Subject: What happened: tempdb xact log Brian,=20 =01; At 11:20am this morning, a stored procedure (source_dest_list_range_sp, Lin= e=20 #172) being run by Daren Farmer caused the tempdb transaction log on=20 unifygasp to fill up.=01; This procedure is run routinely by many other use= rs on=20 a daily basis without incident.=01; At the time of the failure, this stored= =20 procedure had been running since 10:51am, or roughly 30 minutes.=01; I was= =20 notified via automatic page at 11:24am; the page indicating that there was= =20 200MB free.=01; I immediately checked tempdb, which was by full by this tim= e.=01;=20 Three attempts to clear the transaction log prior to 11:30am finally result= ed=20 in=01;a cleared transaction log. =01; Kishore noiced shortly thereafter that there was a problem in the way that= =20 Sybase was accounting for its free space, a condition which may have been= =20 crucial to the failure since nearly 5GB of space was apparently unavailable= =20 to the transaction log.=01; A reboot of unifyprod2 at 1:40pm cleared this= =20 condition. Bill Mallary *=01; william.mallary@enron.com <mailto:william.mallary@enron.com< ( =01;713.345.3485 (office) ( =01;281.960.7181 (cell) =01;
|