First of all following pre-requisites must be checked at the Operating System level.



Packages

SUNWarc

SUNWbtool

SUNWcsl

SUNWhea

SUNWi15cs

SUNWi1cs

SUNWi1of

SUNWlibC

SUNWlibm

SUNWlibms

SUNWsprot

SUNWtoo

SUNWuiu8

SUNWulcf

SUNWxwfnt

Patches

• 125100-04 or higher
• 120473-05 or higher
• 127111-02 or higher
• 137111-04 or higher

Kernel parameters in /etc/system

rlim_fd_max                                     65536

noexec_user_stack                        1

semsys:seminfo_semmni            100

semsys:seminfo_semmsl             256

shmsys:shminfo_shmmax           4294967295

shmsys:shminfo_shmmni            100

ulimit Value Settings

Verify that the owner of the Oracle Application Server and Oracle Database server file systems have the following ‘ulimit’ values:

• time (seconds) = unlimited
• file (blocks) = unlimited
• data (kbytes) = unlimited
• stack (kbytes) = unlimited
• memory (kbytes) = unlimited
• coredump (blocks) = unlimited
• nofiles (descriptors) = 65536

Java requirements

JDK 6 (bundled with R12, no need to manually install)

Operating system utilities

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

Next step is to create required users.

groupadd dba

useradd -g dba oradev

useradd -g dba appldev

passwd oradev

New Password:

Re-enter new Password:

passwd: password successfully changed for oradev

passwd appldev

New Password:

Re-enter new Password:

passwd: password successfully changed for appldev

Now let’s create required directories as root.

mkdir /u01

mkdir /u01/oracle

mkdir /u01/oracle/ERPDEV

mkdir /u01/oracle/ERPDEV/db

mkdir /u01/oracle/ERPDEV/apps

chown oradev:dba /u01

chown oradev:dba /u01/oracle

chown oradev:dba /u01/oracle/ERPDEV

chown oradev:dba /u01/oracle/ERPDEV/db

chown appldev:dba /u01/oracle/ERPDEV/apps

Create Staging area or else you can directly install from DVDs but you may need to switch DVDs during the installation.

Here we have created Staging directory as /u01/R12stage/

There are multiple ways for creating staging areas. The simplest method is to copy all DVD contents to Staging directory in following subfolders.

startCD,  oraDB, oraAppDB, oraApps, oraAS,  NLS-<Language> (if installing NLS)

Or else you can use adautostg.pl to create a staging area automatically.

ORATraining Tip: Execute the following to avoid unexpected errors during the installation since we are doing multiuser installation.
chmod 777 /tmp

ORATraining tip: Sometimes it has been noticed on some Solaris based installation that installation will throw following error.

/u01/R12stage/startCD/Disk1/rapidwiz/rapidwiz: whoami: not found

Execute the following before starting the installation to avoid the issue.

export PATH=$PATH:/usr/ucb/

Starting the installation:

cd /u01/R12stage/startCD/Disk1/rapidwiz

./rapidwiz

ORATraining tip: You can also execute directly with the path like “/u01/R12stage/startCD/Disk1/rapidwiz/rapidwiz/rapidwiz” to avoid selecting DVDs at the end of every component installation.

ORATraining Tip: Sometimes you may encounter following error after starting the installation.

/u01/R12stage/startCD/Disk1/rapidwiz/rapidwiz: /tmp/RapidInstall/bin/runWizard.sh: cannot execute

Execute the following to fix this if you encounter the same.

chmod 777 /u01/R12stage/startCD/Disk1/rapidwiz/bin

Welcome Screen:

Do not change anything in this screen unless you are upgrading existing Oracle Applications release. Express release will go with many default parameters and skip certain steps but not recommended for an Apps DBA.

Keep these blank if installing on test machine. This can always be filled later. You will need a valid CSI number and associated email id for this.

No not change anything in this screen unless you are restarting a failed installation or installing on secondary nodes in case of multinode installation.

