Re: [U2] Verify Universe - was [U2] UniObjects and Triggers
Sara Burns wrote: We have solved our problem with the UniObjects by re-installing UniVerse after we found the checksum for uvapi_slave was different on our two machines. Is there any way to verify that the UniVerse binaries are correct? This would have saved us many hours of testing, red herrings and general desperation. There was nothing visible at the file level which indicated the file had been updated, only the checksum. We have been having disk errors on the machine and have now found that these binaries are on a mirrored set showing errors. That was a surprise as we thought they were on a different disk array. AIX 5.2 ML_01, UniVerse 10.0.11 Sara Burns Yes, when you install uv a checksum check is performed and the checksums are kept in .../uv/checksums You'll find the code to rerun the check in one of the installation scripts (uv.install?). If they could be corrput reload them from the installation medium. HTH -- mats --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Verify Universe - was [U2] UniObjects and Triggers
In following Mats lead and poking around in /.../uv/bin there is a script called csum that seems to do what you want to do, we all want to do. Not being a script writer myself we will need a script reader to look at this and verify that it really does what I think it does. Script reader anyone?? /.../uv/bin/csum Tom Dodds [EMAIL PROTECTED] 630-235-2975 Cell 708-482-4510 Office -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mats Carlid Sent: Wednesday, November 24, 2004 2:40 AM To: [EMAIL PROTECTED] Subject: Re: [U2] Verify Universe - was [U2] UniObjects and Triggers Sara Burns wrote: We have solved our problem with the UniObjects by re-installing UniVerse after we found the checksum for uvapi_slave was different on our two machines. Is there any way to verify that the UniVerse binaries are correct? This would have saved us many hours of testing, red herrings and general desperation. There was nothing visible at the file level which indicated the file had been updated, only the checksum. We have been having disk errors on the machine and have now found that these binaries are on a mirrored set showing errors. That was a surprise as we thought they were on a different disk array. AIX 5.2 ML_01, UniVerse 10.0.11 Sara Burns Yes, when you install uv a checksum check is performed and the checksums are kept in .../uv/checksums You'll find the code to rerun the check in one of the installation scripts (uv.install?). If they could be corrput reload them from the installation medium. HTH -- mats --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Verify Universe - was [U2] UniObjects and Triggers
OK I'll bite ( again ) yes the uvhome/bin/csum script does check the checksums saved from the installation 'tape' . Usage: cd to uvhome (bin/)csumlistOfGroups where the list is one or more of DOCIC OBJSTARTUPUVODBC FILESIZE JDBC PORTINGUCI DEVELOPGCIMAIN QA UOJ HTH -- mats Tom Dodds wrote: In following Mats lead and poking around in /.../uv/bin there is a script called csum that seems to do what you want to do, we all want to do. Not being a script writer myself we will need a script reader to look at this and verify that it really does what I think it does. Script reader anyone?? /.../uv/bin/csum Tom Dodds [EMAIL PROTECTED] 630-235-2975 Cell 708-482-4510 Office -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mats Carlid Sent: Wednesday, November 24, 2004 2:40 AM To: [EMAIL PROTECTED] Subject: Re: [U2] Verify Universe - was [U2] UniObjects and Triggers Sara Burns wrote: We have solved our problem with the UniObjects by re-installing UniVerse after we found the checksum for uvapi_slave was different on our two machines. Is there any way to verify that the UniVerse binaries are correct? This would have saved us many hours of testing, red herrings and general desperation. There was nothing visible at the file level which indicated the file had been updated, only the checksum. We have been having disk errors on the machine and have now found that these binaries are on a mirrored set showing errors. That was a surprise as we thought they were on a different disk array. AIX 5.2 ML_01, UniVerse 10.0.11 Sara Burns Yes, when you install uv a checksum check is performed and the checksums are kept in .../uv/checksums You'll find the code to rerun the check in one of the installation scripts (uv.install?). If they could be corrput reload them from the installation medium. HTH -- mats --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
[U2] Verify Universe - was [U2] UniObjects and Triggers
We have solved our problem with the UniObjects by re-installing UniVerse after we found the checksum for uvapi_slave was different on our two machines. Is there any way to verify that the UniVerse binaries are correct? This would have saved us many hours of testing, red herrings and general desperation. There was nothing visible at the file level which indicated the file had been updated, only the checksum. We have been having disk errors on the machine and have now found that these binaries are on a mirrored set showing errors. That was a surprise as we thought they were on a different disk array. AIX 5.2 ML_01, UniVerse 10.0.11 Sara Burns Integration Manager Public Trust Phone: +64 (04) 474-3841 (DDI) Mobile: 027 457 5974 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Information contained in this communication is confidential. If you are not the intended recipient the information should not be used, disclosed, copied or commercialised. The information is not necessarily the views nor the official communication of Public Trust. No guarantee or representation is made that the communication is free of errors, virus or interference. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Verify Universe - was [U2] UniObjects and Triggers
Sara Burns wrote: We have solved our problem with the UniObjects by re-installing UniVerse after we found the checksum for uvapi_slave was different on our two machines. Is there any way to verify that the UniVerse binaries are correct? If you have a known good install to compare to, you could use the unix diff command. The easiest way to get access to the good binaries would probably be to NFS mount the `cat /.uvhome`/bin directory from the good install to the questionable machine. It wouldn't be too hard to write a script to automate the process. I think something like this would work: cd `cat /.uvhome`/bin for FILENAME in `ls` do diff ./$FILENAME /path/to/nfs/mount/$FILENAME /tmp/uv_verify.log done -John -- John Hester System Network Administrator Momentum Group Inc. (949) 833-8886 x623 http://memosamples.com --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniObjects and Triggers
We have done a cksum of uvapi_slave in uv/bin on our two machines and find them to be different. Both are running 10.0.11 Should we expect them to be different? As we have had some reported disk errors on the development machine we are going to try re-installing UniVerse tomorrow morning. A reboot last night did not help. Anyone got any more suggestions? Sara Burns Integration Manager Public Trust Phone: +64 (04) 474-3841 (DDI) Mobile: 027 457 5974 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Information contained in this communication is confidential. If you are not the intended recipient the information should not be used, disclosed, copied or commercialised. The information is not necessarily the views nor the official communication of Public Trust. No guarantee or representation is made that the communication is free of errors, virus or interference. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniObjects and Triggers
I think the Trigger may be the victim not the cause. This may provide some further information. We have been using UniObjects for VB and UniObjects for Java to write to UniVerse files for about a year. Last week we started doing testing on our Development server using a new set of programs using UniObjects for Java also writing to UniVerse files. We started getting errors when the file to be updated had a trigger. The files in question have not changed. They are type 18. Triggers have been in place for over a year. If we remove the trigger the update works. If we replace the trigger, without it actually doing anything, the session appears to abort. The license is not released. We have stopped and restarted UniVerse daily, prior to backups but this has not solved the situation. We have rebooted the Development server the day we found the problem, (which initially manifested itself as all licences being used), but will try this again tonight. The UniRPC log did not show anything useful. The older programs, using the same mechanisms, are still running in our Production environment without problems. These are both UniObjects for VB and Java writing to type 18 files with triggers. Development machine - IBM p660 AIX 5.2 ML_01, UniVerse 10.0.11 Production machine - IBM p660 AIX 5.2 (no patches), UniVerse 10.0.11 Both machines are also running Oracle 9.0.2 and Vantive 8.5. The only useful information we have was that on the day the problem started we found a message in Oracle, which was launching UniObjects for Java, which indicated that a string was too long for the string buffer. This error message appeared to have been generated from the RPC layer and may have somehow corrupted the RPC mechanism. I am trying to raise this with IBM as I no longer seem to be able to view the knowledge base myself. Sara Burns Integration Manager Public Trust Phone: +64 (04) 474-3841 (DDI) Mobile: 027 457 5974 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Information contained in this communication is confidential. If you are not the intended recipient the information should not be used, disclosed, copied or commercialised. The information is not necessarily the views nor the official communication of Public Trust. No guarantee or representation is made that the communication is free of errors, virus or interference. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniObjects and Triggers
Saran, I believe this has been a problem for a couple of years at least as I ran into a similar problem at a client site a few years ago. The apllication vendor ended up using a different interface. I believe it is a problem with the underlying implementation of uv/uniobjects. Check with IBM. Phil Walker +64 21 336294 [EMAIL PROTECTED] Gnosys Consulting Limited 11 Woodward Road, Mount Albert, Auckland 1003, New Zealand -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sara Burns Sent: Saturday, November 20, 2004 10:01 AM To: U2 List ([EMAIL PROTECTED]) Subject: [U2] UniObjects and Triggers We have found some odd behaviour with a new development using UniObjects for Java. UniVerse 10.0.11 on AIX 5.2 with ML_01 We are getting errors when trying to write to a file (standard Type 18) which has a trigger. If we remove the trigger the write is successful but replace the trigger and the process aborts. We cannot see anything useful in the logs. We have been using UniObjects for Java (and VB) for quite some time without problems. We found this on our development machine when all our licences had been used. These processes were not releasing a licence when they aborted. Is this a known issue and if so is there an easy fix? Any information or suggestions will be very useful. Regards Sara Burns Integration Manager Public Trust Phone: +64 (04) 474-3841 (DDI) Mobile: 027 457 5974 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Information contained in this communication is confidential. If you are not the intended recipient the information should not be used, disclosed, copied or commercialised. The information is not necessarily the views nor the official communication of Public Trust. No guarantee or representation is made that the communication is free of errors, virus or interference. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
[U2] UniObjects and Triggers
We have found some odd behaviour with a new development using UniObjects for Java. UniVerse 10.0.11 on AIX 5.2 with ML_01 We are getting errors when trying to write to a file (standard Type 18) which has a trigger. If we remove the trigger the write is successful but replace the trigger and the process aborts. We cannot see anything useful in the logs. We have been using UniObjects for Java (and VB) for quite some time without problems. We found this on our development machine when all our licences had been used. These processes were not releasing a licence when they aborted. Is this a known issue and if so is there an easy fix? Any information or suggestions will be very useful. Regards Sara Burns Integration Manager Public Trust Phone: +64 (04) 474-3841 (DDI) Mobile: 027 457 5974 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Information contained in this communication is confidential. If you are not the intended recipient the information should not be used, disclosed, copied or commercialised. The information is not necessarily the views nor the official communication of Public Trust. No guarantee or representation is made that the communication is free of errors, virus or interference. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
