4 Replies Latest reply: Jul 17, 2013 8:12 AM by nagulan.selvakumar RSS

    Dataguard configuration in production

    Aryacool

      Hi friends,

       

        I need to configure my production environment (primary database) for a standby database. i have a question for this i need to do some changes in parameter file(spfile/pfile) at any moment shall i need to bounce my  primary database or it need down time ?

       

      Thanks & regards,

      Arya

        • 1. Re: Dataguard configuration in production
          mseberg

          Hello;

           

          I believe most of these of these work ALTER SYSTEM scope BOTH:

           

          FAL_SERVER                                   ( ALTER SYSTEM )

          STANDBY_FILE_MANAGEMENT      ( ALTER SYSTEM )

          DB_UNIQUE_NAME

          DB_FILE_NAME_CONVERT

          LOG_FILE_NAME_CONVERT

          log_archive_dest_1

          log_archive_dest_2

          LOG_ARCHIVE_DEST_STATE_1

          LOG_ARCHIVE_DEST_STATE_2

          LOG_ARCHIVE_MAX_PROCESSES

           

          DB_UNIQUE_NAME is not Modifiable so you need a bounce.



          DB_UNIQUE_NAME

           

          Best Regards

           

          mseberg

           

          Message was edited by: mseberg

          • 2. Re: Dataguard configuration in production
            CKPT

            Aryacool wrote:

             

            Hi friends,

             

              I need to configure my production environment (primary database) for a standby database. i have a question for this i need to do some changes in parameter file(spfile/pfile) at any moment shall i need to bounce my  primary database or it need down time ?

             

            Thanks & regards,

            Arya

             

            To configure Data Guard at any point you no need to bounce primary database. That is sweetest part of it.

            If you are using SPFILE then you can go for both,if you using PFILE then you have to edit the PFILE and also perform changes at memory as well(scope=memory).

             

            Thank you

            • 3. Re: Dataguard configuration in production
              Aryacool

              Hi mseberg,

               

                   Thanks for your reply. DB_UNIQUE_NAME already there in production/primary server this means no need of bounce the primary database.

               

              Regards,

              Arya

              • 4. Re: Dataguard configuration in production
                nagulan.selvakumar

                Hi,

                 

                To configure dataguard, it doesn't actually requires DB bounce as we configure dataguard in my company without bounce. All the required parameters can be set using alter system command to set on the primary database memory even if you use pfile to startup. When using pfile don't forget to edit it to carry all the parameters that were set on the primary database to configure dataguard so that when the DB undergoes bounce later or at scheduled maintenance window, the settings will be preserved and there won't arise problems to the dataguard setup.