Top
PRIMECLUSTER Wizard for Oracle 4.2 Configuration and Administration Guide
FUJITSU Software

2.2.3 userApplication Creation

Operating userApplication is configured as follows:

Scalable operation with Oracle9i RAC

userApplication

Description

Resources

app1,app2

Controls Oracle instances and listeners.
It is created on each node.

Oracle resource (instance, listener)
Gds resource

app3

Starts up or stops userApplication (app1 and app2) simultaneously on all nodes. (Option)

Controller resource

app4,app5

Used as standby for Gls or takeover network. (Option)
Create them according to operating conditions.

Gls resource, etc

Information

The following setup values are recommended for app1 and app2. The other attributes not described below are optional.

Attributes

Values

Operation method

Standby

AutoStartUp

Optional
If you control userApplication startup and stop on all nodes by using the controlling userApplication, be sure to specify No.

AutoSwitchOver

No

PersistentFault

1

Standby operation

userApplication

Description

Resources

app1

userApplication on all operation nodes

Oracle resource (instance, listener)
Gds resource
Fsystem resource
Gls resource

Information

The following setup values are recommended for userApplication app1. The other attributes not described below are optional.

Attributes

Values

Operation method

Standby

AutoSwitchOver

HostFailure|ResourceFailure|ShutDown

PersistentFault

1

HaltFlag

yes

The flow of userApplication creation is as follows:

1

userApplication with No Oracle Resources
userApplication Operation Check

2.2.4
2.2.5
2.2.6

2

Oracle Database Creation and Setting

2.2.7

3

userApplication with Oracle Resources
userApplication Operation Check

2.2.9
2.2.10
2.2.11
2.2.12

Information

PersistentFault remains the same resource status (Faulted) even after RMS is restarted in the event of a resource failure. Users are supposed to locate the fault and check completion of recovery processing then start userApplication manually. For example, if a failure occurs, users can detect which userApplication failed even after server reboot. Even though AutoStartUp setup is set, userApplication will not be started, and automatic startup will prevent recurrence of the failure.