| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: A SQL statement fails darkly
ORA-600 errors should definitely be pursued with Oracle Support, mainly to get ORA-600s documented with Oracle so that the can be fixed or handled more gracefully in the Oracle code and thus everyone benefits.
Metalink is great start for finding info on a particular ORA-600 if you have access.
Unless an upgrade is an option or a patch is available, then generally the only option is to find a workaround to the ORA-600. This means finding out when it occurs, what command actually provoked the error, and finding ways of avoiding the situation.
There are several reasons for discussing ORA 600s outside of Oracle support though. An Oracle support person is usually a junior person (at one point turnover was every 9 months with mainly newbies filling the vacant spots). My experiences with support in the past year have been extremely junior level except for maybe 1 out 10 people. I have had Oracle support people refuse to share pertinent information they felt they couldn't discuss. For this reason, I'd appreciate feedback from the online community if it was out there. One big problem is that Oracle censors alot of valuable info from bug reports. Its much better than it use to be with alot of bug info available in Metalink, but still I have found valuable information in unpublished bugs that have showed me information leading to a workaround for the particular ORA-600s that I've run into. Also I imagine there are a fair number of people on the newsgroup without Metalink or Support. I currently don't have support access, and there have been tons of times I'm either playing on my home LINUX box or NT laptop with Oracle and have not had access to support or metalink. I'd like to encourage people share their experiences with ORA 600 if they could help other people out. (of course everyone needs use their own sense of discretion for what is appropriate or not)
For this particular Oracle 600, I'd like to start the ball rolling. From Metalink:
RDBMS Version: 8.1.6
Operating System and Version: Window NT4
ORA-600:[sdbput_2] may be related to bug 1690703 where this error can be signalled during sort operations. The bug is fixed in Oracle9i. A workaround is to set sort_area_retained_size = sort_area_size.
I recommend you apply the latest patchset for 8.1.6 on NT, which is 8.1.6.3.5 and monitor for further occurrence of these errors. If you encounter the ORA-600:[sdbput_2], set sort_area_retained_size = sort_area_size to verify it resolves the error.
On Tue, 30 Oct 2001 10:04:49 GMT, nsouto_at_optushome.com.au.nospam (Nuno Souto) wrote:
>In a valiant and sublime effort,Alexei Ustyuzhaninov
>frowned, dipped a thumb in soot and doodled:
>
>>ORA-00600: internal error code, arguments: [sdbput_2], [64716], [],
>>[], [], [], [], []
>
>Alexei, ORA-600 means: call ORACLE support.
>No other avenue would be recommended.
>
>
>Cheers
>Nuno Souto
>nsouto_at_optushome.com.au.nospam
Best Wishes
Kyle Hailey
http://oraperf.sourceforge.net
 |
 |