Re: sql blocking problem

Hi ÀÌ¿µÇÑ,

Firstly, as you don't have a where condition in your update statement, are you aware that *ALL* rows are going to be updated. Are you really really sure you want to do this ?

If someone is updating a row you want to update, basically you wait until the other transaction has completed. Oracle has a sophisticated queuing mechanism so you get access to the locked row when it's your turn.

If you get impatient, contact your DBA to determine which bugger has a row locked and for a small price they might "unlock it" for you (a couple of rum and cokes usually does me).

If this must be processed with minimal locking issues, you have the option to lock the table in exclusive mode first (with the 'lock table t_count in exclusive mode' command). Generally try and discourage this, you now lock everyone else out of the table.

However, going back to my first question, do you really want to update all the rows in the table?

Good luck

Richard
"ÀÌ¿µÇÑ" <hotyoung_at_netnsec.com> wrote in message news:uKPW8.100856$nP6.10413306_at_news.bora.net...
> I made homepage counter with Oracle.
>
> Action of counter is executed to SQL statement such as lower part.
>
> update t_count set work_date = '20020710', visit_cnt = visit_cnt+1
>
> This program is made with Pro*C. After execute above SQL statement,
execute
> commit statement.
>
> By the way ..
>
> At the same time, in case of program that execute above SQL statement ran
> much, above SQL is not processed in Oracle and phenomenon that become
> blocking happens.
>
> How can i solve this problem?
>
> please~~~ help.. me..
>
>
>
Received on Wed Jul 10 2002 - 02:24:51 CDT