vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| We have several machines currently running the DB2 V7 Run-time Client that we would like to actually be running the App Dev Client. To 'upgrade' (within the same version) this client software can we simply install the App Dev Client on 'top of' the Run-time Client? Will the install routine uninstall the Run-time Client under the covers during the install of the App Dev Client? Also, is this type of 'upgrade' possible/supported during a Version-to-Version upgrade, such as when migrating from V7 to V8? Thanks. Perry Shindle |
| |||
| You can install the Appl Dev Client with the Run-time Client, insure they are at the same release and fixpack level... Also if you plan on connecting a v7 client to a v8 server, then the clients must be at minimun v7 fixpack 8. You can't connect a v8 client to a v7 server (If you happen to expect major problems). |
| |||
| It is not a good thing to connect with a v7 client to v8 server. I crashed the server via ODBC and V7 twice, and once through the CLP. To do it in the CLP just type in "SET SCHEMA CURRENT USER" and the server itself crashes. B. |
| |||
| You can't connect a v8 client to a v7 server (If you happen to expect major problems). Can you be more specific with this statement doug? We have been testing the DB2 v8.2 windows Admin Client with various 3rd party reporting tools and with native sql queries against a few different DB2 v7.2 aix servers. We are preparing to roll this out to our user machines. We have had absolutely no issues so far, but you're comments make me nervous. Pleease elaborate if possible. Thank you, Richard McCutcheon. Honda of Canada Manufacturing. |
| |||
| We have db2 8.2 clients connecting to 7.2 databases all the time without any problems. I am not sure where those errors are coming from, but I don't think they are related to the client version, but to something wrong on the server itself. The only annoyance of the 8.2 admin client is the health center status beacon, which writes worthless messages to the db2diag.log To disable it (tools -> tools settings -> health center status beacon -> uncheck everything). |
| |||
| <leonardobgil@gmail.com> wrote in message news:1136902768.102500.122950@g49g2000cwa.googlegr oups.com... > We have db2 8.2 clients connecting to 7.2 databases all the time > without any problems. > > I am not sure where those errors are coming from, but I don't think > they are related to the client version, but to something wrong on the > server itself. > > The only annoyance of the 8.2 admin client is the health center status > beacon, which writes worthless messages to the db2diag.log > > To disable it (tools -> tools settings -> health center status beacon > -> uncheck everything). It may work for your limited range of SQL statements, but it does not work for everything. IBM does not support clients connecting to back-level servers, even when 7.2 supported. |
| |||
| This is from v8's Infocenter at ibm.com. So looks like IBM supports it at least To access a DB2 Universal Database Version 7 server on a Linux, UNIX, or Windows operating system from a DB2 Version 8 client, you must * Have DB2 Version 7 FixPak 8 or later installed on your server; and * Have run the db2updv7 command. |
| |||
| I'd always tought that support was: 1 level up, 2 levels down. A V8.2 client should be able to connect up to V??? and down to V7.1.0 or V7.2 server. A V7.2 + client should be able to connect to A V8.1. server (I don't think a V8.2+). If one has a V8.2 server, I'd think that you'd need a V8.1 or V8.2 client. But then you'd be ready for V?? coming out sometime in this near future. Regards, Pierre. -- Pierre Saint-Jacques SES Consultants Inc. 514-737-4515 "Mark A" <nobody@nowhere.com> a écrit dans le message de news: w66dnXSFVPUPnVneRVn-ow@comcast.com... > <leonardobgil@gmail.com> wrote in message > news:1136902768.102500.122950@g49g2000cwa.googlegr oups.com... >> We have db2 8.2 clients connecting to 7.2 databases all the time >> without any problems. >> >> I am not sure where those errors are coming from, but I don't think >> they are related to the client version, but to something wrong on the >> server itself. >> >> The only annoyance of the 8.2 admin client is the health center status >> beacon, which writes worthless messages to the db2diag.log >> >> To disable it (tools -> tools settings -> health center status beacon >> -> uncheck everything). > > > It may work for your limited range of SQL statements, but it does not work > for everything. IBM does not support clients connecting to back-level > servers, even when 7.2 supported. > |
| |||
| Thank you for all of the replies on this thread. But I am still looking for the answer to my original question (which is repeated below). Can anyone help me on this please? ================================================== ================== We have several machines currently running the DB2 V7 Run-time Client that we would like to actually be running the App Dev Client. To 'upgrade' (within the same version) this client software can we simply install the App Dev Client on 'top of' the Run-time Client? Will the install routine uninstall the Run-time Client under the covers during the install of the App Dev Client? Also, is this type of 'upgrade' possible/supported during a Version-to-Version upgrade, such as when migrating from V7 to V8? Thanks. |
| ||||
| pshindle@comcast.net wrote: > Thank you for all of the replies on this thread. But I am still > looking for the answer to my original question (which is repeated > below). > Can anyone help me on this please? > ================================================== ================== > > We have several machines currently running the DB2 V7 Run-time Client > that we would like to actually be running the App Dev Client. To Which version of the app dev client? If it's the same or higher level, you can just install app dev client over top of the runtime client, and you'll end up with both. The disadvantage is that, if you're on Windows, you'll need both fixpacks in order to apply a new level of the code. (Unix/Linux has one fixpack for all products, so you'll continue using the same fixpack to upgrade both at the same time.) However, since I think you're on Windows, you should also be able to go into the add-remove programs to uninstall the runtime client after having installed the application development client. Your instance(s) should remain intact. > 'upgrade' (within the same version) this client software can we simply > install the App Dev Client on 'top of' the Run-time Client? Will the > install routine uninstall the Run-time Client under the covers during > the install of the App Dev Client? No, it won't uninstall the runtime client under the covers. > Also, is this type of 'upgrade' possible/supported during a > Version-to-Version upgrade, such as when migrating from V7 to V8? Sure. That should work just fine. |
| Thread Tools | |
| Display Modes | |
|
|