Indeed. Seems to me that Oracle spends more time trying to figure out a way =not= to support you. We're running some Oracle Financials at work, and they have an "apache" interface to some of their stuff. In order for Oracle to "support" Apache, you have to use exactly their specific Apache that comes bundled on the Oracle install media. You wouldn't believe how long a directory tree you have to traverse in order to just get to the httpd.conf file. That, and the fact that the only way to install it scatters all kinds of crud all over your disk. I spent an afternoon one day weeding out unneeded stuff from their "apache" installation, and finally just gave up because it was just so much stuff.
I've heard horror stories from our oracle group about them not even wanting to talk with you until after x,y,and z patches had been installed even though the patches have nothing to do with the problems at hand.
Not impressed with it am I.
Thats too bad my Oracle DBA came to me the other day asking to start using this on DEV with the hopes of prod but if its going to be a pain to support I am going to have to see some real benefit to it.
I've heard horror stories from our oracle group about them not even wanting to talk with you until after x,y,and z patches had been installed even though the patches have nothing to do with the problems at hand.
Ive got one more for you, I had a pseries box sliced up into a few partitions one of which was running RHEL4(Power). OS was on, x server running ready to do the install right? wrong! After applying a few dozen patches the thing still did not work and *then* they looked at my hardware setup and told me unless there was a true graphics card on the system you cant use the gui setup (which is in and of itself insane). I lost 16 man hours applying patches!