From: Serge Rielau on 21 Dec 2007 22:50 2803stan(a)gmail.com wrote: > <<I presume you are not aware of DB2 procedure resolution rules. >> > > Thanks for the reminder -- I haven't had to think of this for some > time. But, with all the advertising of "autonomous" functioning, and > all the automatic resizing of tablespaces, etc, etc, wouldn't you > think that db2's dbm, having placed the stored procedure (or the UDF > or whatever) where it wants it (I have no r�le in that placement), > that db2 could keep track of where it is? It could make its own entry > in a .ini file, or somewhere else more private, like a table. This > path stuff is one of the last things that one wants to keep track of. > > I ended the last sentence with a preposition. I must be upset. So > I'll sign off before I do something worse, like USE ALL CAPS. Don't.. there is a chance you would look back at this thread in the future and regret... This has absolutely nothing to do with self managing databases. May I remind you that PATH is not a DB2 special. It's in PostgreSQL, SQL Server, oh.. and Unix, Windows, Linux, .... All complaining will not help. You'll have to deal with it. Cheers Serge -- Serge Rielau DB2 Solutions Development IBM Toronto Lab
From: 2803stan on 23 Dec 2007 15:40 <<Don't..>> Have no fear, the line before and the line after my "SS" were meant to be mild humo(u)r. I'm not good at emoticons! <<May I remind you . . . oh.. and Unix, Windows, Linux, .... >> Sure, but the last time either of us had to deal, hands on, with PATH was in OS/2 (RIP). For example, Windows has tens of thousands of references to little pieces of programs in storage. But the paths are all in the registry, and the user never gets his/her hands dirty unless, rarely, when working with what's left of DOS. Anyway, the matter at hand . . . After changing things in the db2cli.ini file, I now have the stored procs back, but the UDFs can't be found. And just before writing this, I got my first ever (I've been using db2 since version 2) SQLSTATE 56098 on an SP that has been in use without a glitch for at least a year. I'm the owner and am signed on as such. In order to keep business going, I'm going to reinstall Version 8.x and wait this out. (I did check the memory and HDD of my machines, and no errors are found after full-day runs.) SS
From: Serge Rielau on 23 Dec 2007 19:52 2803stan(a)gmail.com wrote: > Anyway, the matter at hand . . . After changing things in the > db2cli.ini file, I now have the stored procs back, but the UDFs can't > be found. And just before writing this, I got my first ever (I've > been using db2 since version 2) SQLSTATE 56098 on an SP that has been > in use without a glitch for at least a year. I'm the owner and am > signed on as such. SQLSTATE 56098: An error occurred during implicit rebind or prepare. There are multiple SQLCODEs that can get you there. What was the complete message? (May be echo-ed in the db2diag.log). > In order to keep business going, I'm going to reinstall Version 8.x > and wait this out. (I did check the memory and HDD of my machines, > and no errors are found after full-day runs.) I doubt this is install related, and it sure isn't HDD related. Cheers Serge PS: I do not consider the windows registry a marvel of innovation. -- Serge Rielau DB2 Solutions Development IBM Toronto Lab
From: 2803stan on 24 Dec 2007 20:31 On Dec 23, 7:52 pm, Serge Rielau <srie...(a)ca.ibm.com> wrote: > 2803s...(a)gmail.com wrote: > > Anyway, the matter at hand . . . After changing things in the > > db2cli.ini file, I now have the stored procs back, but the UDFs can't > > be found. And just before writing this, I got my first ever (I've > > been using db2 since version 2) SQLSTATE 56098 on an SP that has been > > in use without a glitch for at least a year. I'm the owner and am > > signed on as such. > > SQLSTATE 56098: An error occurred during implicit rebind or prepare. > > There are multiple SQLCODEs that can get you there. > What was the complete message? (May be echo-ed in the db2diag.log). > > > In order to keep business going, I'm going to reinstall Version 8.x > > and wait this out. (I did check the memory and HDD of my machines, > > and no errors are found after full-day runs.) > > I doubt this is install related, and it sure isn't HDD related. > > Cheers > Serge > > PS: I do not consider the windows registry a marvel of innovation. > > -- > Serge Rielau > DB2 Solutions Development > IBM Toronto Lab Yes Cheers . . . Best wishes for the holiday season. I know that you are snowed in; I don't know if you got clobbered as they did in Montréal. I have friends in Montréal who can't move. I am in South Florida and used to live (for 35 years) in Canada. Cheers and sympathy! Hard to go on after that. But . . . I am in a position on my test setup, where I can uninstall everything and start from scratch. Redo the database setup, tablespaces, buffers, tables, stored procedures, triggers, UDFs, etc Do you think that I should do that for V9.5, without the changes in PATH which I have never needed before, and without which everyone else seems to do fine? It would take about 5 hours. This would tell me if something stupid went wrong in the previous installation (either of the database), but not of the OS. Otherwise, I will just reinstall V8.x. I know that it works fine, but it doesn't lead me to the advantages that I want in XML. I have to do something. Right now I am mired and cannot develop this application further. SS
From: 2803stan on 24 Dec 2007 20:59 Even More Cheers . . . Remi Martin Grand Fin Champagne Napoleon! If you visit South Florida, I promise you a taste. If I have to come to TO (as I do from time-to-time), well, no one has that anyway . . . I didn't mention in the last message that I could redo everything in V8.x and, if it all worked, upgrade (via usual path) to V9.5 SS
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: WBI Monitor Next: The column name as com.ibm.db2.jcc.b.dc@1d5b3a |