Loading SearchUnify's search
If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search
If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
DID THIS PAGE HELP YOU?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!
IBM DB2 Z/OS connection issue
You may encounter the following connection issue when you use a recently
released IBM Data Server Driver for JDBC and SQLJ and Data
Server:
com.ibm.db2.jcc.am.SqlInvalidAuthorizationSpecException: [jcc][t4][2010][11246][4.33.31] Connection authorization failure occurred. Reason: Local security service non-retryable error. ERRORCODE=-4214, SQLSTATE=28000
To
avoid this issue, you have to enter the following parameter,
"securityMechanism=3;"
, in the
JDBC
parameters
in the
Advanced settings
tab
of any DB2 component, or in tCreateTable.
For more information on this
issue, search for
securityMechanism
in the
IBM
documentation.
IBM DB2 Z/OS timestamp issue
You may encounter the
PM92838
issue when you use timestamp with DB2
components using IBM DB2 Z/OS version 13.
To avoid this issue, you have to:
change the column
DBType
to
TIMESTAMP
, and set manually a proper date
pattern in tDB2SCDELT when you use SCD Type 2
change the column
DBType
to
TIMESTAMP
for tDB2SP when you use timestamp
parameter in the
Schema Column
column
enter the following parameter,
"deferPrepares=false;"
,
in the
JDBC parameters
in the
Advanced
settings
tab for any other DB2 components
For more information on this issue, search for
deferPrepares
in the
IBM
documentation.
Deployment error for Routes with cMap due to Saxon dependencies
The classloading conflicts preventing a Route containing cMap to run have
been fixed. You can now run a Route containing cMap and other components that
require the Saxon open source library without having conflicts.
Issue with the
IS_REPAIRING_NAMESPACES
option in XML
SAX Writer
The
IS_REPAIRING_NAMESPACES
option used in the XML
SAX Writer (javax.xml.stream.XMLStreamWriter) causing issues about XML control and
automatic prefix generation has been removed.
To avoid further issues, all
namespaces are now declared in the Namespace Containers as xmlns declarations
on the root element produced by the XML SAX Writer.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!
