Thursday, January 17, 2008



A blog entry on ASM from Christian Bilien with a link to an article on ASM internals with plentiful grotty technical details.


This blog entry is a good example of thinking beyond the obvious to attain a solution. Often when we are faced with a core dump our instinct is to blame the code. But you should always step back a bit and look at all the factors involved: Did we just upgrade the hardware? Did we make key environmental changes? Did we upgrade the RDBMS (as in this case)? In all of these cases we need to make sure that everything works, not just on the surface, but in action, preferably after a restart of everything (sometimes an installer will get the program running, but the next time around the settings that are in memory but didn't make it into configuration files come around to bite you). As always for the DBA, the trouble is not that you are paranoid. The trouble is that they really are out to get you. Several other excellent postings on the Experiments from the Field Blog this week, by the way. Highly recommended.

No comments:

Official, Youbetcha Legalese

This blog is provided for information purposes only and the contents hereof are subject to change without notice. This blog contains links to articles, sites, blogs, that are created by entities other than Oracle. These links may contain advice, information, and opinion that is incorrect or untested. This blog, links, and other materials contained or referenced in this blog are not warranted to be error-free, nor are they subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this blog, links and other materials contained or referenced in this blog, and no contractual obligations are formed either directly or indirectly by this blog, link or other materials. This blog may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. The opinions and recommendations contained in this blog(including links) do not represent the position of Oracle Corporation.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.