|
Oracle® E-Business Suite Certified Configuration Getting Started Guide
Release 11i (11.5.8) for UNIX Part No. B10675-01 |
|
This chapter provides information on optional implementation and administration utilities available for Oracle E-Business Suite Certified Configuration. This chapter covers the following:
|
CAUTION: These utilities are intended for use by experienced implementors and administrators. Incorrect use of these utilities can cause data loss or errors in software setup. |
This section provides information on the following administration utilities:
Three database administration (DBA) scripts are available. The scripts are in the /mount_point/oracle/admin/SID/script directory. Table 3-1 describes each script.
Table 3-1 DBA Scripts
| Script | Description |
|---|---|
create_ctrl.sql
|
Runs in Server Manager to recreate the database control file in the current Oracle Applications environment. |
shutdown_apps.sh
|
Stops the current Oracle Applications environment. |
startup_apps.sh
|
Starts the current Oracle Applications environment. |
There are two Oracle Internet Directory (OID) administration scripts available: create_ctrl.sql and oidenv.sh [start|stop]. These scripts are in the/oid_mount_point/oracle/admin/SID/script directory.
The create_ctrl.sql script runs in Server Manager to recreate the database control file in the current OID environment.
The oidenv.sh [start|stop] script starts or stops the Oracle Internet Directory environment. To use this script, make sure you log in as the OID user.
There are two OLAP administration scripts available. The scripts are located in the /olap_mount_point/oracle/admin/SID/script directory. The following table describes each script.
Table 3-2 OLAP Administration Scripts
| Script | Description |
|---|---|
exapcctl.sh [start|stop] |
Starts or stops the Web server. User must be logged in as the OLAP user.
|
exexpctl.sh [start|stop] |
Starts or stops the Oracle Express server if the /usr/local/bin/super script is on the system. User must be logged in as the OLAP user.
If the script is not available, then the # cd $OLAP_HOME/bin # express [start|stop] |
The password change utility changes the passwords for apps and applsys users, and all APPS and APPLSYSPUB schemas to the same password. The change_password.sh utility is in the /mount_point/applmgr/BOL/scripts directory. Run the script as the apps user.
When changing the passwords, update the passwords for the APPS and APPLSYSPUB schemas in the files in Table 3-3.
Table 3-3 Schema Files
| Schema | File |
|---|---|
APPS
|
$
|
APPLSYSPUB
|
$FND_TOP/resource/appsweb.cfg $OA_HTML/bin/appsweb.cfg |
VERITAS NetBackup is used to back up the file system, and the database of the Oracle E-Business Suite Certified Configuration. In order to utilize this software, configure both a NetBackup server and a NetBackup client. When you set up VERITAS client, you will need to provide values for the parameters in Table 3-4.
Table 3-4 VERITAS Client Parameters
| Parameter | Description |
|---|---|
| FSBACKUP_CLASS | The class to perform file system backup. |
| FSBACKUP_SCHED | The schedule defined for file system backup.
Note: The file system backup is the most substantial data backup. |
| BPBACKUP_CLASS | The class to perform Oracle database backup. |
| BPBACKUP_SCHED | The schedule defined for Oracle database backup. |
| SERVER | The hostname of the NetBackup 3.4GA server. |
| CLIENT_NAME | The hostname of the Oracle E-Business Suite Certified Configuration server to back up. This must match the name that you used to register the client on the server. |
The following tasks describe how to set up a NetBackup Client.
Create a new class on the VERITAS NetBackup server to back up the Oracle E-Business Suite Certified Configuration server file systems.
Create a schedule for the Oracle E-Business Suite Certified Configuration server file system backup.
Log in as the root user.
Open the /usr/openv/netbackup/bp.conf file using the following commands:
# cd /usr/openv/netbackup # vi bp.conf
Add the following lines to specify the values for the client:
VERBOSE=99 BPBACKUP_CLASS=BPBACKUP_CLASSBPBACKUP_SCHED=BPBACKUP_SCHEDFSBACKUP_CLASS=FSBACKUP_CLASSFSBACKUP_SCHED=FSBACKUP_SCHEDSERVER=SERVERCLIENT_NAME=CLIENT_NAME
The values are the variables that were determined for the environment. The following is an example:
VERBOSE=99 BPBACKUP_CLASS=Oracle_tst BPBACKUP_SCHED=Oracle FSBACKUP_CLASS=Appl_tst FSBACKUP_SCHED=Appliance SERVER=bkupsrv.us.oracle.com CLIENT_NAME=ebizcc.us.oracle.com
|
See Also: For more information about configuring classes and schedules, refer to the VERITAS NetBackup documentation. |
There are two options to back up the database:
The /mount_point/oracle/admin/SID/scripts/hbk directory contains the oracle_hot_backup.sh script. You must run the script as the oracle user, ormount_point.
If any errors occur, then the script sends an e-mail message to the system administrator. In order for the system administrator to receive e-mail messages, update the e-mail address in the oracle_hot_backup.sh script with the system administrator’s e-mail address. The default e-mail address is System.Administrator@oracle.com, and it occurs seven times in the script.
This script performs a hot backup of the data files, redo logs, control files, archive logs, and initSID.ora file of the 11i database in the mount_point environment to the /mount_point/backup directory. It will generate the error and log files in the /mount_point/oracle/admin/SID/scripts/hbk directory.
You can schedule the hot backups to run on a regular basis. The following tasks describe how to setup the schedule:
Log in as the root user.
Open the crontab file in an editor.
Add the following line to the crontab file:
0 0 * * * /mount_point/oracle/admin/SID/scripts/hbk/oracle_hot_backup.sh
In the preceding command, the hot backup is scheduled to run at midnight.
The following tasks describe how to run an Oracle Recovery Manager (RMAN) script to perform a database backup on the Oracle E-Business Suite Certified Configuration:
Set the following the environment variables for the client that will run the backup:
NB_ORA_SERV=backup serverNB_ORA_CLASS=Oracle classNB_ORA_SCHED=Oracle schedule
An example of the settings is as follows:
NB_ORA_SERV=congee.us.oracle.com NB_ORA_CLASS=Oracle_tst NB_ORA_SCHED=Oracle
Run a few file system backups to ensure the client is properly registered on the server.
Verify that you set the following environment variables:
ORACLE_HOME
ORACLE_SID
NB_ORA_CLASS
NB_ORA_SCHED
NB_ORA_SERV
Perform a database backup using the RMAN script. The following is an example of the rman script:
run {
allocate channel t1 type 'SBT_TAPE';
backup database;
}
The preceding example backs up the entire database to the VERITAS Netbackup server.
|
Note: Specify the channel type asSBT_TAPE or tape in order to send the backups to the server.
|
Save the script as x.rman.
Run the x.rman script using the following command:
$ORACLE_HOME/bin/rman nocatalog targetuser/password with sysdba\privscmdfilepath/x.rman
The NLS Toolkit is in the /admin/ebso/nls directory. This tool enables you to install a base language or an additional language into your Oracle E-Business Suite Certified Configuration environment. It assumes that you installed APPSAUTO in the /admin/appsauto directory. Table 3-5 lists the current supported languages.
Table 3-5 Language Codes
| Language |
Language Code LANG
|
|---|---|
| Arabic | AR |
| Brazilian Portuguese | PTB |
| Canadian French | FRC |
| Croatian | HR |
| Czech | CS |
| Danish | DK |
| Dutch | NL |
| European French | F |
| European Portuguese | PT |
| European Spanish | E |
| Finnish | SF |
| German | D |
| Greek | EL |
| Hebrew | IW |
| Hungarian | HU |
| Italian | I |
| Japanese | JA |
| Korean | KO |
| Latin American Spanish | ESA |
| Norwegian | N |
| Polish | PL |
| Romanian | RO |
| Russian | RU |
| Simplified Chinese | ZHS |
| Slovak | SK |
| Swedish | S |
| Taiwan Chinese | ZHT |
| Thai | TH |
| Turkish | TR |
Before running the tool, perform the following steps:
Stop all application processes.
Increase the applmgr mount point by 6 GB per language that you plan to add.
Create 6 GB of temporary space per language for staging the patch, making sure that the apps user can write to the temporary space.
Make available the NLS patch nls11i.zip. You can either mount the patch from the psd-sun.us.oracle.com:/image/1158/nls/LANG directory or from the Oracle E-Business Suite Certified Configuration environment CD-ROM for your particular language.
Turn off database archiving to avoid generating an excessive number of archive log files while patching the application.
As the apps user, run nlsenv.sh to start the tool:
$ cd /admin/ebso/nls/bin $ ./nlsenv.sh LANG TYPE
In the example above, substitute one of the language codes in Table 3-5, "Language Codes" for the LANG variable, and B or I for the TYPE variable. Use B if you are installing the language as the base language or I if you are installing it as an additional installed language.
When prompted, enter the following information:
E-mail address - Enter the address in the form, firstname.lastname. The toolkit assumes that the suffix is @oracle.com, therefore you do not need to specify it.
System password - Enter the SQL*Plus system user password.
Applsys Password - Enter the SQL*Plus applsys user password.
To add more than one language, wait for the nlenv.sh to finish, then mount nls11i.zip of another language, and rerun nlsenv.sh.