A short demonstration of how incorrect fixed object stats can really bog down an E-Business Suite instance startup.
-
General Info
-
Categories
-
Feeds
-
Content License
-
Posted elsewhere
A short demonstration of how incorrect fixed object stats can really bog down an E-Business Suite instance startup.
Two recent requests in rapid succession (“why is the instance running so slowly when I do X?” and “why is this mount point filling up with .dbg files?”) prompted me to dust off an old script.
Trying to start a database listener that doesn’t exist generates log files. In older versions of the database, it’s just one file, but what about in 11g, with its fancy Automatic DIagnostic Repository?
Sometimes, even on the 3rd or 4th run-through of a database upgrade test, it’s possible to miss something. Practice makes perfect.
Random notes about the March 2010 VanOUG meeting presentations
Notes on upgrading OLAP workspaces when migrating a database from 32-bit to 64-bit Linux.
Is opatch failing with the message “ApplySession failed: Patch ID is null.”? Might want to verify your opatch version…
Oracle has, at long last, released a version of the RDBMS for Mac OS X Intel. Not all features are supported, but on the other hand, it will run natively even on a non-Server version of Leopard. Woohoo!
When installing Grid Control on a Linux or Unix platform, a recommended practice is to install the monitoring agent software as a user that doesn’t own the ORACLE_HOMEs to be monitored. This poses a challenge when configuring monitoring for some targets, particularly those based on Oracle Application Server 10g. This post lists some changes you can make to work around a variety of target discovery and metric collection errors.
Here are my impressions of two Oracle certification exams I’ve had the opportunity to take in the past few months: 1Z0-040 (Oracle Database 10g: New Features for Administrators), and the beta version of 1Z0-238 (Oracle EBS R12: Install, Patch and Maintain Applications)