[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::rdb_wish

Title:Oracle Rdb Wishes and Suggestions
Notice:Please READ note 1.0 before using WRITE or REPLY
Moderator:NOVA::SMITHI
Created:Fri Apr 07 1989
Last Modified:Mon Jun 02 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:809
Total number of notes:4111

585.0. "Rdb bugcheck and opcom request from a customer" by CSC32::M_ROBSON (What's that watermellon for?) Thu Sep 09 1993 15:41

T.RTitleUserPersonal
Name
DateLines
585.1Would this doKERNEL::JACKSONPeter Jackson - UK CSC TP/IMFri Sep 10 1993 06:4810
585.2voila!CSC32::S_MAUFEthis space for rentFri Sep 10 1993 12:0753
585.3NOVA::SMITHIheading Down Under to the Great South Lands...Sun Sep 19 1993 17:174
585.4checked in for v7 & v8 - better late than neverHOTRDB::LASTOVICAUse a fork Luke!Thu May 15 1997 14:0836
<COMMENT>
    AUTHOR: Norm Lastovica
    RELATED NUMBERS: Various requests (rdb_wish 533, 635, 448, 410)
    FIXED by CTS #: KODA CTS 13999 (BUGCHK.B32)
    PLATFORMS AFFECTED: OpenVMS
    INTERFACE(s) AFFECTED: all
<ENDCOMMENT>

<HEAD2>(Operator Notification of Bugchecks\opcombugchk)

<IVMS2>

<P>
When an Oracle Rdb process writes a bugcheck dump file
the system operator classes CLUSTER and CENTRAL are now 
notifified.  The operator message includes the Oracle
Rdb version number, the user name, process ID and the 
bugcheck dump file name.

<P>
To disable this notification, define the logical name
RDM$BUGCHECK_IGNORE_FLAGS to include "O" in the translation.
This will result in the current behaviour (no operator
notification).  There is, however, no way to alter the 
operator classes that are notified.

<p>
Following is an example operator message:

<CODE_EXAMPLE>(KEEP\WIDE)
%%%%%%%%%%%  OPCOM  15-JAN-1997 04:55:11.78  %%%%%%%%%%%
Message from user SYSTEM on RDBNT
Oracle Rdb Database DUA0:[DB]DB.RDB;1 Event Notification
Process 00000EFA generating bugcheck dump file DUA0:[DB]RDSBUGCHK.DMP;
<ENDCODE_EXAMPLE>