It is interesting, though there are definitely a couple of pieces I
disagree with. For one, the ODA adds complexity, it does not reduce it. I
would never recommend an ODA for anyone. SQLnet files should all go in a
directory defined by $TNS_ADMIN. Its been that way with oracle for a very
long time now, I dont see a reason to change it.
A single listener makes a lot of sense, I have seen some multiple listener
environments, but I never really saw the point.
He doesnt mention RAC, but in these days of virtualization, I havent seen
many true RAC use cases. VMware allows your virtual machine to restart
within 5 minutes or less on a new host if it crashes, and adding CPU and
memory can be done hot in most cases, so with the exception of a very few
cases where no down time at all can be tolerated, RAC is pretty well
obsolete, which really reduces complexity for the DBA.
On Fri, Feb 14, 2020 at 8:36 AM Jared Still <jkstill@xxxxxxxxx> wrote:
it isn't just oracle that is getting more complex: all software is
looking the the revolt against complexity soon...
re this comment in the article
- put your Oracle*Net configuration files in /etc because you don’t
want multiple files in multiple homes
before doing this, it would be good to understand the ramifications of
putting tnsnames.ora (if used) in /etc
ie. no tnsnames.ora in any OH will then ever be considered, probably not
what you may expect
On Mon, Jan 27, 2020 at 02:19 Juan Miranda <jmirandavigo@xxxxxxxxxxx>
*It’s so easy to increase complexity without any good reason. *
*Simplifying is the power of saying NO. No to interesting features and
configurations that are not absolutely necessary. *
*All you need for your databases is reliability, safety, availability,
*Simplicity helps you in that way.*
Certifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultant at Pythian
Pythian Blog http://www.pythian.com/blog/author/still/