The Payment Administrator is a collection of settings to define the various components used to create payables documents using the Payment Process Request.  There is a wide variety of processing options available and the Payment Administrator groups these together in a single place. This article will focus on two of the more common elements, the Payment Process Profile and Payment Formats.


In order to properly manage internal software license usage within a global company, license management, administration and support must be carefully considered. A centralized licensing infrastructure is ideal, allowing for:


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: