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..

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
 

/*+ hint(argument) */

/*+ hint(argument-1 argument-2) */

All hints except /*+ rule */ cause the CBO to be used. Therefore, it is good practise to analyze the underlying tables if hints are used (or the query is fully hinted.

There should be no schema names in hints. Hints must use aliases if alias names are used for table names. So the following is wrong:

select /*+ index(scott.emp ix_emp) */ from scott.emp emp_alias

better:

select /*+ index(emp_alias ix_emp) */ … from scott.emp emp_alias

Why using hints

It is a perfect valid question to ask why hints should be used. Oracle comes with an optimizer that promises to optimize a query’s execution plan. When this optimizer is really doing a good job, no hints should be required at all.

Sometimes, however, the characteristics of the data in the database are changing rapidly, so that the optimizer (or more accuratly, its statistics) are out of date. In this case, a hint could help.

It must also be noted, that Oracle allows to lock the statistics when they look ideal which should make the hints meaningless again.

Hint categories

Hints can be categorized as follows:

• Hints for Optimization Approaches and Goals,
• Hints for Access Paths, Hints for Query Transformations,
• Hints for Join Orders,
• Hints for Join Operations,
• Hints for Parallel Execution,
• Additional Hints

Documented Hints

Hints for Optimization Approaches and Goals

• ALL_ROWS
  One of the hints that ‘invokes’ the Cost based optimizer
  ALL_ROWS is usually used for batch processing or data warehousing systems.
• FIRST_ROWS
  One of the hints that ‘invokes’ the Cost based optimizer
  FIRST_ROWS is usually used for OLTP systems.
• CHOOSE
  One of the hints that ‘invokes’ the Cost based optimizer
  This hint lets the server choose (between ALL_ROWS and FIRST_ROWS, based on statistics gathered.
• RULE
  The RULE hint should be considered deprecated as it is dropped from Oracle9i2.

See also the following initialization parameters: optimizer_mode, optimizer_max_permutations, optimizer_index_cost_adj, optimizer_index_caching and

Hints for Access Paths

• CLUSTER
  Performs a nested loop by the cluster index of one of the tables.
• FULL
  Performs full table scan.
• HASH
  Hashes one table (full scan) and creates a hash index for that table. Then hashes other table and uses hash index to find corresponding records. Therefore not suitable for < or > join conditions.
• ROWID
  Retrieves the row by rowid
• INDEX
  Specifying that index index_name should be used on table tab_name: /*+ index (tab_name index_name) */
  Specifying that the index should be used the the CBO thinks is most suitable. (Not always a good choice).
  Starting with Oracle 10g, the index hint can be described: /*+ index(my_tab my_tab(col_1, col_2)) */. Using the index on my_tab that starts with the columns col_1 and col_2.
• INDEX_ASC
• INDEX_COMBINE
• INDEX_DESC
• INDEX_FFS
• INDEX_JOIN
• NO_INDEX
• AND_EQUAL
  The AND_EQUAL hint explicitly chooses an execution plan that uses an access path that merges the scans on several single-column indexes

Hints for Query Transformations

• FACT
  The FACT hint is used in the context of the star transformation to indicate to the transformation that the hinted table should be considered as a fact table.
• MERGE
• NO_EXPAND
• NO_EXPAND_GSET_TO_UNION
• NO_FACT
• NO_MERGE
• NOREWRITE
• REWRITE
• STAR_TRANSFORMATION
• USE_CONCAT

Hints for Join Operations

• DRIVING_SITE
• HASH_AJ
• HASH_SJ
• LEADING
• MERGE_AJ
• MERGE_SJ
• NL_AJ
• NL_SJ
• USE_HASH
• USE_MERGE
• USE_NL

Hints for Parallel Execution

• NOPARALLEL
• PARALLEL
• NOPARALLEL_INDEX
• PARALLEL_INDEX
• PQ_DISTRIBUTE

Additional Hints

• ANTIJOIN
• APPEND
  If a table or an index is specified with nologging, this hint applied with an insert statement produces a direct path insert which reduces generation of redo.
• BITMAP
• BUFFER
• CACHE
• CARDINALITY
• CPU_COSTING
• DYNAMIC_SAMPLING
• INLINE
• MATERIALIZE
• NO_ACCESS
• NO_BUFFER
• NO_MONITORING
• NO_PUSH_PRED
• NO_PUSH_SUBQ
• NO_QKN_BUFF
• NO_SEMIJOIN
• NOAPPEND
• NOCACHE
• OR_EXPAND
• ORDERED
• ORDERED_PREDICATES
• PUSH_PRED
• PUSH_SUBQ
• QB_NAME
• RESULT_CACHE (Oracle 11g)
• SELECTIVITY
• SEMIJOIN
• SEMIJOIN_DRIVER
• STAR
  The STAR hint forces a star query plan to be used, if possible. A star plan has the largest table in the query last in the join order and joins it with a nested loops join on a concatenated index. The STAR hint applies when there are at least three tables, the large table’s concatenated index has at least three columns, and there are no conflicting access or join method hints. The optimizer also considers different permutations of the small tables.
• SWAP_JOIN_INPUTS
• USE_ANTI
• USE_SEMI

Undocumented hints:

• BYPASS_RECURSIVE_CHECK
  Workaraound for bug 1816154
• BYPASS_UJVC
• CACHE_CB
• CACHE_TEMP_TABLE
• CIV_GB
• COLLECTIONS_GET_REFS
• CUBE_GB
• CURSOR_SHARING_EXACT
• DEREF_NO_REWRITE
• DML_UPDATE
• DOMAIN_INDEX_NO_SORT
• DOMAIN_INDEX_SORT
• DYNAMIC_SAMPLING
• DYNAMIC_SAMPLING_EST_CDN
• EXPAND_GSET_TO_UNION
• FORCE_SAMPLE_BLOCK
• GBY_CONC_ROLLUP
• GLOBAL_TABLE_HINTS
• HWM_BROKERED
• IGNORE_ON_CLAUSE
• IGNORE_WHERE_CLAUSE
• INDEX_RRS
• INDEX_SS
• INDEX_SS_ASC
• INDEX_SS_DESC
• LIKE_EXPAND
• LOCAL_INDEXES
• MV_MERGE
• NESTED_TABLE_GET_REFS
• NESTED_TABLE_SET_REFS
• NESTED_TABLE_SET_SETID
• NO_FILTERING
• NO_ORDER_ROLLUPS
• NO_PRUNE_GSETS
• NO_STATS_GSETS
• NO_UNNEST
• NOCPU_COSTING
• OVERFLOW_NOMOVE
• PIV_GB
• PIV_SSF
• PQ_MAP
• PQ_NOMAP
• REMOTE_MAPPED
• RESTORE_AS_INTERVALS
• SAVE_AS_INTERVALS
• SCN_ASCENDING
• SKIP_EXT_OPTIMIZER
• SQLLDR
• SYS_DL_CURSOR
• SYS_PARALLEL_TXN
• SYS_RID_ORDER
• TIV_GB
• TIV_SSF
• UNNEST
• USE_TTT_FOR_GSETS