I'm more than a little surprised that you are regularly compiling packages on maintenance windows (as opposed to application deployment) , pinning objects can (and should IMO) be done via a startup trigger and a control table. However having said all that I'd most likely achieve a quiet maintenance window by ensuring all DBA access is via services and not having the services autostart. A blunter instrument would be to keep the listener(s) down On Nov 22, 2011 7:12 PM, "kapil vaish" <kapilvaish1@xxxxxxxxx> wrote: > > Hi Guys , > > For some of our RAC envs, we do following during cold backup . > > 1. Shutdown DB > 2. Take backup > 3. startup DB in restricted mode > 4. Do maintenace work like compile packages, pin packages,some index/table > reorg etc and then > 5. open DB to users ( in normal mode) > > These all DBs are in RAC environment and we don't register them in the > CRS. So, even when the server is shutdown, the DB will not automatically > start and open to users without doing maintenance work. > Now there is a requirement to register all the dbs in CRS along with > services .With this registration, an init.d script is created to start CRs > (crsctl start crs) . CRS will then start up the database and open to > users. I will not be able to do my maintenace work. Are there any options > to start the DB in restricted mode with RAC startup and then run scripts to > do maintenance automatically before the DB is opened to users ? > > any pointers are appreciated .. > > thanks > kapil > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l