Thanks for your help.  I found the cause.  It was a daemon that our
consultants run to gather information and monitor our database.  We stopped
the daemon.  And that took care of the error and core dumps.

Ana


                                                                                       
                            
                    "Mohan, Ross"                                                      
                            
                    <MohanR@STARS        To:     Multiple recipients of list ORACLE-L 
<[EMAIL PROTECTED]>       
                    -SMI.com>            cc:                                           
                            
                    Sent by:             Subject:     RE: ora-07445                    
                            
                    root@fatcity.                                                      
                            
                    com                                                                
                            
                                                                                       
                            
                                                                                       
                            
                    02/05/01                                                           
                            
                    01:45 PM                                                           
                            
                    Please                                                             
                            
                    respond to                                                         
                            
                    ORACLE-L                                                           
                            
                                                                                       
                            
                                                                                       
                            




nothing before or after?


no checkpointing? no archiving?  whats was going
on from, say, 12 noon  or so?


-----Original Message-----
Sent: Monday, February 05, 2001 1:00 PM
To: Multiple recipients of list ORACLE-L






Here is what I get in the alert log:


Errors in file /oracle02/app/oracle/admin/ORTE/udump/orte_ora_15115.trc:
ORA-07445: exception encountered: core dump [lxdgetobj()+60] [SIGSEGV]
[Address not mapped to object] [1651271016] [] []
Mon Feb  5 12:55:20 2001
Errors in file /oracle02/app/oracle/admin/ORTE/udump/orte_ora_15641.trc:
ORA-07445: exception encountered: core dump [lxdgetobj()+60] [SIGSEGV]
[Address not mapped to object] [1651271016] [] []
Mon Feb  5 12:57:44 2001
Errors in file /oracle02/app/oracle/admin/ORTE/udump/orte_ora_16105.trc:
ORA-07445: exception encountered: core dump [lxdgetobj()+60] [SIGSEGV]
[Address not mapped to object] [1651271016] [] []


Thanks


Ana






                    "Mohan, Ross"

                    <MohanR@STARS        To:     Multiple recipients of
list ORACLE-L <[EMAIL PROTECTED]>
                    -SMI.com>            cc:

                    Sent by:             Subject:     RE: ora-07445

                    root@fatcity.

                    com



                    02/05/01

                    11:55 AM

                    Please

                    respond to

                    ORACLE-L









you show a file from your udump.





what is in your bdump? including your alert log.....





-----Original Message-----
Sent: Monday, February 05, 2001 9:55 AM
To: Multiple recipients of list ORACLE-L








I posted a question to the list last week regarding this error and didn't
get any responses.  I'm trying again.  We're on Oracle 8.0.5.2.1, and
Solaris 6.





A few days ago we started receiving ora-07445 errors in the alert log.
This happened when had to reboot the server.  If we shutdown/restart the
database the errors went away.  Starting Friday the errors are happening
when shutting down/starting up the db.  We shutdown the db at midnight and
start it at 2:15 am every day.  We get lots of core dumps and trace files
filling up the file system.  We clean up the files and start the db, after
that we don't receive the errors anymore until next stop/start the db.





I have submitted a tar to Oracle support, but so far they haven't come up
with a solution or a cause for this.  We made the changes they suggested
but it didn't help.  Sun suggested some changes to the hardware, but it
hasn't help either.





Can anyone out there provide some insights on this?  Here is one of our
trace files:





Dump file /oracle02/app/oracle/admin/ORTE/udump/orte_ora_4674.trc
Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production
PL/SQL Release 8.0.5.2.0 - Production
ORACLE_HOME = /oracle02/app/oracle/product/8.0.5
System name:    SunOS
Node name:      auoracle1
Release:        5.6
Version:        Generic_105181-23
Machine:        sun4u
Instance name: ORTE
Redo thread mounted by this instance: 1
Oracle process number: 35
Unix process pid: 4674, image: oracleORTE





Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object),
addr: 0x626c6568, PC: lxdgetobj()+60
*** 2001.02.05.09.20.39.000
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [lxdgetobj()+60] [SIGSEGV]
[Address not mapped to object] [1651271016] [] []
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
-------------------- -------- --------------------
----------------------------





Thanks





Ana E. Choto
American University
Washington, DC





--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: [EMAIL PROTECTED]





Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).










--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: [EMAIL PROTECTED]


Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).







-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to