Database Creation - Buisness Management - Lecture Slides, Slides of Business Administration

Business Management is one of the most important subject in Management Sciences but it also has its scope in engineering. Following are the key points discussed in these Lecture Slides : Database Creation, Using a Script, Connect Internal, Decisions On Sizing, Block Size, Block Size, Integrity Section, Runtime Overhead, Transactional Header, Directory Section

Typology: Slides

2012/2013

Uploaded on 07/29/2013

sajid
sajid 🇮🇳

4.6

(7)

128 documents

1 / 11

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Database creation
Using a script:
Connect internal as sysdba;
create database NAME….;
Using the OEM GUI
Parameters stored in a small DB
Access to other utility pgms eg: RMAN
Can accommodate several DBAs
Key decisions on sizing
Eg: assign a block size once and for all
Docsity.com
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download Database Creation - Buisness Management - Lecture Slides and more Slides Business Administration in PDF only on Docsity!

Database creation

  • Using a script:

Connect internal as sysdba; create database NAME….;

  • Using the OEM GUI
    • Parameters stored in a small DB
    • Access to other utility pgms – eg: RMAN
    • Can accommodate several DBAs
  • Key decisions on sizing
    • Eg: assign a block size – once and for all

Block size

  • Smallest unit of storage in oracle DB
  • Critical perf. Factor as inefficient space use leads to

increase I/O activity

  • Block overhead
    • Integrity section (90 bytes)
    • Runtime overhead (136 bytes)
    • Transactional header (24 bytes and growing)
    • Directory section (Pointers…)
    • And then………..data
  • Big is beautiful? Percentage of overhead decreases

when block size increases, but no right answer here

Approx. 256 b

Block size and row size

  • Table with average row length = 2236 b

(10m records)

  • Block size 4k = 4006 b => one row per

block

  • 8 k => 3 rows per block

Opening and closing the DB

Startup open NAME;

Or

Startup mount NAME;

Alter database open;

Shutdown;

Else – use OEM menus

When DB created (2)

b) Shared SQL Pool created:

  • Stores DD cache: info about data structure
  • Stores library cache: info about SQL statements run
  • LRU algorithm
  • Too small => no re-use and low performance
  • SHARED_POOL_SIZE in init.ora

Parameter files: INIT.ORA

  • Initialisation file for each DB
  • MYDB = > initmydb.ora
  • Contains sizing of SGA and number of

parameters, DB name and block size

  • Read at startup means changes only

implemented at next startup

Data hierarchy in Oracle

  • Data hierarchy in Oracle is specific (and demented!)
  • Normally, unit of storage is file…
    • Managed by OS
    • Can grow / shrink
    • Physical sections logically connected by OS
  • In Oracle a DB = one or more tablespaces
    • One or more objects, indexes, clusters…
    • Fixed size – gets full
    • Extended by DBA only
    • One file can support only ONE tablespace

See figure 3.

About tablespaces

  • Kind of partitioning
    • Except fixed size
      • Extended by dba
    • Oracle very strong at TS level
  • Optimal seems to be around 2GB
  • Strategy = isolate aged data into one

tablespace => can be made read-only

  • Should store similar objects together