Hi dear colleagues.
We use DB2 (v. 10.5) to store our data. After we had applied Fix Pack 8 to database (client and JDBC driver had been also updated) we faced the following problems:
INFO 2017-02-09 14:08:50,541 [server.startup : 1] - Starting repository... ERROR 2017-02-09 14:08:50,811 [server.startup : 1] - failed to initialize file system com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-443, SQLSTATE=38553, SQLERRMC=SYSIBM.SQLTABLES;TABLES;SYSIBM:CLI:-514, DRIVER=3.67.27 at com.ibm.db2.jcc.am.gd.a(gd.java:752)
As recommended here (http://www-01.ibm.com/support/docview.wss?uid=swg21369762) for similar cases we executed the following commands in DB2:
db2 connect to <databasename> db2 bind db2schema.bnd blocking all grant public sqlerror continue db2 terminate
But it has not solved the issues.
What could we forget to do?
How could we try to solve the issue or reveal its root?
Our version of SAS is 9.3. Server OS is AIX, client OS is Windows.
Hi!
Sorry for not having replied!
We have solved the problem by execution of the following actions:
1) Execute commands in DB2:
db2 terminate
db2 CONNECT TO dbname user USERID using PASSWORD
db2 BIND path\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 terminate
2) (VERY IMPORTANT!!!) Restart DB instance.
What kind of connection your sas are using ? ODBC or DB2 engine? If you are using LIBNAME xx DB2 ....... you need update the DB2 client software too. after updating it try make a category and connect to DB2 via its client software. once DB2 client software could connect to DB2, SAS should have no problem .
Hi,
the error message you sent is just a snippet from a log, is that correct?
Could you please send the entire log?
Do you have a metadata server environment?
Any errors or warnings in the EG log, or is it that the tables just don't show?
Have there been any permission changes on the OS and DB2 side?
Thanks
Anja
Hi!
Sorry for not having replied!
We have solved the problem by execution of the following actions:
1) Execute commands in DB2:
db2 terminate
db2 CONNECT TO dbname user USERID using PASSWORD
db2 BIND path\db2schema.bnd BLOCKING ALL GRANT PUBLIC SQLERROR CONTINUE
db2 BIND path\@db2ubind.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 BIND path\@db2cli.lst BLOCKING ALL GRANT PUBLIC ACTION ADD
db2 terminate
2) (VERY IMPORTANT!!!) Restart DB instance.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.