.com Solutions Inc. - Installgen Graphical Interface

Installgen - Graphical Interface - Title Graphic

The Installgen Backup folder tab contains fields to implement the configuration of backup and recovery of the primary database instance and the configuration of a standby database instance.

Installgen Backup Folder tab - 33K

menu: Archivelog
If the database will be running in Archivelog mode, the "Yes" menu item should be selected. In general, this menu item should always be selected as "Yes". Archivelog mode will be configured during the database build process if "Yes" is selected.

field: Archivelog Location
This field contains the name of a directory where the archivelog files will be written by the database. This directory should be large enough to contain more than one day's worth of archivelog files. If RMAN backups are selected on this same folder tabbed section, then the archivelog files will be backed up automatically then removed every night during the backup process.

field: Backup/Export file location
Ideally this directory should be large enough to contain a full database backup, plus a backup of all of the archivelog files, and maybe even a full database export file as well.This directory is also the location where the nightly disaster recovery file will be written. The system administrator can conveniently back up this directory to tape.

menu: RMAN Backup Type
Slight changes are made to the output files by selecting RMAN-OEM vs the other menu selections which are available. However use of the alternate backup techniques is selectable via a prompt when running the post install database configuration script.
The RMAN-OEM selection makes use of another server to store the backup catalog and OEM repository information. It is expected that the same server is being used for the OEM/OMS server and the RMAN catalog (however different tablespaces are used).
The RMAN-CRON selections refers to the use of the database controlfile to store the backup information which would be required to perform a database restore. This information would potentially not be available within the controlfile in the event of a disaster affecting the database server.

field: RMAN Channel Type
The RMAN Channel Type can be "Disk", "sbt_tape" - for tape or the name of the Legato or Veritas media manager configuration being used on the server.

field: RMAN Channel Name
The name to be used for the RMAN channel should be entered here.

field: RMAN Archivelog Channel Format
The format of the RMAN channel which is to be used for RMAN backup scripts when archivelog files are backed up. The channel format includes the path to use to backup the files on the server's hard drive and also the format of the backup file piece names.

field: RMAN Backup Channel Format
The format of the RMAN channel which is to be used for RMAN backup scripts when database data files files are backed up. The channel format includes the path to use to backup the files on the server's hard drive and also the format of the backup file piece names.

menu: OEM/RMAN Server Type
The type of hardware OEM/OMS database is being installed. This information is used for creating the database diagram file. This file is created when there are multiple databases being used together in an OEM/OMS server configuration. This info is used solely for documentation purposes.

field: RMAN Backup Time (24hr format)
This field contains the time when database backups should be scheduled. This information is used for documentation and scheduling purposes to actually schedule the backup job.

field: OEM/RMAN Repository Hostname
The hostname of the server which will contain the OEM/OMS database. This server will contain the OEM Repository and the RMAN backup catalog.
Note: In order for proper functionality of OEM/OMS server communications, both the forward and reverse DNS information must match.

field: OEM/RMAN Repository IP Address
The IP Address of the Oracle database server. This parameter will be used when building the /etc/hosts file on UNIX servers.
Note: In order for proper functionality of OEM/OMS server communications, both the forward and reverse DNS information must match.

field: Additional OEM databases
This field contains a list of additional database instances which will be managed via the OEM/OMS server. This information is used within tnsnames.ora files, and is also used to create the database diagram documentation file.

field: Additional OEM hosts
This field contains a list of the host names of the additional databases which will be managed by the OEM/OMS server. This information is used within tnsnames.ora files, and is also used to create the database diagram documentation file.

field: OEM/RMAN Repository SID
The database SID which will contain the OEM repository and the RMAN backup catalog. The SID can be up to 8 characters long, including underscore characters, letter and numbers.

field: OEM Dbdomain
The OEM Dbdomain (if entered) will be added to the OEM SID to create the full name of the database instance. The format of this name will be OEM SID.Dbdomain. If this field is left blank, the OEM database name will be the same as the OEM SID.

field: OEM Tablespace Name
The name of the tablespace which will be created to contain the OEM Repository tables.

field: OEM Tablespace Size
This size of the tablespace which will be created to hold the OEM Repository tables. Generally this size may start at 50Mb and increase to a higher amount if large numbers of servers are being managed.

field: OEM Tablespace Path
The pathname to use when creating the OEM Repository tablespace.

field: OEM Username
The username for the Oracle database account which will own the OEM repository tables.

field: OEM Owner Account Password
The password for the Oracle database account which will own the OEM repository tables.

field: RMAN Tablespace Name
The name of the tablespace which will contain the RMAN backup catalog tables.

field: RMAN Tablespace Size
This size of the tablespace which will be created to hold the RMAN backup catalog tables.

field: RMAN Tablespace Path
The pathname to use when creating the OEM Repository tablespace.

field: RMAN Owner Account Username
The username for the Oracle database account which will own the RMAN backup catalog tables.

field: RMAN Owner Account Password
The password for the Oracle database account which will own the RMAN backup catalog tables.

field: Standby Database Hostname
The hostname of the server which will contain the standby database. This standby database will be created from the primary server database data. The primary database is referenced by the SID listed on the "General" folder tab.

field: Standby Database IP Address
The IP Address for the standby database server. This information is used with tnsnames.ora files used on the primary and standby servers.

