Page Comparison

Dbvisit Standby considerations with RAC

The Dbvisit Standby Database Configuration file (DDC) created during the setup on each node will have the name of the instance and not the name of the database (dbv_oracle_instance.env).
Dbvisit Standby needs to be scheduled separately on each primary node. It is recommended that Dbvisit Standby is scheduled at different times on each node. For example:
node1 – Schedule every hour at 00, 15, 30, 45
node2 – Schedule every hour at 05, 20, 35, 50
The archive destination location on the standby node must be accessible by all standby nodes in the RAC standby cluster.

Dbvisit Standby RAC Takeover

If a RAC node fails and is unavailable, then Dbvisit Standby on another RAC node can automatically take over the log shipment from the failed node. The Dbvisit Standby RAC Takeover is controlled by the following variables in the dbv{_}oracle_instance.env file:
RAC_TAKEOVER
RAC_TAKEOVER_SID
RAC_TAKEOVER_FORCE

RAC_TAKEOVER values:
Yes = Dbvisit Standby (on this instance) will take over from another instance when that instance is unavailable.
No = Dbvisit Standby (on this instance) will NOT take over from another instance when that instance is unavailable. 

RAC_TAKEOVER_FORCE values:
Yes = Dbvisit Standby (on this instance) will take over from another instance regardless of whether that instance is available or not.
No = Dbvisit Standby (on this instance) will NOT take over from another instance unless the instance is not available and RAC_TAKEOVER = Yes. 

RAC_TAKEOVER_SID
Specify the instance name that Dbvisit Standby processing should take over if that instance is unavailable.
The instance name must be different to the current instance name.

Example :(2 Nodes)

If the RAC setup contains 2 nodes (racnode1, racnode2) with instance names RACDB1 and RACDB2, then:
On racnode1 the dbv_RACDB1.env will contain:
RAC_TAKEOVER_SID=RACDB2
On racnode2 the dbv_RACDB2.env will contain:
RAC_TAKEOVER_SID=RACDB1
This ensures that if either node is unavailable, the other node will takeover log shipment to the standby database(s).

Example :(3 Nodes)

The RAC_TAKEOVER_SID is not too different with a 3 node set up, as for a 2, and you just specify the next node in the sequence in a rolling/circular fashion. So, if the RAC setup contains 3 nodes (racnode1, racnode2, racnode3) with instance names RACDB1, RACDB2 and RACDB3 then:

On racnode1 the dbv_RACDB1.env will contain:
RAC_TAKEOVER_SID=RACDB2

On racnode2 the dbv_RACDB2.env will contain:
RAC_TAKEOVER_SID=RACDB3

On racnode3 the dbv_RACDB3.env will contain:
RAC_TAKEOVER_SID=RACDB1

This ensures that if a particular node is unavailable, the 'next' node will takeover log shipment to the standby database(s). And if there are more than 3 nodes in the RAC configuration then you just follow this same approach and specify the 'next' node, in a rolling/circular fashion.

Standby node setup with RAC

The standby database can be configured as a single instance database or as a RAC database with several instances on different standby nodes.
Single standby database instance (Figure 3 – RAC primary database with single instance standby database)

• All primary nodes need to send the archive logs to the single standby node.
• Dbvisit Standby will apply the archives from all threads to the standby database.
• Dbvisit Standby is scheduled on the standby server using the instance name from one of the primary nodes. Example if the RAC configuration has 2 instances called RACDB1 and RACDB2 and the standby database is called RACDB, then Dbvisit Standby is executed on the standby server using the command:

dbvisit RACDB1
RAC standby database instances (Figure 2 – RAC primary database with RAC standby database)

• All primary nodes need to send the archive logs to a shared location on the RAC standby cluster.
• Dbvisit Standby only needs to be scheduled on one standby instance to apply the archives from all threads to the standby database.
• Dbvisit Standby must be dormant on all the other standby nodes. An automated job can be scheduled to enable Dbvisit Standby if it is detected that the standby node on which Dbvisit Standby is active is no longer available.

oracle@dbvrlin301[/usr/local/dbvisit/standby]: ./dbvisit_setup

=========================================================
     Dbvisit Standby Database Technology (6.0.62.11060)
           http://www.dbvisit.com
=========================================================
=>dbvisit_setup only needs to be run on the primary server.
Is this the primary server? <Yes/No> [Yes]:
=========================================================
     Dbvisit Standby Database Technology (6.0.62.11060)
           http://www.dbvisit.com
     Dbvisit Database setup
       Default values will be shown in []
  Options:
       1) New Dbvisit Database setup (combines options 2,3,4)
       1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
       2) New Dbvisit Database configuration (DDC) file setup
       3) New Dbvisit Archive Management Module (AMM) setup
       4) New Dbvisit Database repository (DDR) setup
       5) Manage Dbvisit Database repository (DDR)
       6) Update Dbvisit Database configuration (DDC) file
       7) Create Standby Database (and template)
       8) Synchronize Standby Database
       9) Uninstall Dbvisit Database repository (DDR)
       E) Exit
