Things that have helped in the past also revolve around changing the FETCH size in your connection settings. Lowering this number will potentially increase the fetch time, but provide a more consistent retrieval of rows… especially on networks that have a lot of noise.
thanks for posting the solution with this transactional parameter.
However when doing this (I needed this solution to be able to access a mysql table through an oracle database via a db link), the BO desktop client (BO 6.5) is no longer capable of contacting the server.
We are forced to start deski in “offline mode” which off course prevents us from downloading reports from corp docs or see-ing universe updates.
What is the underlying cause for not being able to contact the server anymore?
best regards,
Ruben
By the way: when we do not include the transactional parameters in de oracle.sbo file, then the error reported by deski is
ORA-01002: fetch out of sequence ORA-02063: preceding line from [mysql database] when trying to query the mysql table via oracle.