Index

A B C D E F G H I J L M N O P Q R S T U V W

A

abort mode

taking single-instance databases offline in, 5

access to resources, 2.2.1

accounts

adding to database password file, 7.5.1

changing domain name for Oracle Services for MSCS account, 4.3.1.1

privileges and permissions, 4.3

to manage a single-instance Oracle database, 7.5

under which generic service runs, 8.3.2.3, 8.3.2.3, 8.3.2.3

under which Oracle Services for MSCS runs, 4.3.1.1

active/active configurations, 3.1.2

active/passive configurations, 3.1.1

Add Resource to Group operation

troubleshooting, 7.2.2

Add Resource to Group Wizard

generic services, 8.3.2

Oracle single-instance databases, 7.3.3

adding a generic service to a group, 8.3

account, 8.3.2.3

cluster disks, 8.3.2.4

dependencies, 8.3.2.5

display name, 8.3.2.2

image name, 8.3.2.2

node name, 8.3.2.2

possible owner nodes, 8.3.2.1

registry keys, 8.3.2.6

service name, 8.3.2.2

startup parameters, 8.3.2.3

steps, 8.3.1

virtual addresses, 8.3.2.5.2

adding a single-instance Oracle database to a group, 7.3

authentication information, 7.3.3.4

database name, 7.3.3.3

instance name, 7.3.3.3

Oracle Net listener, 7.4.2

password, 7.3.3.5

possible owner nodes, 7.3.3.1

prerequisites, 7.3.1

service name, 7.3.3.3

steps, 7.3.2

tnsnames.ora file, 7.3.2

virtual addresses, 7.3.3.2

Administrator privileges

logging in to a cluster, 4.3.2

specifying with the FSCMD command, 5

alert files, B.4

allocating IP addresses for a cluster, 2.4

application log

troubleshooting startup problems, 6.4

application software

rolling upgrade of, 1.2.2

applications

automatic reconnection after failover, 1.2.4

failover, 1.2.4, 2.7.2

mission-critical, 3.1.2

archived files, 7.10.8.3

authentication

checking preferences in Oracle Enterprise Manager, 7.10.9

log on as batch user access rights, 7.10.9

permissions and privileges required, 4.3

REMOTE_LOGIN_PASSWORDFILE initialization parameter, 7.5

SYSDBA role, 7.5.1

SYSOPER privileges, 7.5.1

troubleshooting DBA authentication, 7.10.6

using SYS for databases, 7.5.1

availability

RAID technology, 2.1.1

B

backup operation

sample FSCMD commands in a script, 5

bandwidth

increasing with multiple virtual addresses, 2.3

benefits

of configuring generic services using Oracle Fail Safe, 8.1.1

of Oracle Fail Safe, 1.2

bequeath protocol adapter

Oracle Fail Safe connection to single-instance database and, 7.4

BYPASS value, 7.3.3.5

C

changing

domain name for Oracle Services for MSCS account, 4.3.1.1

checkpoints

prior to database failover, 2.6.2

client connections

to single-instance Oracle databases, 7.4.2

clients

access to resources, 2.3

accessing groups with multiple virtual addresses, 4.7

cluster connections, 2.7.2

connecting to resources using multiple virtual addresses, 4.7

reconnecting to a single-instance database after failover, 7.9

registering addresses of, A.1

cluster alias

definition, 2.5

Oracle Fail Safe Manager and, 2.5

registering address of, A.1

use of, 2.5

cluster disks

generic services and, 8.3.2.4

Oracle single-instance databases and, 7.3.1

RAID hardware and, 1.3

redundancy and, 2.1.1

D

data files

adding new, 7.7

database account

SYS, 7.5, 7.10.9

database administrator

changing the password, 7.10.6

connecting as internal, 7.10.6

DBA_AUTHORIZATION parameter, 7.3.3.5, 7.5

Database Configuration Assistant (DBCA), 7.2.1

creating the Oracle Net configuration, 7.2.1

net service name entry and, 7.2.1

database password file

adding accounts to for a database, 7.5.1

database recovery

optimization for single-instance databases, 7.6

databases

adding a new data file, 7.7

backup operations on, 7.7

using FSCMD commands, 5

changing DBA passwords, 7.10.6

checkpointing and, 2.6.2

clients lose single-instance database connection, 7.10.10

