Wednesday, November 10, 2010

Oracle Infogram This Week: EBS, Exadata, Design, RDBMS

A followup on the Exadata webinar that the folks over at Pythian blog offered, a recorded version: Exadata Implementation Results.

Also at Pythian is a link to the latest Log Buffer, a blog of links similar to the Infogram in many ways: Log Buffer #205, A Carnival of the Vanities for DBAs.

Also in the realm of Exadata, be sure to tune in to the Oracle Exadata Online Forum November 16th. The Oracle Data Warehouse Insider lets us know it's coming up.

Data Entry and Money

It's amazing what a single field can do. Have you reviewed your website and internal forms lately? I remember working a contract where one suggestion saves us millions of keystrokes a year. 999 times out of a thousand users were calling for an 'XYZ' type of file, but you had to type that XYZ in every time. By defaulting the field we saved all those extra keystrokes. That contract was also a good learning platform for me on taking care about changing fields around when dealing with 'heads down' data entry people. That seems to be a dying breed in these days of mice and Java clients, but the elements of good form design are just as important as ever. Oracle AppsLab has a link to an article on how Expedia saved a bundle of money and prevented customer frustration (which loses masses of money) by simply dropping an optional field: Expedia Saved $12 Million a Year by Deleting One Input Field.


A blog that's a new one to me, Oracle by Madrid, has a good posting on alternatives for dealing with getting access to the alert log when it is secured (that is to say, the DBA getting to it, since there are some companies with such comprehensive security that access isn't a given). One of the alternatives is an external table: Reading the alert.log as a local table

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.