MAintenance Wizard ora

8/10/2019 MAintenance Wizard ora

1/10

Installing the Maintenance Wizard: A Step-by-Step Guide [ID 329476.1]

Modified05-JAN-2011 TypeHOWTO StatusPUBLISHED

Maintenance Wizard

The following table provides links to all documents relating to Maintenance Wizard. These documents areupdated as new information becomes available.

Maintenance Wizard Reference Documentation Menu

MWOverview

Downloads InstallationInstructions

You Are Here!

User's Guide FAQ Training

In This Document

System Requirements Prerequistite Instructions Installation Steps Post Install Steps Uninstall Steps Submit Feedback

System Requirements

Maintenance Wizard is a standalone product which must be installed into an RDBMS 10 g

ORACLE_HOME on a single UNIX or Linux machine. (Your e-Business Suite Applications may be onother operating systems, however).

It is strongly recommended that you restrict access to the UNIX account under which you are installingthe Maintenance Wizard, as this user will have access to privileged information.

To download the latest version, visitDownloads

Prerequistite Instructions

1. Set up a shellYou must set up either remote shell (rsh/remsh) or secured shell (ssh) between the MaintenanceWizard node and every remote Applications node. The tool will not work without having at leastone of these shells successfully configured. Follow the instructions below for the type of shell youwish to use for remote access:

a. Setting up OpenSSH:Follow this procedure if you will be using OpenSSH:i. On the Maintenance Wizard Node:

a. Log in as the user who will own Maintenance Wizard.b. Generate the ssh key by issuing the following command:

ssh-keygen -t rsa
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215527.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215527.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215527.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430734.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405263.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406917.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#SYSREQhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#SYSREQhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#PREREQhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#PREREQhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#INSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#INSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#POSTINSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#POSTINSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#UNINSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#UNINSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#FEEDhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#FEEDhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#FEEDhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#UNINSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#POSTINSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#INSThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#PREREQhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#SYSREQhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406917.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405263.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430734.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215527.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=215527.1


2/10

c. Press the Enter key three times.d. CD into the .ssh directory, which is located under the home directory.

Note that a file called id_rsa.pub is created.e. Use FTP to copy id_rsa.pub to the /tmp directory of the Remote Nodes.

ii. On the Remote Node(s):a. Login as the user who owns the product being upgraded or maintained.

For Applications tiers, use the applmgr account. For the database tiers,use the oracle account.

b. Remove specialized .login, .profile or similar files which cause extraverbiage to be displayed to the screen.

c. Create a directory called .ssh in the home directory.d. If an authorized_keys file does not exist, create a new, empty one.e. Copy the content of /tmp/id_rsa.pub (from the Maintenance Wizard

Node) into a new file named authorized_keys. (If you already have a filecalled authorized_keys in this directory, open it in vi, go to the bottom ofthe file, add one blank line and then copy and paste the contents of thefile /tmp/id_rsa.pub into the existing file and save it.)

f. Verify that the .ssh directory permission is set to 700.g. Verify that the authorized_keys file permission is set to 600.h. Verify that the $HOME directory does not have write permissions for

group and others.

chmod go-w $HOME

b. Ensure that the ssh daemon is running.c. Repeat the above steps for each Remote Node.

2. Test the installation:a. Login to the Maintenance Wizard Node as Maintenance Wizard owner.b. Execute the following command, replacing [user] with the username on the Remote

Node, and [SERVER] with the host name of the Remote Node:

ssh -l [user] [SERVER] (ssh l oraprod 10.0.30.222)

c. When prompted to confirm the identity, respond "Yes".d. Disconnect from the server.e. Execute the following command:

ssh -l [user] [SERVER] echo 'foo'

Only the word fooshould appear, followed by the prompt, and you should not be askedto enter and ID or password. If you are prompted for a password, verify the following:

The content of the authorized_keys file contains the content of id_rsa.pub of theclient

