ORA-00600 error caused by cursor_sharing

ORA-00600 error caused by cursor_sharing

HOST: IBM S85
Main hardware: 6 CPU + 8 GB memory
System: AIX5.2
Patch: ML04
Database: Oracle 9.2.0.4
Middleware: BEA Tuxedo 8.1
The system is a new oltp-type financial system. The performance stress test performed well before the launch. The results did well after the launch, but the log file reported every 10 minutes:
ORA-00600: internal error code, arguments: [736], [7], [0], [128], [128], [], [], [], []
When we encounter a bug in this section, nnd is just a word.
The customer and company's pressure surge like a flood. I explained that it was a normal phenomenon and I didn't have to make a fuss about it. I quickly collected information.

The use of bad telephone lines in the hotel is still unstable, and the fire is not vented.
After some crazy searches, I soon learned that the problem was caused by my own ingenuity. I added a parameter to improve the general usage of variable binding in domestic applications:

Cursor_sharing = force
I used this parameter normally before, and thought the oracle version was relatively high and thought it was more reassuring. The result was that it was not available here. It is estimated that an update/insert statement caused this bug. Nnd

This application is really confusing to me. I want to help it improve efficiency by using help variables, and I still don't appreciate the result ......
Under pressure, I quickly comment out cursor_sharing = force and use the default cursor_sharing = exact.

The problem was finally solved. But I am unwilling to go over the 9i documentation carefully. We recommend using cursor_sharing = similar.

Haha, this is the best of both worlds, most of the SQL uses the bind variables, ora-600 errors are no longer reported.
[@ More @]