Database Reference
In-Depth Information
System Integration:
As stated earlier, the Oracle suite consists of several
components. Two observed problems here:
•
There are (in the writer's view) too many splinter components,
many of which could be merged.
These components are not all gracefully integrated (one example
•
of this is OJD of Oracle 10G; this component requires some
caution in order to be properly installed and configured).
The reason for this is that Oracle shows signs of after-thought evolution, rather than
purposeful planning. This problem becomes evident when one considers for example,
pre-10G versions of OEM and DBCA. These two products could have been easily merged
with a third — Recovery Manager (RMAN) — into one product, providing comprehensive
coverage of database administration. The problem of integration becomes very
glaring when full installation of Oracle (particularly so on Unix and Linux platforms)
is attempted. You will observe that in Oracle10G and 11G, the OEM has been greatly
improved. This was not always the case.
Code Generation:
Earlier versions of Oracle provided very negligible automatic code
generation. For instance, early versions of Form Builder provided a useful environment
for application development, but did not generate much PL/SQL code. The developer
was still required to memorize SQL and PL/SQL syntax. It must be said, however, that
components such as OEM, OSQLD, and DBCA do generate a considerable amount of
code. It is hoped that this trend will continue in the future.
Database Management:
Most DBMS suites have a simple, straightforward way of
dealing with creating a database and populating it with database objects. Oracle does not.
To achieve this objective, you have to follow the following procedure:
•
Create an Oracle database.
•
Create one or more tablespaces. Each tablespace will consist of at
least one datafile.
•
Create user(s) and grant appropriate quotas to the tablespace(s).
•
Populate the tablespace(s) with database objects.
The DBA or someone with DBA privileges typically does the first three steps. Each of
these steps is multifaceted, involving several subservient steps. By using DBCA and OEM,
these steps have been greatly simplified, but they can still be thought intensive. The final
step can be done by users with appropriate privileges.
Affordability:
Traditionally, Oracle solutions have been prohibitively expensive for
small and medium size companies. In recognition of this, Oracle Corporation provides a
special educational program for colleges and universities in North America. This program
is called the Oracle Academic Initiative (OAI). Under this program, enrolled institutions
pay a nominal membership fee; this entitles them to free access to Oracle products, which
they are authorized to use for education and research purposes.
Combined Effect:
When we combine the effect of all the flaws mentioned, the end
result is that Oracle remains a product that is relatively difficult to learn and use. On
the other hand, if these problems were to be corrected, the product would truly qualify
as a “killer application” [Downes, 1998]. Moreover, Oracle 9I, 10G, and 11G represent
significant improvements over its earlier versions of the product.
