Tools | Thoughts from James H. Lui

During a routine installation, I managed to mis-type the filesystem path for the ORACLE_BASE during execution of the Oracle Universal Installer (./runInstaller).

[nb: ORACLE_BASE by normal definition should be a standard starting filesystem mountpoint under which all other instance-specific data/files for this ORACLE_HOME would be found. Typically contains your diagnostic logs, Fast Recovery Area files, all configuration tool logs, and any Flashback checkpoint saves.

$ORACLE_BASE/diag/.

./asm
./clients
./crs
./diagtool
./lsnrctl
./netcman
./ofm
./rdbms
./tnslsnr

$ORACLE_BASE/admin/<SID>/.

./adump # Audit data./dpdump # Data Pump related
./pfile # init.ora files generated by config tools

–end of note]

Since the service account (oracle) had filesystem permissions to do so, it went ahead and put all of the flashback recovery, diagnostics, and audit trail files (and my backup controlfiles) into the incorrectly named directory. The database itself was running, but how to correct this without starting all over again?

Start with backing up your init.ora configuration from spfile to pfile format:

SQL> create pfile from spfile;

File created.

(this defaults to $ORACLE_HOME/dbs/init.ora)

Then shutdown services:

SQL> shutdown immediate;

Database closed.

SQL> exit;

#oracle> lsnrctl stop

Now go find all the places you’ll need to modify/correct the ORACLE_BASE filepath declarations:

$ORACLE_HOME/dbs/init<SID>.ora

$ORACLE_HOME/network/admin (or $TNS_ADMIN)

listener.ora: ADR_BASE_LISTENER
sqlnet.ora: ADR_BASE
(Note: these two are auto-generated using netca – the Oracle Net Configuration Assistant, if you execute that after making the database and environment-side changes.

$ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml : ORACLE_BASE

All finished editing? Start everything back up:

#oracle> lsnrctl start

SQL> startup pfile=?/dbs/init<SID>.ora — to use revised settings

SQL> create spfile from pfile; — copy new settings to spfile

SQL> shutdown immediate;

SQL> startup; — uses spfile instead

Now future installs using dbca, dbua and netca should recognize your defined/modified/corrected ORACLE_BASE.

http://coll13.mapyourshow.com/5_0/sessions/sessiondetails.cfm?ScheduledSessionID=18A0CFC5

(Now history…but we’re in-queue for #OOW13)
Collaborate asked ” What about Database 12c? ” @IOUG is pleased to deliver! In MHB4A 830A Th, Just before you hop on the plane/bus/car/train/buffalo (it’s Denver…) back home, get tuned in, turned on, updated, clarified, ask your what is it questions, bring clarity to the cloud, plug-in, charge-up and get what you travelled all the way here to find out the details about the database formerly-known-as-next-generation (psst…that means “12c”).

No,it’s not GA yet (General Availability). Yes, we are both knowledgable Beta participants under NDA. Yes – you need to know more than you do today based upon your experience with even 11gR2. Bring your coffee, munchies and your questions. And prepare for some answers. Finally.

How? Because Oracle teams with IOUG for a reason in this area – we know how to educate people, with the right way to do it – even for a product that isn’t here (quite yet.)