Select a port pool here. All default ports will be added by a number selected in port pool and those ports will be assigned accordingly. For example with port pool 10, default ports will change as follows.

Web Server port will become 8010 (8000 + 10)

Forms port will become 9010 (9000 + 10)

Reports port will become 7010 (7000 + 10)

and so on..

This is the working fix for the issue.

Solution-1:

1) Take backup of jvm.dll located at c:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot directory.
2) Copy jvm.dll from C:\Program Files\Java\jre1.6.0_07\bin\client (or whichever highest version of jre you have) to c:\Program Files\Oracle\JInitiator 1.3.1.21\bin\hotspot
3) Clear browser cache and also Oracle Jar cache (Remove all files from c:\documents and settings\<username>\Oralce Jar cache)
4) Close all the browsers and restart

Enjoy !! The issue should have been resolved now !

Solution-2:

In case if you are unable to find the jvm.dll in that location or if the above solution didn’t work for you, you can download the working jvm.dll from this link.

REM
REM FILENAME
REM   cmclean.sql
REM DESCRIPTION
REM   Clean out the concurrent manager tables
REM NOTES
REM   Usage: sqlplus <apps_user/apps_passwd> @cmclean
REM
REM
REM   $Id: cmclean.sql,v 1.4 2001/04/07 15:55:07 pferguso Exp $
REM
REM
REM +==============================+
set verify off;
set head off;
set timing off
set pagesize 1000
column manager format a20 heading ‘Manager short name’
column pid heading ‘Process id’
column pscode format a12 heading ‘Status code’
column ccode format a12 heading ‘Control code’
column request heading ‘Request ID’
column pcode format a6 heading ‘Phase’
column scode format a6 heading ‘Status’
WHENEVER SQLERROR EXIT ROLLBACK;
DOCUMENT
WARNING : Do not run this script without explicit instructions
from Oracle Support
*** Make sure that the managers are shut down     ***
*** before running this script                    ***
*** If the concurrent managers are NOT shut down, ***
*** exit this script now !!                       ***
#
accept answer prompt ‘If you wish to continue type the word ”dual”: ‘
set feed off
select null from &answer;
set feed on
REM     Update process status codes to TERMINATED
prompt
prompt  ————————————————————————
prompt  — Updating invalid process status codes in FND_CONCURRENT_PROCESSES
set feedback off
set head on
break on manager
SELECT  concurrent_queue_name manager,
concurrent_process_id pid,
process_status_code pscode
FROM    fnd_concurrent_queues fcq, fnd_concurrent_processes fcp
WHERE   process_status_code not in (‘K’, ‘S’)
AND     fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND     fcq.application_id = fcp.queue_application_id;
set head off
set feedback on
UPDATE  fnd_concurrent_processes
SET     process_status_code = ‘K’
WHERE   process_status_code not in (‘K’, ‘S’);
REM     Set all managers to 0 processes
prompt
prompt  ————————————————————————
prompt  — Updating running processes in FND_CONCURRENT_QUEUES
prompt  — Setting running_processes = 0 and max_processes = 0 for all managers
UPDATE  fnd_concurrent_queues
SET     running_processes = 0, max_processes = 0;
REM     Reset control codes
prompt
prompt  ————————————————————————
prompt  — Updating invalid control_codes in FND_CONCURRENT_QUEUES
set feedback off
set head on
SELECT  concurrent_queue_name manager,
control_code ccode
FROM    fnd_concurrent_queues
WHERE   control_code not in (‘E’, ‘R’, ‘X’)
AND     control_code IS NOT NULL;
set feedback on
set head off
UPDATE  fnd_concurrent_queues
SET     control_code = NULL
WHERE   control_code not in (‘E’, ‘R’, ‘X’)
AND     control_code IS NOT NULL;
REM     Also null out target_node for all managers
UPDATE  fnd_concurrent_queues
SET     target_node = null;
REM     Set all ‘Terminating’ requests to Completed/Error
REM     Also set Running requests to completed, since the managers are down
prompt
prompt  ————————————————————————
prompt  — Updating any Running or Terminating requests to Completed/Error
set feedback off
set head on
SELECT  request_id request,
phase_code pcode,
status_code scode
FROM    fnd_concurrent_requests
WHERE   status_code = ‘T’ OR phase_code = ‘R’
ORDER BY request_id;
set feedback on
set head off
UPDATE  fnd_concurrent_requests
SET     phase_code = ‘C’, status_code = ‘E’
WHERE   status_code =’T’ OR phase_code = ‘R’;
REM     Set all Runalone flags to ‘N’
REM     This has to be done differently for Release 10
prompt
prompt  ————————————————————————
prompt  — Updating any Runalone flags to ‘N’
prompt
set serveroutput on
set feedback off
declare
c         pls_integer := dbms_sql.open_cursor;
upd_rows  pls_integer;
vers      varchar2(50);
tbl       varchar2(50);
col       varchar2(50);
statement varchar2(255);
begin
select substr(release_name, 1, 2)
into   vers
from fnd_product_groups;
if vers >= 11 then
tbl := ‘fnd_conflicts_domain’;
col := ‘runalone_flag’;
else
tbl := ‘fnd_concurrent_conflict_sets’;
col := ‘run_alone_flag’;
end if;
statement := ‘update ‘ || tbl || ‘ set ‘ || col || ‘=”N” where ‘ || col || ‘ = ”Y”’;
dbms_sql.parse(c, statement, dbms_sql.native);
upd_rows := dbms_sql.execute(c);
dbms_sql.close_cursor(c);
dbms_output.put_line(‘Updated ‘ || upd_rows || ‘ rows of ‘ || col || ‘ in ‘ || tbl || ‘ to ”N”’);
end;
/

