Showing posts with label R12. Show all posts
Showing posts with label R12. Show all posts

Wednesday, June 18, 2008

Create a User Event Trace in 11i / R12

A user event trace is very handy for tracing sql operations to debug various issues. The benefit of a user event trace is that it is linked to a specific user so that only code run by this user is traced. This makes diagnosis easier when compared to similar tracing methods at the database level where all user calls are traced.

Step 1
Login to Oracle Applications and select the System Administrator responsibility.
Choose Profile - System

Step 2
In the find profile field select the user which you wish to trace. In the profile field enter 'Initialization SQL Statement - Custom"
Select find

Step 3
In the find profile results form copy and paste the following into the 'user' field. Do not update the site level field.

begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS='||''''||'10046 TRACE NAME CONTEXT FOREVER, LEVEL 12'||'''');end;

Note: copy and paste the above as one line. Failure to paste the values properly or pasting the values with incorrect syntax will result in this user not being able to login

 trace

Step 4
Save the profile option change. Stop and start the java virtual machine for the change to take effect
11i: use adapcctl.sh
r12: use adoacorectl.sh

Step 5
Login to the application and reproduce the issue. Then quickly log off. Try and avoid any un-necessary keystrokes as this simply makes the log files larger and the issue hard to pinpoint in the logs.

Step 6
login to unix/windows as the oracle user. Navigate to the user dump destination which us usually $ORACLE_HOME/admin/<context>/udump
You will see a series of trace files generated during the time of your issue reproduction. Tkprof all of the generated files and upload both the raw and tkprof files to your service request

You can also check the user dump destination via the following:
sql> show parameter user_dump_dest;

Friday, June 6, 2008

Oracle Apps Interview Questions - Part I

Here are some of the Oracle Apps Interview Questions. These Questions cover from Operating

System Installation, Pre-requisites for Apps, Apps Installation, Architecture, File System. In the

next part of Questions , I will cover more into advanced apps topics. For any doubts you may post

comment so that i could help you.

1)  How to Check the memory of the system while the time of Linux Installation ?
2)  How to assign hostname to a node ?
3)  How to assign IP to a node ?
4)  which are the files where kernel settings and security limits are stored ?
5)  How to check the swap space and physical memory ?
6)  How to do ftp from one node to another node ? Give Eg
7)  How to do copy between two machines ? Give Eg
8)  Give steps to enable ftp and telnet services ?
9)  How to do confiugre nfs server and do a nfs mount from the client machine ?
10) what's the use of TOP, ps commands ?
11) How to create user and groups in Linux ?
12) How to see if user and group already exists ?
13) How to check the release version of OS ?
14) How to check the kernel version of OS ?
15) How to check OS is 32bit/64bit?
16) How will you check whether required os level software has installed?
17) what is the command to check required rpms are installed?
18) How will install and upgrade rpms in linux?
19) What is oraInventory?default location for aix , Linux ?
20) what is oratab ?
21) How can you check the groups to a user belong ?
22) What is configuration file?(config.txt) and where is the default location
23) What is rapid install?
24) Explain Single Node and Multi Node installation ? ( Exp preinstall and postinstall tasks )
25) Explain single user and multi user installation ?
26) What is difference between express install and advanced install ?
27) What is difference between fresh database and vision database install types ?
28) What is minimum /  approx. disk requirement for 11.5.10 for  vis and fresh and stage ?  
29) What is staging area ? How you set up staging area ?
30) Is it possible to install apps without staging area ?
31) How will check perl, java versions?
32) where is location of staging logs ?
33) How can you clear the system after an incomplete installation ?
34) What's the difference between ORACLE_BASE and ORACLE_HOME
35) what is default port pool? what is default range and till what range it support?
36) If some of pre-install test has failed what will you do?
37) If the installtion has terminated before completion What will you do?
38) What are post installtion tests done by rapidwiz?
39) How will you check rapidwiz version?
40) Describe how will you do multinode installtion?
41) What are things will be checked during post installation tests?
42) What are required in post installtion steps additionally?
43) Where is the location of the Rapidwiz logs?
44) How could you Install technology stack alone?
45) What are the software require to maintain oracle application on windows ?
46) What are the Technology Stack Components?
47) What are the software required for Install Oracle Application on unix or linux machines ?
48) How can you check the version of Oracle Apps ?
49) What is Oracle Apps ?
50) Explain three tier architecture in Oracle Apps ( Including login workflow and middle tier services )
51) What is OATM ?
52) What is Oracle Jinitiator ? How can you check the jinitiator version ?
53) Where is location of Oracle Apache Cache and modplsql Cache ?
54) How many oracle Homes are there in 11i and what are they?
55) What is oracle applications technology layer ? what and why are these compnonents used for ?
56) what is Oracle Application Object Library ? How it differs for end user, developer and system admin ?
57) what is OAM ? What is OAM Login URL ?
58) What is Oracle Applications URL and Ebusiness Suite Apps Login URL ?
59) Which is the script location is Oracle apps for middle tier and db tier ?
60) where is the concurrent manger log and out location ?
61) what are environment files ? what are the different types of env files, and locations on both tiers ?
62) what are context files and locations for both tiers
63) what is APPLPTMP and APPLTMP  ?
64) what are they key environment file parameters ?
65) which is the script used to start and stop apache and concurrent manager ? Tell the steps
66) Brief out the file system for Oracle Applications Ebusiness Suite ( and explain each directory structure,
      its contents )
