I avoid opening SR's unless it's absolutely my last option, but I've had this similar experience this week with a severity 2 ticket- took over a day to complete the SR with failures on uploads of logs and trace files that I knew they would need and then had to escalate via phonecalls to duty managers four different times after a ticket would sit at a standstill for over 24 hours, (this was for my ghost sid issue I had this last week, btw is a bug that went back to development for parallel inconsistent close upon degradation...) I really cringe when my manager says, "We're paying for support, submit an SR!" OK, but only if I get a secretary to manage the mess... :) Kellyn Pedersen Sr. Database Administrator I-Behavior Inc. http://www.linkedin.com/in/kellynpedersen www.dbakevlar.blogspot.com "Go away before I replace you with a very small and efficient shell script..." --- On Tue, 6/8/10, Dba DBA <oracledbaquestions@xxxxxxxxx> wrote: From: Dba DBA <oracledbaquestions@xxxxxxxxx> Subject: anyone having trouble contacting oracle support? To: "ORACLE-L" <oracle-l@xxxxxxxxxxxxx> Date: Tuesday, June 8, 2010, 1:07 PM I have had a tier 1 (production down) ticket open with oracle for 1.5 hours and it has not been assigned. It took me a good 30 minutes to open it because I kept getting site errors. Then I spent about an hour on hold when I called in and they said they are having server issues. I was on hold for about an hour when I called in. So I take it alot of people are having problems?