DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2000
    The system I work on has a staging database and a production database.

    Data is inserted into the production database with a link from the staging database.

    The activity on the production database is small except for these updates. Thus, I want several small RBS's and one big RBS for large updates.

    The data is inserted or updated from staging instead of selected from production. That means that the developers cannot set the RBS for the transaction. Otherwise, we could use

    set transaction use rollback segment tralala;

    Does anyone have a trick to set the RBS in a distributed transaction?

    Thanks in advance.
    David Knight
    OCP DBA 8i, 9i, 10g

  2. #2
    Join Date
    Dec 2000
    Ljubljana, Slovenia
    Try forcing the load process to be driven from the production site, although it will still be initiated from the staging database:

    At the production site, write a stored procedure that will perform the loading process by reading data from the staging database. That way, youŽll be able to use "set transaction use rollback segment tralala; " at the begining of each transaction.

    You can call this procedure from your staging database via db_link, so you still have the control of the loading process from that side.

    Makes sence?
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.