Orcale Tutorial Content


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
  • 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
  • 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
  • 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
  • Dealing With Database Corruption

    ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﺒﻭﺍﺴﻁﺔ ﺍل:RMAN

    ﻋﻤﻠﻴﺔ ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻫﻲ ﻤﻥ ﻤﻴﺯﺍﺕ ﺍلRMAN ، ﻓﻠﻭ ﻗﺎﻡ ﻤﺩﻴﺭ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﺒﻌﻤل ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻋﻥ ﻁﺭﻴﻕ ﺍلUser-Managed Backup

    ﻓﺈﻥ ﻋﻤﻠﻴﺔ ﺍﻻﺴﺘﺭﺠﺎﻉ ﺴﺘﺘﻡ ﻋﻠﻲ ﻤﺴﺘﻭﻱ ﺍلData File ﻭﺫﻟﻙ ﻷﻥ ﺍلUser-Managed Restore ﻻ ﺘﺴﺘﻁﻴﻊ ﻋﻤل Block Recovery ﻭﺇﻨﻤﺎ ﻟﻭ ﺤﺩﺙ ﻤﺸﻜﻠﺔ ﻓﻲ ﻜﺘﻠﺔ

    ﻭﺍﺤﺩﺓ ﻓﻲ Data File ﻓﻼﺒﺩ ﻤﻥ ﻋﻤل ﺍﺴﺘﺭﺠﺎﻉ ﻟﻜل ﺍلData File، ﻭﺴﻭﻑ ﺘﻜﻭﻥ ﺍﻟﺨﻁﻭﺍﺕ ﻜﺎﻟﺘﺎﻟﻲ:

    1- ﻭﻀﻊ ﺍلData File ﻓﻲ ﺍﻟﻭﻀﻊ Offline.

    2- ﻋﻤل Restore ﻟلData File ﻤﻥ ﺍﻟﻨﺴﺨﺔ ﺍﻻﺤﺘﻴﺎﻁﻴﺔ ﺍﻟﺘﻲ ﺃﺨﺫﺕ ﻗﺒل ﺤﺩﻭﺙ ﺍﻟﻤﺸﻜﻠﺔ.

    3- عمل Recover للData File.

    4- ﺠﻠﺏ ﺍلData File ﻓﻲ ﺍﻟﻭﻀﻊ Online.

    ﺃﻤﺎ ﺇﺫﺍ ﺍﺴﺘﺨﺩﻡ ﻤﺩﻴﺭ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﺍلRMAN ﻓﺈﻨﻪ ﻴﺴﺘﻁﻴﻊ ﺘﺤﺩﻴﺩ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﺃﺜﻨﺎﺀ ﻋﻤﻠﻴﺎﺕ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ، ﺒﺎﻟﻁﺒﻊ ﺇﺫﺍ ﺍﺴﺘﺨﺩﻤﺕ ﺍلUser-Managed Backup

    ﻓﺎﻨﻙ ﺘﺴﺘﻁﻴﻊ ﺘﺤﺩﻴﺩ ﻤﺸﺎﻜل ﺍلHardware Corruption ﻭﺫﻟﻙ ﻷﻥ ﻨﻅﺎﻡ ﺍﻟﺘﺸﻐﻴل ﻴﻘﻭﻡ ﺒﻤﻌﺭﻓﺔ ﺍﻟﻤﺸﻜﻠﺔ ﻋﻨﺩ ﻗﺭﺍﺀﺓ ﺍﻟﻤﻠﻑ ﺃﺜﻨﺎﺀ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻟﻜﻨﻪ ﻻ ﻴﺴﺘﻁﻴﻊ ﺍﻜﺘﺸﺎﻑ

    ﺍلSoftware Corruption، ﻭﺫﻟﻙ ﻷﻥ ﺍﻟﻤﻠﻑ ﻴﻅل ﻤﻘﺭﻭﺀﺍﹰ ﻋﻥ ﻁﺭﻴﻕ ﻨﻅﺎﻡ ﺍﻟﺘﺸﻐﻴل.

    ﺃﻤﺎ ﺒﺎﻟﻨﺴﺒﺔ ﻟلRMAN ﻓﺈﻨﻬﺎ ﺘﻘﻭﻡ ﺒﺎﻟﺘﺤﻘﻕ ﻤﻥ ﻤﺤﺘﻭﻴﺎﺕ ﺍﻟﻜﺘل ﺃﺜﻨﺎﺀ ﻋﻤﻠﻴﺎﺕ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ، ﻓﻠﻭ ﺘﻡ ﺍﻟﻌﺜﻭﺭ ﻋﻠﻲ ﻜﺘﻠﺔ ﻓﺎﺴﺩﺓ ﻓﺈﻥ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﺴﻭﻑ ﻴﺘﻭﻗﻑ ﻟﻭ ﺃﺭﺩﺕ ﺃﻨﺕ ﺫﻟﻙ،

    ﻟﻜﻥ ﻴﻤﻜﻨﻙ ﻤﻭﺍﺼﻠﺔ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﺤﺘﻰ ﻟﻭ ﺘﻡ ﺍﻟﻌﺜﻭﺭ ﻋﻠﻲ ﻜﺘل ﻓﺎﺴﺩﺓ ﻭﺫﻟﻙ ﻤﻥ ﺨﻼل ﺘﺴﺠﻴل ﻋﻨﻭﺍﻨﻴﻥ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻓﻲ الRepository.

    ﻭﺍﻟﻴﻙ ﺍﻟﻤﺜﺎل ﺍﻟﺘﺎﻟﻲ ﻭﻫﻭ ﻴﻭﻀﺢ :



    Set maxcorrupt for datafile 5 to 50;

    Backup datafile 5;



    ﻓﻲ ﻫﺫﺍ ﺍﻟﻤﺜﺎل ﻗﺎﻡ ﻤﺩﻴﺭ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﺒﻌﻤل ﻨﺴﺦ ﺍﺤﺘﻴﺎﻁﻲ ﻟلData File ﺭﻗﻡ 5 ﺤﺘﻰ ﻟﻭ ﻭﺼل ﻋﺩﺩ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﺨﻤﺴﻴﻥ ﻜﺘﻠﺔ،

    ﻓﺴﻭﻑ ﻴﺘﻡ ﺘﺨﺯﻴﻥ ﻋﻨﻭﺍﻨﻴﻥ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻓﻲ ﺍلRepository، ﺃﻤﺎ ﺇﺫﺍ ﺘﺠﺎﻭﺯ ﻋﺩﺩ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﺨﻤﺴﻭﻥ ﻜﺘﻠﺔ ﻓﺴﻭﻑ ﺘﻔﺸل ﻋﻤﻠﻴﺔ ﺍلBackup.

    ﻨﺴﺘﻔﻴﺩ ﻤﻥ ﻫﺫﻩ ﺍﻟﺨﺎﺼﻴﺔ ﻓﻲ ﺇﻜﻤﺎل ﻋﻤﻠﻴﺎﺕ ﺍﻟﻨﺴﺦ ﺍﻹﺤﺘﻴﺎﻁﻲ ﺤﺘﻰ ﻟﻭ ﺍﺤﺘﻭﻱ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻋﻠﻲ ﺒﻌﺽ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ،

    ﻋﻤﻭﻤﹰﺎ ﺃﻨﺕ ﻜﻤﺩﻴﺭ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﺘﺴﺘﻁﻴﻊ ﻤﺘﺎﺒﻌﺔ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻋﻥ ﻁﺭﻴﻕ V$DATABASE_BLCOK_CORRUPTION ﺤﻴﺙ ﻴﺤﺘﻭﻱ ﻋﻨﻭﺍﻨﻴﻥ ﺍﻟﻜﺘل

    ﺍﻟﺘﻲ ﺴﺒﺒﺕ ﺍﻟﻤﺸﻜﻠﺔ ﺒﺤﻴﺙ ﻴﺘﻡ ﺘﺴﺠﻴل ﺭﻗﻡ ﺍﻟﻤﻠﻑ ﻭﺭﻗﻡ ﺍﻟﻜﺘﻠﺔ، ﺃﻤﺎ ﻋﻨﻭﺍﻥ ﺍﻟﻜﺘﻠﺔ ﻓﻲ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻓﻴﺘﻡ ﺘﺴﺠﻴﻠﻬﺎ ﻜﺴﺠل ﻓﻲ V$BACKUP_CORRUPTION

    ﺇﺫﺍ ﻜﺎﻥ ﻨﻭﻉ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ BACKUP SET ﺃﻭ V$COPY_CORRUPTION ﺇﺫﺍ ﻜﺎﻥ ﻨﻭﻉ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ IMAGE COPY.

    ﻓﻲ ﺍﻟﻭﻀﻊ ﺍﻟﻁﺒﻴﻌﻲ ﻻ ﻴﺘﻡ ﺍﺴﺘﺨﺩﺍﻡ ﺍﻟﺨﻴﺎﺭ SET MAXCORRUPT ﻤﻤﺎ ﻴﺅﺩﻱ ﺫﻟﻙ ﻟﻔﺸل ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻋﻨﺩ ﻋﺜﻭﺭﻩ ﻋﻠﻲ ﺃﻭل Block Corruption.

    ﻭﺃﻨﺕ ﻜﻤﺩﻴﺭ ﻟﻘﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﺘﺴﺘﻁﻴﻊ ﺘﺠﺎﻫل ﻋﻤﻠﻴﺔ ﺍﺨﺘﺒﺎﺭ ﺍﻟﻜﺘل ﺃﺜﻨﺎﺀ ﻋﻤل ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻭﺫﻟﻙ ﻤﻥ ﺨﻼل ﺒﻌﺽ ﺍﻟﺨﻴﺎﺭﺍﺕ،

    ﻓﻠﻭ ﺃﺭﺩﺕ ﻤﺜﻼﹰ ﺘﺠﺎﻫل ﺴﻼﻤﺔ ﺍﻟﻜﺘل ﻤﻥ ﻤﺸﺎﻜل ﺍلPhysical Corruption ﻓﻤﺎ ﻋﻠﻴﻙ ﺇﻻ ﺃﻥ ﺘﻜﺘﺏ ﺍﻷﻤﺭ NOCHECKSUM ﺃﺜﻨﺎﺀ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ.

    ﻜﺫﻟﻙ ﺘﺴﺘﻁﻴﻊ ﺍﻟﺘﺄﻜﺩ ﻤﻥ ﺴﻼﻤﺔ ﺍﻟﻜﺘل ﻤﻥ ﺍﻟﻤﺸﺎﻜل ﺍﻟﻤﻨﻁﻘﻴﺔ Logical Corruption من خلال الامر CHECK LOGICAL.

    ﺇﺫﺍ ﻜﺎﻥ ﻤﺩﻴﺭ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﻴﻨﺠﺯ ﻤﻬﺎﻤﻪ ﻓﻲ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﺒﻭﺍﺴﻁﺔ ﺍلUser-Managed Backup، ﻓﻘﺩ ﻴﻭﺍﺠﻪ ﺒﻌﺽ ﺍﻟﻤﺸﺎﻜل ﻋﻨﺩ ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ،

    ﻓﻠﻭ ﺤﺩﺙ ﺃﻥ ﻓﺴﺩﺕ ﻜﺘﻠﺔ ﻭﺍﺤﺩﺓ ﻓﻲ ﺃﺤﺩ ﻤﻠﻔﺎﺕ ﺍلData File ﻓﻼﺒﺩ ﻤﻥ ﺍﺴﺘﺭﺠﺎﻉ ﻫﺫﺍ ﺍﻟﻤﻠﻑ ﺒﺄﻜﻤﻠﻪ ﻭﺫﻟﻙ ﻷﻥ ﺍلUser-Managed Backup ﻻ ﺘﺩﻋﻡ 

    ﺍلBlock Media Recovery.

      ﺃﻤﺎ ﺃﺫﺍ ﻜﺎﻥ ﻤﺩﻴﺭ ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﻴﺴﺘﺨﺩﻡ ﺍﻷﺩﺍﺓ RMAN ﻓﺈﻨﻪ ﻴﺴﺘﻁﻴﻊ ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻓﻘﻁ، ﻤﻤﺎ ﻴﻘﻠل ﺍﻟﻭﻗﺕ ﺍﻟﻤﺴﺘﻐﺭﻕ ﻓﻲ ﺍﻻﺴﺘﺭﺠﺎﻉ ﻭﻜﺫﻟﻙ ﺃﺜﻨﺎﺀ ﺍﻻﺴﺘﺭﺠﺎﻉ

    ﺘﻅل ﻗﺎﻋﺩﺓ ﺍﻟﺒﻴﺎﻨﺎﺕ ﻤﻔﺘﻭﺤﺔ ﻭﻴﻅل ﻜﺫﻟﻙ ﺍلData File ﻤﻔﺘﻭﺤﺎﹰ ﻭﻴﺴﺘﻁﻴﻊ ﺍﻟﻤﺴﺘﺨﺩﻤﻭﻥ ﻤﻭﺍﺼﻠﺔ ﻋﻤﻠﻬﻡ ﺴﻭﺍﺀ ﺘﻠﻙ ﺍلSessions ﺍﻟﺘﻲ ﺘﺤﺘﺎﺝ ﺍﻟﻭﺼﻭل ﻟﻠﻜﺘل ﺍﻟﺘﻲ ﻴﺘﻡ ﺍﺴﺘﺭﺠﺎﻋﻬﺎ.

    ﻟﺤﻅﺔ ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻋﻥ ﻁﺭﻴﻕ ﺍلRMAN ﻴﺘﻡ ﺘﺯﻭﻴﺩ ﺍلRMAN ﺒﻘﺎﺌﻤﺔ ﺍﻟﻜﺘل ﺍﻟﺘﻲ ﻨﺤﺘﺎﺝ ﻻﺴﺘﺭﺠﺎﻋﻬﺎ، ﻓﺘﻘﻭﻡ ﺍلRMAN ﺒﺎﻟﺒﺤﺙ ﻋﻥ ﻫﺫﻩ ﺍﻟﻜﺘل ﻓﻲ ﻤﻠﻔﺎﺕ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ

    ﺴﻭﺍﺀ ﺃﻜﺎﻥ ﺫﻟﻙ ﺍﻟﻨﺴﺦ ﺍﻻﺤﺘﻴﺎﻁﻲ ﻤﻥ ﺍﻟﻨﻭﻉ Backup Set ﺃﻭ ﺍﻟﻨﻭﻉ Image Copy ﻭﺘﻘﻭﻡ ﺒﺈﺭﺠﺎﻋﻪ ﻟﻠﻤﻠﻑ، ﺜﻡ ﺘﻘﻭﻡ ﺒﺎﺴﺘﺨﺩﺍﻡ ﻤﻠﻔﺎﺕ ﺍﻷﺭﺸﻴﻑ ﺍﻟﻤﻨﺎﺴﺒﺔ ﻟﺘﻁﺒﻴﻕ ﺍﻟﺘﻐﻴﻴﺭﺍﺕ ﺍﻟﺘﻲ ﺤﺩﺜﺕ،

    ﻭﺩﺍﺌﻤﺎﹰ ﻤﺎ ﻴﺘﻡ ﺍﻻﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺎﻤل Complete Recovery، ﻭﻟﻜﻥ ﻴﻅل ﺍﻟﻤﺴﺘﺨﺩﻤﻭﻥ ﻴﺴﺘﻠﻤﻭﻥ ﺭﺴﺎﺌل ﺍﻟﺨﻁﺄ 01578-ORA ﻤﺎﺩﺍﻡ ﻴﺤﺎﻭﻟﻭﻥ ﺍﻟﻭﺼﻭل ﻟلCorrupted Blocks ﻗﺒل ﺇﻜﻤﺎل ﺍﻻﺴﺘﺭﺠﺎﻉ.

    ﻴﺘﻡ ﺍﺴﺘﺭﺠﺎﻉ ﺍﻟﻜﺘل ﺍﻟﻔﺎﺴﺩﺓ ﻋﺒﺭ ﺍلRMAN ﻋﻥ ﻁﺭﻴﻕ ﺍﻷﻤﺭ BLOCKRECOVER.


    RMAN> blockrecover datafile 5 block 5,7;