Presentation is loading. Please wait.

Presentation is loading. Please wait.

Database Administration Judy Riniker and Greg Girard from the KSU Information Systems Office.

Similar presentations


Presentation on theme: "Database Administration Judy Riniker and Greg Girard from the KSU Information Systems Office."— Presentation transcript:

1 Database Administration Judy Riniker and Greg Girard from the KSU Information Systems Office

2 Topics KSU Information System Office, Database Administration Oracle Database Architecture Database Administration Short Demo of OEM

3 KSU Information Systems Office Database Administration Staff CA IDMS Database Administrators (2)CA IDMS Database Administrators (2) –Student data 7 Gb –Student financial and loan data 9 Gb –Total 17 Gb of Production Data –Test and development –OS/390

4 KSU Information Systems Office Oracle Database Administrators (5) –Human Resources Production 23 GbProduction 23 Gb Stress Test 23 GbStress Test 23 Gb Development2.1 GbDevelopment2.1 Gb Training1.7 GbTraining1.7 Gb Delivered1.2 GbDelivered1.2 Gb Upgrade436 MbUpgrade436 Mb

5 KSU Information Systems Office Oracle Database Administrators (5) –Facilities FinancialsFinancials –Production 6.8 Gb –Test 6.9 Gb –Development4.2 Gb Facilities Management SystemFacilities Management System –Production2.1 Gb –Test2.1 Gb –Development2.1 Mb

6 KSU Information Systems Office Oracle Database Administrators (5) –Student Related Systems KATS Interface 220 MbKATS Interface 220 Mb DARSDARS –Production3.6 Gb –Test3.6 Gb –Helpdesk 685 Mb –Department 4.4 Gb

7 KSU Information Systems Office Oracle Database Administrators (5) –Telecommunications Production Billing13.4 GbProduction Billing13.4 Gb Production Billing 1.7 GbProduction Billing 1.7 Gb Production Call loading 4.5 GbProduction Call loading 4.5 Gb Production Directory 1.0 GbProduction Directory 1.0 Gb Test Directory 1.0 GbTest Directory 1.0 Gb

8 KSU Information Systems Office Oracle Database Administrators (5) –Division of Continuing Education Production 1.1 GbProduction 1.1 Gb Test 847 MbTest 847 Mb Development1.7 GbDevelopment1.7 Gb Development807 MbDevelopment807 Mb Design820 MbDesign820 Mb

9 KSU Information Systems Office Oracle Database Administrators (5) –Application/Database Utilities & Tools OEM 590 MbOEM 590 Mb Internet Directory500 MbInternet Directory500 Mb Version Control285 MbVersion Control285 Mb ISO Development1.6 GbISO Development1.6 Gb Video Server2 Gb RawVideo Server2 Gb Raw

10 Tables, Indexes, Views Peoplesoft 7.5 HRMS (HR)Peoplesoft 7.5 HRMS (HR) –Tables4099 –Indexes 5947 –Views2922 Oracle Financials (Facilities Accounting)Oracle Financials (Facilities Accounting) –Tables2344 –Indexes5019 –Views2811 FAMIS (Facilities Work Management)FAMIS (Facilities Work Management) –Tables333 –Indexes202 –Views 31

11 Server Hardware Sun Microsystems: E4500, E1000, E450, Sparc10Sun Microsystems: E4500, E1000, E450, Sparc10 Storage: RAID 10 - Striped and mirroredStorage: RAID 10 - Striped and mirrored CPUs range from 50 MHz Sparc to 248 MHz UltraSparcCPUs range from 50 MHz Sparc to 248 MHz UltraSparc RAM 192 Mb to 3G.RAM 192 Mb to 3G. CNS does the Unix System AdministrationCNS does the Unix System Administration

12 Oracle Database Instance ArchitectureArchitecture –Memory Areas –Processes –Physical Files

13 Oracle Database Overview Data filesParameterControlRedo Log Archive Database Redo Log Buffer Data Buffer Cache Library Cache Data Dict. Cache Shared Pool SGA Instance SMONDBW0PMONCKPTARCHLGWR User Process Server Process PGA Memory Processes Physical Files