=========================================================
Please enter choice : 1a
 

    END USER LICENSE AGREEMENT
    PLEASE READ THIS END USER LICENSE AGREEMENT ("AGREEMENT") CAREFULLY
    BEFORE DOWNLOADING THE LICENSED PRODUCT.  BY CLICKING "I AGREE" BELOW, YOU
    ARE REPRESENTING THAT YOU HAVE THE RIGHT AND AUTHORITY TO LEGALLY BIND
    YOURSELF OR YOUR COMPANY, AS APPLICABLE AND YOU ARE AGREEING TO BE BOUND BY
    THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE SUPPORT AGREEMENT.  IF
    YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT AND THE SUPPORT AGREEMENT,
    CLICK "I DO NOT AGREE" AND YOU WILL NOT BE PERMITTED TO DOWNLOAD THE
    LICENSED PRODUCT.
    1. Interpretation.
    The following terms have the following meanings throughout this Agreement:
    "Agreement" means this end user license agreement;
    "Authorized Users" means individuals within Your organization who are
    authorized by you to use the Licensed Product.
    "Error" means a defect in the Licensed Product which causes the Licensed
    Product not to operate substantially in accordance with the specifications
    published in the Documentation.
    "Dbvisit" means Dbvisit Software Limited, a New Zealand company
    (no. 2180317) based in Auckland, New Zealand, except where the Order
    Document expressly states that one of its affiliate companies enters into
    this Agreement, in which case, "Dbvisit" means that specified company.
    "Documentation" means the user and technical documentation for the Licensed
    Product, and any update to the Documentation issued by Dbvisit from time to
    time;
    "License Fee" means the license fees in respect of the Licensed Product set
    out in the Order Document.
    "Licensed Product" means the software product(s)  described in the Order
    Document or downloaded, installed, run, accessed or used by you, the
    accompanying Documentation and any fixes issued to you pursuant to this
    Agreement, and if you purchase Support, updates or new releases in respect
    of that Licensed Product provided to you by Dbvisit in the course of
    providing that Support.
    "Order Document" means the invoice, the purchase quotation or other
    document setting out your order, as issued to you by Dbvisit and
    identifying the Licensed Product(s), any special terms and any associated
    Support you wish to purchase.
    "Support" means maintenance and support services for the Licensed
    Product(s) provided by Dbvisit under the Support Agreement.
    "You" or "Your" means the individual, or other legal entity for which you
    are accepting this Agreement and Authorized Users of that company or
    entity.
<more>
    2. License.
    2.1 License:
    Dbvisit grants you, a non-exclusive, non-assignable, non-sublicensable
    right and license to download, install, run, access and use the Licensed
    Product on the terms and conditions set out in this Agreement. Your use of
    the Licensed Product shall include the right to use one production instance
    of the Licensed Product and make a reasonably necessary number of copies of
    the Licensed Product for the purpose of developing and testing replication
    applications provided that such development and testing is performed on a
    similar environment to the licensed environment and that the applications
    being developed or tested will be applied to the licensed environment.
    You may make a copy for your own back-up archival purposes.  You may print
    reasonable quantities of the Documentation for your own use. All copies of
    the Licensed Product(s) and Documentation shall replicate Dbvisit's
    proprietary rights notices.
    2.2 Delivery & Installation:
    The Licensed Product is provided to you by electronic download from
    authorised web site(s) as described in the Documentation or by delivering
    physical media to you.  You will need to install the Licensed Product on
    properly configured and compatible computer equipment according to the
    system requirements specified in the Documentation and according to the
    license type as specified on the Order Document .  After payment of the
    Licence Fee, Dbvisit will send you a certificate with a software licence
    key for the Licensed Product ("Product Certificate").  You will be required
    to enter that software licence key in order to use the Licensed Product.
    If you fail to pay the License Fee for the Licensed Product within thirty
    (30) days from the date of the applicable Order Document, the Licensed
    Product will cease to function. If you are loading data into the Licensed
    Product, you will also need to ensure that your data is in a proper format.
    If the Licensed Product is to interoperate and exchange data with other
    program(s), you will ensure the Licensed Product and other program(s) are
    properly configured and tested.
    2.3 License Fees:
    You must pay the License Fee by the due date specified in the applicable
    invoice in accordance with the electronic transfer details set out in the
    Order Document.  All fees and payments must be in the currency noted on the
    applicable Order Document.  You are not permitted to use the Licensed
    Product until payment of the License Fee is received by Dbvisit, except in
<more>
    the case of an evaluation version in accordance with (and for the limited
    period specified by) clause 3.1 below. Unless otherwise stated, all amounts
    payable under this Agreement are:
    a)	exclusive of any sales tax, goods and services tax or value added tax
    payable which must be paid by you, if applicable, at the time of payment of
    each invoice; and
    b)	shall be paid gross without deduction of any withholding taxes and, if
    subject to any withholding taxes, you shall ensure that such sum is paid to
    Dbvisit as shall, after deduction of any withholding tax, be equivalent to
    the amount due.
    3. Permitted Use of the Licensed Product.
    3.1 Evaluation Version:
    If you obtained an evaluation version of the Licensed Product, it may be
    installed for the sole purpose of evaluating its features to determine its
    suitability for your needs.  The evaluation version contains a time-out
    feature that will disable its use after 30 days from the date of
    installation.  You may not use the evaluation version or other bundled
    software of the Licensed Product beyond the end of that period.
    3.2 Operating License:
    Subject to your payment of the License Fee by its due date specified in
    the invoice, you may install and use the Licensed Product in accordance
    with the restrictions and limitations set forth in this Agreement and the
    licensing and usage rules for the type of Licensed Product you have
    acquired, as set out in the Documentation and/or Order Document.  Unless
    the Order Document and/or Documentation for the Licensed Product expressly
    states that the Licensed Product is for hosting use, the Licensed Product
    must only be downloaded, installed, run accessed or used for your internal
    use.  If the Order Document and/or the Documentation expressly state that
    the Licensed Product is for hosting use, the Licence Product must only be
    used for hosting (as defined in the applicable Order Document and/or
    Documentation) and must not be used for your internal use.
    4. Reservation of Rights.
    4.1 Your Rights:
    The Licensed Product is licensed, not sold to you.  The intellectual
    property rights in the Licensed Product shall at all times remain the
    exclusive property of Dbvisit or other owner identified in the
    Documentation.  You agree to use the Licensed Product strictly in