configuration data, 7.3.3

configuring database resource to use shared servers, 7.4.5

configuring using wizard input, 4.2

EXCLUSIVE access, 7.5

group resource, 2.2.2

identity, 7.3.3.3

improving connection time, 7.4.1

Is Alive polling, 7.10.6

listeners for standalone, 7.2.4

LOCAL_LISTENER parameter in the initialization file, 7.4.5.1

name, 7.3.3.3

net service name entry, 7.2.1

Oracle8i or later using shared servers, 7.4.5.1

resolving an unstable state, 7.10.4

security, 7.5

SHARED access, 7.5

shared servers and MSCS cluster nodes, 7.4.5

steps for configuring, 7.3.2, 7.3.2

synchronizing password files, 7.5.1

taking offline, 5, 5, 7.7

due to change in password, 7.10.6

for cold backup operation, 7.7

Pending Timeout, 7.10.4

problems, 7.10.6

with FSCMD command, 7.6

testing shutdown on the secondary node, 4.2

updating tnsnames.ora file for remote client access, 7.4.3.1

upgrading, 7.2.3

upgrading with Oracle Database Upgrade Assistant, 7.5.3

using shared servers, 7.4.5

using SQL*Plus for cold backup operations, 7.7

verifying, 6.1.2, 6.1.3

virtual addresses, 7.3.3.2

E

ENABLEISALIVE parameter, 5, 7.10.5

error handling

scripts and, 7.10.1

errors

FS-10066, 7.10.8.1

FS-10070, 7.10.8.1

FS-10101, 7.10.9

ORA-01031, 7.10.9

reporting, B.1

returned for insufficient privileges, 7.10.9

tracking information in a trace file, B.3

user authentication, 7.10.9

written to the Oracle Net listener log, 7.10.4

external procedures

configuring, 7.4.4

F

failback

effect of preferred owner nodes list on, 2.7.1, 2.7.1

move group operation effect on, 2.7.1

failback policy

dumping information about, 6.2

specifying, 2.7

verifying with Verify Group operation, 6.1.2, 7.10.2

failover period, 2.6.8

failover policy

for groups, 2.6.8

failover threshold, 2.6.8

failovers, 2.6

applications, 1.2.4

automatic application reconnection, 1.2.4

checking with the Verify command, 4.2

client applications and, 2.7.2

database checkpointing and, 2.6.2

definition, 2.1

disabling during backup operations, 7.7

due to resource failure, 2.6.1.1

dumping information about policies, 6.2

effect of possible owner nodes list on, 2.6.11

effect of preferred owner nodes list on, 2.6.11

effect of resource restart policy on, 2.6.9

fastest, 3.1.1

for load-balancing, 2.6

groups and, 2.2.2

in an active/active configuration, 3.1.2

limiting repeated, 2.6.8

node failures and, 2.6.1.2

node to which group moves during, 2.6.11

planned, 2.6, 2.6.2

replaying transactions and, 1.2.4

troubleshooting, 7.10.5

unit of, 2.2.2

unplanned, 2.6

verifying with Verify Group operation, 6.1.2, 7.10.2

failures

unplanned, 2.6.1

verifying resources to prevent, 6.1.2, 6.1.3

Fibre Channel

shared storage interconnect, 1.3

file corruption

in tnsnames.ora and listener.ora files, 7.10.8.1

files

alert, B.4

archived, 7.10.8.3

rollback, 7.10.8.4, 7.10.8.4

trace, B.4

flags

tracing Oracle Services for MSCS errors, B.3

FSCMD command, 1.2.2

DISABLEISALIVE parameter, 5, 7.10.5

DUMPCLUSTER parameter, 5

ENABLEISALIVE parameter, 5, 7.10.5

example usage in a script, 5

examples, 5

MOVEGROUP parameter, 5

OFFLINEGROUP parameter, 5

OFFLINERESOURCE parameter, 5

ONLINEGROUP parameter, 5

ONLINERESOURCE parameter, 5

parameters and qualifiers, 5

syntax, 5

usage notes, 5

use in an active/active configuration, 3.1.2

VERIFYALLGROUPS parameter, 5

VERIFYCLUSTER parameter, 5

VERIFYGROUP parameter, 5

FsDbError.bat script, 7.10.1

