Get the solution from the other source.

AS a DBA it is not surprise if you can not solve a specific issue.

Many issues can not be solved by yourself And many issues have no root cause actually.

Weird issue often was triggered for a big enough system by a very simple steps you took.

Thus DBA always has many works to do if they’d like.

They are not satisfied with the only workaround on the issue even though the workaround works well.

They want to find what is the root cause on the issue then they can control the issue well.

So Almost all DBAs like to do the deeply investigation on the issue and give their own explanations on the certain issue.

They like to do the experiment to reproduce the issue in their house.

But when the issue happened in the Prod it seems there is no enough time to be given to do this especially for the high availability system.

Recover the availability of the system asap seems to be more crucial than finding the root cause at that time.

On such occasion, Dealing with the issue with your own indigence is necessary and the ability to Brainstorm with other DBAs is also a good habit. Maybe your friends or co workers had the experience on such issue. Do not always think you can do everything. No one has all the answers! To consult with other DBA friends on what you believed was an extremely thorny problem is a good idea. Often you will be surprised when the other DBA sees an obvious fact that you have simply missed. Regardless of the methord or tools used, the knowledgeable DBA will be able to consider a much broader range of potential solutions on certain issue. This is because a good DBA will always understand the cause-and-effect relationship between database changes and performance. He will also see that many offered solutions are irrelevant, because they do not only focus on the underlying problem. So making DBA friends is a good habit to a DBA. Be generosity and give your answers when asked.Helping the others also is a chance to improve your own ability and extend your own experience.

Plus, getting the hints from the internet is also important.

You can not depend on the Oracle support and DBa friends all the time. No one is more familiar with your system and your application.

You can try to get the hints from internet and combine them with you practical application and analyze the cause and effect between them, you can figure out the solution in most time.

No one can replace you to resolve the issue if the issue is related to your specific application or even specific configuration setting.

You can integrate all possible reasons, review all relevant logs and find all possible clues to analyze the cause and effect of the issue.

Summarize:

Do not hesitate to ask help and do not stop to do the analysis by your self.