Loading...
Loading...
Summary:SQL/MP or SQL/MX applications accessing SQL/MP Protection Views (PVIEWs) may fail under certain conditions with SQL error 8300 / 8200 / 8551 and File System error 541, if DP2 version is T9053L04 which is part of L25.09 RVU.If an application uses SQL/MP PVIEW and it encounters this error, thenit may cause an outage for the application as the PVIEW becomes inaccessible.DETAILED DESCRIPTION:SQL/MP or SQL/MX applications accessing a SQL/MP Protection View (PVIEW) may fail with SQL error 8300 or 8200 or 8551 and File System error 541 under the following conditions: |1. The DP2 version of the volume on which the PVIEW resides isT9053L04 (released with L25.09 RVU).CRVSN of the PVIEW has a prefix greater than 000050 (octal).If the SQL/MP application and the PVIEW reside on the same system, SQL error 8300 may be returned. If the SQL/MP application and the PVIEW are on different systems, SQL error 8200 may be returned.Applications that use SQL/MP internally, that do not require an explicit SQL license, may also be affected by this issue.SQL/MX applications running on systems with RVUs older than L25.09, when accessing SQL/MP PVIEWs on systems running RVU L25.09, may return SQL error 8551.CRVSN is an attribute in the File Label. It represents the VSN (VolumeSequence Number) of the volume on which the file was created, recorded at the time of creation. You can display the PVIEW file's CRVSN using the following command in the DIRCHECK utility:label name <PVIEW-FILE-NAME>, format detailExample:> $SYSTEM.ZUTIL.DIRCHECKDircheck - T9208L01^ACM - (22JUL2025)System: \VMWARE4 PID: (3,905) 12-Feb-2026 14:07:111>> label name $SAS7.ABC.TABV, format detailDisplaying (volume directory)...$SAS7.ABCName = ABC TABV RCode = 3 (PView Label)Section Length = 180CRVSN = 000051 000006 000607 VSN = 000051 000006 000671FLAB Create Time = 067674 156746 004600......In this example, CRVSN prefix of the PVIEW $SAS7.ABC is 000051 (octal)which is greater than 000050 (octal). Therefore, this PVIEW mayencounter the problem.You should verify all volumes where PVIEWs may be created in the future to ensure that their VSN values are not already high enough to trigger this issue.If the VSN prefix of a volume is greater than 000050(octal), any PVIEWcreated on that volume may exhibit this problem.Use the CHECKVSN command in the TANDUMP utility to check the VSNprefix of all volumes.Example:> TANDUMPTANDUMP - T9208L01 - (20NOV2024) System \SNIFTER< CHECKVSNCHECKVSN report for 2026/02/13 12:18:45Volume coldload VSN for SAS7 : %000051.%036366 = 3,620,086Volume coldload VSN for OSS : %000002.%027271 = 143,033......In this example, the VSN prefix of volume $SAS7 exceeds 000050 (octal). Therefore, any PVIEW created on this volume may encounter this issue.If the VSN prefix of a volume is 000046 (octal) or higher, you shouldplan to install the fix SPR soon. If the VSN prefix is below 000046 (octal), monitor the rate at which the volume's VSN increases using the CHECKVSN command and schedule the SPR installation accordingly.Example:It takes approximately 4.29 billion internal DP2 operations for the VSN prefix to increase by 1. Therefore, if a volume experiences 100 million internal DP2 operations per day, the VSN prefix will take roughly 42 days to increase by one.The TACL macro PVMAC distributed with this document can be used to list the volumes and PVIEWs at risk on a system. The macro scans all volumes and identifies those with very high VSN prefix. For each identified volume, it further checks for PVIEWs that may exhibit the issue. It also lists volumes that need to be monitored for rate of VSN increase.A sample output of the macro is shown below.> run pvmacScanning volumes and PVIEWs for issue related to HS03575...Only volumes in the STARTED state will be scanned.System is running with DP2 version: T9053L04^L04Volumes at risk with high VSN prefix:VolumeVSN$SYS1000051.000010$SYS000052.000042$SAS7000051.000117Scanning $SYS1 for PVIEWs. This may take a while...PVIEWs on volume $SYS1:2 PVIEW files on volume : $SYS1 At risk:PVIEW files at risk on $SYS1:PVIEW CRVSN VDP-LOGICAL-NAME-------------------------------------------------------------------$SYS1. SQL.PT 000051.000002.000420NOTE: Other existing PVIEWs on $SYS1 do not have the issuedescribed in the OPN HS03575.Scanning $SYS for PVIEWs. This may take a while...PVIEWs on volume $SYS:10 PVIEW files on volume : $SYS At risk: 10PVIEW files at risk on $SYS:PVIEWCRVSNVDP-LOGICAL-NAME$SYS.DAT.ETABV000052.000024.000375$SYS.DAT.PT000052.000034.052172$SYS.DAT.RTABV000052.000024.000531$SYS.DAT.TAB2V000052.000030.000701$SYS.DAT.TABV000052.000026.012000$SYS.DAT.TABV1000052.000030.007211$SYS.DAT1.TABV000052.000016.000766$SYS.DAT2.TABV000052.000030.014750$SYS.ZYS00000.A000001J000052.000040.025476$MS001.DBS.PV1$SYS.ZYS00000.A0000029000052.000040.032046$MS001.MPKSQL.PV1Scanning $SAS7 for PVIEWs. This may take a while...No PVIEW file found on $SAS7Volumes to be monitored for VSN increase:Volume VSN-------------------------$NEW1 000047.077235NOTE: Please monitor the increase in the VSN prefix of these volumes using the CHECKVSN command in the TANDUMP utility, as described in OPN HS03575. Oncethe VSN prefix reaches 000051, any new PVIEW created on that volume may exhibit the issue.Likelihood:Very Likely under the stated conditions
Affected version(s):T9053L04Release Version Updates (RVUs) containing the defective versions:L25.09 - L25.09.02
RVUs containing final fix:Next L-series RVUPREVENTIVE ACTION:Workaround:NoneFix:Install the following SPR:T9053L04^BDR ( DP2 ) - already availableInstallation impact:SYSGEN and system load required.You can check with the GNSC for applicability of the above SPR(s) to RVURs that have been released since publication of this OPN.Please refer to the T9053L04^BDR softdoc for detailed SPR information, including installation instructions, superseded SPRs, and requisite SPR lists.Note: In some cases, requisite SPRs might have greater installation impact than the SPR(s) described in this OPN.Appendix AThe sample TACL macro PVMAC is available at the following URL:https://support.hpe.com/hpesc/public/docDisplay?docId=dp00007556en_usRevision HistoryDocument VersionRelease DateDetails2March 24, 2026Additional information on defect description and conditionsAdded a TACL Macro to list the volumes at risk1February 20, 2026Initial Version
Operating Systems Affected:Nonstop OS L25.09
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.