> > - the installation script furthermore *creates objects in the sys schema*, > namely create view foo as select * from someX$view > I was told <http://www.oraclenerd.com/2009/07/pmdv-lessons-learned.html>...creating objects in the SYS schema would effectively nullify your support contract with Oracle. Others on here are far more versed as I don't spend any time with Oracle support. On Wed, Feb 17, 2010 at 4:47 PM, Jared Still <jkstill@xxxxxxxxx> wrote: > On Wed, Feb 17, 2010 at 1:20 PM, Martin Bach < > development@xxxxxxxxxxxxxxxxx> wrote: > >> >> - the installation script furthermore creates objects in the sys schema, >> namely create view foo as select * from someX$view >> >> This is disturbing for me >> >> > I also find that disturbing. > > If the database is later upgraded so that the data dictionary tables (X$) > change, > and the custom views no longer compile, there is no way to remove them, or > to recompile them. > > Any attempts to recompile them after that happens will always result in an > ORA-00600 [16206]. > > The only way to avoid it is to remember to drop all custom views based on > x$ tables prior to the database upgrade, and then recreate them, whereupon > they may fail. > > It is actually fairly harmless, unless your app needs them, and they no > longer work. > > Jared Still > Certifiable Oracle DBA and Part Time Perl Evangelist > Oracle Blog: http://jkstill.blogspot.com > Home Page: http://jaredstill.com > > >