Robert,
Well, one sure-fire way I know is to type in "oracle" at the UNIX
command-prompt and just hit "return" -- you get a nice little,
serious-looking ORA-00600 [12235] message in your "alert.log" file.
This has been true since Oracle v6, at least. In some situations, you
also get a nice ".trc" file to go with it...
However, I also know it's a sure-fire way to excite any DBAs who have
automated monitoring of their "alert.log" files and trace files, so be
careful about doing this from an inter-personal perspective... ;-)
...especially if they get paged on such errors and you're doing this
experimentation at 3am... :-) ...please don't ask how I would know that?
Tim Gorman
consultant - Evergreen Database Technologies, Inc.
P.O. Box 1802, Evergreen CO 80437-1802
website = http://www.evdbt.com
email = tim@xxxxxxxxx
mobile = +1-303-885-4526
fax = +1-303-484-3608
Robert Freeman wrote:
Hi folks....
Might sound like a silly question, but I'm
looking for some SQL statements (the more basic the better) in 10gR2
that will cause an ORA-0600 error. If you have one and an associated
test case that you could sent that would be great. You can send to me
direct mail rather than through the newsgroup, robertgfreeman@xxxxxxxxx.
RF
Robert G. Freeman
Oracle Consultant/DBA/Author
Principal Engineer/Team Manager
The Church of Jesus Christ of Latter-Day Saints
Father of Five, Husband of One,
Author of various geeky computer titles
from Osborne/McGraw Hill (Oracle Press)
Oracle Database 11g New Features Now Available for Pre-sales on
Amazon.com!
Sig V1.1
--
http://www.freelists.org/webpage/oracle-l
|