FSR_TRACE_OUTPUT value, B.3

FsResOdbs.dll file

functions, 2.2.4

FsResOdbsEx.dll file

functions, 2.2.4

FSS_TRACE_OUTPUT value, B.3

G

General property page

for resources, 2.6.7

generic services

adding to a group, 8.3.1

advantages of configuring using Oracle Fail Safe, 8.1.1

compared to other services Oracle Fail Safe supports, 8.1

configuration steps, 8.3.2

configuring for high availability, 8.3, 8.3.2

creating and adding to a group, 8.3.2

defined, 2.2.4, 8

dependencies, 8.3.2.5

discovering standalone, 8.2, 8.2

display name and, 8.3.2.2

for Windows services, 2.2.4

generic service identity, 8.3.2.2

image name and, 8.3.2.2

LocalSystem account and, 8.3.2.3

node name and, 8.3.2.2

passing parameters to Windows Service Control Manager, 8.3.2.3

placement of data files and, 8.3.2.4

placement of executable files and, 8.3.2.2

possible owner nodes, 8.3.2.1

resource type, 2.2.4

security requirements for, 8.4

service name and, 8.3.2.2

specifying account for, 8.3.2.3

startup parameters, 8.3.2.3

startup type and, 8.3.2.3

steps for configuring for high availability, 8.3.1

troubleshooting, 8.5

virtual addresses, 8.3.2.5.2

what not to configure for high availability, 8.1.2

Windows registry keys and, 8.3.2.6

H

hardware

configuration, 1.3

RAID, 1.3

heartbeat connection, 2.1

definition of, 1.3

host name

registering, A.1

troubleshooting improper name resolution with, A.4

validating proper name resolution, A.2

Hosts files

registering IP address and host names in, A.1

I

image name

generic services and, 8.3.2.2

immediate mode

taking single-instance databases offline in, 5

initialization parameter file

deleting the LOCAL_LISTENER parameter, 7.4.5.1

exporting SPFILE and, 7.3.3.3.1

for highly available single-instance databases, 7.3.3.3, 7.3.3.3

location of, 7.3.3.3

PFILE and, 7.3.3.3.1

placement of, 7.3.3.3

REMOTE_LOGIN_PASSWORDFILE initialization parameter, 7.3.3.5, 7.5, 7.10.6

restrictions on specifying SPFILE and, 7.3.3.3.1

installation

interactive, 1.2.2

of Oracle Fail Safe, 1.2.2

silent mode, 1.2.2

using a response file with, 1.2.2

instance name

for highly available single-instance databases, 7.3.3.3

J

jobs

troubleshooting access problems, 7.10.9

L

Listener Control Utility (LSNRCTL)

creating listeners, 7.10.8.2

listener.ora files, 4.2

archived, 7.10.8.3

checking configuration data, 7.10.4

configuring multiple, 7.2.4

example, 7.10.8.1

EXTPROC prefix, 7.4.4

modifying, 7.10.8.1

problems configuring the virtual server, 7.10.8.1

rollback files, 7.10.8.1

sample definition, 7.10.8.1

updated by Database Configuration Assistant, 7.2.1

listeners

changes for shared servers, 7.2.5

configuring, 4.2

configuring Oracle Net on nodes with multiple listeners, 7.2.4

created for single-instance databases added to a group, 7.4.2

creating new, 7.10.8.2

creating with Listener Control Utility (LSNRCTL), 7.10.8.2

definition in rollback file, 7.10.8.1

enabling shared sockets and, 7.4.1

log file, 7.10.4

network resources, 2.2.2

output files, 7.10.8.2

problems after changing or creating definition of, 7.10.8.1

problems creating, 7.10.8.2

specifying in the LOCAL_LISTENER parameter, 7.4.5.1

specifying information in the DISPATCHERS parameter, 7.4.5.1

starting, 7.2.4

troubleshooting, 7.10.4

load balancing, 2.6

in an active/active configuration, 3.1.2

static, 2.6.2

local area network, 1.3

LOCAL_LISTENER parameter

adding to single-instance database parameter file, 7.2.5

deletion after removing a single-instance database from a group, 7.4.5.1

specifying listeners in, 7.4.5.1

updating information for the group, 7.4.5.1

writing to the single-instance database parameter file, 7.4.5.1

LocalSystem account

