All Oracle Error Codes
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

RE: [suse-oracle] Large SGA Over SLES8

Bedard, Joe


The Maximum SGA size on SLES 8 that can configured with system defaults
is 1760MB regardless of the kernel parameters. (This is not an SLES
limit but a general 32-bit environment limit. The 64-bit version of
SLES on S/390, AMD64 and IA64 can have massive SGA's with no problems
provided a 64-bit version of Oracle)

There are two strategies to attain larger SGA's on x86 SLES 8.

The first is to lower the mapped base of the Oracle executables.
It's a little involved but can give you SGA's up to 2.7GB's in size.
The draw back is that this strategy cuts into memory space that can be
used by other processes and the PGA if you configure all the way out to
2.7GB's. This page has good info.

The workaround to the above is to configure the shared memory file
system. (shmfs)
Using the SHMFS, SGA's can be configured as large as 62GB's.

Three drawbacks to this strategy, one minor;

The SHMFS is most useful for systems with more than 4GB's of RAM.
Use of the SHMFS precludes the use of multiple DB block sizes.
Setting the indirect data buffers in the init.ora required for using
SHMFS is only in 9i R2.
There is a minor performace hit by using the SHMFS due to some

-----Original Message-----
From: Joao Oliveira [mailto:jcobra@(protected)]
Sent: Wednesday, January 07, 2004 4:10 AM
To: suse-oracle@(protected)
Subject: [suse-oracle] Large SGA Over SLES8


I Am Trying to set sga with 2gb on a machine with 04gb of ram and
when oracle proceed startup I receive

ora-27123 Unable to attach to shared Memory segment.
linux error 22

parameters from init.ora


However in /etc/sysconfig/oracle
the parameter SHMMAX have 3gb (3294967296).

Is it a limit of SLES or Oracle Limit?

Anyone knows a tip to workaround?



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

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