Search found 8 matches
- Mon Mar 26, 2018 7:27 am
- Forum: General
- Topic: Connect to the db failed because of a licensing problem
- Replies: 4
- Views: 11157
- Wed Mar 14, 2018 3:02 am
- Forum: General
- Topic: Connect to the db failed because of a licensing problem
- Replies: 4
- Views: 11157
- Tue Mar 13, 2018 3:57 am
- Forum: General
- Topic: Connect to the db failed because of a licensing problem
- Replies: 4
- Views: 11157
Connect to the db failed because of a licensing problem
Hey guys! When I open datastage (11.3.1) and I run ETL job, then it fails on the following error: APT_CombinedOperatorController,0: Fatal Error: Fatal: SQLExecDirect: DB2 error info message '[IBM][CLI Driver] SQL1598N An attempt to connect to the database server failed because of a licensing problem...
- Fri Feb 09, 2018 7:15 am
- Forum: General
- Topic: Client requested protocol TLSv1 not enabled or not supported
- Replies: 9
- Views: 12798
- Fri Feb 09, 2018 7:12 am
- Forum: General
- Topic: Client requested protocol TLSv1 not enabled or not supported
- Replies: 9
- Views: 12798
I contacted our support, and they recommended that we should use TLSv1 instead of TLSv1.2, if we would like to use hierarchical stage...fix exist, but not for 11.3.
Here is the url for that fix (11.5 ): https://www-01.ibm.com/support/docview. ... wg1JR57423
Here is the url for that fix (11.5 ): https://www-01.ibm.com/support/docview. ... wg1JR57423
- Tue Nov 14, 2017 7:03 am
- Forum: General
- Topic: Client requested protocol TLSv1 not enabled or not supported
- Replies: 9
- Views: 12798
- Thu Nov 09, 2017 7:57 am
- Forum: General
- Topic: Client requested protocol TLSv1 not enabled or not supported
- Replies: 9
- Views: 12798
- Thu Nov 09, 2017 7:19 am
- Forum: General
- Topic: Client requested protocol TLSv1 not enabled or not supported
- Replies: 9
- Views: 12798
Client requested protocol TLSv1 not enabled or not supported
Hi When I click on "Edit assembly" button in Hierarchical Data stage then I get the following error message on engine tier: --------------------------------------------------------------------------------------------------------------------------------- [10/18/17 13:24:29:428 GMT] 0003a4b2...