Q
Problem solve Get help with specific problems with your technologies, process and projects.

10.1.0.3 RAC environment becomes unresponsive

We have a two-node RAC environment. Currently the stack of CRS, ASM and DB (not shared) are all at 10.1.0.3. We are using Data Guard also. This setup appears to become unresponsive. Are you aware if this version has a lot of problems that would make it unsuitable for a production environment?

We have a customer with a two-node RAC environment. Currently the stack of CRS, ASM and DB (not shared) are all at 10.1.0.3. We are using Data Guard also. They have five separate RAC databases in this environment. This setup appears to become unresponsive (e.g., srvctl status stops responding, a Data Guard "show configuration" fails to respond). Whenever we ask Oracle support for support, their first response is upgrade to 10.1.0.5. Are you aware if version 10.1.0.3 generally has a lot of problems that would make it unsuitable for a production environment?
The patch notes for both 10.1.0.4 and 10.1.0.5 do list some fixes that resolve hanging in a RAC environment, though most indicate that they address problems that are accompanied by additional information in the alert log or trace files (repeating reconfiguration messages in the alert log, LMON trace files, etc).

While it's possible upgrading your patch level will help you, my guess is that it is a configuration issue instead. Does this happen with all your databases? Does a single instance with the ASM and Data Guard databases behave properly? Are the Data Guard databases responding (able to connect, open read only, etc)?

I would start with a single instance, add the Data Guard databases, then cluster the production databases (including the modifications to Data Guard) and identify the point of failure. Check for messages in the alert log, review your trace files and, if you can, get system state dumps when you experience the hanging.

To answer your direct question, I am not aware of 10.1.0.3 with ASM and Data Guard in and of itself being a problematic configuration. I don't think upgrading your patch level is a bad idea assuming your platform and application support it, but I would continue exploring exactly where your problem may lie in the expectation that there is something else going on here. Perhaps it is a bug, but if you are reluctant to upgrade I would ask Oracle to explain exactly what issue and/or bug they are trying to address by requesting you to do this. If upgrading is an option I would do it if for no other reason than to move the TAR along so that you can get to the root of the problem.

Good luck,
Bill

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close