Novell LINUX ENTERPRISE 11 - HIGH AVAILABILITY, Руководство пользователя, Страница: 248 / 298

What we use here is the "oradebug" feature and its "ipc" trace utility. It is not optimal
to parse the debugging information, but this might be the only way to find out about
the IPC information. In case the format or wording of the trace report changes,
parsing might fail. There are some precautions you can take to prevent conflicts.
There is also a dumpinstipc option which will make us print the IPC objects which
belong to the instance. Use it to see if we parse the trace file correctly. Three settings
are possible: - none: don't mess with IPC and hope for the best (beware: you'll
probably be out of luck, sooner or later) - instance: try to figure out the IPC stuff
which belongs to the instance and remove only those (default; should be safe) -
orauser: remove all IPC belonging to the user which runs the instance (don't use
this if you run more than one instance as same user or if other apps running as this
user use IPC).
The default setting "instance" should be safe to use, but in that case we cannot
guarantee that the instance will start. In case IPC objects were already left around
because, for instance, of someone mercilessly killing Oracle processes, there is no
way any more to find out which IPC objects should be removed. In that case, human
intervention is necessary, and probably all instances running as same user will have
to be stopped. The third setting, "orauser", guarantees IPC objects removal, but it
does that based only on IPC objects ownership, so you should use that only if every
instance runs as separate user. Please report any problems. Suggestions/fixes wel-
come.
OCF_RESKEY_clear_backupmode
=clear_backupmode
The clear of the backup mode of ORACLE.
OCF_RESKEY_shutdown_method
=shutdown_method
How to stop Oracle is a matter of preference. The default method ("check-
point/abort") is: alter system checkpoint; shutdown abort; This should be the fastest
safe way bring the instance down. If you find "shutdown abort" not to your liking,
set this attribute to "immediate" in which shutdown ensues. If you still think that
there's even better way to shutdown an Oracle instance, please let us know.
238 High Availability Guide