The future of Oracle database administration is constantly
changing. These changes will forever alter the way that Oracle
DBAs perform their work. The following are examples of some
expected changes:
§
:
Just as the UNISYS benchmark used 115 gigabyte data buffers,
many Oracle systems will become fully cached. This is largely a
result of decreasing RAM costs and the advent of 64-bit Oracle
servers.
§
:
The advent of Solid-State Disk (SSD) will produce a faster
replacement for the archaic spinning platters of magnetic coated
media and will someday relive the need for data buffers.
§
:
The Oracle system of the future will run an entire corporate
enterprise on a two server system consisting of a main server
and a geographically distant failover server, which provides
both failover and disaster recovery.
§
:
A single DBA will be able to manage dozens of Oracle instances
in a consolidated environment. This is reminiscent of the
1980s, when the DBA for a large corporation was required to have
credentials, including advanced degrees and skills far exceeding
those of the typical Oracle DBA of the late 1990s.
Having experienced the huge wave of demand for Oracle DBAs in
the early 1990s as the direct result of server deconsolidation,
many DBAs would welcome the return to the old days where they
could manage dozens of Oracle instances within a single server
environment.
The next step is to take a look at disk tuning issues with
Oracle and see how the new AWR and ASH views can help.
SEE CODE DEPOT FOR FULL SCRIPTS