prompt

prompt  ————————————————————————

prompt  Updates complete.
prompt  Type commit now to commit these updates, or rollback to cancel.
prompt  ————————————————————————

prompt

set feedback on

REM  <= Last REM statment —————————————————–

CONCSUB <APPS username>/<APPS password>
<responsibility application short name>
<responsibility name>
<username>
[WAIT=N|Y|<n seconds>]
CONCURRENT
<program application short name>
<program name>
[PROGRAM_NAME="<description>"]
[REPEAT_TIME=<resubmission time>]
[REPEAT_INTERVAL= <number>]
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=<resubmission end date and time>]
[NLS_LANGUAGE=<language of the request>]
[NLS_TERRITORY=<territory of the request>]
[START=<date>]
[IMPLICIT=< type of concurrent request>
[<parameter 1> ... <parameter n>]

Examples:

Active Users
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDSCURS

Prints Environment Variables
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDPRNEV APPL_TOP

Table Name: FND_CONCURRENT_REQUESTS

Column Name: PHASE_CODE
 

 
Table Name: FND_CONCURRENT_REQUESTS

Column Name: STATUS_CODE
 

This document is divided into the following sections:

• Section 1: Terminology
• Section 2: Supported Scenarios
• Section 3: References

The most up-to-date version of this document can be obtained in Note 783188.1.

Section 1: Terminology

Cloning an Oracle E-Business Suite system that uses an Oracle Real Application Clusters (Oracle RAC) enabled database involves numerous different technology components and steps, and would therefore be a complex, error-prone process if carried out manually.

To speed up, simplify, and enhance reliability of the process, Oracle offers the following tools for use in cloning RAC Enabled Oracle E-Business Suite systems:

• Rapid Clone – Command-line tool
• Oracle Application Management Pack for Oracle E-Business Suite (AMP) – GUI-based tool used for automated end-to-end cloning

This document provides details of the RAC scenarios that are currently certified for cloning using these tools. Other scenarios are planned as shown.

Note: Scenarios not shown are not supported.

Section 2: Supported Scenarios

The following table illustrates the various cloning permutations that exist with different versions of Oracle E-Business Suite and its components, operating system software, and the cloning tools available.

Key:

N/A = Not Applicable
TBD = To Be Decided