1 / 13

ISYS366

ISYS366. Installation. System Architectures. Process View Dedicated servers Multi-threaded servers Processor View Single processor systems Multi and parallel processor systems Database View Two-phase commit Replication. Mirroring & RAID. Eats up a lot of disk

dorjan
Download Presentation

ISYS366

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISYS366 Installation ISYS366 - Installation

  2. System Architectures • Process View • Dedicated servers • Multi-threaded servers • Processor View • Single processor systems • Multi and parallel processor systems • Database View • Two-phase commit • Replication ISYS366 - Installation

  3. Mirroring & RAID • Eats up a lot of disk • RAID 1(Redundant Array of Inexpensive Disks) – good for temporary tablespace datafiles, control and log files (provides for redundancy) • RAID 5 – better for OLAP, DSS and DW because writes are so much slower on RAID 5 ISYS366 - Installation

  4. Installation • Before installation – full backup • Read disk and memory requirements • Oracle10g? • 512MB RAM?, 1G?, ????? • 1G to several Gig HD ISYS366 - Installation

  5. Installation • Types of Installation • Upgrade – basically, you are overwriting old files • Migration – you are creating a new directory structure, etc. and copying the datafiles. • Migration is preferable to upgrade. • Suggested configuration • Development server • QA server • Production server ISYS366 - Installation

  6. Installation • Check the EXACT version of your operating system • Get the EXACT installation manual for your OS • Try installing a default instance and “poke around” • NB – Oracle block sizes (8+) should be MULTIPLES of the OS block size • O8i – you can connect as INTERNAL through SQL*Plus ISYS366 - Installation

  7. An Example using Oracle • UNIX • Check and configure shared memory • Create /u01 for S/W and /u02-/u04 for databases • Create a DB admin group in UNIX • Create UNIX Oracle account • Name is usually Oracle • Home is ORACLE_HOME • Assign default shell • Et cetera (environ variables, umask values, etc.) • oratab (/var/opt/oracle) ISYS366 - Installation

  8. Separating Objects (on devices) • Prevents I/O bottlenecks and contention • Raw Disk (partitions) – for both UNIX and NT • Up to 40% performance improvement • Why you need a file handling facility like Oracle's to take advantage of this (compare Ingres) • Oracle Parallel Server requires it. • UNIX and NT buffer cache bypassed ISYS366 - Installation

  9. Separating Objects (on devices) • Raw disk must be owned by Oracle (UNIX) • Oracle block size must be multiple of the physical (disk) block size • Only one data file per raw disk partition • Put raw disk partitions on separate physical device ISYS366 - Installation

  10. Separating Objects (on devices) • Comparison to SQL Server and Ingres file management • SQL Server • Ingres • Separate disks for different type of files • Separate datafiles for data, index, TBS and temp tablespaces • Ensures integrity ISYS366 - Installation

  11. After Installation • Assign user SYSTEM to a new default tablespace and default temporary tablespace (leave SYS alone) • Create a script that will assign all new users to a user tablespace and a default user temporary tablespace ISYS366 - Installation

  12. After Installation • You can examine the tablespaces from DBA_TABLESPACES or USER_TABLESPACES • Other system information from SHOW PARAMETERS, or the V$PARAMETERS table ISYS366 - Installation

  13. Moving Database Files • Systems may be tuned after being created • Shut down instance • Move file (via op sys commands) • Start up the Server Manager, start up the instance, then execute the following command: Alter database rename '/u02/data/mesh97-1.dbf' to '/u03/data/mesh97-1.dbf' • Restart the instance ISYS366 - Installation

More Related