Jonathan,
I have had this recurring problem over the past year or so, and like you, have never received a satisfactory answer. The problem can be fixed temorarily using some of the methods you describe, but never permenantly.
I recall that someone from BusinessObjects suggested that you need sqlnet 2.3.3 to correct this problem. I have not tested this (and given the effort involved in rolling out a new sqlnet version to users all over the world, probably wouldn’t pursue it), but it’s worth a try.
Someone else suggested that if you set your unv parameters to ‘disconnect after n minutes’, the problem goes away. This, as opposed to having ‘disconnect after each transaction’. Again, this is not confirmed as a cure-all.
Good luck.
Jason Beard
AFD Consulting
Listserv Archives (BOB member since 2002-06-25)