Storing Windows-based Oracle Databases on the HP NAS 8000

location of alert logs and trace files
Log and trace files can be an excellent source of information for analyzing problems with the database. If
the Oracle executables/binaries are installed on the NAS 8000, the default location for Oracle to write the
alert log(s) and trace files will also be on the NAS 8000. In an OFA-compliant configuration, by default,
these files would be under the Oracle base directory tree, in the admin/oradb directory(ies) in the bdump,
cdump and udump subdirectories. In the unlikely event of a NAS 8000 system failure, these directories
and their contents may be unavailable which could create a situation in which the files needed by the
Oracle DBA and system administrator to analyze and correct the problem would not be available. The
location of these files can be specified in the init.ora file via the background_dump_dest, and
user_dump_dest parameters. Although a failure affecting the availability of the NAS 8000 is highly
unlikely, these files can be placed on the Oracle server through the use of these parameters.
installation of Oracle on the Oracle server
The most common and recommended configuration is the installation of the Oracle binaries and support
files on the Oracle server with the NAS 8000 being used primarily for storing the Oracle database data
files, redo logs and archived redo logs. In most environments where Oracle is already installed, this is the
configuration that will be adopted. In this scenario, the database administrator must still be careful with the
placement of the database specific alert logs and trace files (see above), although the default location will
place these files on the Oracle server rather than on the NAS 8000.
creating new database(s)
A new database can be created either through the use of the Oracle Database Administration Assistant GUI
(dbassist), or through the use of command file(s) and SQL scripts. The control files, redo logs, archived
redo logs and data files can reside solely on the NAS 8000, or can be mixed on the NAS 8000 and on
the Oracle server. Mixing the location of the data files between the NAS 8000 and the Oracle server also
means that other aspects of database performance and management can be taken into account when
designing and implementing the database. For example, it may be advantageous to have the SYSTEM
tablespace remain on the Oracle server while all of the other tablespaces are placed on the NAS 8000.
Please refer to the section on NVRAM for important information regarding placing the database data files
on both the Oracle server and the NAS 8000. A good method for generating a basic SQL script for
creating a database (if needed), is to use the Database Administration Assistant GUI, but rather than
actually create the database, elect to save the generated command scripts. This usually results in several
command files and SQL script files being created. Once the files have been saved they can be edited as
needed to “fine-tune” the creation script, for example, adding tablespaces, setting the management attribute
of a tablespace (local versus directory), etc. An additional benefit to using a SQL script for creating a
database is the same exact database infrastructure can be created on other systems (such as a development
or secondary site) quickly and easily through executing the same SQL script.
share level security
creating a database with the Oracle Database Administration Assistant (dbassist)
When the NAS 8000 is in ‘Share’ level security, the dbassist GUI tool can be used to create a database. In
Share level security, the NAS 8000 administrator, in conjunction with the Oracle DBA can decide whether
or not to password protect the CIFS share(s) that house the Oracle database. It is recommended that the
shares that house the Oracle database be password protected as well as reserved exclusively for the
database. Depending upon the version of Oracle installed, it may be necessary to create one or more
“permanent” drive mappings on the Oracle server to the Oracle shares on the NAS 8000. Some versions
of the dbassist tool do not recognize Universal Naming Convention (UNC) paths for accessing the NAS
8000. When the initial connection between the Oracle server and the NAS 8000 has been established for
accessing the Oracle share on the NAS 8000, the Oracle server will be queried for the appropriate
password (if the share has been password protected). The Oracle server will only be queried for the
password when the connection is established, not each time a share is accessed. Please refer to the
constraints section for important information regarding the use of HP Virus Pro Real Time Protection on a file
volume with an active Oracle database.
setting service owner in share level security
Since the NAS 8000 is in Share level security, the only security checking performed is if the share has a
password assigned. Because the Oracle server uses the password when the connection to the NAS 8000
7