Hey Gerd, I did end up working with the one that actually installs DB2 software on our mainframe system, David. Turns out they had tried to get around this issue over 4 years ago with no success. At the time, I don't think they was able to get any support from Squirrel support although I don't know how they tried to reach out. So thank you again for responding to me when I started this ticket. David actually compared our working DB2 installations (DB2 & WDB2) to the not working version TDB2. He couldn't...
Hey Gerd, I did end up working with the one that actually installs DB2 software on our mainframe system, David. Turns out they had tried to get around this issue over 4 years ago with no success. At the time, I don't think they was able to get any support from Squirrel support although I don't know how they tried to reach out. So thank you again for responding to me when I started this ticket. David actually compared our working DB2 installations (DB2 & WDB2) to the not working version TDB2. He couldn't...
Hey Gerd, I did end up working with the one that actually installs DB2 software on our mainframe system, David. Turns out they had tried to get around this issue over 4 years ago with no success. At the time, I don't think they was able to get any support from Squirrel support although I don't know how they tried to reach out. So thank you again for responding to me when I started this ticket. David actually compared our working DB2 installations (DB2 & WDB2) to the not working version TDB2. He couldn't...
Hey Gerd, I did end up working with the one that actually installs DB2 software on our mainframe system, David. Turns out they had tried to get around this issue over 4 years ago with no success. At the time, I don't think they was able to get any support from Squirrel support although I don't know how they tried to reach out. So thank you again for responding to me when I started this ticket. David actually compared our working DB2 installations (DB2 & WDB2) to the not working version TDB2. He couldn't...
Thanks Gerd! I did load the latest snapshot and confirmed that it is working as the prior iterations have been. Also, I reached out to our DBA sharing the test java app and asked if he can explain why the test database has the issue but other DB2 dbs do not, just like Squirrel exhibited. If the DBAs come back with a response, I will let you know. But, thank you for finding a workaround that populates the object tree regardless of this config issue/bug. Assuming we never get the test database modified...
Hey again Gerd, I got someone to run the java pointed to the database with the issues we have been working on and they said that no results were returned. Just to be sure they were doing it right, they did point it against one of our DB2 databases that does work, that we can "DB2" and they got the following results: tableTypeName = ALIAS tableTypeName = AUXILIARY TABLE tableTypeName = GLOBAL TEMPORARY TABLE tableTypeName = MATERIALIZED QUERY TABLE tableTypeName = SYNONYM tableTypeName = SYSTEM TABLE...
Hey Gerd, I just recalled I never actually came back and did your last test you requested as I thought I had, so sorry about that! So, per your last request 1) I uploaded the newest copy of the app you gave me and it worked just like it did before. I can provide a log file again if you want it. 2) I clicked on several tables and on the "Info" tab, under property name "Type", the "Value" is "TABLE" for every one that I clicked. 3) I'm not a java developer and I just asked some folks this afternoon...
Hey Gerd! I have good news! I have clicked the object trees on every test, but this time, as you anticipated, I DO see the tables AND if I click on a table, I see the column details and other details on the tabs on the right! I didn't notice any unexpected behavior with my small amount of testing. But, this is great progress! What do you think the next step should be? Do you have more changes for me to test? Eventually, I will want to recommend a stable version with the fix to this issue to our IT...
Gerd - sorry for the delay, I've been out of office and just getting back to catch up on our testing. Thanks for replying with a new version to use in a test. I believe I have limited the loading only to a handful of schemas. For those schemas, the do have tables that should be displayed. The schemas I specified to load, as mentioned previously are: PEGA,PEGAQA,PEGAT,REF,SBRGWC,SBRGWCQA,SBRGWCT & SBRGWCX All of these schemas have tables that should be display. Thx.
Ok, Gerd, I've completed the assignment. I modified the alias through the properties button. I chose "Load schemas filtered by name" & entered "PEGA%,SBRGWC%,REF", which should have limited the loaded schemas to 8 schemas: PEGA,PEGAQA,PEGAT,REF,SBRGWC,SBRGWCQA,SBRGWCT,SBRGWCX. That is all that shows in the in the list of schemas in the objects frame, but I noticed the #1534 shows a whole lot more schema names listed in the log file. I just wanted you to know I did update the properties as you requested....
Gerd, Thank you again for replying so quickly. I pulled the new version you uploaded and ran another test. You are correct, this time there is a BUNCH of #1534 records in the log file this time and from it, you can see it can read the schema names, but it doesn't go down into the tables and other objects in each schema. I've attached the log file as you requested. Please let me know when I can run another test if you need me to do so and thank you so much for your help to figure out this issue! ...
here's the other log file, I had trouble uploading in 1 post
Gerd, Thanks for your quick reply! I’ve installed that snapshot on my pc and I am running a Java 17 instance on that machine. I’m attaching the 2 log files that I could get to write out, jdbc-debug.log and squirrel-sql.log. Unfortunately, I’m not seeing any 1534 entries in the log files. But, I hope what I provide helps AND if you want me to run another snapshot to capture more of the issue, please let me know. Thanks! Paul Stephenson
DB2/Object Tree Issue