Damn, I hate this having to hit reply all thing. L
In case anyone else might be interested …
Pete
"Controlling developers is like herding cats." Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!" Bruce Pihlamae, long-term Oracle DBA From:
Pete Sharman [mailto:peter.sharman@xxxxxxxxxx]
Painful means of death should definitely be inflicted. ;)
Just as a matter of interest, you could end up with more than one row in DUAL in versions that are now ancient history for most of us. I remember in a previous life having a manager do maintenance on the database one night (at his insistence that he knew what he was doing). Next day, all the Forms 3 apps we had died on startup because they had fields populated by a SELECT INTO FROM DUAL type statement. Turned out we now had two rows in DUAL, because the “knowledgeable” manager had run an import twice. We never let him forget what he’d done. J
If memory serves me correctly, later versions now ignore multiple rows in DUAL anyway. Not sure where that came in though – 9.2?
Pete
"Controlling developers is like herding cats." Kevin Loney, Oracle DBA Handbook
"Oh no, it's not. It's much harder than that!" Bruce Pihlamae, long-term Oracle DBA From:
oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Frank B Hansen
Hi Raj
That was the issue !
system@HCRD9397> select object_name , object_type, owner from dba_objects where object_name like '%DUAL%'; OBJECT_NAME
OBJECT_TYPE OWNER
system@HCRD9397> drop table system.dual; Table dropped.
system@HCRD9397> select object_name , object_type, owner from dba_objects where object_name like '%DUAL%'; OBJECT_NAME
OBJECT_TYPE OWNER
system@HCRD9397> select * from dual; D I will now try to hunt down the ones responsible and kill them slowly !
Thanks, Frank
|