field: Standby Database Delay (Hrs)
To prevent user errors (like a dropped table) from destroying both the primary and the standby database servers, a delay may be implemented. The standby server will delay applying archivelog files received from the primary server for the specified interval listed here in order to allow the DBA to have time to activate the standby database before the damaging transaction is applied to the standby server. If no delay is desired, a value of 0 should be entered.

			The Installgen Backup folder tab contains fields to implement the configuration of backup and recovery of the primary database instance and the configuration of a standby database instance. menu: Archivelog If the database will be running in Archivelog mode, the "Yes" menu item should be selected. In general, this menu item should always be selected as "Yes". Archivelog mode will be configured during the database build process if "Yes" is selected. field: Archivelog Location This field contains the name of a directory where the archivelog files will be written by the database. This directory should be large enough to contain more than one day's worth of archivelog files. If RMAN backups are selected on this same folder tabbed section, then the archivelog files will be backed up automatically then removed every night during the backup process. field: Backup/Export file location Ideally this directory should be large enough to contain a full database backup, plus a backup of all of the archivelog files, and maybe even a full database export file as well.This directory is also the location where the nightly disaster recovery file will be written. The system administrator can conveniently back up this directory to tape. menu: RMAN Backup Type Slight changes are made to the output files by selecting RMAN-OEM vs the other menu selections which are available. However use of the alternate backup techniques is selectable via a prompt when running the post install database configuration script. The RMAN-OEM selection makes use of another server to store the backup catalog and OEM repository information. It is expected that the same server is being used for the OEM/OMS server and the RMAN catalog (however different tablespaces are used). The RMAN-CRON selections refers to the use of the database controlfile to store the backup information which would be required to perform a database restore. This information would potentially not be available within the controlfile in the event of a disaster affecting the database server. field: RMAN Channel Type The RMAN Channel Type can be "Disk", "sbt_tape" - for tape or the name of the Legato or Veritas media manager configuration being used on the server. field: RMAN Channel Name The name to be used for the RMAN channel should be entered here. field: RMAN Archivelog Channel Format The format of the RMAN channel which is to be used for RMAN backup scripts when archivelog files are backed up. The channel format includes the path to use to backup the files on the server's hard drive and also the format of the backup file piece names. field: RMAN Backup Channel Format The format of the RMAN channel which is to be used for RMAN backup scripts when database data files files are backed up. The channel format includes the path to use to backup the files on the server's hard drive and also the format of the backup file piece names. menu: OEM/RMAN Server Type The type of hardware OEM/OMS database is being installed. This information is used for creating the database diagram file. This file is created when there are multiple databases being used together in an OEM/OMS server configuration. This info is used solely for documentation purposes. field: RMAN Backup Time (24hr format) This field contains the time when database backups should be scheduled. This information is used for documentation and scheduling purposes to actually schedule the backup job. field: OEM/RMAN Repository Hostname The hostname of the server which will contain the OEM/OMS database. This server will contain the OEM Repository and the RMAN backup catalog. Note: In order for proper functionality of OEM/OMS server communications, both the forward and reverse DNS information must match. field: OEM/RMAN Repository IP Address The IP Address of the Oracle database server. This parameter will be used when building the /etc/hosts file on UNIX servers. Note: In order for proper functionality of OEM/OMS server communications, both the forward and reverse DNS information must match. field: Additional OEM databases This field contains a list of additional database instances which will be managed via the OEM/OMS server. This information is used within tnsnames.ora files, and is also used to create the database diagram documentation file. field: Additional OEM hosts This field contains a list of the host names of the additional databases which will be managed by the OEM/OMS server. This information is used within tnsnames.ora files, and is also used to create the database diagram documentation file. field: OEM/RMAN Repository SID The database SID which will contain the OEM repository and the RMAN backup catalog. The SID can be up to 8 characters long, including underscore characters, letter and numbers. field: OEM Dbdomain The OEM Dbdomain (if entered) will be added to the OEM SID to create the full name of the database instance. The format of this name will be OEM SID.Dbdomain. If this field is left blank, the OEM database name will be the same as the OEM SID. field: OEM Tablespace Name The name of the tablespace which will be created to contain the OEM Repository tables. field: OEM Tablespace Size This size of the tablespace which will be created to hold the OEM Repository tables. Generally this size may start at 50Mb and increase to a higher amount if large numbers of servers are being managed. field: OEM Tablespace Path The pathname to use when creating the OEM Repository tablespace. field: OEM Username The username for the Oracle database account which will own the OEM repository tables. field: OEM Owner Account Password The password for the Oracle database account which will own the OEM repository tables. field: RMAN Tablespace Name The name of the tablespace which will contain the RMAN backup catalog tables. field: RMAN Tablespace Size This size of the tablespace which will be created to hold the RMAN backup catalog tables. field: RMAN Tablespace Path The pathname to use when creating the OEM Repository tablespace. field: RMAN Owner Account Username The username for the Oracle database account which will own the RMAN backup catalog tables. field: RMAN Owner Account Password The password for the Oracle database account which will own the RMAN backup catalog tables. field: Standby Database Hostname The hostname of the server which will contain the standby database. This standby database will be created from the primary server database data. The primary database is referenced by the SID listed on the "General" folder tab. field: Standby Database IP Address The IP Address for the standby database server. This information is used with tnsnames.ora files used on the primary and standby servers. field: Standby Database Delay (Hrs) To prevent user errors (like a dropped table) from destroying both the primary and the standby database servers, a delay may be implemented. The standby server will delay applying archivelog files received from the primary server for the specified interval listed here in order to allow the DBA to have time to activate the standby database before the damaging transaction is applied to the standby server. If no delay is desired, a value of 0 should be entered.

			Home \| Products \| Services \| Downloads \| Order \| Support \| Contact Legal Notices