<more>
    accordance with this Agreement.  You will not loan, rent, sublicense or
    distribute any part of the Licensed Product to persons not licensed under
    this Agreement through public networks or otherwise except to the extent
    expressly permitted in the licensing and usage rules for the type of
    Licensed Product you have acquired (as set out in the Documentation and/or
    Order Document) or otherwise agreed in writing by Dbvisit.  You agree not
    to disassemble, decompile or reverse engineer the Licensed Product.
    You will ensure that all marks, notices or legends pertaining to the
    origin, identity or ownership of the Licensed Product remain intact and
    clearly legible.  These license rights are personal to you and are
    non-transferable in whole or in part to any other person.
    4.2 Compliance Audit:
    Dbvisit shall have the right, not more than once in each year, to audit
    your compliance with the terms of this Agreement. Such audit shall be
    conducted during your normal business hours upon 20 days prior written
    notice.  You agree to allow Dbvisit and its agents access to your offices,
    records and systems for this purpose.
    5. Product Support.
    By downloading, installing, running, accessing or using the Licensed
    Product you agree to the terms of the DbvisitProtect Support Agreement set
    out at http://www.dbvisit.com/support/resources/ in respect of any support
    services specified in the Order Document or otherwise purchased by you.
    6. Registration & Electronic Communications.
    Dbvisit may require electronic registration of the Licensed Product and
    collect information about your Oracle database and servers, including your
    system configuration, installed software and peripheral devices.  Dbvisit
    may use this information to provide support and to verify your compliance
    with this Agreement.  Dbvisit may send you messages at your registered
    email address for this purpose.
    7. Infringement Indemnity.
    Dbvisit will defend or settle any claim, action or proceeding brought
    against you by a third party alleging that the Licensed Product, as
    provided by Dbvisit to you under this Agreement and used in accordance with
    this Agreement and the Documentation, directly infringes any valid
    copyright, trade mark, patent, or the trade secrets of any third party
    ("Claim") by paying final judgments awarded against you or settlement
    amounts; provided that you have provided Dbvisit with prompt written notice
    of the Claim.  Dbvisit has the sole right to control and direct the defense
<more>
    of any Claim. If the use of any of the Licensed Product is, or in
    Dbvisit's reasonable opinion is likely to be, enjoined, then Dbvisit may,
    at its sole option: (a) procure for you the right to continue using the
    Licensed Product, (b) modify the Licensed Product to make it noninfringing
    while substantially preserving the original functionality;
    (c) replace the Licensed Product with functionally equivalent software; or
    (d) if options (a), (b) and (c) are not commercially reasonable, terminate
    this Agreement and refund the unamortized portion of the License Fees paid
    by you for the Licensed Product, based upon a three (3) year straight-line
    depreciation period commencing on the date you first received such Licensed
    Product.
    8.	Warranty.
    8.1 General Warranty:
    Each party hereby represents and warrants to the other party that it has
    the right and authority to enter into this Agreement.
    8.2 Reproduction Warranty:
    If you obtained the Licensed Product by electronic download from authorised
    website(s), Dbvisit warrants the delivered copy against defects in
    reproduction from the master original.  Dbvisit will provide a free
    replacement of defectively reproduced copies upon proof of purchase. This
    is the sole remedy available to you for breach of the warranty in this
    clause 8.2.
    8.3 Limited Performance Warranty:
    Dbvisit warrants to you that it will use commercially reasonable efforts to
    diagnose and rectify all reproducible Errors that materially affect the
    operation of the Licensed Product for a period of three months from the
    date you receive the Product Certificate.  If you have purchased Support,
    then Dbvisit will respond and use commercially reasonable efforts to
    resolve Errors in accordance with the applicable Support Agreement, rather
    than this Section 8.3.  Dbvisit does not warrant that it will be able to
    correct all reported Errors or that use of the Licensed Product will be
    uninterrupted or error free.  NOTWITHSTANDING THIS WARRANTY, ANY CONTENT
    FILES OR OPEN SOURCE FILES ARE PROVIDED STRICTLY ON AN "AS IS AND AS
    AVAILABLE" BASIS. DBVISIT MAKES NO OTHER WARRANTY, EXPRESS OR IMPLIED, WITH
    RESPECT TO THE LICENSED PRODUCT OR ANY SERVICES AND HEREBY DISCLAIMS ANY
    AND ALL EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, WITHOUT
    LIMITATION, ANY WARRANTIES  OF TITLE, ACCURACY, INTEROPERABILITY,
    INTEGRATION, NONINFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR
