M ODULE 2 D ATABASE I NSTALLATION AND C ONFIGURATION Section 1: DBMS Installation 1 ITEC 450 Fall 2012

DBMS I NSTALLATION B ASICS Understand the prerequisites for the specific version of DBMS Version of the operating system Hardware components: cpu, memory, available storage Related software: java, network Read the installation guide Understand the installation process and procedure Follow the explicit instructions Mechanics of the installation process is a relative simple affair Fall ITEC 450

H ARDWARE R EQUIREMENTS Basic CPU requirements: minimum processor speed Storage requirements: available free space, backup DBMS software itself: 1 – 2 GB depending on OS Database: size of applications and data Memory requirements: amount of memory Memory structures: data cache, data dictionary, SGA Application data request -> read the data in the disk -> copy the data to the memory -> process the data -> write the modified data from memory to disk Available swap space Fall ITEC 450

DBMS C ONFIGURATION Understand DBMS components Installation user privilege: Windows – administration role; UNIX – unlimited resource, a special group Licensed DBMS components: partition, spatial, enterprise Platform version requirement: Windows XP or higher, HP-UX 11, Solaris 10, AIX Operating system requirement: patches, kernel parameters, message queue, DLL files Program requirement: C++, Cobol, Perl Define the initial settings Inputs during the installation process Installation configuration file Fall ITEC 450

DBMS I NSTALLATION V ERIFICATION Ensure the clear understanding of all error messages or popup windows Take screen shots of all questionable error messages or popup windows Review installation log files Run tests if possible Fall ITEC 450

U PGRADE AND P ATCH DBMS version – major change, such as Oracle 11g or SQL Server 2008 Release – major function enhancement Patch – bug fixes Example: Oracle (Version 11, Release number 2, Patch release number 1) SQL Server 2008 SP1 CU6 (Version 2008, Release of Service Patch 1, Patch of Cumulative Update package 6) Fall ITEC 450

DBMS C HANGE C ONSIDERATION Database structure changes, application features changes Planning for DBMS changes Testing environment establishment Regression testing of applications: functions, performance Downtime and lost business opportunities during the DBMS change. Supporting software products may lack immediate support : purchased applications, DBA tools, query tools, interface programs Cost of Change Cost of the new version might be changed Planning, installing, testing, and deploying in both DBMS and applications using databases Fall ITEC 450

D ATABASE S TANDARDS AND P ROCEDURES Standards – common practices that ensure the consistency and effectiveness of the database environment Database naming conventions Names of database, data files, objects (table, index, procedure, trigger, etc.) Length of names Abbreviation Roles and responsibilities Database application development standards: coding standards, performance tips and techniques Procedures – scripts and processes for handling specific events Application migration procedures Design review process Fall ITEC 450

M ODULE 2 D ATABASE I NSTALLATION AND C ONFIGURATION Section 2: Oracle Installation 9 ITEC 450 Fall 2012

O PTIMAL F LEXIBLE A RCHITECTURE (OFA) Organize large amounts of complicated software and data on disk, to avoid device bottlenecks and poor performance Facilitate routine administrative tasks such as software and data backup, which are often vulnerable to data corruption Facilitate switching between multiple Oracle databases Adequately manage and administer database growth Help eliminate fragmentation of free space in the data dictionary, isolate other fragmentation, and minimize resource contention Fall ITEC 450

FILE NAMING STANDARDS Fall ITEC 450

F ILE S TRUCTURES FOR O RACLE Windows – Take defaults as much as possible UNIX – Company standards, examples Software - /u01/app/oracle/product/ Administrative files - /u01/app/oracle/admin/hrdb Database files - /u02/oradata/hrdb/control01.ctl Fall ITEC 450

F ILE S TRUCTURES FOR O RACLE Path to Oracle software is called ORACLE_HOME containing Oracle binaries Defined as a variable within your system E.g. ORACLE_HOME/bin/runnit.exe Each installation has its own ORACLE_HOME Examples: C:\oracle\product\11.2.0\db1 c:\oracle\product\11.2.0\client1 Contains a bin directory that holds most of the executables Fall ITEC 450

O RACLE HOME Fall ITEC 450

I NSTALLING THE S OFTWARE Advanced Installation Select Installation Type: Enterprise Edition Select Configuration Option: Install database software only Note: Some of the slides are from Oracle 10g Database Administrator: Implementation and Administration by Gavin Powell and Carol McCullough-Dieter Fall ITEC 450