generic services and, 8.3.2.3

log on as a service privilege

generic services and, 8.4

LOGFILE qualifier

FSCMD command, 5

LSNRCTL utility

troubleshooting listener problems, 7.10.8.2

M

management operations

single-instance database, 7.7

managing

cluster security, 4.3

tnsnames.ora file on client systems, 7.3.2, 7.4.3.1

using a cluster alias, 2.5

Microsoft Windows

registration considerations, A

mission-critical applications

in active/active configurations, 3.1.2

modifying

possible owner nodes list, 2.6.7

move group operation

effect on failback, 2.7.1

MOVEGROUP parameter, 5

MSCS

cluster software, 1.1

displaying database properties with Cluster Administrator, 2.2.4

Is Alive polling, 2.2.4

Pending Timeout value, 7.10.4

resource types, 2.2.4

MSCS Cluster Administrator

displaying Oracle database properties, 2.2.4

use during tracing, B.3

multiple Oracle homes, 4.6

checking for overlapping addresses and single-instance database SID names, 7.10.8.1

configuring multiple listeners, 7.2.4

multiple listeners, 7.2.4

single-instance database SID in listener.ora files, 7.10.8.1

updating tnsnames.ora with Verify Standalone Database command, 7.2.1

N

net service name, 7.3.3.3

added for single-instance databases, 7.2.1

appended with the default domain name, 7.4.3.1

default domain name and, 7.4.3.1

definition

referencing in archived configuration files, 7.10.8.3

entry after adding a single-instance database to a group, 7.4.3.1

entry for new single-instance databases, 7.2.1

highly available single-instance databases and, 7.3.3.3

when configuring the virtual server, 7.10.8.1

network configuration

updating domain name values in sqlnet.ora files, 7.2.1

network name

cluster alias, 2.5

correcting for group, 7.10.8.1

networks

configuration, A

for highly available single-instance databases, 7.4.2

Oracle Net on nodes with multiple listeners, 7.2.4

updating, 7.2.1

verify with Verify Group, 7.10.2

dumping public and private information, 6.2

problems while configuring virtual server, 7.10.8.1

protocol information in tnsnames.ora file, 4.2

tracing configuration information, B.3

node

to which a group fails over, 2.6.11

node failures

effects of, 2.7.2

failover and, 2.6.1.2

node name

generic services and, 8.3.2.2

NODE qualifier

FSCMD command, 5

nodes

adding to an existing cluster, 4.8

cluster, 1.2.1

definition of, 2.1

excluding from possible owner nodes list, 2.6.7

possible owner, 2.6.7

preferred, 2.7

preferred ownership of groups and, 2.6.10

Nodes property page

for groups, 2.6.7

normal mode

taking single-instance databases offline in, 5

O

OFFLINE qualifier

FSCMD command, 5

OFFLINEGROUP parameter, 5

offline-option modes, 5

OFFLINERESOURCE parameter, 5

ONLINEGROUP parameter, 5

ONLINERESOURCE parameter, 5

operating system authentication, 7.3.3.4

ORA_DBA

Windows operating system group, 7.3.3.4

ORA_sid_DBA

Windows operating system group, 7.3.3.4

Oracle database resource type, 2.2.4

Oracle Database Upgrade Assistant

upgrading single-instance databases, 7.5.3

Oracle Enterprise Manager

authentication problems, 7.10.9

setting User Credentials, 7.10.9

troubleshooting authentication problems, 7.10.9

troubleshooting client connection problems, 7.10.9

use in an active/active configuration, 3.1.2

Oracle Fail Safe

installation of, 1.2.2

Oracle Fail Safe Manager, 1.1

cluster alias and, 2.5

compatibility with prior releases of Oracle Fail Safe Server, 4.6

introduction to, 1.2.2

tree view, 1.2.2

verify tools, 1.2.2

wizards, 1.2.2

Oracle Fail Safe Server

Oracle Fail Safe Manager releases and, 4.6

P

parameter file

See initialization parameter file

parameters

SERVER=DEDICATED in tnsnames.ora file, 7.4.5

USE_SHARED_SOCKETS listener parameter, 7.4.1

password files

synchronizing, 7.5.1

passwords

changes cause group problems, 7.10.4

changing for the DBA account, 7.10.6

