Path: news.netfront.net!news.glorb.com!postnews.google.com!i7g2000prf.googlegroups.com!not-for-mail
From: Peter Teoh <htmldeveloper@gmail.com>
Newsgroups: comp.databases.oracle.server
Subject: "warm starting" vs non-"warm starting"?
Date: Wed, 13 Feb 2008 18:50:28 -0800 (PST)
Organization: http://groups.google.com
Lines: 63
Message-ID: <94533dc0-471b-4b6a-9445-780d6d4ea3e9@i7g2000prf.googlegroups.com>
NNTP-Posting-Host: 192.190.205.4
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1202957428 23582 127.0.0.1 (14 Feb 2008 02:50:28 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 14 Feb 2008 02:50:28 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: i7g2000prf.googlegroups.com; posting-host=192.190.205.4; 
 posting-account=-OLFiwoAAABGBCrVVvx5wLu28NHfIKKs
User-Agent: G2/1.0
X-HTTP-UserAgent: Opera/9.25 (X11; Linux i686; U; en),gzip(gfe),gzip(gfe)
Xref: news.netfront.net comp.databases.oracle.server:182427

I created an index on obj$ today:

SQL> create index ooee on obj$(name, obj#);
create index ooee on obj$(name, obj#)
                     *
ERROR at line 1:
ORA-00701: object necessary for warmstarting database cannot be
altered

Don't quite understand this, and did some other things, and after some
time, I discovered this - if u persistently apply the same SQL:

SQL> create index ooee on obj$(name, obj#);
create index ooee on obj$(name, obj#)
                     *
ERROR at line 1:
ORA-00701: object necessary for warmstarting database cannot be
altered

SQL> create index ooee on obj$(name, obj#);
create index ooee on obj$(name, obj#)
                     *
ERROR at line 1:
ORA-00701: object necessary for warmstarting database cannot be
altered

SQL> create index ooee on obj$(name, obj#);
create index ooee on obj$(name, obj#)
                     *
ERROR at line 1:
ORA-00701: object necessary for warmstarting database cannot be
altered

SQL> create index ooee on obj$(name, obj#);
create index ooee on obj$(name, obj#)
                     *
ERROR at line 1:
ORA-00701: object necessary for warmstarting database cannot be
altered

SQL> create index ooee on obj$(name, obj#);
create index ooee on obj$(name, obj#)
                     *
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-00060: deadlock detected while waiting for resource

First there must be a difference between warmstarting and non-
warmstarting.   What is it?   (what is the difference between all the
YYY$ tables vs any other tables - be it in SYS schema or not?   why is
it forbidden to modify these tables vs those non-YYY$ tables - there
must be a reason?  this is because the database is already opened
anyway, so, is it a precautionary measure, or is there a physical
reason not to do this?   if it is a physical reason, there there must
be some other error, which is not likely.   therefore, if this is a
precautionary measure, the list of warm starting tables that is
advised not to be modified must be stored somewhere, and if we can
modify these, the error will go away, right?)

Why the difference in error message - there must be something
executing ASYNCHRONOUSLY IN THE BACKGROUND?

Please enlighten me :-).