User's Manual

114 Preparing the Script Files for Deployment Using Embedded Linux
Editing DTK Task Scripts
The task scripts called by the master batch file do not require any edits
(with the following exceptions) if the default variable values are utilized in
the tkenvset.sh scripts. However, if you make any changes to the default
values set by the tkenvset.sh, you must make the same edits to the matching
default values set in the appropriate task scripts. Locate the "USER
MODIFICATION REQUIRED" heading in the task scripts to find the
variable values you might need to edit. Each of the following task scripts can
be called by the master batch script during a full deployment:
•racrep.sh
•raidcfg.sh
•sysrep.sh
•partcfg.sh
racrep.sh
The racrep.sh sample script applies RAC configuration options to the target
system based on configuration information that has been saved in a
configuration file. User input is optional, depending on variables set in the
racrep.sh sample script. This script uses the racadm wrapper script or the syscfg
utility (depending on the version of RAC on your system) to configure the
RAC in the target system using the RAC configuration file, raccfg.ini, passed
as the first parameter to this script. If this parameter is not passed, the default
variables values used in this script are set in the tkenvset.sh scripts.
An optional second parameter can be passed to this file, which specifies the
IP address to be used to configure the RAC. The raccfg.ini file is generated
with the raccap.sh sample script. See "raccap.sh" for information about using
the raccap.sh sample script to capture RAC configuration information.
NOTE: For x9xx or later systems, racrep.sh and sysrep.sh have duplicate functions.
If you run racrep.sh followed by sysrep.sh, the latter overwrites the former’s
settings.