-
we can a large batch job run monthly that insert lots of record and also query and join some huge tables .. two questions :
1- Can I user SET TRANSACTION TO BIG_ROLLBACK inside stored procedure ( Oracle 8.0.5 ) to prevent regular rollback blow out
2- Do I need to resie redo log groups and files to prevent too many log switch and probably hang
Generally please tell me what cuation I have to do in this kind of large scale process
Thanks guys
An ounce of prevention is worth a pound of cure
-
1. Yes. Use "SET TRANSACTION USE ROLLBACK SEGMENT RBS_NAME;"
2. No asuming that your logs are properly sized.
-
Hi,
Why don’t u follow Dynamic SQL so that u do not have to bather about redo log file size, roll back segments unless u want your transaction to be roll backed.
Does it make sense?.
Regards,
Ganesh.G.
Ganesh.G
-
Originally posted by ganeshg75
Does it make sense?.
No, not to me. Dynamic SQL has nothing to do with batch job workloads (the frequency of log switches) nor with the size of transactions (rollback sizing isue).
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
Not sure if it's available under 8.0.5, but you could also try
DBMS_TRANSACTION.USE_ROLLBACK_SEGMENT('BIG_ROLLBACK');
Cheers,
OCP 8i, 9i DBA
Brisbane Australia
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|