Based on Oracle's dependence on the platform, this article uses the NT platform as an example to describe some features of Oracle on the NT platform, and provides an Oracle System Optimization idea.
Currently, Oracle is developing rapidly as a large-scale database management system. How can we better utilize its powerful data management functions? This has become an important issue in Oracle system optimization. This article attempts to explore its "potential" from the system parameters and other software. It attempts to find out the specific relationship between Oracle and the external environment, that is, the platform dependency of Oracle. This article mainly uses the NT platform as an example, describes the platform dependencies of Oracle.
1. Oracle is only a multi-thread (Multiple Threads) Operating System Process on the NT platform ).
On the NT platform, every background "process" (such as LGWR and DBWR) and dedicated service "process" of Oracle are subthreads of Oracle processes. This multi-threaded Architecture (Muli_threaded Architecture) is very efficient on NT because all sub-threads share resources of the same master process. If you add an Oracle Instance, there will be a new Oracle process, which is also owned by the new process. On the NT platform, the operating system does not mark every Oracle thread with names such as LGWR and DBWR. To View information about threads, you can use SQL statements to query related tables and views in the Data Dictionary ).
For example, to view the internal number of the dbwr thread:
Select B. name, p. spid
From v $ bgpross B, v $ process p
Where B. paddr = p. addr
And name = 'dbwr'
In addition, Oracle's system performance monitoring tool also provides a simple way to view thread information.
[Content navigation] |
Page 1: efficient multi-threaded Structure |
Page 1: space restrictions |
Page 1: parameters and monitoring |
Page 1: Security |