1. NGS Oracle Service

2. Oracle and the NGS
The NGS core nodes, from the outset, have been partitioned into compute and data clusters. As the NGS matures and the requirement for data hosting grows within and outside of the user community.
Oracle has been chosen as the database backend for both users and services offered by the NGS.
The RAL and Manchester sites are designated as the data clusters with each site having the ability to dedicate up to eight nodes for use by Oracle.

3. Overview of Oracle Service
Hardware and OS
At present three nodes of the Manchester Cluster and five of the RAL cluster are dedicated to providing Oracle, each has:
Dual CPU Intel 3.06 GHz nodes (Supermicro motherboard)
4GB Memory per node
2x120GB IDE disks (1 boot, 1 data – with local scratch around 100GB)
Further to this; each site has dedicated 2TB of the SAN to Oracle in 1/2TB partitions.
The ClusterVisionOS software combined with Oracle RAC make it easy to add resource (via additions of nodes to the Oracle RAC configuration or SAN resource to the Oracle Clustered file system) when the need arises.
All nodes are running Redhat Enterprise 3.

4. Installed Software Oracle RAC9.2.0.5
Oracle Clustered File System (OCFS)1.0.
coreutils4.5.3 (OCFS enabled mv,dd,cp)
tar (OCFS enabled tar)

5. Configuration Overview
Both data-clusters have Oracle setup as RAC across multiple nodes.
Each node has independent copies of the Oracle Home directory (user space programs) but a shared copy of the database. Technically; the Oracle Home directory is sourced from a common image to aid maintenance and mitigate upgrade errors.
The databases are shared between nodes via Oracle's own clustered file system.
Fast interconnects between nodes are based on Myrinet
Each node has external internet access on which listeners can run.

6. Operational Model
Both data clusters are running a large Oracle RAC database across multiple nodes for use by end-users.
Oracle schemas are to be used for user privilege, resource, and space separation/allocation. All of which can be set on a per schema basis.
Special case’s for single instances are accepted.
Initial creation of schema will be by NGS DBA
Management of database then by user
Addition of resource will be by NGS

7. Using the Service - what’s required of the User
Access to the NGS (apply here.)
Completion of Database access form
Data population management

8. Using the Service – What Users can expect
Obtaining access
The Oracle Application form is split into the following key areas
General Info; why? Database name?
Database population; wizards, migration, input model
Sizing; growth, estimated size
Expected usage; read only, number of users.
Technical Details
For very detailed information on the OGSA-DAI installation on the NGS users can refer to NGS Oracle Install & Configuration.

9. Using the Service – What Users can expect
Support
All enquiries and production support for the Oracle service is via the Grid Operations Support Centre (GOSC).
The NGS provides dedicated Oracle DBA support; pluging into and utilising the existing DBA infrastructure at each institution.
The NGS has dedicated support from Oracle

10. Using the Service – What Users can expect
Service Details
9-5 Operational support (monitoring, notification, maintenance) other times best endeavours basis.
Fixed backup regime as decided by site (involving defined downtime – daily overnight)
Full change control managed by NGS

11. Case Studies Convert Grid Convert Grid website Work in progress
SRB Service
Mirroring via Oracle Dataguard of RAL's SRB MCAT database. The case study shows:
Database creation process.
Example completion of all necessary forms.
Work in progress

12. Future Development Process and Procedure
The current deployment processes and access procedures are not fixed. As the service matures and user’s needs are better understood, all processes will be subject to review.
Technical
Review native GSI support from Oracle
Review OCFS 2.0

13. Supporting Documentation
MC NGS Oracle Installation and Configuration
Oracle database request form