The Installgen application generates the scripts required to install,
build, backup and document an Oracle database installation. The scripts
created by Installgen implement Oracle´s best practices for over
100 tasks required when performing the installation of Oracle database
servers. This graphical application generates dozens of scripts, configuration
files and documentation within a few seconds. An external module allows
site-specific customization of each generated file.
Installgen generates 52 output files for an Oracle 8.1.7
installation on Windows. These example files are listed below along
with links to diagrams where necessary.
| File# |
Filename |
Extras |
Features |
| 1 |
1_win_817_prepinstall_1.bat |
|
This windows batch file requests that
a shared directory be created and shared on the new Oracle db server.
The install scritps, and utilities are then copied to the shared
directory from the ora_build1 and ora_build4 CDs in the D: drive. |
| 2 |
2_win_817_prepinstall_1.bat |
|
This windows batch file prompts the user
to install the Microsoft MSI installer, Activestate perl, and winzip
eval version. |
| 3 |
3_win_817_prepinstall_1.pl |
|
This script creates c:\archive, c:\backup,
c:\v817 c:\server_scripts and Oracle OFA directories. The Oracle
installation CDs are copied to the server hard drive if requested
by the user. Oracle database software is installed using response
files in silent mode of the Oracle Java-based installer, for the
database and OEM/OMS software.
The database build process is started by executing file: 17_win_817_db_build_1_2.pl |
| 4 |
4_win_817_postinstall_1.pl |
|
This perl script applies the latest patch
to the database and installs the backup, performance tuning and
export jobs. |
| 11 |
11_win_prod3_rotate_alert_log_1.pl |
|
This perl script runs as a Windows Service
during system startup to rotate the Oracle alert.log file. [This
task must be done upon system startup because the alert.log is always
open while the database is running.] |
| 13 |
13_win_rotateoraclefiles_1.pl |
|
This perl script runs nightly via AT
job to remove/rotate Oracle files.
|
| 17 |
17_win_817_db_build_1_1.pl |
|
This perl script is the main script which
builds the Oracle database. |
| 18 |
18_win_817_build_jserver_1.sql |
|
This shell script adds the JServer feature
to the Oracle database. |
| 19 |
19_win_817_build_intermedia_1.sql |
|
This sql script adds the Intermedia feature
to the Oracle database.
|
| 20 |
20_win_817_build_spatial_1.sql |
|
This sql script adds the Spatial feature
to the Oracle database.
|
| |
21_win_817_build_time_series_1.sql |
|
This sql script adds the Time Series
feature to the Oracle database. |
| 23 |
23_win_817_build_sqlplus_help_1.sql |
|
This sql script adds the SQL Plus Help
feature to the Oracle database.
|
| 24 |
24_win_initprod1_1.ora |
|
This file provides the initial
configuration for the Oracle database instance (Windows NT/2000
version). |
| 25 |
25_win_817_tnsnames_1.ora |
|
This file provides configuration
information for Oracle Net8.
|
| 27 |
27_win_817_rman_oem_setup_1.pl |
|
This shell script registers
a production database into the RMAN recovery catalog. This script
is run from the production server, not the OEM/OMS server. |
| 29 |
29_win_817_rman_backup_job_1.pl |
|
This perl script performs
an RMAN full database backup of all datafiles, archivelogs and the
control file. This RMAN backup procedure uses the controlfile for
storage of information about backup sets. |
| 30 |
30_win_817_prod3_rman_restore_db_1.pl |
|
This perl script performs an RMAN full database restore in the
case where all datafiles have been lost.
|
| 31 |
31_win_prod3_closed_db_backup_job_1.pl |
Diagram
disaster_recovery.txt
|
This perl script performs
a closed database backup to the c:\backup location. This script
also builds the closed database restore script when it builds the
perl script for the backup.
Note: This script only needs scheduled if the same task has not
been scheduled via an OEM job. |
| 33 |
33_win_prod3_open_db_backup_job_1.pl |
Diagram
disaster_recovery.txt
|
This perl script creates
a sql script which performs an open database backup to the c:\backup
location. It then executes the sql script it builds in order to
perform the backup. This script also builds the open database restore
sql file when it builds the sql file for the backup. A DBVERIFY
is performed on each of the backup files created during the backup
process.
Note: This script only needs scheduled if the same task has not
been scheduled via an OEM job. |
| 35 |
35_win_prod3_export_full_db_1.pl |
|
This perl script performs
a full database export to the c:\backup location.
Note: This script only needs scheduled if the same task has not
been scheduled via an OEM job. |
| 36 |
36_win_prod3_controlfile_backup_to_trace_1.pl |
|
This perl
script backs up the control file to trace.
Note: This script only needs scheduled if the same task has not
been scheduled via an OEM job. |
| 37 |
37_win_prod3_rebuild_controlfile_1.sql |
|
This sql script rebuilds
the control file.
NOTE: The contents of this file can only be used to rebuild the
control file if no datafiles have been added/moved since the database
was originally created.The best option is to use the lastest backed
up version of the control file backed up to trace (generally done
nightly). In order to use the tracefile information, replace the
#'s with -- for comments. |
| 39 |
39_win_prod3_documentation_1.txt |
|
Contains
basic setup instructions for setting up primary and standby databases
along with the site configuration and database recovery scenarios. |
| 40 |
40_win_prod3_tasklist_sheet_1.slk |
|
Contains a summary
of the tasks required to setup the database.
Note: This file generally requires some manual modification after
the generation process. |
| 41 |
41_win_remove_oracle_1.pl |
|
This perl script removes
the directories,services and utilities of oracle software installed
as part.of the Oracle installation process.
WARNING - This script is used for testing purposes only while testing
installation scripts. For safety, this file is removed from the
server during the execution of the post-install script. |
| 42 |
prod3_overview_diagram_1.svg
(18K) |
|
This XML file in SVG format displays a database diagram for installations
containing multiple servers. The OEM/OMS server is shown along
with the servers which it manages.
Note: This file generally requires some manual modification after
the generation process.
|
| 43 |
43_win_prod3_backup_timeline_1.slk |
|
This spreadsheet in
SYLK format provides a timeline of the various periodic tasks which
are scheduled on the database server. Tasks include performance
tuning, export and backup jobs.
Note: This file generally requires some manual modification after
the generation process. |
| 49 |
49_listener_ora_1.ora |
|
This file provides configuration information
for the Oracle listener. |
| 52 |
52_win_817_patch_db_1.pl |
|
This perl script applies the 8.1.7.4.1patche
to the 32bit Oracle 8.1.7 database on Windows NT/2000. |
| 53 |
53_win_817_db_build_2_1.sql |
|
This sql script is the main script which
builds the Oracle database. |
| 56 |
56_win_817_prod3_schema_stats_job_1.pl |
|
This perl script generates sql scripts
which are then run in order to gather schema statistics for all
schemas except SYS and SYSTEM. |
| 62 |
62_win_817_prod3_rman_oem_backup_job_1.pl |
disaster_recovery.txt |
This perl script performs an RMAN full
database backup of all datafiles, archivelogs and the control file.
The init.ora and pwd files are backed up via OS commands. The control
file is also backed up to a trace file within the c:\backup directory.
Any backup corruption found by RMAN is reported. |
| 64 |
64_win_817EE_prod3_db_installer_response_1.rsp |
|
This file provides the installation responses
Oracle 9i Enterprise Edition (Windows NT/2000) This file allows
the installation to run in silent install mode. |
| 66 |
66_win_817_prod3_oem_installer_response_1.rsp |
|
This file provides the installation responses
for the Oracle Java-based installer program to install the OEM/OMS
software. |
| 67 |
67_win_817STD_prod3_db_installer_response_1.rsp |
|
This file provides the installation responses
for installing Oracle 8i Standard Edition on Windows NT/2000. This
file allows the installation to run in silent install mode. |
| 68 |
68_win_817_patch9013_response_1.rsp |
|
This response file provides information
for a silent install of the 32 bit Oracle 8.1.7.4.1 patch on Windows
NT/2000 Oracle servers. |
| 70 |
70_prod3_primary_tnsnames_1.ora |
|
This file provides configuration information
for the Oracle Net8 configuration for the primary database in a
standby database configuration. |
| 71 |
71_prod3_failover_tnsnames_1.ora |
|
This file provides configuration information
for the Oracle Net8 configuration for the primary and standby databases
in a standby database configuration during a switchover or failover
situation. |
| 72 |
72_prod3_client_taf_tnsnames_1.ora |
|
This file provides configuration information
for the Oracle Net8 configuration for clients to connect to either
the primary or standby databases in a standby database configuration.
TAF (transparent application failover) is used to automatically
switch the connection from the primary to the standby database in
a switchover or failover situation. |
| 74 |
74_win_prod3_standby_listener_1.ora |
|
This file provides configuration information
for the Oracle listener on the standby database in a standby database
configuration. |
| 75 |
75_win_817_prod3_primary_init_1.ora |
|
This file provides the initial configuration
for the Oracle database instance (Windows NT/2000 version).- for
a primary database in a standby configuration.
Note: During the installation process this file will generally be
converted to an spfile for version 9i databases. |
| 76 |
76_win_817_prod3_standby_init_1.ora |
|
This file provides the initial
configuration for the Oracle database instance (Windows NT/2000
version).- for a primary database in a standby configuration. |
| 77 |
77_win_817_prod3_primary_standbysetup_1.pl |
|
This perl script sets up the primary
server in a standby database configuration.
Tasks include: performing the RMAN backup of the primary server,
dynamically changing init.ora parameters to the new standby settings,
copying updated versions of the tnsnames.ora, init.ora, status monitoring,
change role, backup files and archived logs to the standby server, |
| 78 |
78_win_817_prod3_standby_standbysetup_1.pl |
|
This perl script sets up the standby
server in a standby database configuration.
Tasks include: copying updated versions of the tnsnames.ora, init.ora
listener.ora, status monitoring, change role files from network
shared folder, and starting database in managed recovery mode |
| 79 |
79_prod3_standby_status_1.pl |
|
This script checks the automatic application
of archived redo logs on the standby database server. If the standby
database is behind by more than 3 archivelog files - an email is
sent to the DBA.
Note: If a standby delay is used, the max_error_difference will
need to be adjusted accordingly. |
| 80 |
80_win_prod3_standbydb_change_role_1.pl |
|
This perl script changes the role of
the servers in a standby database configuration.
Role changes include:
primary to standby switchover (9i only)
primary to standby failover
standby to primary switchover (9i only)
standby to primary failover
standby to read-only
read-only to standby |
| 81 |
81_prod3_standby_startup_service_1.pl |
|
This perl script runs as a Windows Service
during system startup to startup the standby database instance in
managed recovery mode. |
| 82 |
82_win_prod3_file_replicator_1.pl |
|
This script compares archivelog
directories on the primary and standby servers and copies new logs
from the primary server to the standby server. Archivelog files
are not copied until Oracle has completed writing them on the primary
server.
Notes: This script is expected to be scheduled to run regularly
on the standby server. The primary server's archivelog directory
is expected to be mounted via the network on the standby server.
This script should generally only be required for use with standby
databases on Oracle 8.0.5. Oracle 8.1.5 and higher support copying
of files automatically via the RFS process. |
| 83 |
83_prod3_file_replicator_job_1.pm |
|
This perl module contains the archivelog
directory paths for the primary and standby servers. |
| 84 |
84_prod3_archivelog_move_job_1.pl |
|
This script moves archivelog files more
than 4 hours old to another location.This script should only be
used in situations where an RMAN backup is not going to be scheduled
on the server. The RMAN backup will backup up and then clear the
archivelog files. This script could be used on a standby server
which is not performing RMAN backups.
Notes: If a standby delay is implemented on the standby server,
this delay time needs considered when setting the delay_hours variable
in this program. The RFS process (Oracle 8.1.5 and higher) will
copy archived logs immediately, but the logs will not be applied
until the standby delay interval has elapsed. |
| 85 |
85_prod3_rman_archivelog_backup_job_1.pl |
|
This script backs up archivelog files
via RMAN and removes the archivelog files from the archivelog directory.
This script is useful for situations in which the nightly full database
RMAN backup will not occur soon enough to prevent the archivelog
directory from filling up. |
| 86 |
86_sqlnet_1.ora |
|
This sqlnet.ora file specifies NTS authentication
on Windows servers. |