The permissions of the authorized_keys file are set to 600. The permissions of the .ssh directory are set to 700. The permissions of the $HOME directory do not include execute for group and

other.

If more than the word fooappears, then repeat the step above to remove all .login,.profile or similar files until ONLY the word fooappears.

Setting up rsh/remsh:Follow this procedure if you will be using Remote Shell:

i. On the Remote Node:


3/10

a. Login as the user who owns the product being upgraded or maintained. For Applicationstiers, use the applmgr account. For the database tiers, use the oracle account.

b. Remove specialized .login, .profile or similar files which cause extra verbiage to bedisplayed to the screen.

c. Add the following line to the file ${HOME}/.rhosts, replacing [host] with the MaintenanceWizard host name and [user] with the owner of Maintenance Wizard:

[host] [user]

d. Ensure that the rsh daemon is running.ii. Test the installationneed to start form this

a. Login to the Maintenance Wizard Node as Maintenance Wizard owner.b. Test the remote shell command, replacing [user] with the username on the Remote

Node, and [SERVER] with the host name of the Remote Node. Use the appropriatecommand for your operating system.

rsh -l [user] [SERVER] echo 'foo'remsh -l [user] [SERVER] echo 'foo'Only the word fooshould appear, followed by the prompt, and you should not be asked

to enter and ID or password. If you are prompted for a password, verify the following:

The hostname is correctly spelled in the .rhosts file. The username is correctly spelled in the .rhosts file. The format is hostname, space, username on a single line in the file. If the domain differs between the MW node and the Remote node, you may need

the domain name as a part of the hostname.

If more than the word fooappears, then repeat the step above to remove all .login,.profile or similar files until ONLY the word fooappears.

c. Disconnect from the server.

Maintenance Wizard version 2.x requires Oracle RDBMS 10g(10.2). Do not attempt to "re-use"existing 10gORACLE_HOMES, as this has been known to cause errors during installation. Install a newstandalone Oracle 10gRDBMS ORACLE_HOME for use by Maintenance Wizard.

Note:You CANNOT use the same database that the Applications are running in. The tool must beinstalled in a separate database from the Applications.

a. Set the DISPLAY variable appropriately and export it.

Note:Before you run the Oracle Installer, ensure that an X Windows manager is running.

b. Install RDBMS 10gusing the following command:

./runInstaller

c. Specify the desired ORACLE_HOME location.d. Choose "Enterprise Edition".e. Uncheck the option called "Create Starter database". Click NEXT.


4/10

f. Optionally, specify the oraInventory and operating system group, then click NEXT.g. After successful Product-Specific Prerequisite Checks, choose "Install database Software only"

and click NEXTh. Click INSTALL.i. When the installation has completed, exit the installer.

We also recommend that you apply the latest RDBMS patchset for your operating system.

a. Download the latest 10.2.0.x patchset available for your platform (10.2.0.3 or 10.2.0.4).b. Uncompress the zip file into an stage area (/u01/yourstagedir).c. Set the DISPLAY variable appropriately and export it.

Note:Before you run the Oracle Installer, ensure that an X Windows manager is running.

d. Change to the patchset installer directory.

cd /u01/yourstagedir/Disk1

e. Install the RDBMS 10gpatchset using the following command:

./runInstaller

f. Specify the desired ORACLE_HOME location.g. On the Product-specific Prerequisite Checks screen, correct any reported errors.h. On the Summary screen, click INSTALL.i. When the installation has completed, exit the installer.

Create the database.

a. Set the ORACLE_HOME variable appropriately.

ORACLE_HOME=; export ORACLE_HOME

b. Change to the bin directory.

cd $ORACLE_HOME/bin

c. Run the database creation utility.

./dbca

d. Choose "Create a Database".e. Choose "General Purpose".f. Specify the Global Database Name.g. Specify whether to configure to database with Enterprise Manager.h. Set the default password for the SYS and SYSTEM accounts. (PLEASE, record these in a secure

location!)i. Choose your storage mechanism. We recommend that you choose "File System" and select a

