Skip to main content

RTFM

No, this is not another rant about just anyone who doesn't know how to read manuals.  It's about me.  And I don't know how to read manuals.

After downloading Oracle 10g for Mac OS X, I spent some time getting it installed.  After a false start (where I created the dba group with GUID 201 - the same as the Guest account on Mac OS X), I managed to get it up and running.  There's an excellent guide here, which walks you through just what you need to do and little more:  http://blog.rayapps.com/2009/04/12/how-to-install-oracle-database-10g-on-mac-os-x-intel

Once I could SQL*Plus into the database, I downloaded the Companion CD, and started to install that, thinking that the Oracle HTTP Server would be a part of it.  Well, much to my disappointment, it was nowhere to be found.  After some digging on the OTN Apple Forum, I came across this post:  http://forums.oracle.com/forums/thread.jspa?threadID=654233&tstart=0&start=15

The important line in that post points here:  http://download.oracle.com/docs/cd/B19306_01/relnotes.102/b25285/toc.htm

And if you look at Section 2 - Unsupported Products, you'll notice that Oracle APEX & Oracle HTTP Server are definitely not alone.  In fact, here's the complete list:
  • Oracle Real Application Clusters (Oracle RAC)
  • Oracle Clusterware
  • Automatic Storage Management (ASM)
  • Network File System (NFS)
  • Network-attached Storage (NAS)
  • Raw devices
  • Oracle Application Express (formerly known as Oracle HTML DB)
  • Oracle HTTP Server
  • Oracle Workflow
  • Oracle Enterprise Manager Database Control
  • Oracle Management Agent
  • Pro*Fortran
  • Pro*COBOL
  • iSQL*Plus
  • Oracle Ultra Search
Thus, all was for almost nothing, as a database is just not a database, unless it has APEX in it.  I suppose I'll just wait it out, hoping that at least APEX & the HTTP Server make their way into the next release, which doesn't take as long as the first!

Comments

Byte64 said…
ROTFL!
RTRN!

The good news is that i didn't even start installing it yet...

Flavio
Scott said…
Wish that I could say the same thing! :(

- Scott -
Alex Gorbachev said…
Interesting that iSQL*Plus has been installed automatically (and looks working). So maybe this list might be not supported but *could* work.
Scott said…
Really? That's one of the features that's technically not supposed to be there.

I always de-select it when I install Oracle, so I don't have it.

- Scott -
Scott said…
Alex - thanks for that link! I am up and running now!

- Scott -

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p