<more>
    PURPOSE.
    9. Not Fault Tolerant.
    THE LICENSED PRODUCT IS NOT FAULT TOLERANT AND IS NOT DESIGNED,
    MANUFACTURED OR INTENDED FOR USE IN HAZARDOUS ENVIRONMENTS REQUIRING
    FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES,
    AIRCRAFT NAVIGATION OR COMMUNICATIONS SYSTEMS, AIR TRAFFIC CONTROL, DIRECT
    LIFE SUPPORT MACHINES, OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF THE
    LICENSED PRODUCT COULD LEAD TO DEATH, PERSONAL INJURY OR PHYSICAL OR
    ENVIRONMENTAL DAMAGE.
    10. Limitation of Liability.
    IN NO EVENT SHALL DBVISIT, ITS RESELLERS OR DISTRIBUTORS BE LIABLE, WHETHER
    IN CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, FOR ANY INDIRECT,
    INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING LOST SAVINGS OR PROFIT, LOST
    DATA OR BUSINESS INTERRUPTION EVEN IF DBVISIT IS NOTIFIED IN ADVANCE OF
    SUCH POSSIBILITY).  THIS LIMITATION PROTECTS DBVISIT AND ANY DISTRIBUTOR OR
    RESELLER FROM WHOM YOU OBTAINED THE LICENSED PRODUCT.  SOME JURISDICTIONS
    DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR INCIDENTAL OR
    CONSEQUENTIAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU.
    IN NO EVENT SHALL DBVISIT's LIABILITY FOR DIRECT DAMAGES ARISING UNDER
    THIS AGREEMENT OR RELATING THERETO, EXCEED, THE LICENSE FEES ACTUALLY PAID
    BY YOU FOR THE LICENSED PRODUCT THAT GAVE RISE TO THE LIABILITY.
    11. Term & Termination.
    11.1 General:
    Unless terminated in accordance with this clause, your license will
    continue in perpetuity.  Your license will terminate automatically if you
    breach any provision of this Agreement and fail to cure the breach within
    fifteen (15) days after we have notified you in writing of such breach.
    Your license will immediately terminate if you fail to pay your License Fee
    on the due date or if you breach any of the terms of the Oracle software
    license agreement as notified to us by Oracle.  You may terminate your
    license at any time at your election by permanently deleting the Licensed
    Product from all databases, servers and computers, destroying all copies
    and documentation and ceasing all further use.
    11.2 Effect of Termination:
    Termination of this Agreement will terminate your right to possess or use
    the Licensed Product.  Upon termination for any reason, you agree to
    destroy the original and all copies of the Licensed Product (including
<more>
    Documentation) and cease all further use of it.  Termination will have no
    effect on clause 8 ("Warranties"), clause 9 ("Not Fault Tolerant"),
    clause 10 ("Limitation of Remedies & Liabilities"),
    clause 12 ("Disputes, Choice of Law") and clause 14 ("Payment Default").
    12. Disputes, Choice of Law.
    THIS AGREEMENT SHALL BE GOVERNED BY AND CONSTRUED IN ACCORDANCE WITH THE
    SUBSTANTIVE LAWS OF NEW ZEALAND UNLESS A DIFFERENT STATE's LAWS IS
    EXPRESSLY PRESCRIBED IN THE ORDER DOCUMENT ("SPECIFIED STATE"), IN WHICH
    CASE ONLY THE SPECIFIED STATE's LAWS SHALL APPLY.   THE PARTIES WILL
    INITIATE ANY DISPUTE RESOLUTION PROCEEDING IN NEW ZEALAND OR THE SPECIFIED
    STATE (AS APPLICABLE) AND IRREVOCABLY CONSENT TO THE EXCLUSIVE JURISDICTION
    OF COURTS LOCATED IN NEW ZEALAND OR THE SPECIFIED STATE.  YOU WILL BRING
    ANY ACTION AGAINST DBVISIT ARISING OUT OF THIS AGREEMENT WITHIN ONE YEAR
    AFTER THE CLAIM ARISES, OR BE BARRED.  If Dbvisit is required to enforce
    this Agreement or its rights, you irrevocably agree to receive legal
    notices and papers by electronic mail at your last known email address
    (Dbvisit will also attempt to send you a backup copy by regular mail or
    regular service).
    13. U.S. Government End Users.
    The Licensed Product and related documentation are "Commercial Items" as
    defined in the United States at 48 C.F.R. 2.201, consisting of "Commercial
    Computer Software" and "Commercial Computer Software Documentation" as
    such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202-1 through
    227.7202-4, as applicable.  The Licensed Product and documentation are
    being licensed to U.S. Government end users: (a) only as Commercial Items
    and (b) with only those rights as are granted to all other end users
    pursuant to the terms of this Agreement. Unpublished rights are reserved
    under U.S. Copyright Law.  The Contractor is Dbvisit.
    14. Payment Default.
    If you fail to pay any applicable fees or charges in respect of the
    Licensed Product or Support by the due date for payment specified in an
    invoice then you agree to pay, on demand, the following additional amounts:
    (a) interest on the unpaid License Fee at the rate of 15% per annum from
    the due date to the date of actual payment, (b) US administration fee
    for every week that the License Fee remains unpaid and (c) the actual costs
    of collection incurred by Dbvisit.
    15. Miscellaneous.
    This Agreement constitutes the entire and exclusive agreement between the
<more>
    parties and supersedes all other communications, whether written or oral.
    This Agreement and evidence of its acceptance procedure shall be considered
    an original document with authenticated signature admissible into evidence.
    This Agreement is not assignable, transferable, or sub-licensable by you
    without prior written consent of Dbvisit. This Agreement may be modified or
    amended only by a writing signed by an authorised representative of
    Dbvisit.  It is agreed that resellers and distributors of the Licensed
    Product have no authority to alter this Agreement.  Any provision found by
    a tribunal of competent jurisdiction to be illegal or unenforceable shall
    be automatically conformed to the minimum requirements of law and all
    other provisions shall remain in full force and effect.  Waiver of any
    provision of this Agreement in one instance shall not preclude enforcement
    of it on future occasions. Headings are for reference purposes only and
    have no substantive effect.

Continue ? <Yes/No> [No]: yes
 

------------------------------------------------------------------------------
=>Accept Defaults
Would you like to do a quick setup?
Or would you like Dbvisit to prompt you for all settings and suggest defaults?
Values are Yes or No
Yes = Quick setup (let Dbvisit choose defaults for settings that are not displayed).
No = Dbvisit will prompt for all settings and suggest defaults.
All settings will be displayed at the end of the configuration for review.
Quick setup? [Yes]:
=>Dbvisit will do a quick setup: Yes
Is this correct? <Yes/No> [Yes]:
 

=========================================================
Dbvisit setup begins for RAC.
=========================================================
------------------------------------------------------------------------------
=>
Please specify if this is the first RAC node in the Dbvisit configuration or not.
Values are Yes or No
Yes = First RAC node that Dbvisit is configured for.
No = Dbvisit has been already configured on another node in this RAC configuration.
First Dbvisit RAC node? [Yes]:
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>TMP
Please enter temporary directory for Dbvisit to use.
This directory is used to hold the Dbvisit temporary and trace files.
This directory must exist on the primary and standby servers.
Dbvisit Temporary directory is [/usr/tmp]:
=>Dbvisit Temporary directory will be: /usr/tmp
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>PATH
Please set the PATH to the server (or OS) environment.
Do not include the ORACLE_HOME in the path.
Server environment PATH is [/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/sbin:/sbin]:
=>PATH will be: /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/sbin:/sbin
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
Please specify for which Oracle instance you would like to configure Dbvisit. For RAC, the instance local to this node must be chosen. Not the database. For example, the database
may be called RACDB
and has the following instances: RACDB1 and RACDB2.
Choose RACDB1 or RACDB2 depending on which instance is running on this node.

