Shadowing from P4 to RDBMS

[garlit]

We recently had an outage to SC Prod and the SysAdmin around at the time purged sqlqueue to reduce size of the pool. As a result, our RDBMS is no longer in sync with P4. To resync I have to reshadow P4 tables to Sybase and that requires an outage to SC. It's a 24x7 shop. Any idea how it could be done while still allowing access to SC?

Thanks!
Jane

[cherijj]

We just did an upgrade that required a 24 hour outage so we could re-synch our sql database. I refreshed our test system with production data and they used that while we were down. Once it was back up, Helpdesk re-entered all the tickets. Best we could come up with... :wink:

[edmedina]

Actually here is trick we use with one of our customers. right now they have three tables that are shadowed to Oracle that are very large. Each would take about 8 -10 to shadow. **I won't get into why they haven't done archiving yet but they need to soon**. Anyway, what we do if we need to shadow is the following:
1. Back a cold back up of the scbd files. This requires SC to be down.
2. Once back ups are done bring SC back up and put into logging mode. Make sure sqlqueue is not running as a process
3. Bring up a test environment that has access to a test Oracle database. The test environment should be brought up with the latest backup from production.
4. Start your push for the shadow.
5. Once completed have your Oracle dba take an unload of the tables you just pushed and load them to the production Oracle database.
6. Take Sc out of logging mode. Go to your dbdict and set the shadow value from 0 to 1.
7. Once SC has completed moving it's data from the log file to the scdb files go ahead and start sqlqueue and let that run.

This should get your shadow back in synch with minimum amount of outage time. We have done this a couple of times and learned that this must be done during weekends. This keeps the log file from getting too big as the activity in the environment is lowest during those days.