![\"twitter\"](\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" "\\"Share")
<\/a><\/a>![\"linkedin\"](\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" "\\"Share")
<\/a>![\"mail\"](\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" "\\"Share")
<\/a>Configuration <\/strong><\/em>: Remarque :Toutes les op\u00e9rations SQL se font connect\u00e9 en tant que “as sysdba” <\/strong><\/p>\n 1. Configuration des bases en archivelog et force logging SQL> ALTER DATABASE FORCE LOGGING; 2. Cr\u00e9er une sauvegarde de la base primaire<\/strong><\/p>\n A) Cr\u00e9er les standby controlfile B) Cr\u00e9er les standby redo log . Il est conseill\u00e9 :<\/p>\n log<\/p>\n<\/li>\n<\/ul>\n C) Effectuer une sauvegarde de la base primaire ((il est possible de le faire \u00e0 chaud par rman)<\/p>\n Arr\u00eater la base primaire<\/p>\n Faire une copie physique dans un r\u00e9pertoire de sauvegarde des types de fichier suivants : Red\u00e9marrer la base primaire<\/p>\n 3. Modification ou cr\u00e9ation des param\u00e8tres d\u2019initialisation des bases primaire et standby<\/strong><\/p>\n Base ayant le r\u00f4le primaire (PTEST) <\/em>: Base ayant le r\u00f4le standby (STEST) :<\/em> 4. Configurer le listener, Oracle services names de la base primaire et de la standby<\/strong><\/p>\n A) Configurer les fichiers $ORACLE_HOME\/network\/admin\/listener.ora pour l’enregistrement statique<\/p>\n listener.ora :<\/em><\/p>\n SID_LIST_LISTENER_PRIMARY = SID_LIST_LISTENER_STANDBY = LISTENER_PRIMARY = LISTENER_STANDBY = B) Configurer les $ORACLE_HOME\/network\/admin\/tnsnames.ora<\/p>\n STEST = PTEST<\/p>\n = C) Red\u00e9marrer les listeners des deux bases.<\/p>\n $ORACLE_HOME\/bin\/lsnrctl start LISTENER_PRIMARY 5. Copie du fichier de mot de passe ou g\u00e9n\u00e9ration avec $ORACLE_HOME\/bin\/orapwd 6. Faire un startup mount de la base standby :<\/strong><\/p>\n SQL> startup mount<\/p>\n 7. <\/strong> D\u00e9marrer le recovery sur la base standby<\/strong><\/p>\n A l\u2019aide de la commande suivante : 8. V\u00e9rifier le transport des journaux<\/strong><\/p>\n En for\u00e7ant la cr\u00e9ation d\u2019un archive log sur la base primaire : 9. <\/strong>V\u00e9rifier que le data Guard fonctionne <\/strong><\/p>\n en ex\u00e9cutant la requ\u00eate suivante sur le primary et sur la standby: <\/span><\/p>\n Remarques :<\/em><\/p>\n \n – <\/span><\/span>Dans notre d\u00e9marche nous adopterons la d\u00e9nomination suivante:<\/p>\n PTEST : base primaire<\/p>\n STEST : base standby<\/p>\n – <\/span><\/span><\/span>Toutes les op\u00e9rations SQL se font connect\u00e9 en tant que sys as sysdba<\/em><\/strong><\/p>\n \n \n <\/span>SQL> <\/span>ALTER DATABASE FORCE LOGGING;<\/p>\n <\/span>SQL> alter database archivelog ;<\/p>\n \n <\/span>Cr\u00e9er les standby controlfile<\/p>\n \n <\/span>SQL> alter database create standby controlfile as<\/span><\/p>\n <\/span> <\/span> <\/span>\u2018\/u01\/app\/oracle\/TEST\/standby1.ctl\u2019;<\/span><\/p>\n <\/span><\/p>\n <\/span><\/p>\n <\/span><\/em><\/p>\n <\/span> <\/span><\/span>Cr\u00e9er les standby redo log .<\/p>\n <\/span><\/p>\n <\/span>SQL> ALTER DATABASE ADD STANDBY LOGFILE<\/span><\/p>\n <\/span>‘\/u01\/app\/oracle\/TEST\/srl01.log’ SIZE 10M <\/span>REUSE;<\/span><\/p>\n <\/span><\/span><\/p>\n <\/span>SQL> ALTER DATABASE ADD STANDBY LOGFILE<\/span><\/p>\n <\/span>‘\/u01\/app\/oracle\/TEST\/srl02.log’ SIZE 10M <\/span>REUSE;<\/span><\/p>\n <\/span><\/p>\n <\/span>SQL> ALTER DATABASE ADD STANDBY LOGFILE<\/span><\/p>\n <\/span>‘\/u01\/app\/oracle\/TEST\/srl03.log’ SIZE 10M <\/span>REUSE;<\/span><\/p>\n <\/span><\/p>\n <\/span>SQL> ALTER DATABASE ADD STANDBY LOGFILE<\/span><\/p>\n <\/span>‘\/u01\/app\/oracle\/TEST\/srl04.log’ SIZE 10M <\/span>REUSE;<\/span><\/p>\n <\/span><\/p>\n Il est conseill\u00e9 de cr\u00e9er un fichier stand by redo log de plus que les redo log afin d\u2019\u00e9viter un probl\u00e8me en cas de saturation des redo log<\/span><\/em><\/p>\n <\/span><\/em><\/p>\n <\/span>Arr\u00eater la base primaire ((il est possible de le faire \u00e0 chaud par rman)<\/p>\n \n <\/span>Faire une copie physique dans un r\u00e9pertoire de sauvegarde des types de fichier suivants :<\/p>\n \n – <\/span><\/span>datafiles<\/p>\n
\nRed Hat Enterprise Linux Server release 5.4 (Tikanga)
\nOracle 10GR2
\nPTEST : base primaire
\nSTEST : base standby<\/p>\n
\n<\/strong><\/p>\n
\nSQL> alter database archivelog ;<\/p>\n
\nSQL> alter database create standby controlfile as \u2018\/u01\/app\/oracle\/TEST\/standby1.ctl\u2019;<\/p>\n
\nSQL> ALTER DATABASE ADD STANDBY LOGFILE ‘\/u01\/app\/oracle\/TEST\/srl01.log’ SIZE 10M REUSE;
\nSQL> ALTER DATABASE ADD STANDBY LOGFILE ‘\/u01\/app\/oracle\/TEST\/srl02.log’ SIZE 10M REUSE;
\nSQL> ALTER DATABASE ADD STANDBY LOGFILE ‘\/u01\/app\/oracle\/TEST\/srl03.log’ SIZE 10M REUSE;
\nSQL> ALTER DATABASE ADD STANDBY LOGFILE ‘\/u01\/app\/oracle\/TEST\/srl04.log’ SIZE 10M REUSE;<\/p>\n\n
\n– datafiles
\n– online redo logs
\n– standby controlfile
\n– standby redolog<\/p>\n
\nlog_archive_format=%t_%s_%r.arc
\nlog_archive_dest_2=’service=STEST LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=STEST’
\nlog_archive_config=’DG_CONFIG=(PTEST,STEST)’
\nLOG_ARCHIVE_DEST_STATE_2=ENABLE
\ndb_name=TEST
\ndb_unique_name=PTEST
\nfal_server=STEST
\nfal_client=PTEST
\nDB_FILE_NAME_CONVERT=(‘\/u01\/app\/oracle\/TESTSTANDBY’,’\/u01\/app\/oracle\/TEST’)
\nLOG_FILE_NAME_CONVERT=(‘\/u01\/app\/oracle\/TESTSTANDBY’,’\/u01\/app\/oracle\/TEST’)
\nstandby_archive_dest=\/u01\/app\/oracle\/flash_recovery_area\/STEST\/standby_archive
\nSTANDBY_FILE_MANAGEMENT=AUTO<\/p>\n
\nfal_server=PTEST
\nfal_client=STEST
\nDB_FILE_NAME_CONVERT=(‘\/u01\/app\/oracle\/TEST’,’\/u01\/app\/oracle\/TESTSTANDBY’)
\nLOG_FILE_NAME_CONVERT=(‘\/u01\/app\/oracle\/TEST’,’\/u01\/app\/oracle\/TESTSTANDBY’)
\nSTANDBY_ARCHIVE_DEST=\/u01\/app\/oracle\/flash_recovery_area\/STEST\/standby_archive
\nlog_archive_format=%t_%s_%r.dbf
\nSTANDBY_FILE_MANAGEMENT=AUTO
\nlog_archive_config=’DG_CONFIG=(PTEST,STEST)’
\nLOG_ARCHIVE_DEST_2=’service=STEST LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=PTEST’
\nLOG_ARCHIVE_DEST_STATE_2=DEFER
\nCONTROL_FILES=(“\/u01\/app\/oracle\/TESTSTANDBY\/standby1.ctl”, “\/u01\/app\/oracle\/TESTSTANDBY\/standby2.ctl”, “\/u01\/app\/oracle\/TESTSTANDBY\/standby3.ctl”)<\/p>\n
\n(SID_LIST=
\n(SID_DESC=
\n(GLOBAL_DBNAME=TEST)
\n(ORACLE_HOME = \/u01\/app\/oracle\/product\/10.2.0\/db_1)
\n(SID_NAME=PTEST)
\n)
\n)<\/p>\n
\n(SID_LIST =
\n(SID_DESC =
\n(GLOBAL_DBNAME = TEST)
\n(ORACLE_HOME = \/u01\/app\/oracle\/product\/10.2.0\/db_1 )
\n(SID_NAME = STEST)
\n)
\n)<\/p>\n
\n(DESCRIPTION_LIST =
\n(DESCRIPTION =
\n(ADDRESS = (PROTOCOL = TCP)(HOST = LINUX-ORA10-DATAGUARD-PRIMARY)(PORT = 1521))
\n)
\n)<\/p>\n
\n(DESCRIPTION_LIST =
\n(DESCRIPTION =
\n(ADDRESS = (PROTOCOL = TCP)(HOST = LINUX-ORA10-DATAGUARD-PRIMARY)(PORT = 1522))
\n)
\n)<\/p>\n
\n(DESCRIPTION =
\n(ADDRESS = (PROTOCOL = TCP)(HOST = LINUX-ORA10-DATAGUARD-PRIMARY)(PORT = 1522))
\n(CONNECT_DATA =
\n(SERVER = DEDICATED)
\n(SERVICE_NAME =STEST)
\n)
\n)<\/p>\n
\n(DESCRIPTION =
\n(ADDRESS = (PROTOCOL = TCP)(HOST = LINUX-ORA10-DATAGUARD-PRIMARY)(PORT = 1521))
\n(CONNECT_DATA =
\n(SERVER = DEDICATED)
\n(SERVICE_NAME =PTEST)
\n)
\n)<\/p>\n
\n$ORACLE_HOME\/bin\/lsnrctl start LISTENER_STANDBY<\/p>\n
\n<\/strong><\/p>\n
\nSQL> alter database recover managed standby database disconnect from session;<\/p>\n\n
\nSQL> alter system archive log current ;
\nL\u2019archive log est alors transmis vers le r\u00e9pertoire d\u2019archive de la base standby, et cette derni\u00e8re fait automatiquement un recovery \u00e0 partir du log transmis.<\/p>\n
\nSQL> select max(sequence#) from v$log_history;<\/p>\n\n<\/a> <\/span><\/h1>\n
<\/a><\/h2>\n<\/p>\n
\n
<\/a><\/h2>\n
<\/a><\/h2>\n