ORA-600 Error

[pt35258]

We are experiencing a ORA-600 error on 11G (same code against 10G is ok)

.NET 4, dot Connect for Oracle 6.60.258

According to our DBA:
Seems like we hit a bug in 11g because of ANSI syntax and large JOINS. The bug number/patch number is 9324531. We have had limited success setting the optimizer_features_enable parameter back to 10.2.0.4.

1. Is there a suggestion from Devart on how to address?
2. DBA recommends changing joins from ANSI syntax to oracle Syntax, ex:
instead of using syntax like "LEFT OUTER JOIN" use "where table_a.column = table_b.column".

Appreciate any suggestions

[Pinturiccio]

Does this issue persist if you use SQL Plus on Oracle 11G? If yes, this is an Oracle issue. In any case try to use a workaround recommended by DBA.

[pt35258]

Thanks for the response.
How do I change the join syntax?

We are using EF + LINQ so the associated tables are just referenced using .Include statements and the resulting SQL is generated at runtime.

is there a way to influence the syntax that the DEVART provider generates or do we need to fall back to declaring the explicit joins in the LINQ query?

[pt35258]

Yes, the issue does repeat on 11G if I:

- use the same LINQ query in LINQPAD

- or if I use a EF profiling tool to capture the generated SQL statements and run them in SQL Developer.

[Shalex]

Unfortunately, changing JOIN generation from ANSI syntax to Oracle syntax is not easy task. It could make sense for supporting Oracle 8 and Oracle 9, but this is not actual now, as you understand.

This is an Oracle bug, and they should fix it. Maybe they will release a patch for this problem.

Possible workaround. Do you really need Include? You can avoid using it with the help of Lazy Loading. This can be a temporary solution although summary performance of your application will be decreased.

[pt35258]

We are expereincing this error again.

Devart.Data.Oracle.OracleException: ORA-00600: internal error code, arguments: [kkqcscpopn_Int: 0], [], [], [], [], [], [], [], [], [], [], []

(Last time we painfully refactored our EF entity nodel to decrease the column ocunt.

The Oracle error indicates this likely cause
Internal errors from query with ANSI join and many columns

The Oracle recommendation is to rewrite the query to avoid ANSI join syntax.

Since the sql is generated at runtime by dotConnet for Oracle, I am asking again can you chg the product so that the syntax pattern used can be controlled by a parameter?

[Shalex]

We will investigate the possibility to implement the switch from ANSI to Oracle syntax and post here about the results. There is no timeframe at the moment.

[alva114]

Hi,
ORA-00600 error is the most annoying situation for any user. I too found this error while accessing the Oracle database file. Luckily found a post that helped to fix this error sharing you the lick hope it works for you.

http://oracle.filerepairtool.net/blog/f ... 1210-error