Hi Sony,
Commit will slow down your script. (I mean use the reasonable number of transactions
per commit)
Perhaps you can set your Rollback segment optimal value to null.
Your rollback will never shrink : )
Sinardy
-Original Message-
Sent: 06 January 2003 10:09
To: Multiple recipients
Try to commit for every one transaction on your script, it will be helpful.
>
>
> [EMAIL PROTECTED]
>
> mTo:
> [EMAIL PROTECTED]
>
> Sent by: cc:
>
> [EMAIL PROTECT
Any commits in the script that you run?
Ron Thomas
Hypercom, Inc
[EMAIL PROTECTED]
Each new user of a new system uncovers a new class of bugs. -- Kernighan
Sergei,
My first guess will be you are using a loop and you are committing
intermittently. If so, then the rollback segment used is not RBIG20. Any
time a commit or rollback occurs, you are starting new transaction and
hence a new rollback segment may be allocated; in this case it's R27.
The sec
Sergei;
Is it a simple update/insert into a single table ??
Does the table have any triggers on it ?
Do you commit anywhere in the update and then do another update/insert ?
How about showing the update/insert code you are running.
-Original Message-
Sent: Friday, January 03, 20
Title: RE: strange issue with setting transaction
Sergei, are you committing in your "transaction"? A transaction ends with a commit or rollback. Therefore if you execute set transaction use rollback... then commit, the next transaction will grab whatever rbs it wants unless you s
Sergei,
Do you get the same error each time?
Here is what I think is happening (please, gurus, correct me if I am
wrong). Your transaction needs to create a read consistent version of a
block to see if another transaction has modified the row you are interested
in modifying. Thus it
Sergei wrote:
>
> I am running 8.1.6 on solaris 2.8.
>
> Before running a large update, I tried to set a specific rollback
> segment by:
> Set transaction use rollback segment RBIG20;
>
> The transaction runs for a while and fails with:
>
> ORA-01555: snapshot too old: rollback segment number 2
