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/
