Select Page

Working with Oracle Support

Chuck Edwards | | April 22, 2010

Let’s face it, dealing with Oracle Support can be a nightmare.  Oracle Support often responds in what feels like a put-them-off-so-they-won’t-bother-me fashion, which drags out even Severity 1 issues.  The sobering fact is, sometimes Oracle Support is necessary, and the keys to working with them are:

  • Avoiding their involvement in first place
  • Knowing how to focus and streamline a request through the system

The advantage to using a managed service provider like Blue Gecko is that we manage many customers who all deal with similar problems.  Once we resolve an Oracle bug the first time (through the TAR process or not) we don’t have to go through the entire resolution process again; subsequent customers get the benefit of our collective knowledge with every interaction. 

Because we see so many issues in so many environments, and because of our outstanding staff, who are less likely to require Oracle Support for more than true software bugs, we help our customers avoid the cumbersome support process in the first place. When dealing with Oracle Support, the key is focus:  Deliver tightly defined diagnostics, clear problem descriptions, keep the Oracle Support engineers focused on the specific problem at hand, and the support process will be faster and more accurate every time.  Blue Gecko DBAs deal with Oracle Support on behalf our customers all the time. 

We are 7×24, so we can follow a Severity 1 issue through the night without burning people out from lack of sleep.  Plus, because we are experienced DBAs, we can tell when the troubleshooting process is getting off track and either steer it back in line or escalate within Oracle Support at any time of the day or night.

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Shortcut to Fixing a Corrupted Oracle Inventory

Oracle Central Inventory files are essential to installing and patching software. The process for fixing a corrupted file can be found here.

Chad Cleveland | February 23, 2016

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.


Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.