ORA-00600 INTERNAL ERROR when inserting
ORA-00600 INTERNAL ERROR when inserting
Hi,
Database Version is 8.1.7.2,
Forms Version is 6.0.8.17.1
When the user click a button that inserts into a table, they used to get the following message:
ORA-00600 INTERNAL ERROR CODE,arguments:[qersoGBnosortRowP],[1],[],[],[],[],[],[].
The insert statement was of the form:
insert into target_table(index,program,fiscal_year)
select distinct index,program,fiscal_year
from temporary_table
group by index,program,fiscal_year,object,object_detail.
The query was executing fine in SQL*Plus, but the insert threw the same error.
I modified the insert statement to:
insert into target_table(index,program,fiscal_year)
select index,program,fiscal_year
from temporary_table
group by index,program,fiscal_year
After dropping the distinct and reducing the number of group by columns, the insert was successful.
I want to know how the removal of the distinct and reducing the number of group by columns would affect the insert statement.
TIA
Software/Hardware used:
Software/Hardware used:
ASKED:
May 13, 2004 1:40 PM
UPDATED:
May 20, 2004 8:00 PM
Answer Wiki:
1) can't group by a column you don't reference
2) the distinct may return more than one value
To see all answers submitted to the Answer Wiki: View Answer History.
1) can’t group by a column you don’t reference
2) the distinct may return more than one value
TIA,
Actually, you can group by a column that isn’t in your select; however it may result in exact duplicates in your result set. In your case, you handled this through the use of ‘distinct’. Not sure the purpose of your distinct and then grouping to a further detail level–doesn’t seem logical to me.
I notice that your original sql had no select columns that were a ‘group by’ expression, such as count or sum. distinct isn’t a group by expression. I’m surprised that SQL*Plus was running it ok.
S.Holtmeyer
Don’t understand the logic either. I am just maintaining the system. Threw up the internal error for the first time after being in production for nearly 4 years, so that is how I came to notice the SQL.
Thanks anyway for your replies.