Informix Universal Server 9.14 UC7 and HP 10.20
We are using HP/UX 10.20 and Informix Universal Server. We are currently using Informix 9.13 UC3 on our production systems and are having problems. We use web datablade version 3.31 UC2. We also use the Verity Text Search datablade version 1.10 UC1A4. We have been suggested to upgrade to 9.14 UC7. As a first step we began upgrading to 9.14 UC7 on the development environment. It is identical to the production environment using HP 10.20. We have sucessfully installed 9.14 UC7 Universal Server. We can bring the database up online. As part of the upgrade it was decided to upgrade the web datablade to 3.32 UC5. We are having problems registering the datablade using the blademgr utility. Are there any know problems with compatibility of products like web databalade and universal server ? Has any one experienced this problem during upgrades ? Any pointers... and helpful hints .... Thanks in advance. Ram Sent via Deja.com http://www.deja.com/ Before you buy.
In article <7u7e38$jq8$1@nnrp1.deja.com>, ram_cnc <rsivaguru@my-deja.com> wrote: > We are using HP/UX 10.20 and Informix Universal Server. We are currently > using Informix 9.13 UC3 on our production systems and are having > problems. > > We use web datablade version 3.31 UC2. We also use the Verity Text > Search datablade version 1.10 UC1A4. > > We have been suggested to upgrade to 9.14 UC7. As a first step we began > upgrading to 9.14 UC7 on the development environment. It is identical to > the production environment using HP 10.20. > > We have sucessfully installed 9.14 UC7 Universal Server. We can bring > the database up online. As part of the upgrade it was decided to upgrade > the web datablade to 3.32 UC5. We are having problems registering the > datablade using the blademgr utility. > > Are there any know problems with compatibility of products like web > databalade and universal server ? > > Has any one experienced this problem during upgrades ? > > Any pointers... and helpful hints .... What errors are you getting from blademgr? Check the blademgr log files in /tmp/blademgr for details about the specific error. Might point you right to what is wrong. How did you upgrade? Is the 3.31 UC2 source directory still in $INFORMIXDIR/extend during the upgrade? If it becomes a major problem and you are only using the web blade specific features in the web* (or wb*) tables, unload them all, drop the tables and unregister the old blade. Then bounce the server and then register the new blade and load all of your saved tables. I've never used the web blade on hp-ux so there might be soemthing there as well. Tony -- -- The opinions expressed here are mine and only mine. asalerno@my-deja.com www.summitdata.com Sent via Deja.com http://www.deja.com/ Before you buy.
In article <7u7hf9$mhq$1@nnrp1.deja.com>, Antonio Salerno <asalerno@my-deja.com> wrote: > In article <7u7e38$jq8$1@nnrp1.deja.com>, > ram_cnc <rsivaguru@my-deja.com> wrote: > > We are using HP/UX 10.20 and Informix Universal Server. We are > currently > > using Informix 9.13 UC3 on our production systems and are having > > problems. > > > > We use web datablade version 3.31 UC2. We also use the Verity Text > > Search datablade version 1.10 UC1A4. > > > > We have been suggested to upgrade to 9.14 UC7. As a first step we > began > > upgrading to 9.14 UC7 on the development environment. It is identical > to > > the production environment using HP 10.20. > > > > We have sucessfully installed 9.14 UC7 Universal Server. We can bring > > the database up online. As part of the upgrade it was decided to > upgrade > > the web datablade to 3.32 UC5. We are having problems registering the > > datablade using the blademgr utility. > > > > Are there any know problems with compatibility of products like web > > databalade and universal server ? > > > > Has any one experienced this problem during upgrades ? > > > > Any pointers... and helpful hints .... > > What errors are you getting from blademgr? > Check the blademgr log files in /tmp/blademgr for details about the > specific error. Might point you right to what is wrong. > We looked at the log files for blademgr. It says something to the effect that insert failed since a row already exists. My thought is that the web.3.31.UC2 datablade has installed / inserted some rows into the system tables sysbldobjects and so forth. Since there is no specific command to upgrade the web datablade (you have to use only register command even for an upgrade)the upgrade process invokes some sql statements that insert rows into the tables where there is already a row from the previous release. This causes the error and the registration of the web datablade stops. My system is down I could not pull in the exact log file messages. > How did you upgrade? Is the 3.31 UC2 source directory still in > $INFORMIXDIR/extend during the upgrade? > YES. > If it becomes a major problem and you are only using the web blade > specific features in the web* (or wb*) tables, unload them all, drop the > tables and unregister the old blade. Then bounce the server and then > register the new blade and load all of your saved tables. > Some thing to try when the server comes up. > I've never used the web blade on hp-ux so there might be soemthing there > as well. > > Tony > -- > -- > The opinions expressed here are mine and only mine. > asalerno@my-deja.com > www.summitdata.com > > Sent via Deja.com http://www.deja.com/ > Before you buy. > Sent via Deja.com http://www.deja.com/ Before you buy.
In article <7u7vaj$1h3$1@nnrp1.deja.com>, ram_cnc <rsivaguru@my-deja.com> wrote: > In article <7u7hf9$mhq$1@nnrp1.deja.com>, > Antonio Salerno <asalerno@my-deja.com> wrote: > > What errors are you getting from blademgr? > > Check the blademgr log files in /tmp/blademgr for details about the > > specific error. Might point you right to what is wrong. > > > We looked at the log files for blademgr. It says something to the effect > that insert failed since a row already exists. My thought is that the > web.3.31.UC2 datablade has installed / inserted some rows into the > system tables sysbldobjects and so forth. Since there is no specific > command to upgrade the web datablade (you have to use only register > command even for an upgrade)the upgrade process invokes some sql > statements that insert rows into the tables where there is already a row > from the previous release. This causes the error and the registration of > the web datablade stops. > > My system is down I could not pull in the exact log file messages. I vaguely remember there being problems upgrading from one version of the web blade to another. I cannot remember the exact versions. I thought it was from a 3.30 to a 3.32. I can't find the notes that I had on it. I think I have upgraded 3.31 to 3.32. Usually the upgrade works fine. When you register, and it's an upgrade, blademaneger tells you it's upgrading the blade. > > If it becomes a major problem and you are only using the web blade > > specific features in the web* (or wb*) tables, unload them all, drop > the > > tables and unregister the old blade. Then bounce the server and then > > register the new blade and load all of your saved tables. > > > Some thing to try when the server comes up. This might be your best bet, unless you call tech support and there is something simple they can tweak. If you are still using APB, you might want to try only unloading the non-APB data from the web* tables. Then when you register the new blade, load the APB stuff from the $INFORMIXDIR/extend/web/apb directory first, then reload your tables. This way, if they added anything to the APB code (which I doubt) you can get whatever it was. If you are using DDW, then just unload (the wb* tables), then after the new blade registers, load the tables back in. Don't know if you also need the web* tables. Tony -- -- The opinions expressed here are mine and only mine. asalerno@my-deja.com www.summitdata.com Sent via Deja.com http://www.deja.com/ Before you buy.