Recently, one of my clients required that I secure several of their printers in E-Business Suite so that only certain users could access them. User specific printer security is not standard functionality in Oracle E-Business Suite 12.1.1 but with a little security-through-obscurity we met the requirement to the clients satisfaction. The requirement was a result of the inital setup which caused these printers to appear on the Printers list of values in the Concurrent Request submission screen under "Options".

 

The purpose of this post is to outline how storage works on Exadata.  We’ll look at the host-based storage on the compute nodes and storage server nodes, and then look at the cell storage characteristics, mapping these to ASM storage and finally, database storage. 

 
In this post, I'm going do to a little follow-up to the blog at:
 
 
I received quite a bit off both online and offline feedback on this post and wanted a chance to re-position my messaging a bit.
 
Direct Reads and Smart Scan
 
The most significant performance feature of Exadata is generally agreed to be smart scan.  There are several prerequisites for smart scan – most notably, the query must perform direct reads.
 
I frequently encounter "pixel perfect" custom reports in both 11i and R12 that were created using Oracle Reports for data extraction into an XML stream then passed to the BI Publisher Output Post Processor for formatting, typically as a PDF.

 

I recently attended RMOUG and saw a presentation for Database Workload Replay, a feature I've been meaning to take through its paces for quite awhile but never made time to test it out. Tonight I decided to give it a shot to see how difficult the process was, and as I discovered, it wasn't too bad at all.   Below I'm going to walk through the steps to do some simple Workload Replay tests.  Nothing earth-shattering about any of this, it's pretty well documented.

 

This is the first of a three part series on "How Smart Companies Manage Data in the 21st Century." I am going to focus on trends and statistics for this first part and then as we progress, we will dive into how to get actionable information out of data.

 

Over the years, Oracle DBAs and developers have used different techniques to identify performance problems. Many books have been written, white papers published, blogs blogged upon, and so forth.  Nearly every Oracle DBA has the term “tuning” somewhere on their resume.  Common tuning approaches have included:

 
For quite some time, Oracle's kernel has been well-instrumented to capture detailed wait event information.  Google “Oracle wait events” and you’ll come up with a wide range of great papers and publications about Oracle wait events, and also see http://docs.oracle.com/cd/E11882_01/server.112/e16638/toc.htm.
 
Several cluster-specific wait events are populated in RAC environments.  
 
Oracle Database Appliance Installation
 
In this post I'm going to share  the end-to-end process of getting an Oracle Database Appliance (ODA) up and running at a client site.  No pictures, just words.   And right up front, I'm going to tell you this is likely going to be the shortest blog I'll ever post on www.centroid.com/knowledgebase.