Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I have Oracle 10gR2 installed on Redhat Linux 5.4 on two servers (primary and physical standby).

When I import data into the primary server while the standby is started it takes too long to complete (didn't wait for it to finish). When I shutdown Oracle on the standby server it completes in 15 minutes.

Is this really due to standby? How can I speed up this slow imp? Here is the command line used:

imp userid=/ file=base.dmp ignore=yes log=log1.log
share|improve this question

1 Answer 1

up vote 3 down vote accepted

It depends on the configuration you have in place.

Oracle uses log shipping (as default) to feed the transactions into the standby database. In order to make sure that ALL transactions are recovered on the standby database, we should make sure that the primary database is running in FORCE LOGGING mode. Switching FORCE LOGGING may cause a difference in performance on the primary database, where FORCE LOGGING mode would be a little slower than without force logging mode.

Just shutting down could - depending on the configuration - bring the primary database to a halt (protected standby database). When the primary and standby databases are on different hardware they should hardly influence each other, other than that the transactions need to be saved and transported to the standby site. If you run in sync mode the primary could be slowed more than when running a-sync which is the default.

The configuration that makes sure that the performance impact on the primary is the least, is the max performance mode, in which the transactions are only shipped when the redo logfile is full. It also gives the least data protection.

share|improve this answer
    
They should hardly influence each other assuming that the network between the servers has enough bandwidth to allow the archiver to copy the logs over the network faster than the primary can generate them at peak utilization. If the network between the servers doesn't have enough bandwidth and the import process generates a bunch of REDO, the primary could easily be stuck waiting on network transfers to the standby server. –  Justin Cave Feb 4 '13 at 15:58

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.