|Oracle9i Real Application Clusters Administration
Release 2 (9.2)
Part Number A96596-01
When you execute the Discover Node command from the Console, the Management Server contacts the Oracle Intelligent Agent installed on that node to discover the Oracle services installed on the node. The Management Server then places the new information in the repository, and updates the hierarchical tree in the Navigator window of the Console, displaying a broad view of all nodes and their respective services.
The synchronization of data in multiple caches so that reading a memory location by way of any cache will return the most recent data written to that location by way of any other cache. Sometimes called cache consistency.
A diskless cache coherency mechanism in Real Application Clusters that provides copies of blocks directly from a holding instance's memory cache to a requesting instance's memory cache.
A set of instances that cooperates to perform the same task.
The generic term a Real Application Clusters database.
See cluster database.
See cluster database.
An operating system-dependent component that discovers and tracks the membership state of each node by providing a common view of membership across the cluster. The CM also monitors process health, specifically the health of the database instance. The Global Enqueue Service Monitor (LMON), a background process that monitors the health of the Global Cache Service (GCS), registers and de-registers from the CM.
See: Cluster Manager (CM).
A specially formatted description of the destination for a network connection. A connect descriptor contains destination service and network route information.
A feature that balances the number of active connections among various instances and shared server dispatchers for the same service. Because of service registration's ability to register with remote listeners, a listener is always aware of all instances and dispatchers regardless. This way, a listener can sends an incoming client request for a specific service to the least loaded instance and least loaded dispatcher regardless of its location.
The Oracle Enterprise Manager Console gives you a central point of control for the Oracle environment through an intuitive graphical user interface (GUI) that provides powerful and robust system management. The Console provides menus, tool bars, and launch palettes that enable access to Oracle tools. The Console consists of four separate windows. See also: Navigator Window,Group Window, Event Management Window, and job window.
Disk and Execution Monitor. A program that is not invoked explicitly, but lies dormant waiting for some condition to occur.
An Oracle tool for creating and deleting databases and for managing database templates.
A server that requires a dedicated server process for each user process. There is one server process for each client. Oracle Net sends the address of an existing server process back to the client. The client then resends its connect request to the server address provided. Contrast with shared server.
Database and application environments that help with decision support or data warehouse systems.
A process that enables many clients to connect to the same server without the need for a dedicated server process for each client. A dispatcher handles and directs multiple incoming network session requests to shared server processes. See also shared server.
The process of recovery over a cluster.
Shared memory structures that serialize access to database resources and are associated with a session or transaction. In Real Application Clusters, enqueues can be global to a database. Enqueues are local to one instance if Real Application Clusters is not enabled.
A tool for creating, deleting, and modifying Oracle Enterprise Manager configurations and settings.
Part of the Console. The Event Management window enables the administrator to remotely monitor critical database and system events.
A write-only global block access mode. In this mode no other access is allowed.
The process of failure recognition and recovery.
Sets of free lists available for use by one or more instances.
The Database Configuration Assistant's preconfigured database template for a hybrid database environment. This template includes datafiles.
Process that implement Cache Fusion. It maintains the block mode for blocks in the global role. It is responsible for block transfers between instances. The Global Cache Service employs various background processes such as the Global Cache Service Processes (LMSn) and Global Enqueue Service Daemon (LMD).
Processes that manage remote Global Cache Service (GCS) messages. Real Application Clusters provides for up to 10 Global Cache Service Processes. The number of LMSn varies depending on the amount of messaging traffic among nodes in the cluster.
Global resources that coordinate access to data blocks in the buffer caches of multiple Real Application Clusters instances to provide cache coherency.
The full name of the database that uniquely identifies it from any other database. The global database name is of the form
Dynamic performance views storing information about all open instances in a Real Application Clusters cluster. (Not only the local instance.) In contrast, standard dynamic performance views (
V$) only store information about the local instance.
A service that coordinates enqueues that are shared globally.
The resource agent process that manages requests for Global Cache Service (GCS) resources to control access to blocks. The LMD process also handles deadlock detection and remote resource requests. Remote resource requests are requests originating from another instance.
The background LMON process monitors the entire cluster to manage global resources. LMON manages instance deaths and the associated recovery for the Global Cache Service (GCS). In particular, LMON handles the part of recovery associated with global resources. LMON-provided services are also known as Cluster Group Services.
An architecture that stores, processes, and retrieves data in native languages. It ensures that database utilities and error messages, sort order, date, time, monetary, numeric, and calendar conventions automatically adapt to the native language and locale.
Inter-instance synchronization mechanisms that provide cache coherency for Real Application Clusters. The term can refer to both Global Cache Service (GCS) resources and Global Enqueue Service (GES) resources.
A component that receives requests from SRVCTL to execute administrative job tasks, such as startup or shutdown. The command is executed locally on each node, and the results are returned to SRVCTL. GSD is installed on the nodes by default.
Part of the Console. The Group window provides a customized graphical representation of key objects. It is created by the administrator.
Systems with redundant components that provide consistent and uninterrupted service, even in the event of hardware or software failures. This involves some degree of redundancy.
A hybrid database is one that has both OLTP and Data Warehouse processing characteristics. See General Purpose.
A parameter designating the continuation file of an initialization parameter file.
An instance initialization parameter file that contains parameters unique for an instance and points to initdbname.ora for database parameters.
A common database initialization parameter file shared among the instance that contains database parameters.
For a Real Application Clusters database, each node within a cluster usually has one instance of the running Oracle software that references the database. When a database is started, Oracle allocates a memory area called the System Global Area (SGA) and starts one or more Oracle processes. This combination of the SGA and the Oracle processes is called an instance. Each instance has unique Oracle System Identifier (sid), instance name, rollback segments, and thread ID.
The method used by Real Application Clusters guaranteeing that all cluster members are functional or active. IMR polls and arbitrates the membership. Any members that do not show a heartbeat by way of the control file or who do not respond to periodic activity inquiry messages are presumed terminated.
Represents the name of the instance and is used to uniquely identify a specific instance when clusters share common services names. The instance name is identified by the
INSTANCE_NAME parameter in the instance initialization file, initsid.ora. The instance name is the same as the Oracle System Identifier (sid.) See also: Oracle system identifier (sid).
A number that associates extents of data blocks with particular instances. The instance number enables you to start up an instance and ensure that it uses the extents allocated to it for inserts and updates. This will ensure that it does not use space allocated for other instances.
See: Oracle Intelligent Agent.
The communication link between nodes.
A high-speed operating system-dependent transport component. The IPC transfers messages between instances on different nodes. Also referred to as the interconnect.
Part of the Console. The Job window enables the administrator to automate repetitive activities.
A low-level serialization mechanism that protects in-memory data structures in the System Global Area (SGA). Latches do not protect datafiles, are automatic, and are held for a very short time in exclusive mode. Because latches are synchronized within a node, they do not facilitate internode synchronization.
A protocol for accessing on-line directory services.
A process that resides on the server to listen for incoming client connection requests and manage the traffic to the server. When a client requests a network session with a server a listener receives the request. If the client information matches the listener information, then the listener grants a connection to the server.
A listener configuration file that identifies the protocol addresses on which the listener is accepting connection requests and the services the listener listens for.
The Oracle Enterprise Manager Management Server provides centralized intelligence and distributed control between the Console and the managed nodes, and processes system management tasks sent by the Console and administers the distribution of these tasks across the enterprise. The Management Server stores all system data, application data, and information about the state of managed nodes in a repository. The repository is a set of tables stored in a database. High performance and scalability is ensured because the workload is automatically shared and balanced when there are multiple Management Servers.
A list of blocks containing available space drawn from any extent in a table.
The average time (usually expressed in hours) that a component works without failure. It is calculated by dividing the total number of failures into the total number of operating hours observed. The term can also mean the length of time a user can reasonably expect a device or system to work before an failure occurs.
The average period of time that a component will work until failure.
The average time that it takes to get a failed piece of hardware back on line. Outside the context of Real Application Clusters, the acronym MTTR is also used for Mean Time to Repair.
The capability of having more than one Oracle home directory on a machine.
See: null (N).
The method used by a client application to resolve a net service name to a connect descriptor.
Part of the Console. The Navigator window contains an object browser that provides an organized, consistent, and hierarchical view of the database objects in the network.
A simple name for a service that resolves to a connect descriptor. Users initiate a connect request by passing a user name and password along with a net service name in a connect string for the desired service.
A protocol developed by Sun Microsystems, and defined in RFC 1094, that enables a computer to access files over a network as if the files were on local disks.
A node is a machine on which an instance resides.
Null indicates that an access mode is not assigned to a block or resource.
The processing of transactions by computers in real time.
Software that consists of several software components developed by Oracle or by other vendors. The OSD clusterware maps the key operating system and clusterware services required for proper operation of Real Application Clusters.
Oracle Enterprise Edition is an Object-Relational Database Management System (ORDBMS). It provides the applications and files to manage a database. All other Real Application Clusters components are layered on top of Oracle Enterprise Edition.
A system management tool that provides an integrated solution for centrally managing your heterogeneous environment. Oracle Enterprise Manager combines a graphical Console, Management Server, Oracle Intelligent Agent, repository database, and tools to provide an integrated, comprehensive systems management platform for managing Oracle products.
A process that runs on each of the nodes. It functions as the executor of jobs and events sent by the Console by way of the Management Server. High availability is ensured since the agent can function regardless of the status of the Console or network connections.
A software component that enables connectivity. It includes a core communication layer called the Oracle Net foundation layer and network protocol support. Oracle Net enables services and their applications to reside on different computers and communicate as peer applications.
An add-on application for Oracle Enterprise Manager that offers tabular and graphic performance statistics for Real Application Clusters. The statistics represent the aggregate performance for all instances running on Real Applications.
A breakthough architecture that enables clusters to access a shared database. Real Application Clusters includes the software component that provides the necessary Real Application Clusters scripts, initialization files, and datafiles to make the Oracle9i Enterprise Edition an Oracle9i Real Application Clusters database.
The Oracle System Identifier (sid) identifies a specific instance of the running Oracle software. For an Real Application Clusters database, each node within the cluster has an instance referencing the database.
The database name, specified by the
DB_NAME parameter in the
INITDB_NAME.ORA file, and unique thread ID make up each node's sid. The thread ID starts at 1 for the first instance in the cluster, and is incremented by 1 for the next instance, and so on. See also: instance name.
A tool to install the Oracle relational database software. You can also use the Oracle Universal Installer to launch the Database Configuration Assistant (DBCA).
A file used by the Oracle server that provide specific values and configuration settings that are used on database startup. The keyword
PFILE is used in the startup command.
Each Oracle Enterprise Manager administrator can set up specific user names, passwords, and roles for nodes, listeners, databases, and other services that you administer in the network.
An Oracle tool that enables you to back up, copy, restore, and recover datafiles, control files, and archived redo logs. It is included with the Oracle server and does not require separate installation. You can invoke RMAN as a command line utility from the operating system (O/S) prompt or use the GUI-based Enterprise Manager Backup Manager.
A set of tables in an Oracle database that stores data required by Oracle Enterprise Manager. This database is separate from the database on the nodes.
See: Recovery Manager (RMAN).
The ability to add additional nodes to Real Application Clusters applications and achieve markedly improved scale-up and speed-up.
A preconfigured, ready-to-use database that re quires minimal user input to create. See also: starter database.
Server Management uses the SRVCTL utility (installed on each node) to manage configuration information that is used by some Oracle tools. For example, SRVCTL serves as a single point of control between the Oracle Intelligent Agent and the nodes. Only one node's Oracle Intelligent Agent is used to communicate with SRVCTL. SRVCTL on that node then communicates to the other nodes through Oracle Net.
Server Management (SRVM) comprises the components required to operate Oracle Enterprise Manager in Real Application Clusters. The SRVM components, such as the Intelligent Agent, Global Services Daemon, and SRVCTL, enable you to manage cluster databases running in heterogeneous environments through an open client/server architecture using Oracle Enterprise Manager.
A binary parameter file that resides on the Oracle Server. This file contains parameter settings that are both global and instance-specific. These parameter settings are persistent across instance shutdown and instance startup events.
When you execute the Discover Node command from the Console, the Management Server contacts the Oracle Intelligent Agent installed on that node to discover the Oracle services installed on the node. The Management Server then places the new information in the repository and updates the hierarchical tree in the Navigator window of the Console, displaying a broad view of all nodes and their respective services.
A logical representation of a database. This is the way a database is presented to clients. A database can be presented as multiple services and a service can be implemented as multiple database instances. The service name is a string that is the global database name, a name comprised of the database name (
DB_NAME) and domain name (
DB_DOMAIN), entered during installation or database creation.
A feature whereby PMON automatically registers information with a listener. Because this information is registered with the listener, the
listener.ora file does not need to be configured with this static information.
The buffer state name for shared access mode to a block.
A protected read block access mode. No writes are allowed in shared mode. In shared mode, any number of users can have simultaneous read access to a resource. See also: exclusive (X) access mode.
A server that is configured to allow many user processes to share very few server processes, so the number of users that can be supported is increased. With shared server configurations, many user processes connect to a dispatcher.
The binary parameter file that resides on the Oracle Server.
RMAN creates a snapshot control file to resynchronize from a read-consistent version of the control file. This is a temporary snapshot control file. RMAN only needs a snapshot control file when resynchronizing with the recovery catalog or when making a backup of the current control file.
A configuration file for the client or server that specifies:
sqlnet.ora file typically resides in the
$ORACLE_HOME/network/admin directory on UNIX platforms and in the
%ORACLE_HOME%\network\admin directory on Windows platforms.
See: seed database.
A database administration role that contains all system privileges with the
ADMIN OPTION, and the
SYSOPER system privilege.
SYSDBA also permits
CREATE DATABASE and time-based recovery.
A database administration role that permits a database administrator to perform any of the following commands:
ALTER DATABASE OPEN/MOUNT,
ALTER DATABASE BACKUP,
ARCHIVE LOG, and
SYSOPER includes the
Each Oracle instance has its own set of online redo log groups. These groups are called a thread of online redo. In non-Real Application Clusters environments, each database has only one thread that belongs to the instance accessing it. In Real Application Clusters environments, each instance has a separate thread, that is, each instance has its own online redo log. Each thread has its own current log member.
The number of the redo thread to be used by an instance as specified by the
THREAD initialization parameter or the
THREAD clause in the
ALTER DATABASE ADD LOGFILE statement. You can use any available redo thread number but an instance cannot use the same thread number as another instance.
A file that contains net service names. This file is needed on clients, nodes, the Console, and the Oracle Performance Manager machine.
A runtime failover for high-availability environments, such as Real Application Clusters and Oracle Real Application Clusters Guard, TAF refers to the failover and re-establishment of application-to-service connections. It enables client applications to automatically reconnect to the database if the connection fails, and optionally resume a SELECT statement that was in progress. This reconnect happens automatically from within the Oracle Call Interface (OCI) library.
A memory-based networking interface.