Description of problem:
I'm getting 'Could not install database' when running Satellite installer on sun-x4600m2-01.rhts.eng.bos.redhat.com.


Version-Release number of selected component (if applicable):
Satellite 5.4.0 (on RHEL5-U5)


How reproducible:
always


Steps to Reproduce:
1. Install RHEL5-U5 on sun-x4600m2-01.rhts.eng.bos.redhat.com
2. # ./install.pl --answer-file=.../answers.txt --non-interactive --disconnected --run-updater


Actual results:
# ./install.pl --answer-file=.../answers.txt --non-interactive --disconnected --run-updater
[...]
* Setting up database.
** Database: Installing the database:
** Database: This is a long process that is logged in:
** Database:   /var/log/rhn/install_db.log
*** Progress: #
Could not install database.
# tail /var/log/rhn/install_db.log
[...]
SQL> SQL> SQL> rem
SQL> rem $Header: utlxplan.sql 08-may-2004.12:53:19 bdagevil Exp $ xplainpl.sql
SQL> rem
SQL> Rem Copyright (c) 1988, 2004, Oracle. All rights reserved.
SQL> Rem NAME
SQL> REM    UTLXPLAN.SQL
SQL> Rem  FUNCTION
SQL> Rem  NOTES
SQL> Rem  MODIFIED
SQL> Rem     bdagevil   05/08/04  - add other_xml column
SQL> Rem     bdagevil   06/18/03  - rename hint alias to object_alias
SQL> Rem     ddas       06/03/03  - increase size of hint alias column
SQL> Rem     bdagevil   02/13/03  - add plan_id and depth column
SQL> Rem     ddas       01/17/03  - add query_block and hint_alias columns
SQL> Rem     ddas       11/04/02  - revert timestamp column to DATE (PL/SQL problem)
SQL> Rem     ddas       10/28/02  - change type of timestamp column to TIMESTAMP
SQL> Rem     ddas       10/03/02  - add estimated_time column
SQL> Rem     mzait      04/16/02  - add row vector to the plan table
SQL> Rem     mzait      10/26/01  - add keys and filter predicates to the plan table
SQL> Rem     ddas       05/05/00  - increase length of options column
SQL> Rem     ddas       04/17/00  - add CPU, I/O cost, temp_space columns
SQL> Rem     mzait      02/19/98 -  add distribution method column
SQL> Rem     ddas       05/17/96 -  change search_columns to number
SQL> Rem     achaudhr   07/23/95 -  PTI: Add columns partition_{start, stop, id}
SQL> Rem     glumpkin   08/25/94 -  new optimizer fields
SQL> Rem     jcohen     11/05/93 -  merge changes from branch 1.1.710.1 - 9/24
SQL> Rem     jcohen     09/24/93 -  #163783 add optimizer column
SQL> Rem     glumpkin   10/25/92 -  Renamed from XPLAINPL.SQL
SQL> Rem     jcohen     05/22/92 -  #79645 - set node width to 128 (M_XDBI in gendef)
SQL> Rem     rlim       04/29/91 -  change char to varchar2
SQL> Rem     Peeler     10/19/88 - Creation
SQL> Rem
SQL> Rem This is the format for the table that is used by the EXPLAIN PLAN
SQL> Rem statement.  The explain statement requires the presence of this
SQL> Rem table in order to store the descriptions of the row sources.
SQL> 
SQL> create table PLAN_TABLE (
  2          statement_id       varchar2(30),
  3          plan_id            number,
  4          timestamp          date,
  5          remarks            varchar2(4000),
  6          operation          varchar2(30),
  7          options            varchar2(255),
  8          object_node        varchar2(128),
  9          object_owner       varchar2(30),
 10          object_name        varchar2(30),
 11          object_alias       varchar2(65),
 12          object_instance    numeric,
 13          object_type        varchar2(30),
 14          optimizer          varchar2(255),
 15          search_columns     number,
 16          id                 numeric,
 17          parent_id          numeric,
 18          depth              numeric,
 19          position           numeric,
 20          cost               numeric,
 21          cardinality        numeric,
 22          bytes              numeric,
 23          other_tag          varchar2(255),
 24          partition_start    varchar2(255),
 25          partition_stop     varchar2(255),
 26          partition_id       numeric,
 27          other              long,
 28          distribution       varchar2(30),
 29          cpu_cost           numeric,
 30          io_cost            numeric,
 31          temp_space         numeric,
 32          access_predicates  varchar2(4000),
 33          filter_predicates  varchar2(4000),
 34          projection         varchar2(4000),
 35          time               numeric,
 36          qblock_name        varchar2(30),
 37          other_xml          clob
 38  );
create table PLAN_TABLE (
*
ERROR at line 1:
ORA-04031: unable to allocate 4176 bytes of shared memory ("shared
pool","unknown object","sga heap(1,0)","object queue ")


Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options


Expected results:
Should work


Additional info:
Please note system itself have 32GB RAM and 140GB HDD.