You can find requirements for Dbvisit StandbyMP software installation on this page. There are requirements which common for all installation, and requirements which are platform specific (Windows / Linux) and also specific for each database platform.
You always need to fullfill all applicable requirements to your concrete installation at the same time. For example, if installing Dbvisit StandbyMP on Windows Oracle Server, you will need to fulfill Common Requirements, OS Platform Windows Requirements and Database Platform Oracle Requirements.
| Table of Contents | ||
|---|---|---|
|
...
Dbvisit StandbyMP supports following SMTP server communication protocols: StartTLS ,TLS/SSL or NoEncryption.
2. OS Platform
...
Requirements
These requirements must be satisfied When installing Dbvisit StandbyMP on specific OS platform (Windows/Linux).
...
Following is a list of Linux platform specific requirements.
Default installation directory is /usr/dbvisit (this can be modified during installation)
We recommend to installing Dbvisit StandbyMP as same OS user which runs Database Engine (oracle, postgres …)
If you have dedicated mount for /tmp, make sure it is NOT mounted with “noexec” option. This can be verified with for example “mount -l” command.
After the Dbvisit StandbyMP installation, user can choose to create systemctl service for dbvagentmanager and dbvcontrol to automate startup. In this case, root access will be required to start and stop these components.
SELINUX must be set to disabled or permissive. In Enforcing mode SELINUX will prevent dbvagentmanager and dbvcontrol services from working correctly. You can find out the status by running:
...
Chronyd and ntpd services will ensure system date correct synchronization. If system date is not synchronized, there can be issues with connection issues because of certificates validity (which is based on actual date).
2.2 Windows
If installing Dbvisit Standby onto a Windows Based environment the following pre-requisite checks should be performed:
A. User performing Installation
This is for example any named user administrator account who will perform Dbvisit StandbyMP software installation.
The User performing installation of Dbvisit Standby may be a local or a domain user who is part of Local Administrators group
Default installation directory is C:\Program Files\Dbvisit (this can be modified during installation). User running the Dbvisit installation will assume ownership of installation directory C:\Program Files\Dbvisit
B. Dbvisit StandbyMP User specified during installation
During Dbvisit StandbyMP installation you will be prompted for username and password. This user will be used for running Dbvisit StandbyMP dbvagentmanager service and will be interacting directly with the database engine.
This user needs to be local or a domain user who is part of Local Administrators group
This user needs to be granted the "Log On As Service" policy to allow the user to run the Dbvisit Standby Services. To grant, run from command line:
| Code Block |
|---|
secpol.msc |
And afterwards add user:
...
This user must have complete privileges to interact with the database Engine present on the server
| Info |
|---|
During installation, it is possible to not specify any user for Dbvisit StandbyMP dbvagentmanager service. In such case, dbvagentmanager service will be created to run as “Local System” |
| Info |
|---|
Dbvisit StandbyMP dbvcontrol service is always created to run as “Local System” |
| Note |
|---|
We highly recommend that user performing the installation = Dbvisit StandbyMP User specified during installation = user running database engine on the server. For example if your Oracle Database Instance service runs as domain user Mycompany\oracle we recommend using this user for Dbvisit StandbyMP installation as well as specifying this username for the dbvagentmanager service during installation. |
C. Other Requirements
For installation It is recommended that User Account Control be turned off - not strictly required, but highly recommended.
For the duration of installation it is recommended to turn of any 3rd party antivirus software (excluding Windows Defender). It can be enabled again after installation is completed, if whole Dbvisit installation directory is whitelisted and excluded from scan
3. Database Platform Requirements
Below you will find requirements specific for individual database platform. There are different requirements for Windows and Linux platforms.
3.1 Oracle
A. Linux
We strongly recommend to use user who was used for oracle home installation (typically oracle) for installation of Dbvisit StandbyMP prouct
Installation user must have same user and group id equivalency on primary and standby server:
| Code Block |
|---|
[oracle@czlin0231 ~]$ id
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba),54323(oper),54324(backupdba),54325(dgdba),54326(kmdba),54330(racdba) |
B. Windows
User who is selected to run Dbvisit StandbyMPdbvagentmanager service during installation must be member of following groups:
| Code Block |
|---|
ora_dba
Local Administrators
Oracle Home DBA group - (if using 12c make sure the user is in the new Oracle Home DBA group) |
| Note |
|---|
Any operating system user who will work with Dbvisit StandbyMP product in the future (for example using dbvctl or dbvcli command line tools) must be member of those groups as well |
C. Common
Dbvisit StandbyMP doesn’t require Oracle Listener for its operation
When installing Dbvisit on RAC or SEHA environments, additional prerequisites must be fulfilled. See Oracle RAC and SEHA documentation for further details: <<<< TBD >>>>>
ORACLE_HOME system-wide environment variable must be set to existing oracle home software location
PATH system-wide environment variable must include ORACLE_HOME\bin directory