Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
SLES9 32 bit multiple databases and kernel.shmmax

SLES9 32 bit multiple databases and kernel.shmmax

2005-06-02       - By michael.d.taylor@(protected)

Reply:     1     2  

I am evaluating the use of SLES9 for running large manufacturing/advanced
planning based Oracle ERP 11.5.10 instances.  On Solaris, we would normally
require a 2-4 GB SGA in order to get all of our critical processes to
complete without erroring out.  64 bit Linux is not yet certified for the
ERP database, but seems to work fine in my testing.  We normally purchase
server quality 4 CPU machines with lots of RAM.  There may be 1 or 2
instances on a production box, I know ugh, but with 150 instances, some
things have to share.  Normally, 5 or 6 instances will be on a development
box running Solaris.  

On a similar class Linux machine with the 32 bit OS loaded, if I startup 1
1.7 GB SGA instance, I get the following error starting a second instance
even with less than 1 GB of SGA:

  SQL> startup
  ORA-27102 (See ORA-27102.ora-code.com): out of memory
  Linux Error: 22: Invalid argument

I am using SLES9 SP1 plus latest kernel patch (2.6.5-7.151-bigsmp)

sysctl.conf looks like the following:

kernel.shmmax=3294967296
kernel.shmall=3294967296
kernel.sem=1250 32000 100 256
vm.disable_cap_mlock=1
net.ipv4.ip_local_port_range= 1024 65000
net.core.wmem_default=262144
net.core.wmem_max=262144
net.core.rmem_default=262144
net.core.rmem_max=262144

Are there any ideas of what I can do to allow the oracle user to be able to
start multiple large SGA instances?  I would have thought kernel.shmmax
would have been per process not per user.  The testing machine has 32 GB of
RAM.  I cannot increase kernel.shmmax beyond 4 GB, and even at 4 GB, I
cannot start 2 1.7 GB SGA instances.

Thanks,
-Michael Taylor

--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting