Orcale Tutorial Content

Loading...

Getting Started - البدء مع إدارة قواعد البيانات
  • أنواع مستخدمي قواعد البيانات:
  • مهام مسؤول قاعدة البيانات:
  • SQL Statements:
  • Identifying Your Oracle Database Software Release - تحديد إصدار اوركل
  • About Database Administrator Security and Privileges- أمان وامتيازات مسؤول قاعدة البيانات
  • Database Administrator Authentication - مصادقة مسؤول قاعدة البيانات
  • Creating and Maintaining a Database Password File - إنشاء ملف كلمة المرور
  • Oracle Architectural Components - مكونات قاعدة البيانات أوركل
  • ﻤﻜﻭﻨﺎﺕ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ
  • Oracle Instance
  • Oracle Database
  • Installing Oracle Database - تثبيت الأوركل
  • Installing oracle database 10g in windows
  • Creating and Configuring Database - إنشاء قاعدة البيانات
  • ﺍﻟﺘﺨﻁﻴﻁ ﻟﻘﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ
  • ﺇﻨﺸﺎﺀ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﺒﺎﻟﻁﺭﻴﻘﺔ ﺍﻟﻴﺩﻭﻴﺔ علي Windows:
  • ﺇﻨﺸﺎﺀ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﻋﻥ ﻁﺭﻴﻕ ﺍل(DBCA)
  • About Creating an Oracle Database
  • About Selecting a Character Set
  • Prerequisites for Database Creation
  • Creating a Database with the CREATE DATABASE Statement
  • Specifying CREATE DATABASE Statement Clauses
  • Specifying Initialization Parameters
  • Controlling The Database -التحكم في قاعدة البيانات
  • التحكم في قاعدة البيانات - Controlling The Database
  • ﺘﺸﻐﻴل ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ
  • ﺇﻏﻼﻕ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ
  • Opening a Database in Read-Only Mode
  • Opening a Database in Restricted Mode
  • Managing Tablespaces and Data files
  • ﻤﻔﺎﻫﻴﻡ ﻋﺎﻤﺔ ﻋﻥ ﺍل: Tablespaces
  • عملي
  • Control File & Redo Log Files
  • Control File
  • ﺘﻐﻴﻴﺭ ﺍﺴﻡ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ
  • Redo Log Files
  • Administrating Users - إدارة المستخدمين
  • ﺇﻨﺸﺎﺀ ﻭﺇﺩﺍﺭﺓ ﺍﻟﻤﺴﺘﺨﺩﻤﻴﻥ
  • Quota
  • ﻭﺴﻴﻠﺔ ﺍﻟﺘﺤﻘﻴﻕ
  • ﺍﻟﺼﻼﺤﻴﺎﺕ - Privileges
  • ROLES
  • PROFILES
  • Database Security & Monitoring - تأمين ومراقبة قاعدة البيانات
  • Database Security
  • ﻤﺭﺍﻗﺒﺔ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ - AUDITING
  • Oracle Net Services & Database Link & Metrlized Viewِ
  • Oracle Net Services
  • ﺍﻟﺘﺤﻜﻡ ﻓﻲ ﺍﻟﻭﺼﻭل ﻟﻘﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ
  • External Procedures
  • Clients Side
  • Database Link
  • Materialized Views
  • Undo Management & Flashback Technology
  • UNDO MANAGEMENT
  • Flashback Query
  • Flashback Table
  • Flashback Versions Query
  • Flashback Transaction
  • Flashback Drop
  • Flashback Database
  • Managing Shared Servers
  • Why Shared Server
  • Dedicated Server
  • Shared Server Architecture
  • ﻤﺘﻰ ﻨﺴﺘﺨﺩﻡ ﺍل Shared Server ؟
  • Using Globalization Support
  • Globalization
  • ﺍﺨﺘﻴﺎﺭ وتغيير ﺍل Character Set
  • ﻤﺴﺘﻭﻴﺎﺕ ﺍل Globalization
  • ﺍﺴﺘﺨﺩﺍﻡ ﺍل Zones Time
  • Logical Backup & Recovery
  • Use Export Utilities to Export Data
  • TABLES EXPORT Using Export Utilities
  • SCHEMAS EXPORT Using Export Utilities
  • TABLESPACE EXPORT Using Export Utilities
  • DATABASE EXPORT Using Export Utilities
  • Use Import Utilities to Import Data
  • TABLES IMPORT Using Import Utilities
  • SCHEMAS IMPORT Using Import Utilities
  • DATABASE IMPORT Using Import Utilities
  • DATA PUMP
  • TABLES EXPORT Using Data Pump
  • SCHEMAS EXPORT Using Data Pump
  • DATABASE EXPORT Using Data Pump
  • TABLES IMPORT Using Data Pump
  • SCHEMAS IMPORT Using Data Pump
  • DATABASE IMPORT Using Data Pump
  • SQL*Loader
  • Physical Backup & Recovery
  • Physical Backup
  • ﻜﻴﻑ ﻨﻬﻴﺊ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﻟﺘﻌﻤل ﻓﻲ ﺍﻟﻨﻤﻁ ARCHIVELOG؟
  • Cold Backup
  • Full Database Recovery
  • Loss of a Non-SYSTEM Data File
  • Loss of a SYSTEM Data File
  • Loss of an Un-archived Online Log Files
  • Loss of Control Files
  • Loss Unbackup Datafile
  • Damage Tempfile
  • Damage Temporary Tablespace
  • Damage Online Logfile Member
  • Point in Time Recovery
  • Backup and Recovery Options
  • Hot Backup
  • Recovery Manager (RMAN)
  • مقدمة
  • مكونات ال Recovery Manager (RMAN)
  • ﺃﻨﻭﺍﻉ ﺍﻻﺘﺼﺎل ﺒﺎل RMAN
  • ﺨﻴﺎﺭﺍﺕ وأنماط ﺍﻟﻨﺴﺦ ﺍﻹﺤﺘﻴﺎﻁﻰ
  • RMAN Configuration Setting
  • Recovery Catalog
  • RMAN Backups
  • Data Files Backup
  • Tablespaces Backup
  • Archived Redo Log Files Backup
  • Control File Backup
  • Database Backup
  • Incremental Backups
  • RMAN Commands
  • Complete Recovery
  • Incomplete Recovery
  • Restore ControlFile and spfile
  • Managing Resources
  • Consumer Groups
  • Resource Manager Plans
  • Resource Manager Configuration
  • Create Consumer Group
  • Update Consumer Group
  • Delete Consumer Group
  • Privileges & Resource Manager
  • Join To Consumer Group
  • Move Active User To Other Consumer Group
  • Create Resource Manager Plans & Directive
  • Update Resource Manager Plans
  • Update Resource Manager Plan Directives
  • Delete Resource Manager Plan Directives
  • Delete Resource Manager Plans
  • Create Simple Plan
  • Consumer Group Mapping
  • Automating Tasks with the Scheduler
  • The Scheduler Architecture
  • Jobs
  • Programs
  • Schedules
  • Using Programs and Schedules
  • Job Classes
  • Windows
  • (Privileges) ﺍﻟﺼﻼﺤﻴﺎﺕ
  • Job Logs
  • Dealing with Locking
  • Shared & Exclusive Locks
  • Manual Lock Table
  • The Enqueue Mechanism
  • Lock Contention
  • Deadlocks
  • Diagnostic Sources
  • Alert Log
  • Background Trace Files
  • Server-Generated Alerts
  • Editing Thresholds
  • User Trace Files
  • Instance-Level SQL Tracing
  • Session-Level SQL Tracing
  • Dealing With Database Corruption
  • Block Corruption
  • ﺍﻜﺘﺸﺎﻑ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ (Detecting Block Corruptions)
  • The DBVERIFY Utility
  • The ANALYZE Command
  • DBMS_REPAIR Backage
  • ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﺒﻭﺍﺴﻁﺔ ﺍل:RMAN
  • Managing & Monitoring Memory
  • The System Global Area
  • The Shared Pool
  • The Database Buffer Cache
  • The Default, Keep, and Recycle Pools
  • The Nonstandard Block Size Pools
  • Sizing the Database Buffer Cache
  • The Log Buffer
  • The Large Pool
  • The Java Buffer
  • The Steams Buffer
  • Automatic Shared Memory Management
  • Enable Automatic Shared Memory Management
  • The Program Global Area (PGA)
  • Performance Tunning
  • Invalid Objects
  • Unusable Indexes
  • Rebuild Invalid Inexes
  • Optimizer Statistics
  • Gathering Statistics
  • The Automatic Workload Repository (AWR)
  • The Automatic Database Diagnostic Monitor (ADDM)
  • The SQL Tuning Advisor
  • The SQL Access Advisor
  • The Mean Time to Recover Advisor
  • The Segment Advisor
  • The Undo Advisor
  • Managing & Monitoring Memory

    The Database Buffer Cache

    ﻴﻘﻭﻡ ﺍلServer Processes ﺒﻌﻤل ﻨﺴﺦ ﻟلDatafile Block ﺇﻟﻲ Database Buffer Cache، ﻓﺈﺫﺍ ﺘﻡ ﺘﻌﺩﻴل ﺍلBlock ﻓﻲ ﺍلDatabase Buffer Cache  ﻓﺴﻭﻑ

    ﻴﻘﻭﻡ ﺍﻟﻤﻌﺎﻟﺞ DBWn ﺒﻜﺘﺎﺒﺔ ﺍلBlock ﻓﻲ ﺍلDatafiles.

    ﺍﻟﺘﻬﻴﺌﺔ الإفتراضية ﻟلInstance ﺘﻘﻭﻡ ﻋﻠﻲ ﺘﻜﻭﻴﻥ ﺍلDatabase Buffer Cache  ﻜﺠﺯﺀ ﻭﺍﺤﺩ ﻤﻥ ﺍﻟﺫﺍﻜﺭﺓ ﻻﺴﺘﻘﺒﺎل ﺍلBlocks ﻓﻲ ﺍﻟﺫﺍﻜﺭﺓ ﻟﻜﻥ ﻤﻥ ﺍﻟﻤﺤﺘﻤل ﺃﻥ ﻴﺘﻡ

    ﺘﻘﺴﻴﻡ ﻫﺫﺍ ﺍﻟﺠﺯﺀ ﻤﻥ ﺍﻟﺫﺍﻜﺭﺓ ﻜﺄﺠﺯﺍﺀ ﺼﻐﻴﺭﺓ ﻟﺘﺤﺴﻴﻥ ﺍﺴﺘﻌﻤﺎل ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ.

    ﺴﻨﺘﺤﺩﺙ ﺍﻵﻥ ﻋﻥ ﺍﻟﺨﻭﺍﺭﺯﻤﻴﺔ ﺍﻟﺘﻲ ﺘﺴﺘﺨﺩﻤﻬﺎ ﺍﻷﻭﺭﻜل ﻻﺨﺘﻴﺎﺭ ﺍلBuffers ﺍﻟﺘﻲ ﺴﻴﺘﻡ ﻭﻀﻊ ﺍلBlocks ﻓﻴﻬﺎ، ﻭﺃﻴﻀﺎﹰ ﻟﺘﺤﺩﻴﺩ ﺍلBlocks ﺍﻟﺘﻲ ﺴﻴﺘﻡ ﻜﺘﺎﺒﺘﻬﺎ ﻤﺭﻩ ﺃﺨﺭﻱ ﻓﻲ ﺍلDatafile.

    :The LRU List and the Checkpoint Queue

    ﺠﻤﻴﻊ ﺍلBuffers ﻓﻲ ﺍلDatabase Buffer Cache  ﺴﺘﻜﻭﻥ ﻓﻲ ﺃﺤﺩ ﺍﻟﺤﺎﻻﺕ ﺍﻟﺜﻼﺜﺔ ﺍﻟﺘﺎﻟﻴﺔ:

    Pinned: ﻭﻫﻭ Buffer ﻴﺘﻡ ﺍﺴﺘﺨﺩﺍﻤﻪ ﺍﻵﻥ ﻓﻲ ﺍﻟﺫﺍﻜﺭﺓ ﻭﻤﺎ ﻟﻡ ﻴﺘﻡ ﺍﻻﻨﺘﻬﺎﺀ ﻤﻥ ﺍﻟﻌﻤل ﻓﻲ ﻫﺫﺍ ﺍلBuffer ﻓﻼ ﻨﺴﺘﻁﻴﻊ ﺍﺴﺘﻌﻤﺎل ﻫﺫﺍ ﺍلBuffer ﻓﻲ ﻋﻤﻠﻴﺎﺕ ﺃﺨﺭﻱ.

    Dirty: ﻭﻫﻭ Buffer ﻴﺤﺘﻭﻱ ﻨﺴﺨﺔ Block ﻫﻲ ﻓﻲ ﺍﻟﺤﻘﻴﻘﺔ ﺘﺨﺘﻠﻑ ﻋﻥ ﺍﻟﻨﺴﺨﺔ ﺍﻟﻤﻭﺠﻭﺩ ﻓﻲ ﺍﻟﺩﻴﺴﻙ، ﻭﻫﻲ ﻋﺒﺎﺭﺓ Block ﺘﻡ ﻨﺴﺦ ﻟﻪ ﻓﻲ ﺍلCache ﻭﺘﻡ ﺘﻌﺩﻴﻠﻪ ﻭﻟﻜﻥ

    ﻟﻡ ﻴﺘﻡ ﻜﺘﺎﺒﺘﻪ ﻓﻲ ﺍﻟﺩﻴﺴﻙ، ﻓﻤﻥ ﻏﻴﺭ ﺍﻟﻤﻤﻜﻥ ﺠﻠﺏ Block ﺁﺨﺭ ﻤﻥ ﺍلDatafile ﻭﻭﻀﻌﻪ ﻓﻲ ﻫﺫﺍ ﺍلBuffer ﻤﺎ ﻟﻡ ﻴﺘﻡ ﺘﻨﻅﻴﻔﻪ ﺃﻭﻻﹰ ﻋﻥ ﻁﺭﻴﻕ ﺍلDBWn ﺍﻟﺫﻱ ﻴﻘﻭﻡ ﺒﻜﺘﺎﺒﺘﻪ ﺃﻭﻻﹰ ﻓﻲ ﺍلDatafile.

    Free: ﻭﻫﻭ Buffer ﻟﻴﺱ Pinned ﻭﻻ Dirty ﻭﻫﺫﺍ ﻴﻌﻨﻲ ﺃﻥ ﻫﺫﺍ ﺍلBuffer ﺇﻤﺎ ﻏﻴﺭ ﻤﺴﺘﻌﻤل ﺃﻭ ﺘﻡ ﺘﻨﻅﻴﻔﻪ.

    ﻓﻠﺤﻅﺔ ﺘﺸﻐﻴل ﺍلInstance ﻓﺈﻥ ﺠﻤﻴﻊ ﺍلBuffers ﺘﻜﻭﻥ ﻏﻴﺭ ﻤﺴﺘﻌﻤﻠﻪ (Unused).

    ﻓﻌﻨﺩﻤﺎ ﻴﺤﺘﺎﺝ ﺍلServer Process ﻟﻘﺭﺍﺀﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﻓﻲ ﺍﻟﺫﺍﻜﺭﺓ ﻓﻴﺠﺏ ﻋﻠﻴﻪ ﺃﻭﻻﹰ ﺍﻟﺒﺤﺙ ﻋﻥ ﺍلBlock ﻓﻲ ﺍﻟﺩﻴﺴﻙ ﻭﺍﻟﺒﺤﺙ ﻋﻥ ﺍلFree Buffer ﻓﻲ ﺍلDatabase Buffer Cache  

    ﺍﻟﺫﻱ ﺴﻴﺴﺘﻘﺒل ﺍلBlock ﻤﻥ ﺍﻟﺩﻴﺴﻙ ﻤﻊ ﺍﻟﺘﺄﻜﻴﺩ ﻋﻠﻲ ﺃﻨﻪ ﻻ ﻴﻤﻜﻥ ﻨﺴﺦ Block ﻤﻥ ﺍﻟﺩﻴﺴﻙ لPinned Buffer ﻭﺫﻟﻙ ﻷﻨﻪ ﺴﻭﻑ ﻴﻜﻭﻥ ﻤﺤﻤﻲ ﻋﻥ ﻁﺭﻴﻕ  (Locking Mechanism)،

    ﻭﺃﻴﻀﺎﹰ ﻻ ﻴﻤﻜﻥ ﻨﺴﺦ Block ﻤﻥ ﺍﻟﺩﻴﺴﻙ لDirty Buffer ﻤﺎ ﻟﻡ ﻴﺘﻡ ﻜﺘﺎﺒﺔ ﺍﻟﺘﻌﺩﻴﻼﺕ ﻓﻲ ﺍﻟﺩﻴﺴﻙ ﻋﻥ ﻁﺭﻴﻕ ﺍلDBWn، ﻭﻟﻜﻥ ﻴﻤﻜﻥ ﻨﺴﺦ ﺍلBlock ﻓﻲ ﺍلFree Buffer ﻭﺫﻟﻙ ﻷﻥ

    ﺍﻟﺒﻴﺎﻨﺎﺕ ﺍﻟﻤﻭﺠﻭﺩﺓ ﺒﻪ ﻤﺘﺎﺤﺔ ﺃﻴﻀﺎﹰ ﻓﻲ ﺍﻟﺩﻴﺴﻙ. ﻫﻨﺎﻙ ﺍﻟﻌﺩﻴﺩ ﻤﻥ ﺍلFree Buffer ﻓﻲ ﺍلDatabase Buffer Cache ، ﻭﻟﻜﻥ ﺍﻟﺴﺅﺍل ﺍﻟﺫﻱ ﻴﻁﺭﺡ ﻨﻔﺴﻪ ﻤﺎ ﻫﻭ ﺍلFree Buffer

    ﺍﻟﺫﻱ ﺴﻴﺨﺘﺎﺭﻩ ﺍلServer Process ﻟﺘﺨﺯﻴﻥ ﺍلBlock؟ ﻫﺫﺍ ﺍﻷﻤﺭ ﻤﻬﻡ ﺒﺎﻟﻨﺴﺒﺔ ﻟﻸﺩﺍﺀ، ﺍﻻﺨﺘﻴﺎﺭ ﻴﺘﻡ ﺒﻨﺎﺀ ﻋﻠﻲ (LRU) Least Recently Used  ﻓﺠﻤﻴﻊ ﺍلBuffers

    ﻓﻲ ﺍلDatabase Buffer Cache ﻟﻬﺎ ﻋﻨﺎﻭﻴﻥ ﻭﻴﻭﺠﺩ ﻗﺎﺌﻤﺔ ﺘﻀﻡ ﺠﻤﻴﻊ ﺍلBuffers ﺘﺴﻤﻲ (LRU) ﻭﺘﺘﻡ ﺍﻹﻀﺎﻓﺔ ﻓﻲ ﺍﻟﻘﺎﺌﻤﺔ ﺒﻨﺎﺀً ﻋﻠﻲ ﺁﺨﺭ ﺍلBuffers ﻭﺼﻭﻻﹰ، ﻟﺫﻟﻙ ﻓﺈﻥ ﺍلBuffer

    ﺍﻟﺫﻱ ﺘﻡ ﺍﻟﺤﺼﻭل ﻋﻠﻴﻪ ﻤﻨﺫ ﺒﺭﻫﺔ ﺴﺘﺘﻡ ﺇﻀﺎﻓﺘﻪ ﻓﻲ ﻨﻬﺎﻴﺔ ﺍﻟﻘﺎﺌﻤﺔ (LRU).

    ﻋﻨﺩﻤﺎ ﻴﺘﻡ ﺍﻟﺒﺤﺙ ﻋﻥ ﻁﺭﻴﻕ ﺍلServer Process ﻴﺘﻡ ﺘﺭﺸﻴﺢ ﺍلBuffer ﺍﻷﻗل ﺍﺴﺘﺨﺩﺍﻡ ﻤﺅﺨﺭﺍﹰ  (Least recently used end of the LRU list)، ﺒﻴﻨﻤﺎ ﻴﺘﻡ ﻭﻀﻊ ﺍلBuffer ﻓﻲ ﺍﻟﻘﺎﺌﻤﺔ ﺒﻨﺎﺀً

    ﻋﻠﻲ ﺍﻷﻜﺜﺭ ﺍﺴﺘﺨﺩﺍﻡ ﻤﺅﺨﺭﺍﹰ (Most recently used end of the LRU list) ﻟﺫﺍ ﻓﺈﻥ ﺍلVery Busy Buffer ﻻ ﺘﺘﻡ ﻜﺘﺎﺒﺔ ﻤﺤﺘﻭﻴﺎﺘﻪ ﻓﻲ ﺍﻟﺩﻴﺴﻙ ﻭﺫﻟﻙ ﻷﻥ ﺍلServer Process

    ﻻ ﻴﺘﻡ ﺍﻟﻌﺜﻭﺭ ﻋﻠﻴﻪ ﻷﻨﻪ ﻴﻭﺠﺩ ﻓﻲ (Least recently used end of the LRU list).

    ﻫﻨﺎﻙ ﻗﺎﺌﻤﺔ ﺃﺨﺭﻱ ﻟلBuffers ﺘﺴﻤﻲ Checkpoint Queue، ﻫﺫﻩ ﺍﻟﻘﺎﺌﻤﺔ ﺘﺤﺘﻭﻱ ﻋﻠﻲ ﺍلDirty Buffers ﻭﺍﻟﺘﻲ ﺘﻨﺘﻅﺭ ﻜﺘﺎﺒﺔ ﻤﺤﺘﻭﻴﺎﺘﻬﺎ ﻓﻲ ﺍﻟﺩﻴﺴﻙ ﻋﻥ ﻁﺭﻴﻕ ﺍلDBWn Process.

    ﺍلServer Processes ﻴﻘﻭﻡ ﺒﻌﻤﻠﻴﺔ ﺍﻟﺒﺤﺙ ﻓﺈﺫﺍ ﻭﺠﺩ Free Buffer ﻗﺎﻡ ﺒﺈﻀﺎﻓﺘﻪ ﻓﻲ ﺍﻟﻘﺎﺌﻤﺔ (LRU) ﻭﺇﺫﺍ ﺘﻡ ﺍﻟﻌﺜﻭﺭ ﻋﻠﻲ Dirty Buffer ﻴﻘﻭﻡ ﺒﺈﻀﺎﻓﺘﻪ ﻟﻠﻘﺎﺌﻤﺔ Checkpoint Queue.

      ﺒﺎﻟﻁﺒﻊ ﻴﺘﻡ ﺇﻀﺎﻓﺔ ﺍﻟﻌﻨﺎﻭﻴﻥ ﻟﻠﻘﻭﺍﺌﻡ ﻭﻟﻴﺱ ﺍلBuffer.

    ﺇﺫﺍﹰ ﺍلQueue Checkpoint ﺘﺤﺘﻭﻱ ﻋﻠﻲ ﺍلDirty Buffers ﻭﺒﻌﺩ ﻜل ﻓﺘﺭﺓ ﻴﺘﻡ ﻜﺘﺎﺒﺔ ﻤﺤﺘﻭﻴﺎﺕ ﻫﺫﻩ ﺍلBuffers ﻋﻥ ﻁﺭﻴﻕ ﺍلDBWn ﺇﻟﻲ ﺍﻟﺩﻴﺴﻙ ﻭﻤﻥ ﺜﻡ ﺘﺼﺒﺢ Clean or Free Buffer،

    ﺤﺘﻰ ﻴﻤﻜﻥ ﺍﺴﺘﺨﺩﺍﻤﻬﺎ ﻤﺭﻩ ﺃﺨﺭﻱ.

    ﻫﺫﺍ ﻴﻌﻨﻲ ﺃﻥ ﺍلServer Process ﻴﻨﺘﻅﺭﻩ ﻋﻤﻼﹰ ﻜﺜﻴﺭﺍ ﻓﻬﻭ ﻴﻘﻭﻡ ﺃﻭﻻﹰ ﺒﺎﻟﺒﺤﺙ ﻋﻥ ﺍلBlock ﻓﻲ ﺍﻟﺩﻴﺴﻙ ﻭﻴﻘﻭﻡ ﺒﺎﻟﺒﺤﺙ ﻋﻥ ﺍلFree Buffers ﻭﺃﻴﻀﺎﹰ ﻴﻘﻭﻡ

    ﺒﺎﻟﺒﺤﺙ ﻋﻥ ﺍلDirty Buffer ﻭﻴﻘﻭﻡ ﺒﻭﻀﻌﻬﺎ ﻓﻲ ﺍلCheckpoint Queue ﻟﺘﺘﻡ ﻜﺘﺎﺒﺘﻪ ﻻﺤﻘﺎﹰ ﻓﻲ ﺍﻟﺩﻴﺴﻙ.

    ﻫﺫﻩ ﺍﻵﻟﻴﺔ ﺍﻟﺒﺴﻴﻁﺔ ﺘﺴﻤﺢ ﻟﻸﻭﺭﻜل ﺒﺈﺒﻘﺎﺀ (Disk I/O) ﻓﻲ ﺍﻟﺤﺩ ﺍﻷﺩﻨﻰ.

    ﻓﺎلDBWn ﻴﻘﻭﻡ ﺒﻜﺘﺎﺒﺔ ﻓﻘﻁ ﺍل Dirty and Static Buffer، ﺃﻤﺎ ﺍلBuffer ﺍﻟﺘﻲ ﻟﻡ ﻴﺘﻡ ﺘﻐﻴﻴﺭﻫﺎ ﻓﻠﻥ ﻴﺘﻡ ﻜﺘﺎﺒﺘﻬﺎ ﻓﻲ ﺍﻟﺩﻴﺴﻙ، ﻜﺫﻟﻙ ﺍلDirty Buffer ﺴﻭﻑ ﻴﺘﻡ ﻜﺘﺎﺒﺘﻬﺎ ﻓﻲ ﺍﻟﺩﻴﺴﻙ ﻓﻘﻁ

    ﺇﺫﺍ ﻟﻡ ﻴﺘﻡ ﺍﻟﺘﻌﺎﻤل ﻤﻌﻬﺎ ﻟﺒﻌﺽ ﺍﻟﻭﻗﺕ. ﺍﻟﻠﺤﻅﺔ ﺍﻟﻭﺤﻴﺩﺓ ﺍﻟﺘﻲ ﺘﻜﺘﺏ ﺒﻬﺎ ﺠﻤﻴﻊ ﺍلDirty Buffer ﺇﻟﻲ ﺍﻟﺩﻴﺴﻙ ﻫﻲ ﻟﺤﻅﺔ ﺤﺩﻭﺙ ﺍل Database Checkpoint، ﻜﺫﻟﻙ ﻟﺤﻅﺔ ﺤﺩﻭﺙ

    ﺍلTablespace Checkpoint ﻴﺘﻡ ﻨﻘل ﺠﻤﻴﻊ ﺍلDirty Buffer ﺍﻟﺨﺎﺼﺔ ﺒﻬﺫﺍ ﺍلTablespace ﺇﻟﻲ ﺍﻟﺩﻴﺴﻙ، ﻭﻴﺘﻡ ﺤﺩﻭﺙ ﺍلTablespace Checkpoint ﺒﺼﻭﺭﺓ ﺁﻟﻴﺔ ﻨﺘﻴﺠﺔ ﻟﻠﻌﻤﻠﻴﺎﺕ ﺍﻟﺘﺎﻟﻴﺔ:

    Dropping the Tablespace

    Making the Tablespace read-only

    Putting the Tablespace into hot backup mode

    Taking the Tablespace offline

     

    --------------------------------------------------------------