kieranm
Member
Hi
I was browsing the tips section and saw this tip which looks very helpful since the users get this mesSage quite a bit. I was just wondering is it still relevant for our release, (Xe Sp23, Oracle 8.1.something on Solaris) as I remember this from a few years ago?
Thanks
Kieran
To prevent the occurance of 'Commit failed' errors in transaction processing
This issue is caused when Oracle forfeits the cursors created in the previous connection when OneWorld middleware creates a new connection.
Add the following to the JDE INI on both the client machine and the server:
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
Client machine needs to be on SP11.1 or higher. Server needs to be at SP16 or higher.
NOTE: Both client and server need to be at the same SP level. If logic is processed on the server then both client and server need to be at SP16 or higher.
I was browsing the tips section and saw this tip which looks very helpful since the users get this mesSage quite a bit. I was just wondering is it still relevant for our release, (Xe Sp23, Oracle 8.1.something on Solaris) as I remember this from a few years ago?
Thanks
Kieran
To prevent the occurance of 'Commit failed' errors in transaction processing
This issue is caused when Oracle forfeits the cursors created in the previous connection when OneWorld middleware creates a new connection.
Add the following to the JDE INI on both the client machine and the server:
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
Client machine needs to be on SP11.1 or higher. Server needs to be at SP16 or higher.
NOTE: Both client and server need to be at the same SP level. If logic is processed on the server then both client and server need to be at SP16 or higher.
