Question & Answer
Question
Are there any fixes that I have installed for Information Server, Version 8.1 GA which are not included in Fix Pack 1 for Information Server, Version 8.1?
Answer
After the process of creating the fix pack has begun, additional fixes can no longer be introduced. IBM development has compiled this list of fixed APARS which have not been included in Fix Pack 1 for Information Server, Version 8.1.
Check your Version.xml file to see if any of your installed patches are on this list prior to installing Fix Pack 1. If you have a patch on this list, please do not install Fix Pack 1. Contact IBM Technical support to obtain a new patch which can be installed on top of Fix Pack 1 so that you do not experience loss of functionality as a result of applying the fix pack.
There is also a Fix List document available which contains a table of the fixed APARS included in Fix Pack 1. The link to the Fix List document is available in the "Related Information" section below.
Fixed APARs that are not included in Fix Pack 1 | |
Issue | Component |
| Connectivity IBM: DB2 CONNECTOR USING BULK LOAD FAILING USING DECIMAL TYPE DATAFIELD WITHOUT SCALE | |
| Connectivity IBM: DB2 CONNECTOR STAGE HAS PROBLEM WITH PARSERING UNDERSCORE. ITTREATS "_" AS A DELIMITER. | |
| Connectivity Infrastructure: PXBridge incorrectly enforces node map and node pool constraints | |
JR34519 | Connectivity Microsoft: Misleading runtime error messages were reported in OLEDB stage. |
| Connectivity Netezza: JOB, DATASET ---> TRANSFORMER ---> NETEZZA EE, ABORTS WITH ERRORS. | |
| Connectivity ODBC: ODBC EE WRITE WITH MODE UPSERT(INSERT ONLY) TRUNCATING AND/ORREPEATING THE DATA | |
| Connectivity ODBC: A WRONG 'CREATE TABLE"" SQL STATEMENT IS GENERATED WITH [CREATE]IN ODBC CC STAGE | |
| Connectivity ODBC: WARNING MESSAGE GENERATED BY LOOKUP STAGE: CONVERTING A NULLABLESOURCE TO A NON-NULLABLE RESULT. | |
| Connectivity ODBC: ODBC CONNECTOR LOGS SOME OF THE FATAL ERRORS AS WARNINGS AND DONOT ABORT THE JOB | |
| Connectivity Oracle: ABNORMAL TERMINATION OF DS SERVER JOB WITH ORAOCI9 STAGE WHEN READING CLOB | |
| Connectivity Oracle: ORA-01406 ERROR IN READING LITERAL BY ORACLE ENTERPRISE STAGE | |
| Connectivity Oracle: APPLIED PATCH JR34496 THE PERFORMANCE IS DEGRADING. | |
| Connectivity Oracle: IMPORTING TABLE VIA PLUG-IN ORAOCI9 DOES NOT POPULATE THELOCATOR INFORMATION CORRECTLY FROM ORACLE 11G. | |
| Connectivity Oracle: COPYRIGHT CHARACTER [0XA9] IS CAUSING ISSUE WHEN USING UTF8 IN ORAOCI | |
| Connectivity Oracle: GARBLED CHARACTER BY BULKLOAD ON ORACLE CONNECTOR | |
| Connectivity Oracle: ORACLE COLUMN NAME CONTAINING $ NOT IMPORTING CORRECTLY. | |
| Connectivity Sybase: REQUEST SUPPORT FOR -B FOR BATCH SIZE IN BCP FOR SYABSEENTERPRISE STAGE. | |
| Connectivity Sybase: PERFORMANCE ISSUE WHEN GENERATING SQL AND DATA FILE IN THEIQBULK12 PLUGIN (MANUAL LOAD METHOD). | |
| Connectivity Teradata: Users can not provide ""terasync"" password as encrypted string | |
| DataStage Client: INVALID CREDENTIAL ERROR IMPORTING MODEL INTO BG ON DISTRIBUTEDINFORMATION SERVER 8.1 SYSTEM | |
| DataStage Client: Unable to delete imported job in newly created project. | |
| DataStage Core: CALLING A THE ROUTINE KEYMGMTGETNEXTVAL MORE THAN ONCE IN THESAME PROCESS RESULTS IN BOTH SEQUENCES SHARING THE SAME NEXTV | |
DataStage Core: PX ENTERPRISE FTP STAGE FAILS WHEN WILDCARD CHARACTERS ARE USED:' FTP://T1000L3/'DSNAT1.NAT* ' FAILS WITH MAIN_PROGRAM: FATAL | |
| DataStage Core: CHANGE THE SDKSEQUENCES FILE CREATION TO TYPE 30 FILES. | |
| DataStage Core: CANNOT CREATE NEW PROJECTS WITH NON-DEFAULT SHORT DATE FORMAT | |
JR34844 | DataStage Core: CUSTOMER NEEDS SEPARATE ADMINS FOR DIFFERENT PROJECTS |
| DataStage Core: DSXIMPORTSERVICE.SH SCRIPT INSERTING UNIX TERMINATORS | |
| DataStage Core: EXCEPTION OCCURS ON DESIGNER WITH A PARTICULAR OPERATION. | |
| DataStage Core: REPEATABLY OPENING AND CLOSING STAGE EDITORS WILL EVENTUALLYCAUSE THE DESIGNER TO CRASH IN VARIOUS DIFFERENT WAYS. | |
| DataStage Parallel Framework: IIS-DSEE-TFUU-00009 ENCODING CONVERSION ERR WHEN TRYING TOREAD DATA FROM A TABLE WHICH NAME IS JAPANESE DOUBLE BYTE | |
JR34286 | DataStage Tools: WOULD LIKE TO DISABLE THE ""SAVE PASSWORD"" OPTION IN THE LOGINWINDOW OF THE IS MANAGER CLIENT APPLICATION. |
| DataStage Tools: ISTOOL BUILD PACKAGE FAILURE IF TWO DATASTAGE SERVERS ARERUNNING WITH SAME INSTANCE/NAME | |
| FAST TRACK: FAST TRACK JAVA.LANG.NULLPOINTER EXCEPTION GENERATING JOB | |
| FAST TRACK: WHEN EXPORTING A MAPPING DEFINITION FROM THE FASTTRACK CLIENT TOCSV, THE ANNOTATIONS OF THE LOOKUP DEFS DO NOT GET EXPORTED. | |
| FAST TRACK: DELETION AND RE-IMPORTATION OF TABLE METADATA INVALIDATESFASTTRACK MAPPINGS | |
| FAST TRACK: FAST TRACK DON'T SEE THE PROJECT IF DATASTAGE PORT IS NOT DEFAUL | |
| ISD: Error when using Text over JMS with JMS Listener Port | |
| ISD: Ignore Errors flag is not respected in Text Over JMS | |
| ISD: Ignore Errors flag is not respected in Text Over JMS | |
| QualityStage: COPY OF RULES THEN RENAME STILL LINKS TO COPY OF NAME | |
| QualityStage: RUNNING STANDARDIZATION AND CASS IN SAME JOB FAILS INENVIRONMENT FOR CASS CYCLE M | |
| QualityStage: ISSUES USING MD ERROR RETURNED FROM WEIGHT LIBRARY: INPUT COLUMNXXX COULD NOT BE FOUND IN THE DATA DICTIONARY | |
| XMETA: CERTAIN IA UI OPERATIONS, FOR EXAMPLE, OPENING A DATA RULE, TAKES A LONG TIME TO COMPLETE WHEN THE COMMON REPOSITORY | |
| XMETA: REQUIRE ABILITY TO EXPORT/IMPORT ""SHAREDNESS"" OF METADATA | |
Related Information
[{"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.1.0.1;8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
23 June 2018
UID
swg21414409