Versions Compared

Old Version 10

changes.mady.by.user Anton Els

Saved on

compared with

New Version 11

changes.mady.by.user Donna Zehl

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Dbvisit Standby will start sending the required archive logs to the standby server in sequential format (based on sequence number).
    • By default:
      • If an archive log was generated since the last run this log will be shipped to the standby database and no additional "logswitch" will be performed.
      • If NO archivelogs were generated since the last run, a "logswitch" will be executed on the database which will start the creation of a new archivelog that will then be transferred to the standby server.
    • Forcing a logswitch:
      • If you want to ensure the gap between the primary and standby server is similar to the scheduled gap, you can set the LOGSWITCH=Y in the DDC file.  This will force Dbvisit Standby to execute a logswitch on every execution on the primary server.  Note that this can cause additional overhead on the database server depending on current system load and I/O subsystem (especially slow I/O subsystem - storage)
    • Archive logs will be compressed before being send to the standby server if the COMPRESS variable is set in the DDC file.
      • Compression:
        • By default compression of the archive logs are enabled
        • gzip is used for compression on Linux (COMPRESS=/bin/gzip) and Dbvisit Standby's internal compression "dbvisit" is used on Windows (COMPRESS=dbvisit)
        • The default uncompress values will be set to gunzip (UNCOMPRESS=/bin/gunzip) on Linux and Dbvisit Standby's internal uncompress will be used on Windows (UNCOMPRESS=dbvisit)
        • To disable compression, set COMPRESS=N 
        • The compression settings are specified in the DDC file on the primary server.
      • ARCHDEST
        • The ARCHDEST location is used by Dbvisit Standby and is not the same location as the database Archive Destination or Recovery Area.
        • This location should be created on both the Primary and Standby servers and should have read/write permission for both the "oracle" and "grid" accounts if ASM role separation is used.
        • ARCHDEST must be on an Oracle supported filesystem type, i.e. ext3/ext4. Common Internet Filesystem (CIFS) is not supported.
        • Dbvisit Standby will transfer the Archive logs to the ARCHDEST location on the standby server as specified in the DDC file.
        • If ASM storage is used on the primary:
          • Archive logs will be copied out of the ASM storage to the ARCHTMP directory as specified by the DDC file.  ARCHTMP will be the same as the specified ARCHDEST location by default, but can be specified to be a different location if required.

...