Preventive Service Planning
Abstract
This document provides a list of all APARs fixed in any 8.1.x release level of IBM Storage Protect™ for Database: Data Protection for Microsoft SQL Server 8.1.x.
Content
This document is divided into linked sections. Use the following links to go to the section of the document that you require.
Data Protection for Microsoft SQL Server 8.1.x
This table lists APARs delivered in the Data Protection for Microsoft SQL Server.
IBM Storage Protect™ API 8.1.x
This table lists APARs delivered in the IBM Spectrum Protect™ Application Program Interface (API) that might affect Data Protection for Microsoft SQL Server operations.
IBM Storage Protect™ Backup-Archive Client 8.1.x
This table lists APARs delivered in the IBM Spectrum Protect™ Backup-Archive Client that might affect Data Protection for Microsoft SQL Server operations.
Note: All fixes are cumulative updates to the previous level.
Data Protection for Microsoft SQL Server 8.1.x
APAR | Severity | Fixed level | Description |
---|---|---|---|
IT14378 | 2 | 8.1.0 | THE QUERY OF ALL AVAILABLE BACKUPS TAKEN FROM MS SQL SERVER MAY TAKE SEVERAL HOURS |
IT14714 | 3 | 8.1.0 | VERIFY ONLY RESTORE ERRONEOUSLY REMOVES DATABASE FROM ALWAYS ON AVAILABILITY GROUP |
IT14785 | 3 | 8.1.0 | ALWAYS ON DB MIGHT BE REMOVED FROM AAG IF WRONG CASE SENSITIVITY IS USED IN RESTORE COMMAND |
IT15644 | 3 | 8.1.0 | LOG BACKUP WILL THROW A EXCEPTION WHEN THERE IS NO FULL BACKUP IN ADVANCE |
IT15776 | 3 | 8.1.0 | WITH THE FIX FOR APAR IT10203 INSTALLED THE DATA PROTECTION SQL REPORTS IN THE ERROR LOG |
IT16087 | 2 | 8.1.0 | DATA PROTECTION FOR SQL TRACE DOES NOT CAPTURE ERROR DETAILS IF THERE IS A PROBLEM OBTAINING DATABASE PROPERTY INFORMATION |
IT16600 | 2 | 8.1.0 | DOC: CONCURRENT FLASHCOPY MANAGER BACKUPS OF SAME DATA SOURCE ARE NOT RECOMMENDED TO BE STARTED SIMULTANEOUSLY |
IT16843 | 1 | 8.1.0 | DATA PROTECTION FOR SQL BACKUP REPORTS ANS1304W 'ACTIVE BACKUP VERSION COULD NOT BE FOUND |
IT16894 | 2 | 8.1.0 | LEGACY FULL BACKUP OF SYSTEM DATABASES FAILS DUE TOTHE SQL SERVER DATABASE COMPATIBILITY LEVEL |
IT17137 | 4 | 8.1.2 | DSMFECC-01.PS1 FAILS IF ONLY 1 OR LESS BACKUPS ARE IN IBM SPECTRUM PROTECT STORAGE FOR THE NODE |
IT17467 | 3 | 8.1.2 | DATA PROTECTION FOR SQL TRACE NOT CAPTURING DETAILS ON COMCOCREATE INSTANCE FUNCTION ERROR DURING LEGACY BACKUP OR RESTORE |
IT17592 | 2 | 8.1.2 | DP FOR MICROSOFT SQL SERVER BACKUP FAILS WITH TIMEOUT RESULT:0X80131501' MESSAGES WITH 'USE ALTERNATE LOGIN' OPTION |
IT18773 | 3 | 8.1.2 | DSMAGENT.EXE CRASHES AFTER A DATA PROTECTION FOR SQL OR EXCHANGE BACKUP FOLLOWING A SPECTRUM PROTECT SNAPSHOT FOR WINDOWS BACKUP |
IT19065 | 4 | 8.1.2 | TRACE FILE HAS 'DEVBUILD' IN ITS HEADER. |
IT19168 | 2 | 8.1.2 | IN THE MICROSOFT MANAGEMENT CONSOLE SOME SQL SERVER INSTANCES MAY NOT BE LISTED |
IT19381 | 3 | 8.1.2 | ANE4993E & ACO3005 NOT REPORTED IN ACTIVITY LOG WHEN A LAN-FREE RESTORE FOR SPECTRUM PROTECT FOR DATABASES: DP FOR MS SQL FAILS |
IT19728 | 3 | 8.1.2 | DOC: DOCUMENTATION LACKS SPECIFIC DETAILS FOR COMMUNICATING WITH ALWAYS ON AVAILABILITY GROUPS |
IT20292 | 2 | 8.1.2 | FULL SQL BACKUP MAKES PRECEDING FILE, GROUP, SET, DIFFERENTIAL AND LOG BACKUPS EXPIRE ACCORDING TO VER DELETED AND RET ONLY |
IT18358 | 2 | 8.1.2 | DSMAGENT MAY PRODUCE INCORRECT MESSAGE DURING DATA PROTECTION FOR SQL/EXCHANGE RESTORE WHEN ENCRYPTKEY SAVE IS USED |
IT20987 | 4 | 8.1.4 | OUTPUT OF MMC DASHBOARD AND GET-FCMMMC ACTIVITY CMDLET MAY BE EMPTY DUE TO DAMAGED TDPSQL/EXCH.LOG.XML FILE |
IT21334 | 3 | 8.1.4 | FULL SQL LEGACY BACKUP OF AN MS-SQL INSTANCE WITH MANY DATABASES CAN BE DELAYED BY OVERHEAD PROCESSING |
IT21432 | 3 | 8.1.4 | TSM SCHEDULER WIZARD MACRO CONTAINS INCORRECT START/ENDDATE/TIME |
IT21475 | 3 | 8.1.4 | INCORRECT ERROR MESSAGE "ANS1026E (RC136) THE SESSION IS REJECTED: THERE WAS A COMMUNICATIONS PROTOCOL ERROR" |
IT21471 | 2 | 8.1.4 | DATA PROTECTION FOR SQL "ANS0344E (RC2107) CANNOT SEND DATA WITH A ZERO BYTE SIZEESTIMATE" WITH ALWAYS ON DATABASE LEGACY BACKUP |
IT21853 | 2 | 8.1.4 | AUTHENTICATION WITH AAG CLUSTER NOT WORKING |
IT22005 | 2 | 8.1.4 | NODE CANNOT AUTHENTICATE IN FAILOVER CLUSTER CONFIGURATION |
IT22708 | 2 | 8.1.4 | REMOTE MOUNT OPERATIONS FAIL WITH FMF0601E |
IT20664 | 2 | 8.1.4 | UNABLE TO SET ALWAYSON PREFERENCES IN DATA PROTECTION FOR SQL GUI WHEN SQL SERVER INSTANCE USES NON-DEFAULT PORT |
IT20881 | 2 | 8.1.4 | A FAILED DATA PROTECTION FOR SQL BACKUP MAY SHOW AS SUCCESSFUL WITHIN THE SQL SERVER |
IT22874 | 2 | 8.1.6 | ACO5551I NO MATCHING BACKUPS FAILURE WITH DATA PROTECTION FOR SQL SERVER RESTORE FILES FOR A COPYFULL VSS BACKUP |
IT23594 | 3 | 8.1.6 | EXTRANEOUS ANS0102W WARNING FOR LANGUAGES WHICH ARE NOT SUPPORTED BY DATA PROTECTION FOR MS-SQL |
IT23706 | 3 | 8.1.6 | DOC: DATA PROTECTION FOR SQL DOCUMENTATION DOES NOT REFERENCE THE EDITION LIMITATION OF BACKING UP ALWAYS ON SECONDARY REPLICAS |
IT23927 | 3 | 8.1.6 | DOC: REFERENCE FOR 'TDPSQLC SET LANGUAGE' MISSING IN THEDATA PROTECTION FOR MICROSOFT SQL MANUAL |
IT24505 | 3 | 8.1.6 | DATA PROTECTION FOR MS SQL REDIRECTED RESTORE OF INACTIVEALWAYSON BACKUP FAILS WITH "CANNOT RESTORE WITH RELOCATION" |
IT23311 | 2 | 8.1.6 | MSSQL SERVER MAY SHOW AS SUCCESSFUL BACKUP WHEN TDPSQL BACKUP FAILS DUE TO THE STORAGE IS OFFLINE DURING THE BACKUP TIME |
IT17314 | 2 | 8.1.7 | ACO5170E FAILURE FOR DATA PROTECTION SQL RESTORE EVEN THOUGH THE LOCAL DSMAGENT NODE IS SET |
IT25809 | 3 | 8.1.7 | STATUS MESSAGES ARE CORRUPTED IN NON-ENGLISH LOCALES |
IT25871 | 3 | 8.1.7 | FCM MMC GUI ONLY CAN SHOW ONE SQL INSTANCE FOR THIS REMOTE MACHINE WHICH HAS MULTIPLE SQL INSTANCES |
IT26483 | 2 | 8.1.7 | CONFIGURATION WIZARD IN SPECTRUM PROTECT FOR DATABASE DOES NOT DETECT MS SQL INSTALLED WHEN MULTIPLE SQL INSTANCES |
IT28469 | 3 | 8.1.8 | LOG RESTORE OPERATIONS MAY RECOVER A DATABASE BUT ERRORS MAY OCCUR WHEN USING "STOPAT" |
IT28559 | 3 | 8.1.8 | DOC: DATA PROTECTION FOR SQL USER'S GUIDE DESCRIPTION OF CONSIDERATIONS FOR A PARTIAL RESTORE ARE CONTRADICTORY |
IT28560 | 3 | 8.1.8 | DATA PROTECTION FOR SQL PARTIAL RESTORE TO ALTERNATE LOCATION REPEATS FIRST BATCH UNTIL IT ENDS MISTAKENLY WITH RC=0 |
IT28969 | 3 | 8.1.9 | SQL VSS RESTORE CAN FAILS WHEN USING AUTOSELECT BECAUSE IT ATTEMPTS TO RESTORE THE SAME OBJECT TWICE |
IT29739 | 3 | 8.1.9.1 | DATA PROTECTION FOR SQL BACKUPS REPORT 'ACO6212I INVALID OBJECTS' MESSAGE DESPITE SUCCESSFUL PREVIOUS BACKUPS |
IT30746 | 3 | 8.1.9.1 | MMC GRAPHICAL USER INTERFACE DOES NOT USE FROMSQLSERVER OPTION FROM CONFIGURATION FILE |
IT31265 | 3 | 8.1.9.1 | "ANS1088E FILE SPACE '' DOES NOT EXIST" IS REPORTED DURING MICROSOFT SQL SERVER BACKUPS DESPITE THE FIX FOR APAR IT15776 |
IT31923 | 3 | 8.1.9.1 | OUTPUT OF THE MMC DASHBOARD AND THE CMDLET "GET-FCMMMCACTIVITY" CAN BE DEPLETED BY A DISFIGURED *.XML INPUT FILE. |
IT31860 | 3 | 8.1.9.1 | CORRECTION REQUIREMENT FOR THE UPPER CASE AAG NAMES IN THE FILESPACES FOR DP SQL |
IT32387 | 2 | 8.1.9.1 | ACO5424E MESSAGE IS RETURNED WHEN PERFORMING BACKUP OF MS SQL DATABASE USING DP FOR MS SQL |
IT32645 | 3 | 8.1.9.1 | A DATA PROTECTION FOR MICROSOFT SQL SERVER RESTORE MIGHT BE LOOPING |
IT34880 | 2 | 8.1.9.2 | DATA PROTECTION FOR SQL BACKUPS REPORT 'ACO6212I INVALID OBJECTS' MESSAGE DESPITE SUCCESSFUL PREVIOUS BACKUPS |
IT32644 | 3 | 8.1.9.2 | THE RULE "CONFIGURING RECOVERY AGENT" INDICATES STATUS "SKIPPED" |
IT33750 | 3 | 8.1.9.2 | INCORRECT CLIENT-SIDE DEDUPLICATION INFORMATION SHOWN BY DATA PROTECTION FOR MICROSOFT SQL SERVER WHEN QUERYING LEGACY BACKUPS |
IT33813 | 2 | 8.1.12 | DATA PROTECTION FOR SQL BACKUPS FAIL WITH ACO5403E ERROR DUE TO VDI GETCONFIGURATION TIMEOUT. |
IT34859 | 3 | 8.1.12 | THE IBM SPECTRUM PROTECT FOR DATABASES: DATA PROTECTION FOR SQL SERVER MAY FAIL WITH ANS1315W(RC15) AND ANS4994S MESSAGES |
IT35428 | 3 | 8.1.12 | DATA PROTECTION FOR MICROSOFT SQL SERVER MIGHT ABRUPTLY END DURING LEGACY BACKUP |
IT35849 | 3 | 8.1.13 | BACKUP IS SHOWN SUCCESSFUL IN GUI (WITH 0 SEC) WHEN DATABASE NAME HAS '&' IN IT THOUGH IT IS FAILED FROM CLI |
IT36508 | 4 | 8.1.13 | TDPSQLC INACTIVATE' MIGHT NOT PROCESS ALL ELIGIBLE FILES |
IT37364 | 3 | 8.1.13 | DATA PROTECTION FOR SQL INACTIVATE USING QUERYNODE=BOTH DOES NOT WORK IN AAG ENVIRONMENT |
IT37697 | 3 | 8.1.13 | A LEGACY SQL BACKUP USING VERSION 8.1.12.0 CAN CAUSE VERY HIGH CPU UTILIZATION |
IT38194 | 3 | 8.1.13 | DATA PROTECTION FOR MICROSOFT SQL SERVER INSTALLATION ON WINDOWS MODIFIES ALREADY INSTALLED NEWER VERSION GSKIT FILES |
IT38500 | 4 | 8.1.14 | DATA PROTECTION FOR SQL MIGHT ACCEPT A CONNECTION WITH AN MS-SQL SERVER INSTANCE NAME WHICH WAS NOT REQUESTED |
IT38757 | 2 | 8.1.14 | DATA PROTECTION FOR SQL OPTION VDITIMEOUT NOT WAITING INDEFINITE LY WHEN VALUE IS 0 |
IT37582 | 3 | 8.1.14 | SQL RESTORE FAILS IF LESS STRIPES ARE USED FOR RESTORE THAN FOR BACKUP |
IT40278 | 3 | 8.1.17 | DATA PROTECTION FOR MICROSOFT SQL 8.1.13 DOES NOT DISPLAY TASK MANAGER SCHEDULES IN GUI |
IT38421 | 2 | 8.1.17 | OPERATIONS CENTER REPORTS PROTECTED SIZE OF LARGE SQL DATABASES AS ZERO BYTES ON FRONT END CAPACITY |
IT41243 | 3 | 8.1.17 | MICROSOFT SQL DATABASE LEGACY OR VSS BACKUP IS FAILING WITH RC 4 02 AND RC=1914 WHEN THERE IS A QUOTE IN THE DATABASE NAME |
IT42212 | 3 | 8.1.17 | MICROSOFT SQL SERVER FULL BACKUP OPERATIONS END WITH %ERRORLEVEL % DIFFERENT FROM 0 |
IT38393 | 3 | 8.1.17 | "AUTO SELECT" FEATURE IN DATA PROTECTION FOR MS SQL FAILS TO IDENTIFY THE RELEVANT LOG BACKUPS FROM THE LIST |
IT39134 | 3 | 8.1.17 | RESTORE OF CDC ENABLED DATABASE USING /KEEPCDC SWITCH ADDS CLEANUP AND CAPTURE JOBS WITH DEFAULT SETTING |
IT38360 | 2 | 8.1.17 | USING THE DATA PROTECTION FOR SQL CONFIGURATION WIZARD, STEP 4-C SHOULD INCLUDE INSTRUCTIONS FOR VSS. |
IT43229 | 3 | 8.1.19 | TDPSQLC BACKUP COMMAND CAN FAIL WITH ACO5053E FOR LONG NAMES |
IBM Storage Protect™ API 8.1.x
APAR | Severity | Fixed level | Description |
-None- |
IBM Storage Protect™ Backup-Archive Client 8.1.x
APAR | Severity | Fixed level | Description |
-None- |
Related Information
Was this topic helpful?
Document Information
Modified date:
15 December 2023
UID
swg21990776