GC_DB_LOCKS (Oracle7 Only)
by Brian Laskey, David C. Kreines
Oracle Database Administration: The Essential Refe
- Dedication
- Preface
- I. DBA Tasks
- 1. Introduction
- 2. Installation
- 3. Maximizing Oracle Performance
- 4. Preventing Data Loss
- 5. Oracle Networking
- Oracle Names
- MultiProtocol Interchange
- Connecting to Non-Oracle Databases
- Network Manager Data Storage
- Using Network Manager
- Files Created by Network Manager
- Oracle Net8 Assistant
- Manual Network Configuration
- Sample SQL*Net Files
- SQL*Net Troubleshooting
- 6. Security and Monitoring
- 7. Auditing
- 8. Query Optimization
- 9. Oracle Tools
- 10. The Oracle Instance
- 11. The Oracle Database
- 12. Initialization Parameters
- 13. SQL Statements for the DBA
- SQL Commands by Task
- SQL Command Syntax
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- Reference Section
- column_constraint_clause
- auto_extend_clause
- for_clause
- filespec
- autoextend_clause
- global_index_clause
- local_index_clause
- table_constraint_clause
- table_ref_clause
- column_ref_clause
- column_constraint_clause
- index_organization_clause
- segment_attrib_clause
- partition_clause
- autoextend_clause
- 14. The Oracle Data Dictionary
- Static Data Dictionary Views
- Dynamic Performance Data Dictionary Views
- 15. System Privileges and Initial Roles
- 16. Tools and Utilities
Name
GC_DB_LOCKS (Oracle7 Only)
Synopsis
Values:1 to unlimited
Default:0
Multiple Instances:Must have identical values
Specifies the total number of PCM locks covering data blocks cached in the multiple SGAs of a parallel server. This parameter must be set to a value greater by at least 1 than the sum of the locks set with the GC_FILES_TO_LOCKS initialization parameter. GC_DB_LOCKS is always rounded up to the next prime number in order to ensure that PCM locks are available for datafiles not specified in GC_FILES_TO_LOCKS.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.