67) Whats the difference between APPS,APPLSYS,APPLSYSPUB users ?
68) what are the diff types of users available is oracle apps ?
69) What is Multiple Organization ? How can you check if MO is enabled ?
70) How can you check if multiple languages are installed with oracle apps ?
71) How can you check if an oracle apps installations in multi node or single node and in which
      node each services are running ?
72) How can you check how many database are up and running in both linux and windows machines
73) How can you check if concurrent manager and apache server is up and running
74) Where is apache access log and error log location
75) Where is the location of Oracle Alert logfiles and Trace files ( Give complete path )

Tuesday, June 3, 2008

Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications

 

 

A. Introduction

When starting a Forms-based session in Applications it is possible to pass various useful parameters like formname=xyz, or lang=US, or NLS=xyz etc. This is really helpful when debugging Forms. In addition, there are two other parameters config=debug and record=all which make it possible to perform Forms Runtime Diagnostics (FRD.)

FRD is a runtime event-based logging system intended to aid in the debugging of Forms applications. FRD is enabled at runtime on a user by user basis.  When a form is run with FRD enabled, a combination of external user-application interactions and internal Forms processing events are written in chronological order to a log on the file system.

<>FRD generates extensive output useful for analysis and debugging, and it is therefore recommended FRD be utilized as a logging mechanism only when specific issues are encountered.
 

B. The Contents of an FRD Log File

The following data is typically collected in an FRD trace file:

- Trigger firing: includes name and hierarchical location.

- Built-in Execution: includes name and IN and OUT parameter types and values.

- Messages: includes message numbers and text.

- The opening of forms executables (.fmx) and menu executables (.mmx)

- Unhandled exceptions: includes error message if available, otherwise only
   error numbers.

- All external user events via normal runtime (RT) recording mechanism

To see more details about the expected output in Forms, please see
<Note:62664.1> Forms Server Logging and Forms Runtime Diagnostics (FRD) Explained.
 
C. Tracing in R12

1. Set the user value for profile option  'ICX: Forms Launcher' to be

   'http://hostname.domain:port/forms/frmservice?record=forms'

2. By default, this will enable tracing for errors only. As an optional step, you can enable different trace options (e.g. user actions, user-exit events, dbsql events, network events) by setting a trace group in file $ORA_CONFIG_HOME/10.1.2/forms/server/ftrace.cfg

3. Login to the Personal Home Page,  navigate to the form and perform the steps that you wish to trace.

4. Locate the file in the directory set by variable FORMS_TRACE_DIR. Note: by default, this directory is named forms_<pid>.trc, where <pid> is the process identifier.

Related reference:
<Note:373548.1> Using Forms Trace in Oracle Applications Release 12.

D. Tracing in 11.5.10

1. Make the user value for profile option  'ICX: Forms Launcher' the same as the site value

   e.g. copy value of ICX: Forms Launcher for the site Test115
   'http://testserver.oracle.com:8005/dev60cgi/f60cgi'
    to be the value for the user.

2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD

   e.g. update the value of  ICX: Forms Launcher for the user to be
   'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log'

3. Login to the Personal Home Page,  navigate to the form and perform the steps that you wish to trace.

4. Locate the file in the directory set by variable $FORMS60_TRACE_PATH. Note: the default directory for
$FORMS60_TRACE_PATH is $ORACLE_HOME/forms60/log.

Related reference:
<Note:290210.1> Forms FRD Trace With New Variable FORMS60_TRACE_PATH.


E. FRD Tracing in 11.5.x to 11.5.9

This method enables users to run FRD tracing through the Personal Home Page by setting debugging to true using the profile option 'ICX: Forms Launcher'.

When accessing Applications through the Personal Home Page (PHP), there is no way to pass command line parameters such as config=debug and record=all for the duration of a single session. For example, you cannot add these variables to the PHP connect string
http://testserver.oracle.com/OA_HTML/US/ICXINDEX_test115.htm.

The advantages of using the profile option 'ICX: Forms Launcher' are that you can easily trace the activities of multiple users and assign different log file names.

With Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter $FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.

Steps:

To start tracing in this way, modify Profile Option 'ICX: Forms Launcher' at USER level to include the Forms parameters required for FRD logging:

1. Make the user value for profile option  'ICX: Forms Launcher' the same as the site value

   e.g. copy value of ICX: Forms Launcher for the site Test115
   'http://testserver.oracle.com:8005/dev60cgi/f60cgi' to be the value for the user.

2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD

   e.g. update the value of  ICX: Forms Launcher for the user to be
  'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log'

3. Save this change at the USER level, and the next time you access the test115 database through PHP, the Forms variables will be enabled.

E. Points to Consider When Running FRD

1. Check that sufficient space exists in the directory in which the FRD log file is to be created

2. For each run of FRD, specify a different log file name. The FRD log file will replace an existing file of the same filename.