problems with REMOTE_LOGIN_PASSWORDFILE parameter, 7.10.6

Pending Timeout value

setting, 7.10.4

troubleshooting, 7.10.4

performance

in an active/active configuration, 3.1.2

permissions

insufficient return error ORA-01031, 7.10.9

PFILE

See initialization parameter file

pinging

verifying network communication between cluster nodes, A.2

planned failover

static load balancing, 2.6.2

planned group failover, 2.6.2

planned maintenance, 2.6.2

policies

dumping failover and failback information, 6.2

polling

failures, 7.10.4, 7.10.6

possible owner nodes list

adjusting, 2.6.7

effect on failover, 2.6.11

effect on resources, 2.6.7

excluding nodes from, 2.6.7

for a generic service, 8.3.2.1

for a group, 2.6.7, 2.6.7

for a resource, 2.6.7

for a single-instance Oracle database, 7.3.3.1

in determining failover node, 2.6.11

modifying, 2.6.7

resources and, 2.6.7

specifying, 2.6.7, 2.6.7

Verify Group command and, 2.6.7, 2.6.7, 2.6.7, 4.8

preferences

setting to avoid access problems, 7.10.9

preferred owner nodes list

effect on failback, 2.7.1, 2.7.1

effect on failover, 2.6.10, 2.6.11

move group operation and, 2.7.1

private disks

generic services and, 8.3.2.4

private interconnect, 1.3, 2.1

privileges

generic services and, 8.4

granting on each cluster node, 7.5.1

required, 4.3

protocol address, 7.4.2

public interconnect, 1.3

PWD qualifier

FSCMD command, 5, 5

Q

quorum disk

dumping information about, 6.2

R

RAID

hardware, 1.3

technology, 2.1.1

redundancy

servers and, 2.1.1

registering

host names and IP addresses, A.1

pinging to validate proper name resolution, A.2

troubleshooting improper name resolution, A.4

registration

dumping information about resource, 6.2

registry editor

registering host names and IP addresses, A.1

registry keys

generic services and, 8.3.2.6, 8.3.2.6

replicating across cluster, 8.3.2.6

REMOTE_LOGIN_PASSWORDFILE initialization parameter, 7.10.6

setting, 7.10.4

when password files are not used, 7.3.3.5

when password files are used, 7.3.3.5

resource types

custom, 2.2.4

generic service, 2.2.4

IP addresses, 2.2.4

MSCS, 2.2.4

Oracle database, 2.2.4

Oracle MTS Service, 2.2.4

physical disks, 2.2.4

resources, 1.1

access to, 2.2.1

accessing through a virtual server, 2.3

client access to, 2.1

defined, 2.2.1

dependencies, 2.2.3, 2.2.3

discovering, 4.4

disks used by the database configuration, 4.2

DLLs, 2.2.4

effect of group Nodes property page changes on, 2.6.7

examples of, 2.2.2

failover policy effect on groups, 2.6.8

failure of, 2.6.1.1

General property page for, 2.6.7

placing online, 5

using FSCMD, 5

possible owner nodes list and, 2.6.7

renaming, 4.5

repairing misconfigured, 7.10.2

restart policy, 2.6.9

returning to a preferred owner node, 2.7

taking offline, 5, 5

using FSCMD, 5

verifying configuration of, 6.1.2, 6.1.2, 6.1.3

rollback

clusterwide operation, 7.10.3

files, 7.10.8.1, 7.10.8.4

rolling upgrade

of application software, 1.2.2

S

sample database

privileges required, 7.10.9

troubleshooting problems with, 7.10.7

scripts

FSCMD commands in an active/active configuration, 3.1.2

FsDbError.bat script, 7.10.1

to handle errors when single-instance database cannot be placed online, 7.10.1

using FSCMD commands in, 5, 5

SCSI shared storage interconnect, 1.3

secondary node

creating the database instance on, 4.2

testing database shutdown, 4.2

security

increasing with multiple virtual addresses, 2.3

Oracle Services for MSCS Security Setup tool, 4.3.1.1

requirements

for generic services, 8.3.2.3, 8.4

for single-instance databases, 7.5

synchronizing password files on nodes, 7.5.1

server nodes

attempting to restart, 2.7.2

cluster polling failure, 7.10.6

losing client connections, 7.10.10

registering addresses of, A.1