14 Memory Areas: Memory area used to store database information that is shared by database processesMemory area used to store database information that is shared by database processes –Data Block Buffer Cache holds data blocks that are read from data segments in the database such as tables and indexesholds data blocks that are read from data segments in the database such as tables and indexes Size is set by DB_BLOCK_BUFFERS in the parameter file; but should typically be 1-2% of the total size of the database.Size is set by DB_BLOCK_BUFFERS in the parameter file; but should typically be 1-2% of the total size of the database. LRU Least Recently Used AlgorithmLRU Least Recently Used Algorithm SGA Area : System Global

15 Memory Areas: –Shared SQL Pool During the parse phase of a SQL query, the database server process uses this area to compile the SQL statementDuring the parse phase of a SQL query, the database server process uses this area to compile the SQL statement Stores the data dictionary cache and the library cacheStores the data dictionary cache and the library cache Size is set by SHARED_POOL_SIZE in the parameter file.Size is set by SHARED_POOL_SIZE in the parameter file. SGA: System Global Area

16 Memory Areas: Shared SQL PoolShared SQL Pool –Data dictionary Cache Information about database objects is stored in the data dictionary tables such as user account data, table descriptions, privileges, datafile names, etc.Information about database objects is stored in the data dictionary tables such as user account data, table descriptions, privileges, datafile names, etc. When the information is needed by the database, the data dictionary tables are read and the data returned is stored in the SGA in the dictionary cacheWhen the information is needed by the database, the data dictionary tables are read and the data returned is stored in the SGA in the dictionary cache If too small, database will have to repeatedly query the data dictionary tables for information.If too small, database will have to repeatedly query the data dictionary tables for information. LRU Least Recently Used AlgorithmLRU Least Recently Used Algorithm

17 Memory Areas: Shared SQL PoolShared SQL Pool –Library Cache Stores the most recently used SQL statementsStores the most recently used SQL statements –Text of the SQL Statement –Parse Tree : Compiled version of the statement –Execution Plan: Steps take when executing the statement If a SQL statement is reexecuted and a shared SQL area already contains the execution plan for the statement, the server process does not need to parse the statement.If a SQL statement is reexecuted and a shared SQL area already contains the execution plan for the statement, the server process does not need to parse the statement.

18 Memory Areas: –Redo Log Buffer Describe the changes that are made to the databaseDescribe the changes that are made to the database “Re-do” entries are written in the on-line log files so they can be used in roll forward operations during database recoveries“Re-do” entries are written in the on-line log files so they can be used in roll forward operations during database recoveries The entries are first stored in the SGA area in the Redo Log Buffer and then are periodically written to the physical files.The entries are first stored in the SGA area in the Redo Log Buffer and then are periodically written to the physical files. Size is set by LOG_BUFFER in the parameter file.Size is set by LOG_BUFFER in the parameter file. SGA: System Global Area

19 Memory Areas: –Large Pool Optional areaOptional area Can be dedicated to supporting large SQL statementsCan be dedicated to supporting large SQL statements Size is set by LARGE_POOL_SIZE in the parameter file.Size is set by LARGE_POOL_SIZE in the parameter file. Can also use parameter SHARED_POOL_RESERVED_SIZE instead of large pool.Can also use parameter SHARED_POOL_RESERVED_SIZE instead of large pool. SGA: System Global Area

20 Memory Areas: –Java Pool Services the parsing requirements for Java commandsServices the parsing requirements for Java commands Size is set by JAVA_POOL_SIZE in the parameter file.Size is set by JAVA_POOL_SIZE in the parameter file. SGA: System Global Area

21 Memory Areas: –Memory that is used by a single Oracle user process –PGA is not sharable –Contains: Sort areaSort area Session informationSession information Cursor state (stage in processing current SQL statements)Cursor state (stage in processing current SQL statements) PGA: Program Global Area

22 Oracle Database Overview Data filesParameterControlRedo Log Archive Database Redo Log Buffer Data Buffer Cache Library Cache Data Dict. Cache Shared Pool SGA Instance SMONDBW0PMONCKPTARCHLGWR User Process Server Process PGA Memory Processes Physical Files

23 Processes SMON - System MonitorSMON - System Monitor –Checks for consistency of the database –If necessary, initiates recovery of the database when the database is open –Coalesces contiguous free extents into larger free extents.