3. On certain platforms, the log file is only created after the user exits Applications. Therefore, remember to exit Applications.

4. If no file name is specified for FRD, a unique file name is used based on the operating system process ID. The file is created in the current working directory. The file may be overwritten if the operating system reuses the process ID.

5. The log file is likely to be hundreds of lines long. To keep the content of the trace file to a minimum amount, follow the steps to reproduce a problem precisely and avoid performing any other actions. This is particularly helpful when using for troubleshooting purposes.

6. Specify the tmp directory for the log file location since all users usually have permission to write to it.

7. In a multi-node environment, the trace file is created on the Applications tier.

8. It is recommended to pass FRD variables at the USER level and not at the SITE level since SITE level affects all users.

9. Please create your own user to set this value. Please do not enable FRD for user 'vision' or any of the seeded users since you will then start FRD logs for all people using those login accounts.

10. If the 'ICX: Forms Launcher' profile option is not updatable at the USER level, then you may need to access 'Application Developer' to set the option 'Updatable' for the profile ICX_FORMS_LAUNCHER.

F. Extracts From an FRD Log File For 11i

Below displays brief extracts from a log file. The FRD documents the steps executed from Forms when signing on to Applications 11i and navigating to a form within core Applications.

Forms Runtime Diagnostic Collection Log
File Name: /tmp/form1.frd
Process ID: 19166
Client IP: @  x
Forms 6.0 (Forms Runtime) Version 6.0.8.12.1 (Production)
PL/SQL Version 8.0.6.1.0 (Production)
Oracle Virtual Graphics System Version 6.0.5.36.0 (Production)
Oracle Multimedia Version 6.0.5.33.0 (Production)
Oracle Tools Integration Version 6.0.5.32.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production

Opened file: /stable/oracle/vis006/vis006appl/fnd/11.5.0/forms/US/FNDSCSGN.fmx

ON-LOGON Trigger Fired:
Form: FNDSCSGN

State Delta:
FORM FNDSCSGN
  STATUS     NEW
  BLOCK PROGRESS_INDICATOR
    STATUS     NEW
    RECSTATUS  ""
    FIELD TEXT
      CANVAS     PROGRESS_INDICATOR
      GEOMETRY   100,250:4000,400
      ENABLED    TRUE
      NAVIGABLE  TRUE
      INSERTABLE TRUE
      QUERYABLE  TRUE
      UPDATEABLE TRUE
...
WHEN-NEW-ITEM-INSTANCE Trigger Fired:
Form: FNDSCSGN
Block: SIGNON
Item: USERNAME
...
WHEN-BUTTON-PRESSED Trigger Fired:
Form: FNDSCSGN
Block: SIGNON
Item: CONNECT_BUTTON
...
MENU_TO_APPCORE Trigger Fired:
Form: FNDNLDLG
...
CLOSE_WINDOW Trigger Fired:
Form: FNDNLDLG
...
Executing DO_KEY Built-in:
In Argument 0 - Type: String   Value: EXIT_FORM

KEY-EXIT Trigger Fired:
Form: FNDSCSGN
...

How To Configure Apache In R12 (10.1.3) To Listen On A Restricted Port (< 1024)

 

To configure Apache (10.1.3) in Release 12 of EBS to run on a restricted port.  A port below 1024.

Solution

By default, Oracle HTTP Server runs as a non-root user (the user that installed Oracle Application Server). On UNIX systems, if you change the Oracle HTTP Server Listen port number to a value less than 1024, you must enable Oracle HTTP Server to run as root. 

For more info please reference: Oracle Application Server's Administrator Guide 10g Release 3

If one tries to start up the HTTP Server on a port below 1024 without the HTTP Server running as root, the following error message will be seen in the HTTP Server [ error_log ] file.

            "Error code: [crit] (13)Permission denied: make_sock: could not bind to port #"

Note(s):

             - The steps below require root access.

             - The file that needs to be modified is the hidden file .apachectl
                NOT the apachectl file that resides in the same directory.

Pre Steps

  1. Log into your middle (web) tier as the Applmgr user
  2. Source your Apps environment
  3. Backup your $CONTEXT_FILE on your middle (web) tier
  4. Log into Apps and through OAM modify the following parameters to reflect the new web port.
    • s_webport (web port value < 1024)
    • s_active_webport (s_webport value)
    • s_http_listen_parameter (s_webport value)
    • s_help_web_agent (url constructed with http protocol and s_webport value)
    • s_login_page (url constructed with http protocol and s_webport value)
    • s_external_url (url constructed with http protocol and s_webport value)

    5.   Shutdown Apps and run autoconfig to make the changes take affect.

 Steps

  1. echo $ORA_CONFIG_HOME  [ make note of the absolute path. ] 
  2. $ su root 
  3. Run the following commands on the middle (web) tier Oracle Config home:
         a. $ cd $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin
         b. $ ls -la     [verify that the file exists in the directory ] 
         c. $ chown root .apachectl
         d. $ chmod 6750 .apachectl
  4. Startup your Applications
  5. Test "Login" with the new port
