Re: Splited database query problem.
In theory, if the split was performed correctly (meaning that the links are good), you should not really be able to tell from a session that you are in a split or a non-split database. I.e. the split should be transparent. From the front end, you ARE still the only user of the database (based on file locking and object locking considerations). It is only when you touch the back end that you face potential contention and locking.
That it is NOT transparent suggests that something is wrong with the way the split occurred. When you split, did the "local table" move to the back end? Does the front end retain the database link to ORACLE? Did you work to minimize lock exposure by either setting "Optimistic Locking" (where that is a consideration for front-end queries) or "MIN LOCKS" (which is an ORACLE consideration)?
I'm a certified grandpa (3 times now) and proud of it.
Retired over one year and survived being home all day with the wife. She must really love me.
If I have helped you, please either click the thanks or click the scales.