.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
Proliant DL740 hangs with sles8 (k_smp 2.4.21-190)

Proliant DL740 hangs with sles8 (k_smp 2.4.21-190)

2004-03-04       - By McAllister, Andrew
Reply:     <<     21     22     23     24     25     26     27     28     29     30     >>  

> -- --Original Message-- --
> From: Sightler, Tom [mailto:tsightler@(protected)]
snip
> > To me open files looks low at 1024, but our old system is
> set this way
> > and never hung once.
>
> Did your old system run the same OS and same version of
> Oracle with async IO?  If not then it's probably not fair to
> compare the two.
Oracle version was the same, but we ran SuSE 8 PRO not SLES and had no
async IO.

> I'd at least look at this as, based on your proc output, your
Snip
Good advice.
> to the same as the system limit.  Lot's of Oracle setup docs
> suggest setting both the system file number limit and the
> Oracle users ulimit to 65535 or greater.
>
> We used to get lots of ORA-03113 (See ORA-03113.ora-code.com) errors before we increased
> our limits.  Are you having some of those?  Our current
Yes we are, a fair amount. Usually on the second day after a reboot.
They get worse and worse as time goes on.

When we restarted our server last night we set the file limit for oracle
to 16384.

Thanks
Andy

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