------------------------------------------------------------------------------
=>ORATAB
Dbvisit can use the oratab file to find all the databases on this server.
If you would like Dbvisit to do this, please enter the location of the oratab file.
Specifying the oratab file is not mandatory.
Oratab file is [/etc/oratab]:
=>Oratab will be: /etc/oratab
Is this correct? <Yes/No> [Yes]:
 

The following Oracle instance(s) have been found on this server:
    SID      ORACLE_HOME
    ===      ===========
1)  TSTRAC1  /u01/app/oracle/product/11.2.0/db_1
2)  TSTRAC   /u01/app/oracle/product/11.2.0/db_1
3)  TST      /u01/app/oracle/product/10.2.0/db_1
4)  TST1     /u01/app/oracle/product/10.2.0/db_1
5)  Enter own ORACLE_SID and ORACLE_HOME
Please enter choice : 4
Is this correct? <Yes/No> [Yes]:
=>ORACLE_SID will be: TST1
=>ORACLE_HOME will be: /u01/app/oracle/product/10.2.0/db_1
 

------------------------------------------------------------------------------
=>OWNER
Please enter the account owner that will be used to run Dbvisit.
It is recommended that this be the same user as the Oracle Database owner.
This user should belong to a DBA group.
This user must also exist on the standby database server.
Account that will run Dbvisit is [oracle]:
=>Account owner will be: oracle
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>RSH (remote shell method)
Please enter remote shell method.
Secure remote shell is ssh.
Non-secure shell is rsh.
For both methods, please ensure that it is configured so that no password or passphrase is required and that it is also installed on the standby server.
See the Dbvisit user guide for more information on how to configure either of these methods.
The following methods have been found on this server:
1)   /usr/bin/ssh
2)   /usr/bin/rsh
3)   Enter own method
Please enter choice [1] :
Is this correct? <Yes/No> [Yes]:
=>Remote shell method will be: /usr/bin/ssh
 

------------------------------------------------------------------------------
=>CP (copy or transfer method)
Please choose copy method, to transfer the (archive) log files from the source server to the standby server.
Secure copy is scp.
Non-secure copy is rcp.
rsync is a copying tool that can work over any remote shell.
For the copy method, please ensure that it is configured so that no password or passphrase is required and that it is also installed on the standby server.
See the Dbvisit user guide for more information on how to configure either of these methods.
The following methods have been found on this server:
1)   /usr/bin/scp
2)   /usr/bin/rcp
3)   /usr/bin/rsync
4)   Enter own method
Please enter choice [1] :
Is this correct? <Yes/No> [Yes]:
=>Transfer method will be: /usr/bin/scp
 

------------------------------------------------------------------------------
=>COMPRESS
Please enter compression method.
if an external compression is used, then this must also exist on the
standby server.
It is recommended to disable any other compression routines
used to compress the Oracle (archive) log files for this database.
If you are unsure, choose option 1.
The following compression methods are available:
1)   Dbvisit internal compression (files will be left compressed on server)
2)   SSH compression (files will not be left compressed on server)
3)   No compression
4)   /usr/bin/gzip
5)   Enter own method
Please enter choice [1] : 4
Is this correct? <Yes/No> [Yes]:
=>Compression method will be: /usr/bin/gzip
=>Uncompression method will be: /usr/bin/gunzip
 

------------------------------------------------------------------------------
=>RAC_TAKEOVER_SID
Specify the instance name that Dbvisit processing should take over if that instance is unavailable.
The instance name must be different to the current instance name (TST1).
The standby database may not be kept up to date if an instance is not available and Dbvisit processing is not taken over by another instance.
RAC Takeover SID is []: TST2
=>RAC Takeover SID will be: TST2
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>SOURCE
Please enter primary server [dbvrlin301]
Primary server is [dbvrlin301]:
=>Primary server will be: dbvrlin301
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ORACLE_BASE
Please enter ORACLE_BASE directory.
ORACLE_BASE is the admin directory for the Databases.
Dbvisit does not use the ORACLE_BASE directly, but it is useful for determining where the log directory of Dbvisit should be.
Entering an ORACLE_BASE is optional.
ORACLE_BASE is [/u01/app/oracle/product/10.2.0/db_1]:
=>ORACLE_BASE will be: /u01/app/oracle/product/10.2.0/db_1
Is this correct? <Yes/No> [Yes]: no
ORACLE_BASE is [/u01/app/oracle/product/10.2.0/db_1]: /u01/app/oracle
=>ORACLE_BASE will be: /u01/app/oracle
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>LOGDIR
Please enter log directory for dbvisit.
This is the directory where the log file for dbvisit will be kept.
Dbvisit will attempt to create this directory first time it executes if it does not exist.
Dbvisit log dir is [/dbvisit]: /usr/local/dbvisit/standby/log
=>Dbvisit log dir will be: /usr/local/dbvisit/standby/log
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>DBUSER
Please enter the Oracle database user that will be used to log onto the database TST1.
This user will also own the Dbvisit Database repository (DDR) [dbvisit].
(This user will be created as part of this setup/configuration).
Dbvisit Oracle user is [dbvisit]:
=>Dbvisit Oracle user will be: dbvisit
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>DBPASSWD
Please enter the password for Dbvisit Oracle database user dbvisit.
The password must start with a letter. Subsequent characters may be letters, numbers, or the symbols # (pound sign), $ (dollar sign) or _ (underscore).
Dbvisit Oracle user dbvisit password is [dbvisitpasswd] *************
Please re-enter password: *************
 

