You will no longer receive e-mail notifications from this forum.
Log-In to post
Our last posted beta- Toad for DB2 Beta 184.108.40.206 - expires on July 17 and will be our last posted beta in the 6.3 series...
Somtimes I need to assign a few thousand ID's ( for copying a *** of records from one environment to another). The way to do this is to incremet the sequence of DB2, assuring that no other client will insert into the ID range that I will get.
When I tried getting a NEXTVAL a few thousand times, I recieved an error.
Today this happened again when I ran a statement to update the sequence to the MAX ID that I created by copying records. According to our DB2 expert, the error was coused by the Toad driver.
Selecting "DB Parameters" tab for a LUW database fails with "ERROR  [IBM][DB2/AIX64] SQL0440N No authorized routine named "DB_GET_CFG" of type "FUNCTION" having compatible arguments was found."
Thank you for great work on this new version.
Toad for DB2 Beta 220.127.116.11 (32 bit)
I recently came across the functionality that TOAD will create alter scripts for you via the GUI (Right click on Table --> Alter table --> Change table settings) and an alter script is created.
It corrects pretty good! There is a small issue with it though. My script is 125 lines long right now and one of the statements has the wrong delimiter for an odd reason. I think its just a issues with how the script is created. I have changed my delimiter so # sign, but its using ; sign one line. Here is a screen shot from a code preview.
I think this is a fairly easily fix; most likely an over site.
Thanks for all the hard work with TOAD!
Toad for DB2 Beta 18.104.22.168 (64 bit) - TOAD for Db2 z/OS
I have another suggestion (Or maybe there is a setting I need to turn one). I think this will be an easy one, but correctly its causing a lot of issues for me.
I have a table in DB2 with a column defined as a varchar(120) but when I upload a spreadsheet its reformatting the date field as a time stamp with a bad formatting for db2 time stamp format.
Let me explain in greater detail.
Here is the Table DDL:
CREATE TABLE DateTEST ( ColA varchar(120) )
Here is the spreadsheet:
I am using the import wizard (which I Love and its a great you can create templates and just fire those templates off whenever you want).
Here is screen one of the wizard:
As you can see its keeping the format of Date. Now when we go the next screen its re-formatting the data to this:
Here is the results in the table:
The problem with this format is DB2 can't cast it as a date as I need it in the format of date when I push to final table.
When you run this SQL: Select cast(cola as date) from DateTEST
You get this error: Lookup Error - DB2 Database Error: ERROR  [IBM][DB2] SQL0181N The string representation of a datetime value is out of range.
My suggestion is can you keep it as a date field and not convert the value to a time stamp? Or better yet can you rather format the time stamp as what is stated in the settings?
Such as this:
I know Dates and Time stamps are hard to use in Db2 for z/OS if they are not formatted correctly.
Thanks again for bringing a great product to us.
Toad for DB2 Beta 22.214.171.124 (64 bit)
Getting the below error while connecting to DB2 database.
System Information**********************************************************************Operating System Microsoft Windows 7 Professional 6.1.7600 AMD64
DB21085I Instance "DB2" uses "32" bits and DB2 code release "SQL09075" withlevel identifier "08060107".Informational tokens are "DB2 v9.7.500.4299", "special_27924", "IP23286_27924",
and Fix Pack "5".
*******************************************************************Exception Information**********************************************************************Exception: System.EntryPointNotFoundExceptionMessage : Unable to find an entry point named 'SQLFreeConnAttribsADONET' in DLL 'db2app.dll'.Stack Trace: at IBM.Data.DB2.UnsafeNativeMethods.DB232.SQLFreeConnAttribsADONET(DB2SQLGetConnAttribsADONETParams& pParam) at IBM.Data.DB2.ConnSettingsFromXmlConfig.Dispose(Boolean disposing) at IBM.Data.DB2.ConnSettingsFromXmlConfig.Finalize()
Getting the same error in v6.0, 6.2 and 6.3. I created a new DB2 connection from a cataloged connection; when trying to open in 6.0 and 6.2 it dumps the stack trace:
System.ArgumentOutOfRangeExceptionLength cannot be less than zero.Parameter name: lengthStack Trace: at IBM.Data.DB2.DB2ConnPool.Open(DB2Connection connection, String& szConnectionString, DB2ConnSettings& ppSettings, Object& ppConn) at IBM.Data.DB2.DB2Connection.Open() at Quest.Toad.Db.Connection.OpenConnection(IDbConnection connection) at Quest.Toad.DB2.DB2ToadConnection.OpenConnection(IDbConnection connection) at Quest.Toad.Db.Connection.AllocConnection() at Quest.Toad.Db.Connection.Connect(Boolean notify) at Quest.Toad.Db.Provider.BackgroundConnector.CreateBackgroundConnection()
In 6.3 is appears to swallow the exception, but when I set the connection to connect at startup it displays:
(1) COT2 : Length cannot be less than zero.Parameter name: length
Installation is on Windows Server 2012 R2 virtual machine with .NET 4.6.01055. I have the exact installation and .NET version on a Windows 7 machine that works fine, not sure what's different with this installation. I'm using an AD account with local admin access on both machines. Thanks for any help!
Tried to run an install (ToadForDB2_Beta_126.96.36.1998) on a Windows 7 64bit box, an Error pops up immediately:
"Could not load the DLL Library
The specified module could not be found."
Just wondering if I need to re-install or will 6.3 be released or is there an upcoming beta version.
I try to display the script for a certain z/OS table in TOAD for DB2 (188.8.131.52 (32 bit)) but it will never been shown.There ist just a Line: "-- Generating script in background" showing up and a Task ist running in the backgrout that cannot be canceled.The same happens when I try to extract the DDL.
I tried to do the same in Toad 6.2. There I got a display but with a small error.There is a extra ' in front of the last X'FF': PARTITION 22 ENDING AT (X'FF',X'FF','X'FF') )
CREATE TABLE "#DB26DA1".OHPS_ADRESSE ( PARTNER_NR INTEGER NOT NULL, ADRESS_NR SMALLINT NOT NULL, ERFASSZEIT_TS TIMESTAMP NOT NULL WITH DEFAULT, ART_CD SMALLINT NOT NULL WITH DEFAULT, SPRACH_CD SMALLINT NOT NULL WITH DEFAULT, ZUSTELL_CD SMALLINT NOT NULL WITH DEFAULT, ADRESSZUS CHARACTER(35) FOR SBCS DATA NOT NULL WITH DEFAULT, STRASSE CHARACTER(35) FOR SBCS DATA NOT NULL WITH DEFAULT, HAUSNUMMER CHARACTER(10) FOR SBCS DATA NOT NULL WITH DEFAULT, HNRDAR_CD SMALLINT NOT NULL WITH DEFAULT, POSTFACH CHARACTER(10) FOR SBCS DATA NOT NULL WITH DEFAULT, PLZ CHARACTER(10) FOR SBCS DATA NOT NULL WITH DEFAULT, PLZ_ZUS CHARACTER(2) FOR SBCS DATA NOT NULL WITH DEFAULT, ORT CHARACTER(30) FOR SBCS DATA NOT NULL WITH DEFAULT, KANTON_CD SMALLINT NOT NULL WITH DEFAULT, GEMEINDENR CHARACTER(5) FOR SBCS DATA NOT NULL WITH DEFAULT, PROVINZ CHARACTER(35) FOR SBCS DATA NOT NULL WITH DEFAULT, LAND_CD SMALLINT NOT NULL WITH DEFAULT, KOMBZEIL_CD SMALLINT NOT NULL WITH DEFAULT, ANREDE_CD SMALLINT NOT NULL WITH DEFAULT, TITELDAR_CD SMALLINT NOT NULL WITH DEFAULT, VORNDARST CHARACTER(30) FOR SBCS DATA NOT NULL WITH DEFAULT, NAMEDAR_CD SMALLINT NOT NULL WITH DEFAULT, NZUSDAR_CD SMALLINT NOT NULL WITH DEFAULT, NOTIZ CHARACTER(70) FOR SBCS DATA NOT NULL WITH DEFAULT, GLTAB_DT DATE NOT NULL WITH DEFAULT, GLTBIS_DT DATE NOT NULL WITH DEFAULT, ERFASSER CHARACTER(8) FOR SBCS DATA NOT NULL WITH DEFAULT, SPRACHCODE CHARACTER(1) FOR SBCS DATA NOT NULL WITH DEFAULT, ORT_ZUSATZ CHARACTER(35) FOR SBCS DATA NOT NULL WITH DEFAULT, INTKFZ CHARACTER(3) FOR SBCS DATA NOT NULL WITH DEFAULT, POSTFACH_DEF SMALLINT NOT NULL WITH DEFAULT, HIST_TS TIMESTAMP WITH DEFAULT ) PARTITION BY RANGE ( PARTNER_NR, ADRESS_NR, ERFASSZEIT_TS ) ( PARTITION 1 ENDING AT (10399999), PARTITION 2 ENDING AT (10799999), PARTITION 3 ENDING AT (11199999), PARTITION 4 ENDING AT (11599999), PARTITION 5 ENDING AT (11999999), PARTITION 6 ENDING AT (12399999), PARTITION 7 ENDING AT (12799999), PARTITION 8 ENDING AT (13199999), PARTITION 9 ENDING AT (13599999), PARTITION 10 ENDING AT (13999999), PARTITION 11 ENDING AT (14399999), PARTITION 12 ENDING AT (14799999), PARTITION 13 ENDING AT (14999999), PARTITION 14 ENDING AT (15199999), PARTITION 15 ENDING AT (15399999), PARTITION 16 ENDING AT (15599999), PARTITION 17 ENDING AT (15799999), PARTITION 18 ENDING AT (15999999), PARTITION 19 ENDING AT (16199999), PARTITION 20 ENDING AT (16399999), PARTITION 21 ENDING AT (16599999), PARTITION 22 ENDING AT (X'FF',X'FF','X'FF') ) IN DPSH002.SPSH019 AUDIT NONE DATA CAPTURE NONE NOT VOLATILE APPEND NO;
I just installed the latest beta version of TOAD. So far its pretty sweet! I am digging the widgets.
I was wondering if there was a future plan to allow you to re-size widgets? I created one with some SQL but it's outputting 8 columns and the widget only shows the first 4.
Toad for DB2 Beta 184.108.40.2068 (64 bit)
Thanks so much!
We have just posted our Toad DB2 v220.127.116.11 beta drop. This drop contains our latest fixes for the product.
Please download the latest beta from:
Please post any beta feedback on the forum at:
If you have issues installing with the exe - try these msi installers:
Use the installer with the same bit-ness as your DB2 client....
I have a suggestion for TOAD and I think its pretty easy to make happen or I hope.
Whenever I create stored procedures I always start my parameters with am '@' sign. When you right click and execute a proc within TOAD it will be default put an '@' in front of parameters.
My issue is I already have that '@' sign so now I have two of them.
Here is an example:
Is there any way we can have a check box to enable auto putting an '@' sign in variables or have the software look for them before doing the call?
It just sucks my proc always fail when I use the gui to execute the proc. Here is a sample DDL:
CREATE PROCEDURE sysproc.ParmExample(in @Parm1 varchar(500)) VERSION V1 LANGUAGE SQL PARAMETER CCSID EBCDIC DYNAMIC RESULT SETS 1 CALLED ON NULL INPUT P1: BEGIN DECLARE RESULT_CSR CURSOR WITH RETURN FOR Select @Parm1 as Parm1 from SYSIBM.SYSDUMMY1 SY; --display result open RESULT_CSR; END P1#
GRANT EXECUTE ON PROCEDURE sysproc.ParmExample TO PUBLIC#
I just one more suggestion. This is not causing an error, but it shows a red line for syntax error.
I have changed my statement delimiter to a '#' sign, but when you right click and execute a proc it is using a ';' sign. Is there anyway to make TOAD so it will use the delimiter you set in the settings of the application?
here is a screen shot:
Thanks for much for your hard work on this product! I love all the new features and glad to see active dev on the application.
I am using Toad for DB2 Beta 18.104.22.168 (64 bit) for z/OS.
We have just posted our Toad DB2 v22.214.171.124 beta drop.
(We had to renumber our beta builds so this build number is less than the previous drop's but do not worry - it is the latest).
We have a automation script that writes to an excel file. In 6.2 the Header fields are the proper width. When I run the same script in 6.3, the column width in Excel are narrower and the headers are not displayed.
We did not change the Office installation. I'm wondering why this is so, and if you can fix this please.
I'm keeping 6.2 ( and running my automation scripts there) for this reason.
I think I already suggested that it would be a great help if I could run a query on several schemas / environments and be able to save or review the results.
Another help would be if there would be a search feature in the result window. When I run a update I add a select statement to verify that the update has the result that I expected. I have to scroll through the results to see how many rows the select returned. It would be easier use find and search for "rows found".
Another thing I noticed is that only if the select is the last statement in the script is the resulting "rows found" written to the results window. It would be more effective if I could add a select before and after the update statement and see the amount of rows found before and after the update.
We posted an updated Toad DB2 beta - v126.96.36.1998.
Please visit the beta page to download the latest beta drop at:
To view the changes in our latest beta drop, please review the latest beta release notes at:
When comparing the data between two schemas and a row containing a CLOB exists in the source, choosing "make target like source" results in two statements. The first one is an Insert statement with part of the of CLOB and a second statement updating the CLOB using || ( adding the rest of the text to the existing content of the CLOB). This is very handy where the CLOB is bigger than 32K, When the content is less than 32K the same could be attained by a single Insert.
The reason this bothers me is that if the record exists already, the result is that the reulting CLOB is updated and un-usable.
A practical solution is to to create either only an Insert or an an Insert with two updates, verifyng that the resulting cell contains exactly what the source cell contains even if the record exists.
You may wonder how could the record exist if the compare decided on an Insert? The answer is that I have an automation script running the resulting statement on many schemas ( including the source).
For all objects (tables, views, tabelspaces, Indexes, etc.) the DATABASE Information in the "Dependencies"-Tab ist not shown, on any Level.