Oracle10g Universal Installer New Features

Database Management Choices Local or Centrally Managed
Local OEM Database Control for managing standalone database installations
Centrally Managed OEM Grid Control for managing multiple, enterprise-wide Oracle databases & RAC
Requires:
Oracle Management Agent
Oracle Management Service
Oracle Management Repository
Grid Control Console

OEM requires an Oracle HTTP Server which is now bundled on the Companion CD

To invoke OEM: http://localhost:5500/em (The default port number is 5500)
To configure OEM: $ORACLE_HOME/bin/emca (Enterprise Manager Control Assistant)
Start/Stop dbconsole process: emctl [ start | stop | status ]

You can change the default port number by editing $ORACLE_HOME/install/portlist.ini

Automatic Pre-Install Checks
Checks operating system version compatibility, 32-bit/64-bit compatibility checks. Looks for relevant O/S patches. Checks UNIX kernel paramerers, sufficient memory and disk space and that the ORACLE_HOME is empty.

New File Storage Options
Choice of configuring ASM, Raw devices or file system files.

Backup & Recovery Options
Enable automatic backups and create a flash recovery area

DB User Password Specification
Set passwords for SYS, SYSTEM, DBSNMP & SYSMAN users

Cluster Ready Services
Software to virtualise existing cluster software (Veritas Cluster Server, HP ServiceGuard, SUNCluster)

Enterprise Configuration Management
Oracle can be configured to gather certain host and database configuration information automatically every 24 hours.

Metalink Integration
Receive security alerts direct from Metalink. Download, stage and apply patches to Oracle server software.

Oracle Software Cloning
Only with OEM Grid Control

Database Cloning
The OUI has a database clone wizard that uses RMAN to clone databases (must be 8.1.7 or higher). It can also clone password files, init.ora and SPFILES.

Installation Performance Enhancements

Only a single CD is required to install Oracle Database 10g
The CD pack consists of:

- Oracle Database 10g software
- Companion Disk (HTTP server, HTML DB, Demo schemas)
- Oracle Database 10g Products (Workflow, Legato)
- Oracle Database 10g Client
- Oracle Documentation
- Oracle Enterprise Manager (OEM) Grid Control & Premium Pack Options

Minimum Hardware Requirements
Memory: 256Mb (512Mb if OEM Database Control)
Disk: 2.5Gb
Swap: 1Gb
/tmp: 400Mb

Easier and Cleaner De-Install
1.shutdown database and ASM instances
2.emctl stop dbconsole
lsnrctl stop
isqlplusctl stop
3.Launch Oracle Universal Installer
4.Click on De-Install
5.Select ORACLE_HOME and click on Remove
6.Remove the directory using rm or equivalent O/S command

Automatically Launch Sofware
Oracle Management Agent
OEM Database Control (dbconsole process)
iSQL*Plus Server (also requires HTTP Server)

Response File Enhancements
New header format for easier manual edits
No need to specify an X-Windows server character-mode console
No need to set DISPLAY environment variable
No GUI classes instantiated

Oracle Server Configuration

Simplified Instance Configuration with DBCA
DBCA understands ASM, SPFILES, UNDO tablespace, pga_aggregate_target, automatic shared memory management and other new 10g (and 9i) features.

Creates a mandatory SYSAUX tablespace, required for the new Advanced Workload Repository. Default size is 500Mb.

Configure a flash recovery area (db_recovery_file_dest, db_recovery_file_dest_size)

Configuration of OEM Premium Pack Options:
Diagnostics:database and host performance monitor, ADDM, AWR, Event/Event History
Tuning:SQL Access Advisor, SQL Tuning Advisor, Object reorgs
Configuration Management:database and host configuration, patch download, staging & deployment, configure policies

Policy Based Database Configuration Framework
Default, pre-configured default configuration recommendations, for example
Critical Patch Advisories for ORACLE_HOMES
Insufficient number of control files
Listener password policy

Policy violations can be prioritised as high and medium in categories:
Storage
Security
Objects
Configuration (of database, host, listener)

Navigate to the OEM page
OEM Database Control -> Diagnostic Summary ->All Policy Violations

Simplified Parameters
The Oracle 10g DBCA categorises init.ora parameters as either Basic, Advanced or Deprecated.
Examples of Basic parameters are db_name, db_block_size, processes, control_files
Examples of Advanced parameters are cursor_sharing, cursor_space_for_time,
Examples of Deprecated parameters are mts_dispatchers, undo_suppress_errors, parallel_automatic_tuning.

select name from V$PARAMETER where ISDEPRECATED = ‘TRUE’;

Irreversible Datafile Compatibility
The compatible parameter is irreversible. The minimum value supported by 10g is 9.2.0. The new default value is 10.0.0

alter database reset compatibility; is now obsolete.

Database Feature Usage

A new Oracle background process, MMON, the Manageability Monitor records database feature usage and certain high-water mark statistics. MMON stores all it’s findings in the AWR and can be viewed by querying dictionary views.

DBA_FEATURE_USAGE	DBA_HIGH_WATER_MARK_STATISTCS
Advanced Replication Oracle Streams FGA/VPD Auditing	Maximum number of datafiles Maximum number of tablespaces Maximum number of concurrent sessions Maximum number of services Maximum size of tables & indexes

Navigate to the OEM pages
OEM Database Control -> Administration -> Configuration Management -> Database Usage Statistics

Upgrading To 10g

Upgrade paths from all terminal releases since 8.0.6 are supported.

Upgrading from	Use Script
8.0.6	u0800060.sql
8.1.7	u0801070.sql
9.0.1	u0900010.sql
9.2.0	u0902000.sql

DBUA - Database Upgrade Assistant
The DBUA breaks down the upgrade into 3 parts.

Pre-Upgrade Validations
Backup the database using RMAN
DBUA will ask if you wish to recompile any invalid objects at the end of the upgrade process.

Upgrade Information Tool( utlu101i.sql )
Suggest a size for the mandatory SYSAUX tablespace
Check the size of online redo log files. Will issue a warning if the online redo logs are < 4Mb
Check tablespaces have enough free space
Init.ora parameters. Check for deprecated and obsolete parameters
DB Version & compatible. Will warn if the compatible parameter is not set correctly.
Provides a time estimate of how long upgrade script will take to run.

Post-Upgrade Status Tool( utlu101s.sql )
Checks DBA_SERVER_REGISTRY for INVALID components
Checks component version compatibility
Suggests any corrective actions following the upgrade. Suggest scripts to run.

At the end of the backup process, DBUA offer the opportunity to back out the upgrade. It does this by restoring the database using RMAN.

Manual Upgrade Steps
1. Install 10g executables into a new ORACLE_HOME with the OUI
2. Run the Upgrade Information Tool ( utlu101i.sql ) and act on any advice
3. Backup the database
4. Copy the parameter file into the new ORACLE_HOME
5. Start the database in upgrade mode with the new startup upgrade command
6. Create a SYSAUX tablespace
7. Run the upgrade script according the version that you are upgrading from. See supported upgrade paths above.
8. Compile any invalid objects ( utlrp.sql )
9. Run the Post-Upgrade Status Tool (utlu101s.sql )
10. Update oratab with the new location of ORACLE_HOME (/etc/oratab, /var/opt/oracle/oratab)

Customer Testimonials

Alex worked on my team in the role of Developer/DBA and helped to support a large, complex, and mission-critical application for our customer. Alex possesses highly developed technical skills, he learns quickly, and he works very well with customers, team-mates, and managers.

Bob Hawkins
Team Manager
OAO Technology Solutions

Email Us