------------------------------------------------------------------------------
=>ORACLE_SID_ASM
If your primary database is using ASM, please set the ASM instance name or leave as default.
If you are not using ASM, then leave it as default (+ASM).
if unsure, leave blank.
ORACLE_SID_ASM on primary server is [+ASM1]:
=>Optional ORACLE_SID_ASM on primary server will be: +ASM1
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=========================================================
Now please enter the information about the
Standby Database
=========================================================
=>DESTINATION
Please enter the name of the standby server (or standby database server).
(Primary server is dbvrlin301)
Standby server is []: dbvrlin305
=>Standby server will be: dbvrlin305
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ORACLE_SID_DEST
If the ORACLE_SID on the standby server dbvrlin305 is different than the ORACLE_SID on the primary server, then it can be specified here.
Default is the same as ORACLE_SID: [TST1]
Please enter instance on standby server dbvrlin305.
Oracle instance on standby server is [TST1]: TST
=>Oracle instance on standby server will be: TST
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ORACLE_BASE_DR
Please enter ORACLE_BASE directory for the standby server dbvrlin305.
ORACLE_BASE is the admin directory for the Databases.
Dbvisit does not use the ORACLE_BASE directly, but it is useful for determining where the log directory of Dbvisit should be on the standby server.
Entering an ORACLE_BASE for the standby server is optional.
ORACLE_BASE for standby server is [/u01/app/oracle]:
=>ORACLE_BASE for standby server will be: /u01/app/oracle
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>BINDIR_DR
Please enter the directory for the dbvisit installation location on the standby server.
This is the directory where the Dbvisit executables will be kept.
This directory must exist on the standby server.
Default location is the same as the on the primary server.

Dbvisit installation dir on the standby server is [/usr/local/dbvisit/standby]:
=>Dbvisit installation dir on the standby server will be: /usr/local/dbvisit/standby
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ARCHDEST
Please enter the directory where Dbvisit will transfer the (archive) log files to on standby server dbvrlin305.
This directory should ONLY contain (archive) log files related to this database. It should not contain any other (non archive log) files.
Please ensure that this directory exists on dbvrlin305 as this cannot be verified.
It is advisable to also create this directory on the primary server dbvrlin301 for graceful switchover to work.
Archive log dir on the standby server is [/oracle/oraarch/TST1]: /u01/app/oracle/dbvisit_archdest/TST
=>Archive log dir on the standby server will be: /u01/app/oracle/dbvisit_archdest/TST
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>MAX_TIMES_TRIED
Please specify the number of times that Dbvisit should attempt to apply the missing log file before raising an error.
Note this number is also used to raise an error if Dbvisit cannot be started in case a previous scheduled Dbvisit is still running.
Ensure that this number is not too low and not too high.
If you are unsure, set to 4
Maximum attempts before raising error when log file is not there is [4]:
=>Maximum attempts before raising error when log file is not there will be: 4
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ORACLE_SID_ASM_DEST
If your standby database is using ASM and ASM instance name on the standby server dbvrlin305
is different than the ASM instance name on the primary server dbvrlin301, then it can be specified here.
Default is the same as ORACLE_SID_ASM: [+ASM1]
If you are not using ASM, then leave it as default.
if unsure, leave blank.
ORACLE_SID_ASM_DEST on standby server is [+ASM1]: +ASM
=>Optional ORACLE_SID_ASM_DEST on standby server will be: +ASM
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>MAILCFG_MAIL_CLIENT
The default mail client is sendmail.
sendmail will need to be configured on this server in order to send mail.
(sendmail does not need to be running in the background to send mail)
Dbvisit comes with its own internal smpt mail client.
If Dbvisit mail client is to be used, specify "Dbvisit".
Alternate mail clients can be set after completing setup.
Please see MAILCFG_SENDMAIL_CLIENT.
Mail client is [sendmail]:
=>Mail client will be: sendmail
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ADMINS
Please enter the administrator email address(es) where emails will be sent upon
success or failure of Dbvisit. Multiple emails
should be separated with a comma (,).
Sample:
support@mycompany.com,dba@mycompany.com
Administrators email is [oracle@dbvrlin301]:
=>Administrators email will be: oracle@dbvrlin301
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>MAILCFG_FROM
Please enter the FROM email address of this server (optional).
If this is not specified when using Dbvisit internal mail, the emails may not arrive.
Mail FROM address is [oracle@dbvrlin301.com]: oracle@dbvrlin301
=>Mail FROM address will be: oracle@dbvrlin301
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>MAILCFG_FROM_DR
Please enter the FROM email address of the standby server (optional).
If this is not specified when using Dbvisit internal mail, the emails may not arrive.
Mail FROM_DR address is [oracle@dbvrlin305.com]: oracle@dbvrlin305
=>Mail FROM_DR address will be: oracle@dbvrlin305
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=========================================================
Primary Archive log Management Module Settings (AMM)
=========================================================
=>ARCHSOURCE_MANAGEMENT
Do you want to setup (archive) log file management on the primary server?
This is used to manage the Oracle logs on the primary server.
- Alerts when certain thresholds have been reached.
- Can delete Oracle archives logs after a set number of days.
- Can keep a constant number of Oracle archive logs on the system.
Values are Yes or No
Yes = Setup and use AMM on primary server.
No = do not use AMM on primary server.
If you are unsure, set to Yes.
Should Dbvisit Archive Log Management Module be used on primary server? [Yes]:
=>Dbvisit Archive Log Management Module on primary server will used: Yes
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>DAYS_TO_KEEP_ARCHSOURCE
Please specify the number of days to keep the Oracle log files on the primary server.
After this the log files will be removed from the server.
To disable this setting, set to 0.
If you are unsure, set to 7
Number of days to keep log files on disk is [7]:
=>Number of days to keep log files on disk will be: 7
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>NUM_ARCHSOURCE_TO_KEEP
Please specify the number of archive log files to keep on the primary server.
Log files greater than this number will be removed (oldest first).
To disable this setting, set to 0.
If you are unsure, set to 0 (disable).
Number of log files to keep on disk is [0]:
=>Number of log files to keep on disk will be: 0
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>ARCHSOURCE_BACKUP_COUNT
Please specify the number of times an archive log has to be backed up by RMAN
before it is deleted from the primary server by Dbvisit Standby.
Values range from 0-15 and is only applicable if RMAN is used to backup archive
log files. This parameter is only applicable to Oracle versions 9 or higher.
To disable this setting, set to 0.
If you are unsure, set to 0 (disable).
Archive log backup count is [0]:
=>Archive log backup count will be: 0
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>THRESHOLD_ARCHSOURCE
Please specify the threshold in percentage (%) of how much disk space may be taken up by the Oracle log files on disk before an alert is triggered on the primary server.
80 means at 80% disk space full an alert will be triggered.
Please specify threshold as an integer.
If you are unsure, set to 80.
Threshold for log file management is [80]:
=>Threshold for log file management will be: 80
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>FRA_THRESHOLD_ARCHSOURCE
Please specify the threshold in percentage (%) of how much FRA space may be taken up by the Oracle log files on disk before an alert is triggered on the primary server.
This setting is valid only for Oracle databases versions 10 or higher that have FRA enabled in the primary database.
80 means at 80% FRA full an alert will be triggered.
To disable this setting, set to 0.
Please specify threshold as an integer.
FRA threshold for log file management is [0]:
=>FRA threshold for log file management will be: 0
Is this correct? <Yes/No> [Yes]:
------------------------------------------------------------------------------
=>DELETE_ARCHSOURCE
Please specify if (archive) log files should be deleted once the threshold (THRESHOLD_ARCHSOURCE) on the primary server is reached.
Once the percentage threshold is reached oldest (archive) log files are deleted first.
The log files WILL have been transferred to the standby server.
(There is no verification that these log files have been backed up).
Values are Yes or No
Yes = Let Dbvisit delete (archive) log files once percentage threshold is met.
No = Dbvisit will only alert once percentage threshold (no log files will be deleted).
If you are unsure, set to No.
Should Dbvisit Archive Log Management Module delete log files once percentage threshold is met? [No]:
=>Dbvisit Archive Log Management Module will delete log files once percentage threshold is met: No
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=========================================================
Standby Archive log Management Module Settings (AMM)
=========================================================
=>ARCHDEST_MANAGEMENT
Do you want to setup (archive) log file management on the standby server?
This is used to manage the Oracle logs on the standby server.
- Alerts when certain thresholds have been reached.
- Can delete Oracle archives logs after a set number of days.
- Can keep a constant number of Oracle archive logs on the system.
Values are Yes or no
Yes = Setup and use AMM on standby server.
No = do not use AMM on standby server.
If you are unsure, set to Yes.
Should Dbvisit Archive Log Management Module be used on standby server? [Yes]:
=>Dbvisit Archive Log Management Module on standby server will used: Yes
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>DAYS_TO_KEEP_ARCHDEST
Please specify the number of days to keep the Oracle log files on the standby server.
After this the log files will be removed from the server.
To disable this setting, set to 0.
If you are unsure, set to 7
Number of days to keep log files on disk is [7]:
=>Number of days to keep log files on disk will be: 7
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>NUM_ARCHDEST_TO_KEEP
Please specify the number of archive log files to keep on the standby server.
Log files greater than this number will be removed (oldest first).
To disable this setting, set to 0.
If you are unsure, set to 0 (disable).
Number of log files to keep on disk is [0]:
=>Number of log files to keep on disk will be: 0
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>THRESHOLD_ARCHDEST
Please specify the threshold in percentage (%) of how much disk space may be taken up by the Oracle log files on disk before an alert is triggered on the standby server.
80 means at 80% disk space full an alert will be triggered.
Please specify threshold as an integer.
If you are unsure, set to 80.
Threshold for log file management is [80]:
=>Threshold for log file management will be: 80
Is this correct? <Yes/No> [Yes]:
 

