What I wrote is what I have been told myself and I am trying to solve a problem I don't know a lot about. Apparently when this load is run from remote users the table locks. I haven't seen it happening myself. I thought that it was direct load because I thought that direct=true is set by...
What I use at the moment is
sqlldr80 control=loader.ctl userid=itmv1/itmv1@devel_ufs
I am not using the direct parameter at all. Should I just add DIRECT=FALSE at the end?
And using conventional path will it make the load slower, but the table willbe accessible i.e. not locked during this...
Hi, it seems to be that the table is locked when sql loader is run. How can I change the behaviour of loader so that the table does not lock? Currenlty I am using direct path, what is the syntax to use conventional path instead?
Thanks for that. How can I check the latency? Is there a way of doing this?
One solution I thought of is to create a new table that will be only used by the remote users. Do you think this will solve the problem?
We have an oracle database which is being updated using an oracle form very often. We are using Oracle Forms 6i and Oracle 8.0.6. The in-house users can update the database simultaneously without any data locks that cause delays. However, we have some remote users in a different country that...
We have an oracle database which is being updated using an oracle form very often. We are using Oracle Forms 6i and Oracle 8.0.6. The in-house users can update the database simultaneously without any data locks that cause delays. However, we have some remote users in a different country that...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.