You need Rdb (Oracle's other database) for that to work:
eg:
SQL> seelct count(*) from pot;
%SQL-I-SPELLCORR, identifier SEELCT replaced with SELECT
334
1 row selected
SQL> show version
Current version of SQL is: Oracle Rdb SQL V7.1-101
Underlying versions are:
Database with filename pas_batch_db
Oracle Rdb V7.1-10
Rdb/Dispatch V7.1-101 (OpenVMS Alpha)
Regards,
Bruce
-----Original Message-----
From: Rachel Carmichael [mailto:wisernet100_at_yahoo.com]
Sent: Tuesday, 22 July 2003 12:04 PM
10gR2 will automatically correct the errors.
I'm waiting for the version that will know that I *meant* to type
"select" when I actually type "seelct"
- Daniel Fink <daniel.fink_at_sun.com> wrote:
> Okay, so its Monday...
>
> What I meant to say is that are the queries with different execution
> plans the ones encountering 7445s. If there is a common thread in the
> execution plans (i.e. hash join instead of nested loops), then the hj
> may be triggering the 7445s.
>
> Actually, 10g will have a new "FORETELL PLAN" feature that will
> predict the execution plan and all associated errors, complaints,
> incorrect data...
>
> "Gogala, Mladen" wrote:
> >
> > Actually, I'm quite unaware of ORA-07745 as an execution plan. Can
> "EXPLAIN
> > PLAN"
> > foretell the error?
> >
> > Mladen Gogala
> > Oracle DBA
> > Phone:(203) 459-6855
> > Email:mgogala_at_oxhp.com
> >
> > -----Original Message-----
> > Sent: Monday, July 21, 2003 6:20 PM
> > To: Multiple recipients of list ORACLE-L
> >
> > Michael,
> > When you say 'different execution plans', what are the
> differences?
> > Is the choice in execution plans causing the ORA-07445? If so, why
> are the
> > execution plans different (there has to be a reason)? Statistics,
> > parameters, etc. will alter the execution plan choices.
> > The 7445 definitely deserves a call to Oracle Support
> (through SAP
> > if need be). 7445s are a royal pain to diagnose (like 600s).
Received on Mon Jul 21 2003 - 20:26:09 CDT
