Adjusting the Rollback segments doesn't fix the root cause of ORA-1555 errors: bad programming and/or scheduling.
Please see the paper "Cats, Dogs and ORA-1555' at www.evdbt.com/papers.htm As for locking the table, why are you doing that? Locking a table turns an expensive multi-user concurrency based RDBMS into an expensize version of MS Excel. There are at times legitimate reasons for locking an entire table, but they are rather rare. Please join an oracle forum such as [EMAIL PROTECTED] if you want more information on the Oracle side. http://www.cybcon.com/~jkstill/util/maillist/maillist.html as for the code to lock the table, check out the Oracle docs under 'LOCK'. There are several modes of locking, with various level of restrictions. e.g. $dbh->do('lock table t1 in share mode'); $dbh->do('lock table t1 in exclusive mode'); HTH Jared On Monday 11 November 2002 12:17, Tim Harsch wrote: > This question comes up from time to time. The answer is: yes you can, but > why would you? > > ie. If you're trying to avoid snapshot too old errors, then you probably > just need to adjust your rollback segments to be effective for your > environment. Locking the table just makes your problems worse in the long > run. > > If you're trying to guarantee read consistency accross several queries in > your script, then turn autocommit off and start a transaction at the > beginning of your script and end the transaction at the end of your script. > > ----- Original Message ----- > From: "John Gedeon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, November 11, 2002 12:06 PM > Subject: Locking a table > > > Is there a way to easily lock a table ? so that no updates can happen > > untill my script is done? > > > > I am using DBD::Oracle? > > > > <>< Proverbs 3:5 "Trust in the Lord with all your heart and lean not on > > your own understanding;"
