Re: Oracle Error 600, [733] ...

From: Andreas Mosmann <mosmann_at_expires-28-02-2010.news-group.org>
Date: Thu, 25 Feb 2010 14:39:53 +0100
Message-ID: <1267105193.96_at_user.newsoffice.de>

Mark D Powell schrieb am 22.02.2010 in
<38e0b443-2f67-4a18-9a3f-3f1781354cb4_at_g11g2000yqe.googlegroups.com>:

> On Feb 22, 5:10 am, Andreas Mosmann <mosm..._at_expires-28-02-2010.news-
> group.org> wrote:

>> Hi,
>>
>> For case of statistics there is made a copy from a database some time
>> ago. I produced a SQL- Statement, that worked fine on the actual
>> database, but when I use the same statement on the other DB I got an
>> Oracle Error 600, followed by some values (the 1st is 733).
>> I do not know the differences between both DBs exactly, but of course
>> the admin changed some preferences for this one way DB. When I looked
>> for the reason of this error to find out, which changes are to be made
>> to get the results of my statement, I read, that there is/was a
>> metalink- Page, that describes some/all 600- errors depending on the 1st
>> parameter.
>> I could not connect to metalink (I did it last time many month ago),
>> because it did not only want to get to know very much of my personal
>> state, but any kind of service number. Assuming that there is no free
>> way to go there anymore I like to ask you the following:
>> - Is there someone, who knows about this web form? Does it exist
>> anymore, so that it is useful to buy such service number?
>> - Does anybody know the problem OE 600, [733]?
>>
>> Best regards
>> Andreas
>>
>> Oracle 9.2.0.7.0
>>
>> --
>> wenn email, dann AndreasMosmann <bei> web <punkt> de

> I suggest you look at fixing your Oracle support access.

> Oracle support note 146580.1 ORA-600 [733] "memory request size is too
> big for this port (o/s)" lists about 10 bug reports related to this
> error.  The note suggests reducing the sort_area_size and
> hash_area_size and re-running the query.  It is not 100% clear in the
> note but this solution may only apply if a hash_join is being used in
> the plan.

> This note may not apply to your issue. Thank you. Probably this is my problem. I changed the sga_max_size to nearly the same value as the original database and retried the query. I harvested a similar error Ora 600, with Parameters [KGHALP1], [0x0]...
When I looked for it at metalink I got a result like known bug, there could be the following symptoms:
.. Ora 600 [733], Ora 600 [KGHALP1] ...
Should be fixed in 9.2.0.6

But I use Oracle 9.2.0.7 AND on the original version it works fine. Does anyone has an idea what to do except patching to 9.2.0.8?

> HTH -- Mark D Powell --
It helped, thank you. BTW: now I know my metalink password.

Andreas

-- 
wenn email, dann AndreasMosmann <bei> web <punkt> de

Received on Thu Feb 25 2010 - 07:39:53 CST