Note(s):

            - After the changes the file listing should look similar to the following.

            $ ls -la
                        drwxr-xr-x  2  applmgr  appsdba      4096  May   8  17:25 .
                        drwxr-xr-x  4  applmgr  appsdba      4096  May   8  17:25 ..
                        -rwx------    1  applmgr  appsdba    14025  May 19  17:25 apachectl
                        -rwsr-s---   1  root        appsdba  421517  May 19  17:25 .apachectl

 

Sunday, April 6, 2008

How to start Apps R12 in forms socket mode for testing

Here are two methods (A and B) of starting the forms server for testing in R12.

A. Modify the existing adformsrvctl.sh script, that starts the forms servlet process, to start the forms server.
1. Create a new copy of the $ADMIN_SCRIPTS_HOME/adformsrvctl.sh, name it something like testformsocket.sh

2. chmod 755 testformsocket.sh

3. In the new file/testformsocket.sh,
Change this line:
if [ "servlet" = "servlet" ]
to
if [ "servlet" = "socket" ]
Save your changes.

4. Now execute this script to start the forms socket listener.
testformsocket.sh start

5. At user level, set the profile 'ICX: form launcher' to http://<hostname:port#>/OA_HTML/frmservlet?serverURL=&connectMode=socket

6. Login as the above user and test the issue.
Enable the java console and review the log to verify that the user has connected using the Socket Mode.

To verify that the forms server is running, you can run something like the following on Unix:
testformsocket.sh status
or
lsof|grep <forms port #>

B. Or you can start the forms server the old way, by running frmsrv.

1. cd $ORACLE_HOME/forms/server

2. Source socket.env
. ./socket.env

3. To start the forms server, run:
frmsrv host=<enter your host name> port=<enter your forms port> &
Example:
frmsrv host=rwmatthe-linux port=9005 &
Note: You can use any available port

4. At the user level, set the ICX: Forms Launcher to:
http://<your host.domain:webport>/OA_HTML/frmservlet?serverURL=&serverPort=<forms server port>&connectMode=socket
5. Login as the above user and test the issue.
Enable the java console and review the log to verify that the user has connected using the Socket Mode.

Note: Make sure to pass the serverPort= or it will use the port defined in FORMS_WEB_CONIG_FILE.
To check to see if the forms server is running, you can run something like the following on Linux:
lsof | grep <forms port #>
or
lsof | grep frmsrv

Saturday, April 5, 2008

Changing Application Tier Platforms for Applications Release 12

It's now possible to migrate your E-Business Suite Release 12 application tier servers

from one operating system platform to another.  Oracle announced the availability of

new Oracle Applications Platform Migration Methodology for E-Business Suite Release 12.

This process provides a way to quickly and easily move an existing Oracle E-Business Suite

middle tier (applications tier) system to a different platform.  The migration utility retains

the exact E-Business Suite patch level; no APPL_TOP or Database synchronization is necessary. 

This allows you to retain existing customizations.

 

Continue Reading on this from Steven Chan Blog


 

Tuesday, April 1, 2008

Downtime and Apache Restricted Mode in Release 12

 

E-Business Suite Release 12 provides a useful mechanism for the Applications administrators

to start the Apache on the applications tier during down time. Applications administrator can

start the apache in a mode called restricted mode. Down time tasks like patching can continue

to be performed while the Apache is in restricted mode. Restricted access to Oracle Applications

Manager (OAM) is available in this mode. This allows the system administrator to monitor tasks

like patching from OAM. When the Apache is started in restricted mode, normal users are

redirected to a downtime URL containing downtime details.

 

Here are the details explained from Oracle Blogs (Steven Chan)

http://blogs.oracle.com/schan/2008/03/25#a2411

Sunday, March 23, 2008

How do you manually regenerate a form in Release 12?

1. Check the FORMS_PATH env variable. Assuming these are US forms the FORMS_PATH should include
$APPL_TOP/resource and $APPL_TOP/forms/US.

2. To compile a form manually from the command line try either of these two command line arguments (replace FNDFBMAS.fmb with the form of your choice.):

frmcmp.sh module=FNDFBMAS.fmb userid=apps/<apps password> module_type=form batch=yes compile_all=yes

frmcmp_batch module=FNDFBMAS.fmb userid=apps/<apps password> module_type=form batch=yes compile_all=yes

Tuesday, January 29, 2008

R12 - Collecting Configuration Information for HTTP, OC4J and OPMN

- Do the following on ALL middle tiers as the application tier user

zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`_iAS_CONFIG.zip \
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf \
$ORA_CONFIG_HOME/10.1.3/config \
$INST_TOP/pids/10.1.3/Apache \
$ORA_CONFIG_HOME/10.1.3/j2ee/ \
$ORA_CONFIG_HOME/10.1.3/javacache/admin \
$ORA_CONFIG_HOME/10.1.3/network/admin \
$ORA_CONFIG_HOME/10.1.3/opmn

How to Enable Enterprise Manager on the Oracle E-Business Suite Release 12

For the process to complete successfully, the database and database listener must be started.
It is not neccessary that any other Apps services are running for this process to complete.

Source the environment for the 10g ORACLE_HOME. With a Release 12 environment this would mean running the _.env script as generated by AutoConfig in the 10gR2 ORACLE_HOME.

Implement a password file and to overcome any ORA-01031 errors on the database.

It is also worth considering converting your Applications database to work with an SPFile
instead of an init.ora. An SPFile is approximately analogous to being a binary equivalent of the init.ora and allows for dynamic changes to many database parameters that previously would have required a database restart.

Next, as the owner of the 10gR2 ORACLE_HOME, run the following command to create the Enterprise Manager repository:-

$ emca -config dbcontrol db -repos create

When the above create command is run you will be prompted for the following:

STARTED EMCA at Oct 15, 2007 12:26:22 PM
EM Configuration Assistant, Version 10.2.0.1.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the values appropriate to your environment:-

Database SID: VIS
Listener port number: 1521
Password for SYS user: change_on_install
Password for DBSNMP user: dbsnmp
Password for SYSMAN user: sysman
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
-----------------------------------------------------------------
You have specified the following settings

Database ORACLE_HOME ................ /oracle/VIS/db/tech_st/10.2.0

Database hostname ................ xxxxxxx.xx.oracle.com
Listener port number ................ 1521
Database SID ................ VIS
Email address for notifications ...............
Outgoing Mail (SMTP) server for notifications ...............
-----------------------------------------------------------------
Do you wish to continue? [yes(Y)/no(N)]: Y

The repository should then start to be created. Typically this can take anywhere between 10 and 60 minutes depending on hardware and database configuration and size.

INFO: Creating the EM repository (this may take a while) ...

When the repository is created the following message should appear....

INFO: >>>>>> The Database Control URL is http://xxxxxxxxxx.xx.oracle.com:1158/em <<<<<<
Enterprise Manager configuration completed successfully
FINISHED EMCA at Sep 13, 2007 2:13:48 PM

Use the above Database Control URL to access the Enterprise Manager console through a browser interface.

Us the following command to drop an EM repository that has already been created:

$ emca -deconfig dbcontrol db -repos drop

To enable or disable browser access to dbconsole use the following command after sourcing
the environment for the 10g ORACLE_HOME. With a Release 12 environment this would
mean running the _.env script as generated by AutoConfig in the 10gR2 ORACLE_HOME.

$ emctl start dbconsole

To disable browser access use the following command:

$ emctl stop dbconsole

Clone and AutoConfig log files location in Oracle E-Business Suite Release 12

Where the logs for the adpreclone.pl are located?

On the database tier:
RDBMS $ORACLE_HOME/appsutil/log//StageDBTier_.log

On the application tier:
$INST_TOP/admin/log/StageAppsTier_.log

Where the logs for the admkappsutil.pl are located?

On the application tier:
$INST_TOP/admin/log/MakeAppsUtil_.log

Where is the logs for the adcfgclone.pl are located?

On the database tier:
RDBMS $ORACLE_HOME/appsutil/log//ApplyDBTier_.log

On the application tier:
$INST_TOP/admin/log/ApplyAppsTier_.log

Where the logs for the adconfig are located?

On the database tier:
RDBMS $ORACLE_HOME/appsutil/log///adconfig.log
RDBMS $ORACLE_HOME/appsutil/log///NetServiceHandler.log

On the application tier:
$INST_TOP/admin/log//adconfig.log
$INST_TOP/admin/log//NetServiceHandler.log

How to get the current Patchset level of Oracle Applications products in R12 ?

1) Login to OAM

(Responsibility "Oracle Applications Manager", menu "OAM Support Cart")

and Navigate: Support Cart -> Applications Signature -> Collect -> Check "Product Information" box -> Click on "View" (eyeglasses)

This will display the following patchset information :

Application Name
Current Patch Level
Product Version
Status (Installed, Shared Product, Inactive)

2) The patchset level information can be retrieved directly via sqlplus with the following diagnostic script :

$AD_TOP/sql/adutconf.sql

Tuesday, November 6, 2007

Oracle Apps Upgrade from 11.5.10.2 to Release 12

Upgradation Instructions for Oracle Applications 11.5.10.2 to Release 12
on Redhat Linux AS 4.0 ( Single Node )

Prerequisites

1) Installation of Maintenance Wizard on standalone server

Maintenance Wizard must be installed into an RDBMS 10g with a 10g iAS
ORACLE_HOME on a UNIX or Linux machine.

Here is an example of Maintenance Wizard Installation on a standalone server.

Instructions for Maintenance Wizard Installation

Required RPMs

kernel-2.6.9.-11.EL  ( uname -r )

binutils-2.15.92.0.2-13.i386.rpm
gcc-3.4.3-22.1.i386.rpm
gcc-c++-3.4.3-22.1.i386.rpm
glibc-common-2.3.4-2.9.i386.rpm
libstdc++-3_1.4.3-22.1.i386.rpm
libstdc++-devel-3.4.3-22.1.i386.rpm
openmotif21-2.30-11.RHEL4.4.i386.rpm

Users and Groups :

groupadd oinstall

groupadd dba

useradd -g oinstall -G dba oracle

Configure Kernel Parameter :

vi /etc/sysctl.conf

kernel.sysrq = 0
kernel.msgmnb = 65535
kernel.shmall = 2097152
kernel.shmmax = 4294967295
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 142
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.rmem_max=262144
net.core.wmem_default=262144
net.core.wmem_max=262144

Save and Run sysctl -p

Set up a shell

You must set up either remote shell (rsh/remsh) or secured shell (ssh) between
the Maintenance Wizard node and every remote Applications node. The tool will
not work without having at least one of these shells successfully configured. Follow
the instructions below for OpenSSH shell you wish to use for remote access:

Setting up OpenSSH: Follow this procedure if you will be using OpenSSH:

On the Maintenance Wizard Node:

Log in as the user who will own Maintenance Wizard.

Generate the ssh key by issuing the following command:

ssh-keygen -t rsa

Press the Enter key three times.

CD into the .ssh directory, which is located under the home directory. Note that
a file called id_rsa.pub is created.

Use FTP to copy id_rsa.pub to the /tmp directory of the Remote Nodes.

On the Remote Node(s):

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.

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

Create a directory called .ssh in the home directory.

If an authorized_keys file does not exist, create a new, empty one.

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 file called authorized_keys in this
directory, open it in vi, go to the bottom of the file, add one blank line and then copy
and paste the contents of the file /tmp/id_rsa.pub into the existing file and save it.)

Verify that the .ssh directory permission is set to 700.

Verify that the authorized_keys file permission is set to 600.

Verify that the $HOME directory does not have write permissions for group and others.

chmod go-w $HOME

Ensure that the ssh daemon is running.

Repeat the above steps for each Remote Node.

Test the installation:

Login to the Maintenance Wizard Node as Maintenance Wizard owner.

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]

      1. When prompted to confirm the identity, respond "Yes".
      2. Disconnect from the server.
      3. Execute the following command:

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

Only the word foo should 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 content of the authorized_keys file contains the content of id_rsa.pub of client

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 foo appears, then repeat the step above to remove all .login,
.profile or similar files until ONLY the word foo appears.

Maintenance Wizard version 2.x requires Oracle RDBMS 10g (10.2.0) with 10g iAS (10.1.3).

We recommend that you do not attempt to "re-use" an existing 10g database. Install a
new standalone Oracle 10g ORACLE_HOME for use by Maintenance Wizard.

10g Release 2 Database Installation

/etc/security/limits.conf

* soft nproc 2047
* hard nproc 16384
* soft nofile 1024
* hard nofile 65536

Create the directories in which the Oracle software will be installed:

mkdir -p /u01/app/oracle/product/10.2.0/db_1
chown -R oracle.oinstall /u01

Login as the oracle user and add the following lines at the end of the .bash_profile file:

TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_1; export ORACLE_HOME
ORACLE_SID=oracle; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib;
export CLASSPATH
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi

Install RDBMS 10g using the following command:

./runInstaller

-Specify the desired ORACLE_HOME location.

-Choose "Enterprise Edition".

-Uncheck the option called "Create Starter database". Click NEXT.

-Optionally, specify the oraInventory and operating system group, then click NEXT.

-After successful Product-Specific Prerequisite Checks, choose

"Install database Software only" and click NEXT

-Click INSTALL.

-When the installation has completed, exit the installer.

-As same user, Install Oracle 10g iAS ORACLE_HOME.

-Install a new standalone Oracle 10g iAS ORACLE_HOME for use by Maintenance Wizard.

-Set the DISPLAY variable appropriately and export it.

Run the installer.

./runInstaller

-Specify the installation directory.

-Choose "Advanced Installation Mode" and click NEXT.

-Choose "Web Server and Process Management" (or "Integrated Web Server,
J2EE Server and Process Management") and click NEXT.

-Select your desired method of port configuration and click NEXT.

-Optionally, select your desired Administration Instance settings and click NEXT.

-Specify your Cluster Topology Configuration and click NEXT.

-Click INSTALL.

-Exit the installer.

When the installation has completed, exit the installer.

-Create the database.

-Set the ORACLE_HOME variable appropriately.

-ORACLE_HOME=<path to the RDBMS HOME>; export ORACLE_HOME

-Change to the bin directory.

-cd $ORACLE_HOME/bin

Run the database creation utility.

./dbca

-Choose "Create a Database".

-Choose "General Purpose".

-Specify the Global Database Name.

-Specify whether to configure to database with Enterprise Manager.

-Set the default password for the SYS and SYSTEM accounts.

-Choose your storage mechanism. We recommend that you choose "File System"
and select a Common Location.

-Specify any desired recovery options.

-Specify NO sample schemas.

-In the Character Sets tab, do NOT modify the Default Language (American)
and Default Date Format (US).

-Specify the desired values for parameters SGA, PGA and processes.

-When the process has completed, exit the Database Creation Assistant. Set up
the listener for the Oracle RDBMS ORACLE_HOME. Create LISTENER.ora and
TNSNAMES.ora files in the Oracle RDBMS $ORACLE_HOME/network/admin directory.

LISTENER.ORA file

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS_LIST =
        (ADDRESS = (PROTOCOL = TCP)(HOST = ias.oneapps.com)(PORT = 1521))
      )
    )
  )
SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = oracle)
      (ORACLE_HOME = /u01/oracle/10.2.0)
      (SID_NAME = oneapps)
    )
  )

TNSNAMES.ora file

ORACLE =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ias.oneapps.com)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = oracle)
    )
  )

Set up the listener for the Oracle iAS ORACLE_HOME. Either copy the
tnsnames.ora file or create a symbolic link.

To copy the file:

cp <ORACLE_HOME>/network/admin/tnsnames.ora <iAS _HOME>/network/admin/

Or, to create a symbolic link:

cd <iAS _HOME>/network/admin
ln -s <ORACLE_HOME>/network/admin/tnsnames.ora tnsnames.ora

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 to your datafile.

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

Verify that Zip and UnZip executables are installed and that ping is in the
$PATH using the following commands:

which zip
which unzip
which ping

Installation Steps

Login to the system as the same UNIX user that you used to install the
RDBMS and iAS.

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=<RDBMS ORACLE_HOME>; export ORACLE_HOME
PATH=$ORACLE_HOME/bin:$PATH; export PATH
TWO_TASK=<connect_string >;export TWO_TASK
TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN
IAS_HOME=<IAS ORACLE HOME >; export IAS_HOME

Create a directory to extract the tool into (this will become your $EOF_HOME).
Oracle recommends that you create the Maintenance Wizard directory in the
RDBMS $ORACLE_HOME directory.  Then set the $EOF_HOME environment variable
as follows:

cd $ORACLE_HOME
mkdir eof
EOF_HOME=$ORACLE_HOME/eof; export EOF_HOME

Download the latest Maintenance Wizard Full Install version ( Patch 6398371
as of now ) and 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

Domain name for Maintenance Wizard Node [us.oracle.com]:
SYSTEM password for the Maintenance Wizard instance [manager]:
Schema name for storing Maintenance Wizard. [NEWEOF]:
Maintenance Wizard patch stage [$EOF_HOME/patches]:
Email for Anonymous FTP []
Metalink Username []:
Metalink Password []:

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

Domain =
Oracle Home =
Connect String =
System Password =
Database Schema =
EOF Patch Stage =
Email for Anonymous FTP =
OracleMetaLink Username =
OracleMetaLink Password =

Choose option 2 to review the todo.txt file for information about additional steps
that you must perform, then choose option 3 to exit the installer.

- Stop and restart iAS.

- opmnctl stopall
- opmnctl startall

Post Install Steps

� Secure the $EOF_HOME/EOF.env file.

  • chmod 700 $EOF_HOME/EOF.env
  • Setup a client machine with Microsoft Internet Explorer (IE) 6.0 or higher.
  • In IE, under Tools -> Internet Options, click Settings. Select the radio button
    for "Every visit to the page."
  • Click OK twice to exit IE Internet Options.
  • Login to the tool using the following URL and the pre-assigned username and
    password: SYSADMIN/SYSADMIN:

http://<hostname>.<domain>:<ApachePort>/EOF/

 

Coming Soon the Pre-Upgrade, Upgrade and Post Upgrade of Release 12.

Thursday, October 18, 2007

Oracle Applications Release 12 Installation on Red Hat Enterprise Linux AS/ES 4.0 (32-bit)

 

Operating Systems Requirements

Kernel Requirements

Red Hat Enterprise Linux AS/ES 4.0
2.6.9-42.EL
To determine version, enter: $ uname - r

 

Required Packages

  • glibc-2.3.4-2.25
  • glibc-common-2.3.4-2.25
  • binutils-2.15.92.0.2-21
  • compat-libstdc++-296-2.96-132.7.2
  • gcc-3.4.6-3
  • gcc-c++-3.4.6-3
  • libgcc-3.4.6-3
  • libstdc++-3.4.6-3
  • libstdc++-devel-3.4.6-3
  • openmotif21-2.1.30-11.RHEL4.6**
  • pdksh-5.2.14-30.3
  • setarch-1.6-1
  • make-3.80-6.EL4
  • gnome-libs-1.4.1.2.90-44.1
  • sysstat-5.0.5-11.rhel4
  • compat-db-4.1.25-9
  • control-center-2.8.0-12.rhel4.5
  • xscreensaver-4.18-5.rhel4.11
  • libaio-0.3.105-2
  • libaio-devel-0.3.105-2

Eg: To Check, # rpm -q <package-name> , To Install, # rpm -Uvh <package-name.rpm>

After installing these patches, run ldconfig -v.

 

JDK 5.0 Requirements

JDK is bundled with Oracle Applications.

 

Software Requirements

  • ar
  • gcc
  • g++
  • ld
  • ksh
  • make
  • X Display Server

Eg : which ar, which gcc, xclock

 

Kernel Settings

Edit the /etc/sysctl.conf file to configure your kernel settings. After editing the file, use the "sysctl -p" command or restart the system to invoke the new settings

 

Parameter                                   Value

kernel.semmsl                               256

kernel.semmns                             32000

kernel.semopm                             100

kernel.semmni                              142

kernel.shmall                                2097152

kernel.shmmax                             Half the size of the physical memory (in bytes), and at least 2147483648

kernel.shmmni                              4096

kernel.msgmax                              8192

kernel.msgmnb                             65535

kernel.msgmni                              2878

fs.file-max                                     65536

net.ipv4.ip_local_port_range          1024 65000

net.core.rmem_default                   262144

net.core.rmem_max                       262144

net.core.wmem_default                  262144

net.core.wmem_max                      262144

 

Domain Name System (DNS) Resolver Parameters

Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values when the operating system is installed. These low values may cause attempted network connections to an Oracle database to fail. If this happens, add or update the following entries to these minimum settings in the /etc/resolv.conf file on each server node:

options attempts:5
options timeout:15
 

Verifying Host Names

Use the following to verify host name settings:

Verify that the /etc/hosts file is formatted as follows:


  1. 127.0.0.1 localhost.localdomain localhost

    <ip_address> <node_name>.<domain_name> <node_name>


  2. Verify that the /etc/sysconfig/network file is formatted as follows:

    HOSTNAME=<node_name>.<domain_name>


  3. If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.



  4. If you changed any files in the previous steps, restart the system.


 

Modifying the Number of Open File Descriptors

Open the /etc/security/limits.conf file and change the existing values for "hard" and "soft" parameters as follows. Restart the system after making changes.

Note: If the current value for any parameter is higher than the value listed in this document, then do not change the value of that parameter.

  * hard nofile 65535
* soft nofile 4096
* hard nproc 16384
* soft nproc 2047
 

Net Service Listeners in Multi-user Installations

Net Service Listeners use the /var/tmp.oracle directory to store temporary files. To give all users in a multi-user installation write privileges, update /var/tmp/.oracle with 777 permissions:

$ chmod 777 /var/tmp/.oracle
 
Create Users and Groups
groupadd dba
useradd -g dba oracle    ( db tier )
useradd -g dba applmgr ( apps tier )
 

Creating the Stage Area Directory



Follow these steps to set up a stage area installation:



Log in as the operating system user with sufficient privileges to mount, unmount, and eject the DVD. This user must also have write privileges to the stage   area that you set up.
Insert the Start Here disk in the DVD-ROM drive.
Mount the DVD (conditional).
If your system runs on a UNIX platform, and if you do not use AutoMount, you must mount the Start Here disk now.
Verify software version (perl).
You must have perl 5.0053 or higher installed, and it must be in your PATH. Use the following commands to identify the perl version and its location. The command is the same for both UNIX and Windows platforms:
perl -v

On UNIX, set the environment variable DISPLAY to an active and authorized display.


Run the adautostg.pl script.
UNIX:
$ cd
$ perl /mnt/cdrom/Disk1/rapidwiz/adautostg.pl

 
image 
 

Starting Rapid Install
Once the stage directory is created, start Rapid Install as described in the following section.
UNIX:
Example
$ cd /u01/Stage12/startCD/Disk1/rapidwiz
$ ./rapidwiz

 


 


image


Proceed with the wizard


 


image


Proceed with the wizard


 


image


Select Accept if you want to install Oracle Configuration Manager ( Not Mandatory )


 


image


if OCM Selected , then you will have to fill up CSI, Metalink Account


 


image


For Single Node fresh Installation, Select Create a new configuration,


If Multi Node Installation, and if this was the second node then you have to load


the configuration file created from the first node ( usually found in /tmp )


 


image


Select Port Pool


 


image


Fill Database Node Configurations


 


image


Select the Licensing


 


image


Select Additional Licensing if reqd.


 


image


Select Country Specific Functionalities


 


image


Select Internationalization Settings


 


image


Select Primary Application Node Settings


The services provide the following functionality, which differs significantly from
Release 11i and also uses new terminology:


This Service Group:               Supports:



Root Services                       Oracle Process Manager (OPMN)


Web Entry Point Services       HTTP Server


Web Application Services       OACORE OC4J
                                            Forms OC4J
                                            OAFM OC4J


Batch Processing Services      Applications TNS Listener
                                            Concurrent Managers
                                            Fulfillment Server


Other Services                        Oracle Forms Services
                                             Oracle MWA Service


 


Applications nodes should have services enabled as follows:
. For Web and Forms services: Root Services, Web Entry Point Services, Web Application Services, and Other Services
. For Concurrent Processing services: Batch Processing Services



As an example, consider a two-node installation where you wish to deploy the Applications database and Concurrent Processing services on Server A, and Web
and Forms services on Server B.
. On Server A, you would select Batch Processing Services.
. On Server B, you would select Root Services, Web Entry Point Services, Web Application Services, and Other Services.


In terms of ORACLE_HOME creation, the result will be that:
Server A has an ORACLE_HOME for the 10g R2 Applications database, plus an ORACLE_HOME for Application Server 10.1.2,  and an ORACLE_HOME for Application Server 10.1.3. 


Server B has an ORACLE_HOME for Application Server 10.1.2, and an ORACLE_HOME for Application Server 10.1.3.


 

image


If your installation if multi-node then you can specify the other server configuration here.


 


image


Automatic validation checking


 


image


Pre-Install Checks passed


 


image


Ready for Installation


 


image


Post Install Checks are passed


 


image


Installation is Complete and Connect to Oracle Application Release 12