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.
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.