Re: ORA-07445 in Alert.log

From: Brian Peasland <dba_at_nospam.peasland.net>
Date: Thu, 31 Aug 2006 22:03:06 GMT
Message-ID: <J4vuLB.79n@igsrsparc2.er.usgs.gov>

jbmorla_at_gmail.com wrote:
> joel garry wrote:

>> Ora 600 and 7445 lookup tool (Note:153788.1):
>>
>> https://metalink.oracle.com/metalink/plsql/f?p=130:3:4161157751554936370::::p3_database_id,p3_docid,p3_show_header,p3_show_help,p3_black_frame,p3_font:NOT,153788.1,1,0,1,helvetica
>>
>>
>> (you may need to click on it again after you login if you get the
>> metalink login screen)
>>
>> Note:211909.1 is the intro to 7445 errors.
>>
>> jg
>> --
>> @home.com is bogus
>> Naw, they don't look that much alike:  http://englishrussia.com/?p=253

>
> Hi
>
> You got this error first:
>
> Thu Aug 31 12:00:19 2006
> Thread 1 cannot allocate new log, sequence 1300
>
>
> Then 6 hours later you got the core dump?
>
> It looks like you have a problem with the undo file size.
>

Huh?

What does "cannot allocate new log" and the subsequent ORA-7445 have to do with the undo size?

Cheers,
Brian

-- 
===================================================================

Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

Received on Thu Aug 31 2006 - 17:03:06 CDT