------------------------------------------------------------------------------
=>DELETE_ARCHDEST
Please specify if (archive) log files should be deleted once the threshold (THRESHOLD_ARCHDEST) on the standby server is reached.
Once the percentage threshold is reached oldest (archive) log files are deleted first.
The log files WILL have been applied to the standby database.
(There is no verification that these log files have been backed up).
Values are Yes or No
Yes = Let Dbvisit delete (archive) log files once percentage threshold is met.
No = Dbvisit will only alert once percentage threshold (no log files will be deleted).
If you are unsure, set to No.
Should Dbvisit Archive Log Management Module delete log files once percentage threshold is met? [No]:
=>Dbvisit Archive Log Management Module will delete log files once percentage threshold is met: No
Is this correct? <Yes/No> [Yes]:
------------------------------------------------------------------------------
Would you like to review all the variables? <Yes/No> [Yes]:
 

=====10 Generic Settings=====
1) TMP=/usr/tmp
2) PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/sbin:/sbin
3) ORATAB=/etc/oratab
4) ORACLE_SID=TST1
5) ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
6) OWNER=oracle
7) RSH=/usr/bin/ssh
8) CP=/usr/bin/scp
9) COMPRESS=/usr/bin/gzip
10) UNCOMPRESS=/usr/bin/gunzip
11) ZIP_EXTENSION=.gz
12) SEND_HEARTBEAT_TIME24=0700
=====15 RAC Settings=====
13) RAC=Y
14) RAC_TAKEOVER=Yes
15) RAC_TAKEOVER_FORCE=No
16) RAC_TAKEOVER_SID=TST2
=====20 Primary Server Settings=====
17) SOURCE=dbvrlin301
18) BINDIR=/usr/local/dbvisit/standby
19) ORACLE_BASE=/u01/app/oracle
20) LOGDIR=/usr/local/dbvisit/standby/log
21) ENCRYPT_PASSWDS=No
22) DBUSER=dbvisit
23) DBPASSWD=******
24) LEAVE_COMPRESS_SOURCE=No
25) SYNCH_DBVISIT_INSTALL=Yes
26) LOGSWITCH=No
27) ORACLE_SID_ASM=+ASM1
=====25 Sys Logon Settings=====
28) SYS_LOGON=No
29) SYS_USER=sys
30) _SYS_PASSWD=
31) SYS_LOGON_STRING=as sysdba
=====30 Standby Server Settings=====
32) DESTINATION=dbvrlin305
33) SSH_PORT=22
34) ORACLE_SID_DEST=TST
35) ORACLE_BASE_DR=/u01/app/oracle
36) BINDIR_DR=/usr/local/dbvisit/standby
Are these variables correct? <Yes/No> [Yes]:
=====30 Standby Server Settings=====
37) LOGDIR_DR=/usr/local/dbvisit/standby/log
38) ARCHDEST=/u01/app/oracle/dbvisit_archdest/TST
39) LEAVE_COMPRESS_DEST=Yes
40) MAX_TIMES_TRIED=4
41) ORACLE_SID_ASM_DEST=+ASM
=====40 Mail Settings=====
42) MAILCFG_MAIL_CLIENT=sendmail
43) ADMINS=oracle@dbvrlin301
44) MAILCFG_FROM=oracle@dbvrlin301
45) MAILCFG_FROM_DR=oracle@dbvrlin305
46) SUCCESSMAIL=Yes
47) SUCCESSMAIL_DR=Yes
=====50 Primary Archive Log Management Settings=====
48) ARCHSOURCE_MANAGEMENT=Yes
49) DAYS_TO_KEEP_ARCHSOURCE=7
50) NUM_ARCHSOURCE_TO_KEEP=0
51) ARCHSOURCE_BACKUP_COUNT=0
52) THRESHOLD_ARCHSOURCE=80
53) FRA_THRESHOLD_ARCHSOURCE=0
54) DELETE_ARCHSOURCE=No
=====60 Standby Archive Log Management Settings=====
55) ARCHDEST_MANAGEMENT=Yes
56) DAYS_TO_KEEP_ARCHDEST=7
57) NUM_ARCHDEST_TO_KEEP=0
58) THRESHOLD_ARCHDEST=80
59) DELETE_ARCHDEST=No
Are these variables correct? <Yes/No> [Yes]:
Redisplay all variables again? <Yes/No> [No]:
 

