Re: select on a view -> ORA-12571

Laurenz Albe schrieb am 08.02.2006 in
<1139389475.59592_at_proxy.dienste.wien.at>:

> Andreas Mosmann <keineemails_at_gmx.de> wrote:

>> there is a view that is compiled fine. It is also possible to select 
>> from this view. And it is also possible to use a where- clause. But if I 
>> use the field VID_SBA inside the where- clause I get an error ORA-12571 
>> an the connection to DB is closed.
>> Where do I have to look for the problem?

> The description of ORA-12571 is
> *Cause: An error occurred during a data send.
> *Action: Not normally visible to the user. For further details, turn
> on tracing and reexecute the operation. If error persists, contact
> Oracle Customer Support.

Now I constantly get
ORA-03113 end-of-file on communication channel

the result is the same, connection broken and thats all.

> This seems like something that should not happen and is possibly a bug,
> particularly if you can reproduce it with a certain query.

> Have a look into the alert log and see if there is a trace file on the
> server that contains additional information.
I looked into alert.log and there is no entry for this time (and around).

> Try client and server tracing and see if new insights can be gained.
When I started it inside SQLPlus with sql_trace = true a tracefile is created with all statements and more in it without the last one, that produces the error.

> If you can't find anything, you'll have to ask Oracle (if you have a
> support contract).
> But be assured that the first thing they will tell you is to upgrade to
> the latest fix level (9.2.0.7) and see if the problem persists.
This will be a problem.
1st: So Oracle is to be installed twice on server and clients, because there are applications running that need 9.2.0.1 2nd: If Oracle is installed second time and the error is up and away and I can't reproduce it my application will be delivered without any guarantee whether the problem is solved or not!

I had the problem months before. As fast as come it went away again without any change by myself. Now, short before the program is delivered the problem came back. The only thing I did is to run some statistics. If I set the database back to before (lot of work) it will be as slow as before, so this can not be the right way :(

> Yours,
> Laurenz Albe

Thank you
Andreas Mosmann

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