Oracle Apps R12 (12.1.1) Installation Issue – RW-50004 , RW-50010

on Thursday, 4 April 2013

Oracle Apps R12 (12.1.1) Installation Issue – RW-50004 , RW-50010



Technology Stack changes in 12.1.1
1. Default database version is 11g  (10g in 12.0.X ; 9i in 11i)
2. Default forms and report version is 10.1.2.3 (10.1.2.2 in 12.0.4 ; 8.0.6 in 11i)
3. Default Web Server version is 10.1.3.4 (10.1.3.0.X in 12.0.X ; 9i/1.0.2.2.2 in 11i).


Disk Space for 12.1.1
Vision Database 194 GB
Application Tier 30 GB

Installation Issue   Oracle Apps Installation is 5 step process

Step1 & Step 2 are database tier related


Step 1 – 0-20% - Oracle Database Software Installation including registration of DB ORACLE_HOME in inventory. To know more about inventory click here
Step 2 - 20-40% - Oracle Database creation including copy of data files from staging area to data top


Install log file for 0-40% is located at $INSTALL_BASE/ db/ tech_st/ 11.1.0/appsutil/ log/<context_name>/MMDDHHMM.log 


Step 3, 4 and 5 are application tier related

Step 3 – 40-60% – Oracle Technology Stack Installation (10.1.2 and 10.1.3 ORACLE HOME) for Application Tier
Step 4 – 60-80%  – APPL_TOP and PRODUCT Top setup
Step 5- 80-100% – Configuration, Startup and Checks

Install log file for 60-100% is located at $INSTALL_BASE/ inst/ apps/ <context_name>/ logs/ MMDDHHMM.log


At around 37% Installer failed with message in log file at  $Install_Base/db/ tech_st/ 11.1.0/ appsutil/ log/ $SID_HOSTNAME/ MMDDHHMM.log ->  RW-50010: Error: – script has returned an error RW-50004: Error code received when running external process. Check log file for details.

after several unsuccessful attempts I looked at /var/log/messages and found messages like
Out of Memory: Killed process 2592 (ovisr12) .


OOM-KILLER - The OOM killer, a feature enabled by default (on Linux) to protect system from hang by terminating processes using high memory.

If kernel cannot find memory to allocate when it’s needed, it puts in-use user data pages on the swap-out queue, to be swapped out. If the Virtual Memory (VM) cannot allocate memory and cannot swap out in-use memory, the Out-of-memory killer may begin killing current user-space processes. It will sacrifice one or more processes in order to free up memory for the system when all else fails.

Solution : 

Turn oom-killer off:
  # echo “0″ > /proc/sys/vm/oom-kill   (turn off)
  # echo “1″ > /proc/sys/vm/oom-kill    (turn on) More information hereThis issue is also reported in Metalink Note # 460790.1
Other possible reasons for RW-50004/RW-50010

1. If RW-50004/10 @ ORACLE_HOME registration with inventory (DB_HOME or Oracle Application Server 10.1.2 & 10.1.3 HOME); check privileges to oraInventory location
or
If this is re-install (from previous failed installation), check ORACLE_HOME is not already registered in Inventory>

2. Corrupt media file – For error like AC-00023: Error: Exception: java. io. File NotFound Exception with RW-50004/10
You are welcome to leave a comment.

0 comments:

Post a Comment