Date: Thu, 28 Mar 2024 21:02:45 +0000 (UTC) Message-ID: <358962206.1.1711659765419@11482368a5b4> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1212586042.1711659765395" ------=_Part_0_1212586042.1711659765395 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When using standby= databases sometimes the unexpected happens, where you are faced with a sta= ndby that still requires recovery (archive logs need to be applied), but th= e archive logs are no longer available, creating an "unrecoverable = archive log gap". There are a number of reasons this may happen, h= uman error, corruption, or disk failures to name just a few. In short= , the standby database needs more recovery and without the required logs, r= ecovery from this scenario might seem impossible. Another issue seen on a r= egular basis is when =E2=80=9Cnologging=E2=80=9D operation= s are being performed on the primary database. The end result is that these= operations are not applied to the standby due to no redo information being= available for these transactions. The standby will appear to be up t= o date, but when these objects are accessed =E2=80=93 when standby is open = read-only, roles were changed with the primary or it is activated =E2=80=93= you will receive errors.
Prior to Dbvisit Standby release 6.0.3= 4, the only options available to recover from these types of issues were to= either recreate the standby database using the =E2=80=9CCreate Standby Dat= abase=E2=80=9D (CSD) feature, or by manually performing incremental backups= on the primary, and using that to recover the standby database. See&= nbsp;here for more details on how this can be done. W= ith release 6.0.34, a new option called =E2=80=9CSynchronize Standby Databa= se=E2=80=9D was added to assist you with quick and easy re-synchronizing of= the standby database with the primary. The process is now fully auto= mated with minimal input required from the end user.
Watch this explanatory video for an ov= erview of the Sync Feature:
Only Oracle Databases, versions 1= 0g Release 2 and later (10.2.0.1) are supported with this feature.=
The following two sections will show how you can perform this task from = the GUI and the command line.