Common Location.j. Specify any desired recovery options.


5/10

k. Specify NO sample schemas.l. In the Character Sets tab, do NOT modify the Default Language (American) and Default Date

Format (US).m. Specify the desired values for parameters SGA, PGA and processes.n. When the process has completed, exit the Database Creation Assistant.

Set up the listener for the Oracle RDBMS ORACLE_HOME. Name it LISTENER_, where is the DB SID for the MW database. Create LISTENER.ora and TNSNAMES.ora files in the OracleRDBMS $ORACLE_HOME/network/admin directory.

Use of a sqlnet.ora file is not necessary for operation of SQL*Net. We strongly recommend againstcreating a sqlnet.ora file. If you are using a sqlnet.ora file and experience database connection issueswith the Maintenance Wizard, it may be related to parameters such as "defaultdomain". Please consultthe SQL*Net manual for details. You may use netca to configure your listener, or modify the followingtemplate:

LISTENER.ORA file, which uses a SID of "MW"

LISTENER_MW =(DESCRIPTION_LIST =

(DESCRIPTION =(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = yourhost.us.oracle.com)(PORT = 1521)))

))

SID_LIST_LISTENER_MW =(SID_LIST =

(SID_DESC =(GLOBAL_DBNAME = MW)

(ORACLE_HOME = /u02/ora10g/10.2.0)(SID_NAME = MW)

))

TNSNAMES.ora file

MW =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = yourhost.us.oracle.com)(PORT = 1521))

)

(CONNECT_DATA =(SERVICE_NAME = MW)

))

Create the NEWEOF tablespace where the Maintenance Wizard schema objects will be stored.Connect to sqlplus as the system user, and execute the following command substituting in the full path toyour datafile.


6/10

create tablespace NEWEOF datafile '/u01/oracle/oradata/eof01.dbf' size 50M AUTOEXTEND ON NEXT5M MAXSIZE 75M;

Note: Do not create a Maintenance Wizard schema; the tool creates it automatically.

Verify that Zip and UnZip executables are installed and that ping and ftp are in the $PATH using the

following commands:which zipwhich unzipwhich ping

If these commands do not successfully locate the executables, you may need to modify your login scriptsso that the PATH variable includes the locations and/or install Zip and UnZip now.

