ECO NUMBER: VMS721_SYS-V1200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 COVER LETTER 1 KIT NAME: VMS721_SYS-V1200 2 KITS SUPERSEDED BY THIS KIT: VMS721_SYS-V1100 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: o VMS721_PCSI-V0100 o VMS721_UPDATE-V0300 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: o VMS721_FIBRE_SCSI-V0500 o VMS721_LAN-V0300 o VMS721_MOUNT96-V0300 o VMS721_SYSLOA_V0200 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-1 4.2 Files patched or replaced: o [SYSEXE]APB.EXE (new image) o [SYSEXE]DEBUG_APB.EXE (new image) -- COVER LETTER -- Page 2 1 May 2002 o [SYS$LDR]EXCEPTION.EXE (new image) o [SYS$LDR]EXCEPTION_MON.EXE (new image) o [SYS$LDR]EXEC_INIT.EXE (new image) o [SYS$LDR]IO_ROUTINES.EXE (new image) o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) o [SYS$LDR]LOCKING.EXE (new image) o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) o [SYS$LDR]MULTIPATH.EXE (new image) o [SYS$LDR]MULTIPATH_MON.EXE (new image) o [SYSEXE]OPCCRASH.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) o [SYSLIB]SDA$SHARE.EXE (new image) o [SYS$LDR]SECURITY.EXE (new image) o [SYS$LDR]SECURITY_MON.EXE (new image) o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) o [SYS$LDR]SYS$CLUSTER.EXE (new image) o [SYS$LDR]SYS$VCC.EXE (new image) o [SYS$LDR]SYS$VCC_MON.EXE (new image) o [SYS$LDR]SYS$VM.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]EXEC_INIT.STB (new file) o [SYS$LDR]IODEF.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) -- COVER LETTER -- Page 3 1 May 2002 o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]MULTIPATH.STB (new file) o [SYS$LDR]MULTIPATH_MON.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYSEXE]SYS$CONFIG.DAT (new file) o [SYS$LDR]SYS$VCC.STB (new file) o [SYS$LDR]SYS$VCC_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 5 PROBLEMS ADDRESSED IN VMS721_SYS-V1200 KIT o A call to $GETJPI to return information about the calling process could return a SS$_NOPRIV status. This occurs if the call is made while a persona representing a security profile that differs from the natural persona (Persona_ID 1) is active. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - SYS$LDR]PROCESS_MANAGEMENT_MON.STB o Calls to the $SNDOPR system service can result in a SS$_MBFULL return status: status = sys$sndopr(&req_desc, 0); -- COVER LETTER -- Page 4 1 May 2002 This change increases the size of the OPCOM mailbox. With faster systems, OPCOM messages are being generated faster and accumulating in the OPCOM mailbox. While increasing the mailbox size will only put off the problem if the rate of incoming messages is greater than the rate at which OPCOM can process them, this change will solve the problem of sudden, short bursts of messages arriving in the mailbox at roughly the same time. The extra space will allow the messages to sit in the mailbox until OPCOM can catch up with its processing. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB o The system can experience an INVEXCEPTN bugcheck at SCH$QEND_C+001E0 Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: Current Image: Failing PC: FFFFFFFF.800CFB50 SCH$QEND_C+001E0 Failing PS: 10000000.00000804 Module: PROCESS_MANAGEMENT (Link Date/Time: 23-JAN-2001 08:37:04.46) Offset: 00007B50 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o The system can crash with a "REFCNTNEG, PFN reference count is negative" bugcheck at MMG$DELETE_BUFOBJ_C+00B7C, SYS$VM+251CC, in routine DELBUFOBJPAGES. Another REFCNTNEG bugcheck, caused by the same problem, could also occur at MMG$DELETE_BUFOBJ_C+00E24, SYS$VM+25474, in routine DECPT_BUFOBJ. The bugcheck is caused by PFN database corruption. The SDA command: -- COVER LETTER -- Page 5 1 May 2002 FORMAT @^QR15/TYPE=PFN can be used to examine the value in the PFN$W_BO_REFC field. If it is greater than or equal to 8000, 32768 decimal, this is the cause of the bugcheck. Images Affected: - [SYS$LDR]SYS$VM.EXE o The system can crash with a INVSECURESTATE at NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C bugcheck. DOUBLEDEALO crashes are also possible. Crash Dump Summary Information ------------------------------ Bugcheck Type: INVSECURESTATE, Invalid state detected by SECURITY subsystem Current Image: DSA20:[SYS0.SYSCOMMON.][SYSEXE]OAFC$SERVER.EXE;1 Failing PC: FFFFFFFF.8019798C NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C Failing PS: 30000000.00000203 Module: SECURITY_MON (Link Date/Time: 17-OCT-2001 01:01:12.57) Offset: 0000B98C Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.STB o The system can crash with an KRNLSTAKNV, Kernel stack not valid, bugcheck during process or image rundown. size field. Crashdump Summary Information: ------------------------------ Bugcheck Type: KRNLSTAKNV, Kernel stack not valid Current Process: Current Image: Failing PC: FFFFFFFF.800243A8 SMP$BUGCHK_HALT_CPU_C+001F8 Failing PS: 00000000.00001F00 Module: SYS$CPU_ROUTINES_2208 (Link Date/Time: 17-MAR-2001 03:15:26.81) Offset: 000163A8 -- COVER LETTER -- Page 6 1 May 2002 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o Doing I/O on a multipath device, when the current path is a secondary, results in an increase in the UCB$L_OPCNT in the primary as well as the current path UCB. Although the UCB$L_OPCNT in the secondary grows faster than in the primary, the UCB$L_OPCNT in the primary should not be changing (except, at most by once per second for polling.) This is easily observed when doing a DIR/SIZE on the system disk. A number of customers and third-parties rely on these counters to be accurate in their performance and capacity planning tools. Images Affected: - SYS$LDR]IO_ROUTINES.EXE - SYS$LDR]IO_ROUTINES_MON.EXE - SYS$LDR]IO_ROUTINES.STB - SYS$LDR]IO_ROUTINES_MON.STB 6 PROBLEMS ADDRESSED IN VMS721_SYS-V1100 KIT o During a system crash, the console does not display the type of bugcheck. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.STB -- COVER LETTER -- Page 7 1 May 2002 o Sporadic Crashes while running OPCCRASH. This change brings OPCCRASH back to the version that is functionally the same as that originally shipped with OpenVMS V7.2-1 Images Affected: - [SYSEXE]OPCCRASH.EXE o When EV67 multiprocessor systems are mostly idle, it is possible for one of the processors to loop trying to update a local event flag for a process. This could cause performance degradation, memory channel timeouts, and in extreme cases, CPUSPINWAIT bugchecks. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o An application that uses signals, may contain processes that hang with an AST (Asynchronous System Trap) queued to it. It hangs until another AST is delivered to the process. Since ASTs are commonly sent to processes, this hang may not be noticed but it will cause some performance degradation. This change will prevent this hang and result in performance improvement. The amount of improvement is dependent on the application causing the hang. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o The following command string should change the path to the disk: $SET DEVICE/SWITCH/PATH=PGB0: $1$DGA11 $DIR $1$DGA11:[000000] $SHOW DEVICE/MULTI -- COVER LETTER -- Page 8 1 May 2002 Sometimes it does not. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB o A system can hang with many processes in MUTEX wait state Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB o Two new variants of the DE600 have been added to the configuration file. Images Affected: - [SYSEXE]SYS$CONFIG.DAT o The F$PID lexical function in DCL does not work as expected when the user running the procedure does not have sufficient privilege to examine other processes. The result may be that process selection in combination with F$CONTEXT returns the wrong PID. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o MOUNT and Mount Verification sanity checks have been relaxed to correct the following issues: o A MOUNT/NOWRITE command on a disk on one cluster will now work correctly even if the disk is mounted with a /WRITE qualifier on another cluster in the SAN (Storage Area Network). Previously, depending on the order in which the mounts were executed, the mount would fail with the error message: -- COVER LETTER -- Page 9 1 May 2002 DIFVOLMNT - different volume already mounted on this device. o If a disk is mounted with a /WRITE qualifier on one cluster and a /NOWRITE qualifier on another cluster in the SAN, MountVerification will fail with a WrongVolume status error on the system which had the disk mounted /NOWRITE. This change allows MountVerification to complete successfully in this configuration. Note: To receive this complete correction you must also install the VMS721_MOUNT96-V0300 and VMS721_FIBRE_SCSI-V0500 ECO kits. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.STB o This kit contains corrections for the following security system errors: o The following error is encountered when issuing a SHOW PROCESS/RIGHTS command: %SYSTEM-F-IVIDENT, invalid identifier format o The following crash occurs during process rundown, accompanied by a corrupted pool look-aside list, and a rightschain with a reference count of -1. INVSECURESTATE Crash at NSA$FREE_RIGHTS_CHAIN_C+68 Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB -- COVER LETTER -- Page 10 1 May 2002 - [SYS$LDR]SECURITY_MON.STB o System Service SYS$GETJPIW, with the JPI$M_NO_TARGET_INSWAP flag set and at least one CTL and PSB item code, e.g. JPI$_IMAGNAME or JPI$_RIGHTS_SIZE, returns a %SYSTEM-F-BADPARAM error. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o If a packet is requested from non-paged pool that is larger than nonpaged pool's maximum allowed size (NPAGVIR), the request fails but nonpaged pool expands to its maximum size even though the request can not be satisfied. Images Affected: - [SYS$LDR]SYSTEM_PRIMITIVES.EXE - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE - [SYS$LDR]SYSTEM_PRIMITIVES.STB - [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB o In a mixed OpenVMS version clustered environment, a fatal invalid identifier format (%SYSTEM-F-IVIDENT) error can result on versions of OpenVMS that are not OpenVMS COE (Common Operating Environment) compliant. This can occur on non-COE compliant OpenVMS systems when attempting to display the rights identifiers of a process that is granted a valid GID COE identifier. The following commands, lexicals, (and respective system services), cause the %SYSTEM-F-IVIDENT system message to be displayed instead of the text translation of this COE GID IDENTIFIER: 1. F$GETJPI("PID_xxx","PROCESS_RIGHTS") 2. F$GETJPI("PID_xxx","RIGHTSLIST") 3. $ SHOW PROCESS/ALL 4. $ SHOW PROCESS/RIGHTS -- COVER LETTER -- Page 11 1 May 2002 Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.STB o A system can fail to boot with the following error: %INIT_IO_DB-F-LOAD_SH_ERROR, Error Loading shadowing driver SYS$SHDRIVER.EXE, error = 0x00000870 Images Affected: - [SYS$LDR]EXEC_INIT.EXE - [SYS$LDR]EXEC_INIT.STB o The following error message is displayed when the SDA utility is invoked: OpenVMS (TM) Alpha system analyzer %SDA-W-SDALINKMISM, link time of SYS$BASE_IMAGE built into SDA$SHARE (22-MAR-2001 11:42) does not match link time of image in system (26-APR-2001 12:37) SDA> Images Affected: - [SYSLIB]SDA$SHARE.EXE - [SYS$LDR]SYS$BASE_IMAGE.EXE 7 PROBLEMS ADDRESSED IN VMS721_SYS-V1000 KIT o The use of HSM on a Multipath device results in a system crash at HSDRIVER+02AF8. This kit enables the use of Hierarchical Storage Manager (HSM) on Multipath devices. Images Affected: -- COVER LETTER -- Page 12 1 May 2002 - [SYS$LDR]IODEF.STB - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB o A system crashes with a DOUBLEDEALO bugcheck at EXE$DEALLOCATE_C+00108 in $BRKTHRU when trying to deallocate P1 pool that has already been deallocated. See crash dump summary information below: Crash Dump Summary ------------------ Bugcheck Type: DOUBLDEALO, Double deallocation of memory block Current Process: CANDOUGF_1 Current Image: $1$DUA0:[SYS1.SYSCOMMON.][SYSEXE]MAIL.EXE Failing PC: FFFFFFFF.80048A28 EXE$DEALLOCATE_C+00108 Failing PS: 20000000.00000200 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 13-SEP-2000 06:34:17.45) Offset: 00012A28 Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB - [SYS$LDR]SYS$CLUSTER.EXE o If host-based volume shadowing is running when I/O transfers to SCSI disks stop, and the disk is a member of a shadow set, then a SHADDETINCON crash occurs. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB -- COVER LETTER -- Page 13 1 May 2002 o Under a heavy I/O load, where the processes DIOCNT is at zero, certain circumstances exist that allow DIOCNT to go from 0 to a negative value. Once this has occurred, it may be possible for an application to hang a process or system with an un-managable RWAST condition. Or, it may be possible for an application to absorb all of non-paged pool with IRPs. This can cause a system to crash with an INSF_NONPAGED, 'Insufficient non- paged pool' bugcheck in SYS$SHDRIVER. See the crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: INSF_NONPAGED, Insufficient nonpaged pool Current Process: NMD_CQS4 Current Image: $2$DUA100:[MARS.V32.][EXE]CI_CQS.EXE;3 Failing PC: FFFFFFFF.92F8A204 SYS$SHDRIVER+70204 Failing PS: 30000000.00000804 Module: SYS$SHDRIVER (Link Date/Time: 24-JAN-2000 9:28:00.85) Offset: 00070204 Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB o A system can crash during boot with a SHADDETINCON bugcheck at SYS$SHDRIVER+7580C in module SHD_THREADS, routine SHTD$ENQ_LOCK_BLOCK. See crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: SHADDETINCON, SHADOWING detects inconsistent state Current Process: NULL Current Image: Failing PC: FFFFFFFF.8047F80C SYS$SHDRIVER+7580C Failing PS: 04000000.00000804 Module: SYS$SHDRIVER (Link Date/Time: 24-OCT-2000 15:06:45.56) Offset: 0007580C Images Affected: - [SYS$LDR]MULTIPATH.EXE -- COVER LETTER -- Page 14 1 May 2002 - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB - [SYS$LDR]IODEF.STB o Pool corruption, caused by double deallocation of an IRP, can occur when the current path to a $1$GGAn: or $a$GKAn: device is a secondary path and a polling I/O arrives while there is an active IRP on that path. Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB - [SYS$LDR]IODEF.STB o When mounting FibreChannel shadowsets, a system can crash with an INVEXCEPTN, 'Exception while above ASTDEL' bugcheck at MULTIPATH_MON+3B2C, routine MPDEV$MAP_STATUS_SHDSET. See the crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.8038FB2C MPDEV$MAP_STATUS_SHDSET_C+0005C Failing PS: 10000000.00000804 Module: MULTIPATH_MON (Link Date/Time: 9-FEB-2001 23:41:29.09) Offset: 00003B2C Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB o The system can crash with an SSRVEXCEPT bugcheck at LOCKING+019CC on an LDQ_U R11,(R26) instruction while processing a resource domain. See crash dump summary below: -- COVER LETTER -- Page 15 1 May 2002 Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: BATCH_3084 Current Image: DSA509:[SSEXE.DP]SPCUSERMAINT.EXE;44 Failing PC: FFFFFFFF.801619CC LOCKING+019CC Failing PS: 38000000.00000203 Module: LOCKING Link Date/Time: 29-MAR-2000 00:58:34.67 Offset: 000019CC Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB o Processes hang in Record Management Services (RMS) during $GET and no apparent locking conflict can be detected. There are cases where the status does not get updated after granting a byte range lock. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB o With multithreaded processes, systems have been seen to hang. Specifically, an AST critical to the file system causes file system I/O operations to hang for all processes. It would be appropriate to suspect this problem is occurring on a system with otherwise unexplained system or application hangs, if the system has multiple CPUs and any multi-kernel-threaded applications. This includes essentially any Java applications. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o An ACCVIO occurs in MESSAGE_ROUTINES near "ALTNUMTIM." There are several ways in which this problem may occur: -- COVER LETTER -- Page 16 1 May 2002 - A process ACCVIOs near the symbol EXE$ALTNUMTIM. - ORA-482 crashes on Oracle 8.1.6 OPS. - An Oracle process exits with the status code 0C, which is an ACCVIO. Since Oracle processes run as detached processes, this status code would appear in the accounting log. Images Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]MESSAGE_ROUTINES.STB o The GETTIMEOFDAY() CRTL function returns an error in ORACLE Parallel Server Version 8.1.6. This can occur in several ways: - The GETTIMEOFDAY() function returns status code 103DFE0. - The VMS user mode system services returns unexpected status codes, including C signal status code, SS$_BREAK, SS$_IMGDMP or SS$_DEBUG. - An ORA-7211 Oracle 8.1.6 OPS crash could occur. - A severe performance slowdown on Oracle 8.1.6 or 8.1.7 OPS could occur. - Oracle 8.1.6 or 8.1.7 OPS might hang. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o A process exits with an error status, but without a process dump. The image dump flag is set for the process. There are several ways this can be seen: 1. Processes don't dump when they exit while executing an exception handler. The process must have the image dump flag set. 2. Oracle8 OPS background processes do not dump when they hit an error. The processes must have the image dump flag set. -- COVER LETTER -- Page 17 1 May 2002 Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o The kill() sys$sigprc CRTL functions return the error SS$_SUSPENDED when the process is neither suspended nor waiting on a resource. The processes is simply waiting on a mutex or is in the transient RWSCS state. This leads to ORA-482 crashes on Oracle 8.1.6 or 8.1.7 OPS could also occur. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o The user stack can become corrupt through repeated issuances of the DEBUG command. The following sequence of commands illustrates the problem: $LINK/DEBUG FOO (where FOO simply executes an infinite loop) $RUN FOO DBG> go DBG> CTRL/Y $DEBUG DBG> go DBG> CTRL/Y $DEBUG %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in DBGKREGISTERS\DBG$ GET_PD_FROM_FP %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in DBGKREGISTERS\DBG$ GET_PD_FROM_FP DBG> g %DEBUG-I-BADSTACKPATCH1, Corrupt stack detected...attempting patch STQ R27,(SP) %DEBUG-W-NORESUME, unable to resume execution, stack or PC corrupted in %PROCESS_NUMBER 1 DBG> -- COVER LETTER -- Page 18 1 May 2002 The user stack is now corrupt. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o An Oracle Parallel Server can crash with an ORA-482 error. The PC is near a routine's prologue code and the FP has been set. R27 is stored on the stack after the FP is set and the process exits with an unhandled exception. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o A system can crash with An INCONSTATE bugcheck at SYS$VCC+0822C. Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Current Process: NULL Current Image: Failing PC: FFFFFFFF.801E822C SYS$VCC+0822C Failing PS: 08000000.00000804 Module: SYS$VCC (Link Date/Time: 18-MAY-2000 00:48:08.10) Offset: 0000822C This is not one of the conditions that the CVCB_CHKLK macro recognizes as temporary, so it bugchecks rather than retries the lock conversion. The restriction that fails in this case is the CVCB lock, which is already in PR mode. Images Affected: - [SYS$LDR]SYS$VCC.EXE - [SYS$LDR]SYS$VCC.STB -- COVER LETTER -- Page 19 1 May 2002 - [SYS$LDR]SYS$VCC_MON.EXE - [SYS$LDR]SYS$VCC_MON.STB o Added the Adaptec Line of SCSI adapters. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB o The system hangs with the AUDIT_SERVER process in RWMBX when Object_Server tries to write to its own mailbox. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB o Shadow sets with FibreChannel members fail to mount with MULTIPATH, resulting in MOUNTVERIFY error messages and member removals. Images Affected: - [SYS$LDR]MULTIPATH.EXE o In the VMS721_SYS-V0800 ECO kit, the image generation for the DEBUG_APB.EXE image was incorrect. This error prevents the newer DEBUG_APB.EXE contained in subsequent VMS721_SYS kits from installing. Instead, the user will see the following informational message: %PCSI-I-RETAIN, file [SYSEXE]DEBUG_APB.EXE was not replaced -- COVER LETTER -- Page 20 1 May 2002 because file from kit has lower generation number This kit will delete the [SYSEXE]DEBUG_APB.EXE;1 file that has the incorrect generation and replace it with an image with a corrected generation. The functionality of the two images will be the same. The kit also corrects the error in the PCSI database. Note that during the installation of this kit you will see the following informational message: PCSI-I-HDRGEN, generation number from image header of file [SYSEXE]DEBUG_APB.EXE found on disk supersedes value from product database This message is expected and can be ignored. Images Affected: - [SYSEXE]DEBUG_APB.EXE o The following fields have been added for the virtual unit and shadow set members in the output of an SDA SHO DEVICE DSA command: o Site Value o Timeout Value Each member will now display Read Cost, Site, SM Timeout. For example: OLD OUTPUT: ----------- $ analyze/SYS SDA> sho dev dsa64 DSA64 Generic_DK UCB: 817CD500 . . . I/O data structures ------------------- ----- Shadow Descriptor Block (SHAD) 817DA080 ----- Virtual Unit status: 0001 normal Members 3 Act user IRPs 0 VU UCB 817CD500 Devices 3 SCB LBN 010F4627 Master FL 817DA3E4 Fcpy Targets 0 Generation Num 2C34A8FF Restart FL 817DA3EC Mcpy Targets 0 009FCC39 Last Read Index 0 Virtual Unit Id 00000000 -- COVER LETTER -- Page 21 1 May 2002 Master Index 1 12610040 ----- SHAD Device summary for DSA64 ----- Device $1$DGA110 Index 0 Status 000000A0 src,valid UCB 816156C0 VCB 817DABC0 Unit Id. 10E1006E 00000001 Device $1$DGA210 Index 1 Status 000000A0 src,valid UCB 81615BC0 VCB 817DB540 Unit Id. 10E100D2 00000001 Device $64$DKA301 Index 2 Status 000000A0 src,valid UCB 81624540 VCB 8166E880 Unit Id. 1161012D 00000040 NEW OUTPUT ----------- $ analyze/SYS SDA> sho dev dsa64 DSA64 Generic_DK UCB: 81540000 . . . I/O data structures ------------------- --- Shadowing Descriptor Block (SHAD) 816EC440 --- Virtual Unit SCB Status: 0001 normal Total Devices 3 VU_UCB 81540000 Source Members 3 SCB LBN 010F4627 Act Copy Target 0 Generation 009FCC39 Act Merge Target 0 Number 2C34A8FF Last Read Index 1 VU Site Value 00000000 Master Mbr Index 1 VU Timeout Value 3600 Device $1$DGA110 Index 0 Status 000000A0 src,valid Read Cost 0000002A Site 00000000 SM Timeout 120 UCB 8153D440 VCB 8161F880 Device $1$DGA210 ... Master Member Index 1 Status 000000A0 src,valid Read Cost 0000002A Site 00000000 SM Timeout 120 UCB 81543800 VCB 8187CA40 Device $64$DKA301 Index 2 Status 000000A0 src,valid Read Cost 0000002A Site 00000000 SM Timeout 120 UCB 81503700 VCB 8179D800 Images Affected: -- COVER LETTER -- Page 22 1 May 2002 - [SYSLIB]SDA$SHARE.EXE 8 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 9 INSTALLATION INSTRUCTIONS: Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS721_SYS /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt This kit requires a system reboot. Compaq strongly recommends that a reboot is performed immediately after kit installation to avoid system instability If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 9.1 Special Installation Instructions: 9.1.1 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following definitions and commands: -- COVER LETTER -- Page 23 1 May 2002 - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V12.0 - De-assign the logicals assigned For example, a sample command file to install the VMS721_SYS-V1200 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS721_SYS/PROD=DEC/BASE=AXPVMS/VER=V12.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Copyright (c) Compaq Computer Corporation, 2002 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the Compaq logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided as is without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND -- COVER LETTER -- Page 24 1 May 2002 REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.