.ora-code.com

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
More than 1GB PGA under Oracle 9.2.0.5/Solaris 9

More than 1GB PGA under Oracle 9.2.0.5/Solaris 9

2005-07-26       - By Billy Verreynne (JW)
Reply:     1     2  


Buechi Martin Wrote:

> Is there a possibility that Oracle 9.2.0.5 under Solaris 9 can
allocate
> more than 1 GB PGA?

Yes.

> We are running an application that bulk collects without a limit
clause.

That's like driving a sportscar on a race track - without brakes. Not
a question of whether it will crash, but a question of just how many
bits and pieces will be left over after the crash.

> A rewrite is in progress, but will take several days.

In my experiences, it takes less than a few minutes to correct a BULK
COLLECT loop that does not use a LIMIT clause. Of course, it depends
on how may BULK COLLECTs there are to fix. But several days? That
sounds like a developer that does not know what he/she needs to do to
fix the code.

> In the meanwhile we are looking for a way to increase the memory
max.

Doubt that it will work as PGA memory is nothing but the data segment
of dedicated or shared server process that runs that PL/SQL code. The
max size of the data segment (DS) is a function of the o/s - the limit
imposed by the kernel (if any) on a DS and whether there is free
memory available to service that process image malloc requests. Seems
like you are running into the latter. Malloc fails. And there is very
little that can be done about it, but to use less memory.

--
Billy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
http://www.freelists.org/webpage/oracle-l