------------------------------------------------------------------------------
=>DDC File
Please specify the name of the Dbvisit Database Configuration (DDC) file.
The DDC file contains all the Dbvisit Standby settings.
The DDC file is a plain text file and can be edited manually or through this setup.
Dbvisit Database Configuration (DDC) file is [TST1]:
=>Dbvisit Database Configuration (DDC) file will be: TST1
Is this correct? <Yes/No> [Yes]:
=>Dbvisit Database configuration (DDC) file /usr/local/dbvisit/standby/dbv_TST1.env created.
------------------------------------------------------------------------------
=>Creating Dbvisit Database repository (DDR).
Database TST1 is up.

------------------------------------------------------------------------------
Please select the default tablespace to install the Dbvisit Database repository (DDR).
The following tablespaces are available:
     Tablespace
     ===========
1)   USERS
2)   Refresh list
Please enter choice : 1
The default tablespace will be: USERS
Is this correct? <Yes/No> [Yes]:
 
------------------------------------------------------------------------------
Please select the temp tablespace to install the Dbvisit Database repository (DDR).
The following tablespaces are available:
     Tablespace
     ===========
1)   TEMP
2)   USERS
3)   Refresh list
Please enter choice : 1
The temp tablespace will be: TEMP
Is this correct? <Yes/No> [Yes]:
 

Dbvisit will now create the Dbvisit Database repository (DDR). Continue (Yes) or return to the menu? <Yes/Return> [Yes]:
User dbvisit created.
Grants to user dbvisit completed.
Dbvisit Database repository (DDR) for dbvisit created.
=========================================================
     Dbvisit configuration completed.
   IMPORTANT!
      Ensure servers dbvrlin301 and dbvrlin305
      are setup for:
            /usr/bin/scp
            /usr/bin/ssh
      without needing a password or passphrase.
   IMPORTANT!
      Ensure the following directories are setup on
      standby server dbvrlin305 with the correct permissions:
      1) /u01/app/oracle
      2) /u01/app/oracle/dbvisit_archdest/TST
      3) /usr/local/dbvisit/standby
 Next steps:
Create standby database using option in main menu:
      7) Create Standby Database
=========================================================
Please press <Enter> to return to main menu...
=========================================================
 

     Dbvisit Standby Database Technology (6.0.62.11060)
           http://www.dbvisit.com
     Dbvisit Database setup
       Default values will be shown in []
  Options:
       1) New Dbvisit Database setup (combines options 2,3,4)
       1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
       2) New Dbvisit Database configuration (DDC) file setup
       3) New Dbvisit Archive Management Module (AMM) setup
       4) New Dbvisit Database repository (DDR) setup
       5) Manage Dbvisit Database repository (DDR)
       6) Update Dbvisit Database configuration (DDC) file
       7) Create Standby Database (and template)
       8) Synchronize Standby Database
       9) Uninstall Dbvisit Database repository (DDR)
       E) Exit
=========================================================
Please enter choice : E
=========================================================


 
     Dbvisit setup completed.
 Any changes to the configuration can be made by either:
1) Manually by editing dbv_TST1.env.
2) Running dbvisit_setup and choosing option:
     -> 6) Update Dbvisit Database configuration (DDC) file
Next steps:
1) Run Dbvisit on this server with command:
       (cd /usr/local/dbvisit/standby)
       dbvisit TST1
2) Run Dbvisit on standby server with command:
       (cd /usr/local/dbvisit/standby)
       dbvisit TST1
Once Dbvisit has been tested, schedule Dbvisit on primary and standby servers using cron or other scheduling tool.
=========================================================