Skip Headers

Oracle® Fail Safe Concepts and Administration Guide
Release 3.3.1 for Windows
Part No. A96684-01
Go To Table Of Contents
Contents
Go To Index
Index

Previous Next

C
Contacting Oracle Support Services

This appendix discusses the following topics:

Topic Reference
Reporting a Problem   Section C.1  
Finding Your Version Information   Section C.2  
Tracing Oracle Fail Safe Problems   Section C.3  
Locating Trace and ALERT Files   Section C.4  

C.1 Reporting a Problem

Some messages recommend calling Oracle Corporation to report a problem. When you call your Oracle Support representative, have the following information available:

1 = Program not usable. Critical impact on operations.
2 = Program usable. Operations severely restricted.
3 = Program usable with limited functions. Not critical to overall operations.
4 = Program circumvented by customer. Minimal effect, if any, on operations.

C.2 Finding Your Version Information

You can find the version of software that you are running in the Oracle Fail Safe Manager help menu.

Choose Help -> About Oracle Fail Safe Manager

C.3 Tracing Oracle Fail Safe Problems

Tracing is available to help you track, report, and examine errors that you receive in Oracle Fail Safe by dumping information about the errors to a log file.

You enable tracing on a per-node basis.

Follow these steps to enable tracing and set tracing flags on the cluster server nodes:

  1. Run the Windows registry editor.

  2. Select the following from the Registry tree:

    HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE -> FailSafe -> Tracing

  3. From the Registry Editor menu bar, select Edit, then Add Value to open the Add String dialog box.

  4. In the Value Name field, enter an Oracle Services for MSCS value from Table C-1.

  5. In the Data Type field, enter REG_SZ.

  6. Click OK to open the String Editor dialog box.

  7. In the String field, enter one or more of the Oracle Services for MSCS strings shown in Table C-1. Separate multiple entries with commas.

  8. Repeat steps 3 through 7 to set additional Oracle Services for MSCS trace flags.

  9. Using MSCS Cluster Administrator, shut down Oracle Services for MSCS.

  10. In the Windows control panel, select Services and stop the Oracle Services for MSCS on each cluster node.

  11. Using MSCS Cluster Administrator, restart Oracle Services for MSCS to begin tracing.

Repeat these steps on each cluster node to ensure that tracing is enabled across the cluster.

Table C-1 Trace Flags for Cluster Server Nodes

Value String Description
FSR_TRACE_OUTPUT A path and file name Specifies the path and file name for the file to which you want tracing information about the Oracle Fail Safe resource DLL to be written. For example:
C:\fsr_ tracelog
FSS_TRACE_OUTPUT A path and file name Specifies the path and file name for the file to which you want tracing information about the Oracle Services for MSCS to be written. For example:
C:\fss_tracelog
FSS_TRACE_FLAGS CLUSTER_MGR Logs information about calls made to the cluster management software.
CR_DBRES Logs information when you create database resources during the Add Resource to Group Wizard.
CR_SAMPLE Captures tracing information about the Create Sample Database operation, including a start and stop entry for each step (with a time stamp).
DB_RES Logs information when the Oracle Fail Safe resource DLL accesses a database.
DEL_SAMPLE Logs information about the Delete Sample Database operation, similar to the CR_SAMPLE operation.
GR_VERIFY Logs information about the Verify Group operation.
LOCAL_TRACE Enables local tracing, which specifies that trace output for a given cluster node be written to the FSS_TRACE_OUTPUT file for that node. If this flag is not specified, then trace output for all cluster nodes is written to the FSS_TRACE_OUTPUT file on the node where Oracle Services for MSCS is running (the node where the Cluster Group resides).

You must specify one or more additional FSS_TRACE_FLAG strings to specify the type of information that you want to have traced. If you specify only the LOCAL_TRACE string, then no trace output is produced.

SQLNET Generates detailed internal information related to the Oracle Net configuration done by Oracle Services for MSCS. Information is logged whenever an operation is performed that requires a change to the Oracle Net configuration. This includes creating and deleting a sample database, or adding and removing a database from a group.
VERIFY_DB Logs information about the Verify Standalone Database operation.

C.4 Locating Trace and ALERT Files

Trace and ALERT files can be located on either a cluster disk or a private disk:


Previous Next
Oracle Logo
Copyright © 1996, 2002 Oracle Corporation

All rights reserved
Go To Table Of Contents
Contents
Go To Index
Index