24 Processes PMON - Process MonitorPMON - Process Monitor –Cleans up failed user processes If an update fails, PMON releases the row locksIf an update fails, PMON releases the row locks DBWR - Database WriterDBWR - Database Writer –Manages the contents of the data block buffer cache and the dictionary cache –Performs batch writes of changed blocks from the SGA area to the data files

25 Processes LGWR - Log WriterLGWR - Log Writer –Manages the writing of the contents of the redo log buffer to the online redo log files CKPT - CheckpointsCKPT - Checkpoints –Updates database status information in the control files –Checkpoints cause DBWR to write all of the blocks that have been modified since the last checkpoint to the data files.

26 Processes ARCH - ArchiveARCH - Archive –After the first redo log is filled, the second redo log will go into use, then the third,…then back to the first –ARCH will make copy of the each redo log before is overwritten –Serves in recovering a database

27 Oracle Database Overview Data filesParameterControlRedo Log Archive Database Redo Log Buffer Data Buffer Cache Library Cache Data Dict. Cache Shared Pool SGA Instance SMONDBW0PMONCKPTARCHLGWR User Process Server Process PGA Memory Processes Physical Files

28 Database filesDatabase files –Control Files(control1.ctl) Records information about all the files in a databaseRecords information about all the files in a database Serves to maintain consistency and aid in recoveryServes to maintain consistency and aid in recovery –Redo Logs (redo_1a.log) Log of all transactionsLog of all transactions Used in recovering in event of a database crashUsed in recovering in event of a database crash 3 or more3 or more

29 Physical Files Database filesDatabase files –Data files Database objects are stored in tablespaces. Tablespace is a logical division of the database.Database objects are stored in tablespaces. Tablespace is a logical division of the database. –System Tablespace (system.dbf file) »Data dictionary –Temporary Tablespace (temp.dbf file) »dynamically created objects that store data during large sorting operations –Rollback Tablespace (rbs.dbf file) »Maintain both statement-level and transaction-level read consistency with in the database –Data Tablespace (hrlarge.dbf file) »User and application tables,objects

30 Physical Files Database filesDatabase files –Data files Each tablespace is made of 1 or more data filesEach tablespace is made of 1 or more data files Creating a new tablespace requires creating a new data fileCreating a new tablespace requires creating a new data file –Alert Log (alert.log) Records commands and command results of major events in the life of a databaseRecords commands and command results of major events in the life of a database –Tablespace creations –Log switching –Startup and shutdowns –Problems (internal errors)

31 Basic Database One or more data filesOne or more data files One or more control filesOne or more control files Two or more online redo logsTwo or more online redo logs –Internally Users/SchemasUsers/Schemas Rollback segmentsRollback segments User TablespacesUser Tablespaces Data dictionary tablesData dictionary tables User objectsUser objects

32 Basic Database –Server SGASGA SMONSMON PMONPMON DBWRDBWR LGWRLGWR CKPTCKPT ARCHARCH Users PGAUsers PGA

33 Database Administration Because an Oracle database system can be quite large and have many users, someone or some group of people must manage this system. The database administrator (DBA) is this manager. Every database requires at least one person to perform administrative duties.

34 Database Administration Installing and upgrading the Oracle server and application tools Allocating system storage and planning future storage requirements for the database system Creating primary database storage structures (tablespaces) after application developers have designed an application

35 Database Administration Creating primary objects (tables, views, indexes) once application developers have designed an application Modifying the database structure, as necessary, from information given by application developers Enrolling users and maintaining system security

36 Database Administration Ensuring compliance with database vendor license agreement Controlling and monitoring user access to the database Monitoring and optimizing the performance of the database Planning for backup and recovery of database information

37 Database Administration Maintaining archived data on tape Backing up and restoring the database – –Logical - Database records Export/Import – –Physical - redo logs, data and control files Offline (Cold) Online (Hot) Contacting database vendor for technical support

38 Tools OEMOEM ScriptsScripts Oracle Support SiteOracle Support Site Demo of OEM


Download ppt "Database Administration Judy Riniker and Greg Girard from the KSU Information Systems Office."

Similar presentations


Ads by Google