Hi,
>
>
> I do not know whether the following will help in identifying
> the problem:
> We are running Oracle's 'analyze' on all our tables once every
> day. Oracle support person us told that there is some problem
> with the cost-based optimization that is done by Oracle (after
> 'analyze'), which causes Oracle to core dump (rarely).
> So, we tried to hint Oracle to not use cost-based optimization (by
> adding '/*+ RULE */' in the query).
>
> With this change, the problem is not happening.
>
> Even without any of these changes, the script with plain DBI version of
> the same query is not having this problem. So, I guess there
> is something that DBIx::Recordset does in addition to our query,
> which is causing this problem.
>
You can set $DBIx::Recordset::Debug to 2 before creating your object, then
you see the SQL that DBIx::Recordset creates and can compare it with the SQL
you use with plain DBI, or try the same SQL Statement without using
DBIx::Recordset.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925151
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
