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
lockups using Oracle10g on SUSE9.3

lockups using Oracle10g on SUSE9.3

2005-09-09       - By Clayton

Reply:     1     2     3     4     5     6     7  

> a typical freeze is very uncommon for Oracle!

I know.  That's what baffles me.


> If a unix system behaves like this it's to 99% hardware and to 90% RAM.
>
> Even if switching to oracle might indicate a problem with ORACLE.
>
> Triple check your RAM.
>
> If possible remove 512MB each at a time and retry.
>
> I don't believe it has something to do with non-certified SuSE 9.3.


I desperately hope it's not RAM.  My last system died due to RAM issues
- it did mean IT was able to upgrade me to a nice shiny new AMD64 though :-)

I've done RAM tests on this computer about a month ago.. let it
memtest86 run over a weekend.  No errors.  I will drop it into memtest86
again this weekend.

No lockups with any other heavy system loads.

I've done a lot of Google searghing for the ORA-01031 (See ORA-01031.ora-code.com) error.. and lots
of people have reported similar problems, but the solutions given
haven't worked in my case.

I'd be happy if I could kill the dB completely and setup a new instance.
 Prob is.. the minute I fire up dbca and click on the SID the computer
locks up.

C.

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