trace flags, B.3

server redundancy, 2.1.1

SERVER=DEDICATED parameter, 7.4.5

service name

generic services and, 8.3.2.2

T

temporary tables

failover and, 7.3.1

third-party proxy servers

using shared sockets and, 7.4.1

TNS listeners

updating net service names in, 7.2.4

TNS_ADMIN Windows environment variable, 7.4.2

TNS_ADMIN Windows registry parameter, 7.4.2

tnsnames.ora files, 4.2

archived, 7.10.8.3

checking Oracle Net configuration data, 7.10.4

EXTPROC_CONNECTION_DATA net service name entry, 7.4.4

modifying for highly available single-instance databases, 7.4.2

parsing to discover single-instance databases, 7.1

problems configuring the virtual server, 7.10.8.1

rollback files, 7.10.8.1

SERVER=DEDICATED parameter and, 7.4.5

single-instance Oracle databases and, 7.3.2

updated by Database Configuration Assistant, 7.2.1

updating, 7.4.2

updating with default domain name values, 7.2.1

trace files, B.4

tracing

enabling, B.3

flags, B.3

transactional mode

taking databases offline in, 5

transactions

failover and, 1.2.4

transparent application failover, 7.9

tree view, 1.2.2

populating with clusters, 2.5

troubleshooting

access to the cluster, 7.10.9

configuring the virtual address, 7.10.8.1

databases, 7.10

Dump Cluster operation, 6.2

generic services, 8.5

IP address and host name registration, 6.1.1, A.4

multiple IP addresses, A.4

order of network adapters, 6.1.1, A.4

security access using Oracle Enterprise Manager, 7.10.9

startup problems, 6.4

unable to place a group online, 7.10.4

users unable to connect to single-instance database, 7.4

verification tools, 6.1

with groups, 7.10.4

U

unplanned failover, 2.6.1

upgrading a single-instance database, 7.5.3

USE_SHARED_SOCKETS parameter, 7.4.1

user

changing account information for Oracle Services for MSCS, 4.3.1.1

domain account for Oracle Fail Safe Manager, 4.3.2

user credentials

setting, 7.10.9

USER qualifier

FSCMD command, 5

V

Verify Cluster operation

description, 6.1

purpose, 6.1.1

Verify Group operation

description, 6.1

FSCMD command, 5

logging information about, B.3

overview, 6.1.2

possible owner nodes list and, 2.6.7, 2.6.7, 2.6.7, 4.8

purpose, 6.1.2

updating information in the cluster registry, 7.7

updating resource dependencies, 7.10.2

Verify Standalone Database operation, 6.1.3, 6.1.3

clusterwide operation status window, 6.1.3

description, 6.1

running on newly created databases, 7.2.1

tracing, B.3

verify tools, 1.2.2

VERIFY_DB string, B.3

VERIFYALLGROUPS parameter, 5

VERIFYCLUSTER parameter, 5

VERIFYGROUP parameter, 5

virtual addresses, 1.2.1

adding to a group, 2.3

cluster alias, 2.5

definition, 2.3

for single-instance Oracle databases, 7.3.3.2

generic services and, 8.3.2.5.2

groups and, 7.3.3

identifying, 2.3

internal cluster communications and, 7.4.3.1

multiple, 2.3, 4.7

reasons for multiple in a group, 4.7

registering, A.1

troubleshooting configuration problems, 7.10.8.1

virtual servers, 1.2.1

configuration, 2.3

configuration problems, 7.10.8.1

definition, 2.3

listener failure and, 7.10.8.1

multiple, 4.7

multiple virtual addresses, 2.3

network configuration for, 7.4.2

registering address of, A.1

updates to tnsnames.ora files during configuration of, 7.4.2

W

wide area network, 1.3

Windows

See Microsoft Windows

Windows cluster

See clusters

Windows environment variables

TNS_ADMIN, 7.4.2

Windows operating system groups

ORA_DBA, 7.3.3.4

ORA_sid_DBA, 7.3.3.4

Windows registry editor, A.1

Windows registry keys

See registry keys

Windows registry parameters

TNS_ADMIN, 7.4.2

WINS

registering IP address and host name, A.1

wizards, 1.2.2

input, 4.2

workloads

setting Pending Timeout to accommodate heavy, 7.10.4