Re: Really strange bug? (View, Partitioning)

Hi,

thanks for the ideas!

(1) RULE-hint has no influence in the behaviour

(2) COUNT(*) worked errorfree, so we broke the * down to the single columns available through the view. Finally we found, that including a certain column, which is generated by a PL/SQL-Function, forces the error. That particular column is not used in the WHERE-clause, it only appears in the SELECT-clause.

(3) On our development system (same OS, same DB-version, same scripts applied to build the DB, only part of the data because production is way to huge) the error is not reproducible.

Next step: Forcing the customer to patch to 8.1.7.3

Again thanx for any help!

On 10 Apr 2002 19:21:26 -0500, Galen Boyer <galendboyer_at_yahoo.com> wrote:

>On Tue, 09 Apr 2002, marc_at_marcblum.de wrote:
>> SELECT *
>> FROM my_view
>> WHERE adress = 'home sweet home'
>> AND my_timestamp
>> BETWEEN to_date('01.03.2002','dd.mm.yyyy')
>> AND to_date('30.04.2002','dd.mm.yyyy')
>>
>> returns NO ROWS!!!!!!!!
>
>I'm not even sure if it would help or shed light, but I'd be curious.
>What does count(*) bring back?
>
>How bout
>SELECT *
> [...]
>AND to_date('30.03.2002','dd.mm.yyyy')?
>
>How bout
>SELECT *
> [...]
>BETWEEN to_date('01/03/2002','dd/mm/yyyy')
>AND to_date('30/03/2002','dd/mm/yyyy')?
>
>other iterations as well?
>
>--
>Galen deForest Boyer
>Sweet dreams and flying machines in pieces on the ground.

regards
Marc Blum
mailto:marc_at_marcblum.de
http://www.marcblum.de Received on Mon Apr 15 2002 - 14:30:38 CDT