How to search the Cause of Errors

I’ve been working on OBIEE and Oracle products in general since 2008, it has been so far a great experience with an enormous amount of information being available freely in internet.

When trying to solve problems this amount of information can be a treasure but also a risk since the information contained in any website can be partial, not relevant or in some cases completely wrong for the subject searched. As an unexperienced person (but also for experienced) it’s difficult to distinguish whether the content of a website can be followed and trusted and sometimes even replies to public forums can’t be a valid source since different problems provide the similar wrong behaviour and can be confused.

I’m very fortunate to work for Rittman Mead, a company made up of experts, which is a unique source of knowledge for any problem or question about work. Almost every possible solution was already experimented by a colleague and if this is not the case either what I’m trying to achieve it’s impossible or too new (and I’ll be the one sharing my knowledge with other colleagues).

In general however this is the standard process I follow when looking for a problem solution or a way to achieve a goal:

  • RTFM: Read the product documentation!
  • Google Search: being smart, write the key fields (e.g. error number, error keywords, components name), check results and check if they exactly apply to the problem.
  • Oracle Support Search: Oracle support is the main place to search for oracle problems. Bugs, Patches and Service Requests can be found there and the replies are coming directly from Oracle support team.
  • Ask internally: If you are member, like me, of a company having experts, ask them, they may have seen the same error/problem and may already know a fix.
  • Ask a question in OTN Forums: There are a lot of peers willing to give an help on any subject. Remember how to ask a question the smart way!
  • #obihackers on IRC: yes IRC, seems odd but there is a growing community of OBIEE experts coming from different companies and parts of the world in IRC channel #obihackers that may give you a good suggestion about what you are looking for.

 

Every route you decide to follow bear in mind what written before: check any reply you find since it could be partial, not relevant or in some cases completely wrong for the subject searched. Don’t start changing parameters only because a single post on a forum said so, try to cross reference (possibly with official documentation) any config changes you’re reading before trying to implement it.

The last rant is about forums and Expertise level based on number of replies, don’t assume a reply is correct just because the person who wrote it it’s level X on a specific forum, especially if the reply tells you to change parameter Y without any other specification.

Level X can be achieved by 10 correct answers out of 10 suggestions by a real expert or 10 correct answers out of 1000 random suggestions by someone that just has a lot of free time. Most of the times experts will give you not only the reply to what you are looking for but also an example, a detail description or a reference to an official document.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

About ftisiot

BI Tech Lead at Rittman Mead, Specialised in OBIEE, Food, Wine and Football lover.