Note:The UnZip source code is available for free at the Info-ZIP website (http://www.info-zip.org/pub/infozip/UnZip.html), along with compiled executables for version 5.41 or higher for everyOracle Applications-certified operating system except IBM RS6000 AIX. A sufficient version of the IBMRS6000 AIX compiled executable (5.42) is currently available at the IBM AIX toolbox web site.

Set the default shell for all UNIX accounts to Korn shell. You must do this for the MW UNIX owner onthe MW node, as well as for all user accounts that will be used on the remote nodes (applmgr, oracle).For Linux ONLY, you will first have to manually install ksh into the /bin directory of each machine. TheUNIX Korn shell is not automatically installed on Linux.

Installation Steps

1. Login to the system as the same UNIX user that you used to install the RDBMS.2. Ensure that the $ORACLE_HOME environment variable is set to point at RDBMS 10g before

proceeding. At a minimum, make sure the following variables are set.

ORACLE_HOME=; export ORACLE_HOMEPATH=$ORACLE_HOME/bin:$PATH; export PATHTWO_TASK=;exportTWO_TASKTNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN

Create a directory to extract the tool into (this will become your $EOF_HOME). Oracle recommendsthat you create the Maintenance Wizard directory in the RDBMS $ORACLE_HOME directory. Then setthe $EOF_HOME environment variable as follows:cd $ORACLE_HOMEmkdir eofEOF_HOME=$ORACLE_HOME/eof; export EOF_HOME

Download the latest Maintenance Wizard Full Install version fromDownloadsand unzip it into${EOF_HOME}.

Change directory to the $EOF_HOME/config directory.

cd ${EOF_HOME}/config Run the installation script../setup.sh

Respond to the prompts shown below. Default values are shown in brackets.

Prompt Description

Enter the domain forMaintenance Wizard Node[us.oracle.com]:

Specify the domain name for the machine where you installed MW.
http://www.info-zip.org/pub/infozip/UnZip.htmlhttp://www.info-zip.org/pub/infozip/UnZip.htmlhttp://www.info-zip.org/pub/infozip/UnZip.htmlhttp://www.info-zip.org/pub/infozip/UnZip.htmlhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430732.1http://www.info-zip.org/pub/infozip/UnZip.htmlhttp://www.info-zip.org/pub/infozip/UnZip.html


7/10

SYSTEM password for theMaintenance Wizard instance:

Specify the password for the SYSTEM schema for the MW database. This isNOTasking for information about the remote Applications instance.

Schema name for storing theMaintenance Wizard data. [MW]:

Type in whatever you want to name the MW schema.

Desired initial password for the

database user:

Type in whatever you want to the MW database schema password to be.

Maintenance Wizard patchDirectory name[$EOF_HOME/patches]:

There is a patching feature in Maintenance Wizard. In order for it to work, it musthave an intermediary location on the Maintenance Wizard node for storing thepatches. The recommended free space for this feature to work is 1GB. If it doesnot exist, you should create this directory now.

Email for Anonymous FTP [] The tool will use this email address as the password for any anonymous FTPconnections to the Oracle FTP site.

My Oracle Support Username []:

My Oracle Support Password:

Patches can be downloaded automatically from My Oracle Support. In order todo this, you must provide a valid My Oracle Support username and password.

Desired initial password for theSYSADMIN user:

Type in whatever you want the tool login password to be for SYSADMIN.

Protocol [http]: Type in which protocol you want the Maintenance Wizard to use: http or https.

Port Number [8080]: Enter the HTTP Port that will be used for Maintenance Wizard.

Proxy hostname: Enter the HTTP Proxy hostname. Leave it blank if no proxy is used.

Proxy port number: Enter the HTTP Proxy port number. Leave it blank if no proxy is used.

You have the option to review your entries and make changes before the install begins.

Domain = yourcorp.comOracle Home = /u01/somedir/your_oh Connect String =yourtnsSystem password = Database Schema = neweof

Maintenance Wizard Patch Stage =/u01/somedir/your_oh/patchesEmail for Anonymous FTP = [email protected] = httpHTTP port = 8080HTTP Proxy hostname =HTTP Proxy port number =My Oracle Support Username [email protected] Oracle Support Password = Maintenance Wizard Password =

Note: The automated patching and administration features of the tool require that a defaults file belocated in the $APPL_TOP/admin/[SID] directory. The file may be named either defaults.txt oradalldefaults.txt. You must update this file whenever you make changes to entries that it references, suchas changing a database password or moving directory paths. For more information about the defaults.txtfile, please seeOracle Applications Maintenance Utilities.

Post Install Steps

1. Secure the $EOF_HOME/EOF.env file.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=289790.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=289790.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=289790.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=289790.1


8/10

chmod 700 $EOF_HOME/EOF.env

2. Setup a client machine with Microsoft Internet Explorer (IE) 6.0 or higher or Firefox 3.0 or higher.3. If you are using IE, navigate to Tools -> Internet Options, Settings. Select the radio button for

"Every visit to the page."4. If you are using IE 7.0 or higher, you need to allow the MW to set the status via a script so that

your autorefresh works properly. Go to Tools -> Internet Options -> Security -> Local IntranetZone -> Custom Level -> Scripting and set "Allow status bar updates via script" to checked.5. Some customers have found that they had to change their Cookie settings as well. If you receive

an ORA-1403 in the Apache error log while trying to log into the tool, you should go to Tools ->Internet Options -> Privacy Tab, click Advanced. In the Cookies section, choose Overrideautomatic cookie handling. Under First-party cookies, select Accept. Select Always Allow SessionCookies.

6. Save and exit the IE Internet Options.7. Login to the tool using the following URL and the pre-assigned username and password that you

assigned it when you chose back in step 7 of Installation: SYSADMIN/YOURPASS:

http://.:

8. Download theUser Guideto learn how to create and configure customers and projects.

Uninstall Steps

For installations that were originally installed at 2.14 and above:

1. Change directory to $EOF_HOME/config.

cd $EOF_HOME/config

2. Run the uninstall.sh script.

./uninstall.sh

3. Remove Maintenance Wizard directories from the system.4. Remove directories/files created under each remote user's home directory.5. Remove entries from .rhosts or authorized_keys files.

For all other installations:

1. Login to the database as the sys user.2. Drop the Maintenance Wizard user and objects.

drop user neweof cascade;

3. Drop all directory objects that begin with "CONFIG_INSTANCE_" or "LOG_INSTANCE_".

declarecursor all_dirs isselect * from dba_directorieswhere directory_name like 'CONFIG_INSTANCE_%'or directory_name like 'LOG_INSTANCE_%';

begin
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430734.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430734.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430734.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=430734.1


9/10

for each_dir in all_dirsloop

execute immediate 'drop directory ' || each_dir.directory_name;end loop;

end;/

4. Stop and restart the database.5. Remove Maintenance Wizard directories from the system.6. Remove directories/files created under each remote user's home directory.7. Remove entries from .rhosts or authorized_keys files.

Feedback

Maintenance Wizard Forum Submit Feedback

Disclaimer

The information, software, products and services contained on this web site may be out of date or include omissions, inaccuracies or othererrors. The information, software products and services contained on this web site, including the materials, are provided "as is" and withoutwarranty. Oracle does not warrant that the information in the materials is up to date or error free, nor does it provide any other warranties,whether expressed or implied in law, including the implied warranties of merchantability or fitness for a particular purpose. The materials arenot a program or documentation under the terms of your license agreement(s) with Oracle.

In no event shall Oracle be liable for any direct, indirect, incidental, special or consequential damages, or damages for loss of profits,revenue, data or use, incurred by you or any third party, whether in an action in contract or tort, arising from your access to, or use of, thisweb site or any other hyperlinked web site.

Oracle reserves the right to make changes or updates to this web site or the products or programs described in this web site at any timewithout notice.

Related

Products

Oracle E-Business Suite > Applications Technology > Lifecycle Management > MaintenanceWizard

Keywords

SETUP.SH; EOF; INSTALLATION

Errors

ORA-1403

Back to top

Article Rating

Rate this document

Comments
http://forums.oracle.com/forums/forum.jspa?forumID=351http://forums.oracle.com/forums/forum.jspa?forumID=351mailto:[email protected]?Subject=MW%20feedback%20&BODY=Feedback%20from%20note%20329476.1mailto:[email protected]?Subject=MW%20feedback%20&BODY=Feedback%20from%20note%20329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#tophttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#tophttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=329476.1#topmailto:[email protected]?Subject=MW%20feedback%20&BODY=Feedback%20from%20note%20329476.1http://forums.oracle.com/forums/forum.jspa?forumID=351


10/10

Excellent

Good

Poor

Did this document help you?

Yes

No

Just browsing

How easy was it to find this document?

Very easy

Somewhat easy

Not easy

Provide feedback for this article. Please use 'Contact Us' for other feedb

Important Note:this feedback may be anonymously visible to othercustomers until processed by Oracle Support.

Cancel
http://cancelfeedbackbox%28%29/http://cancelfeedbackbox%28%29/

MAintenance Wizard ora

Documents

Transcript of MAintenance Wizard ora