Starting a database and updating tables before schedules run

[MCubitt]

When I do a database copy, I clear up some data before letting folk in to the copy.

Currently, I shutdown the destination, copy the datafiles over the existing ones, start (open) the database with a hacked control file.

Then I run a script to update tables for various reasons. One update is to deactivate batch schedules in our core system (since they should only run in LIVE).

The trouble is, it seems that when the database starts (opens) the schedule says "ooh, I was due to run a while ago (in source db) and so I better run now!".

Is there a way to start the database but not let anything start ? Would this be mount mode? The trouble is, I have to run updates and API calls to action the halt. I wonder if a mounted DB will allow this.

Thanks


Applications Support
UK

 

[KenCunningham]

We have a similar requirement for no batch processing in a test environment, but are fortunate in that I can just pull the PID of the batch schedule agent and kill it as part of the startup process. This is because the batch scheduler is an entirely different application to the database. I assume that's not the case in your instance?

 

[MCubitt]

You are right, (I think) but we do not SOME batch schedules to work, just not all.




Applications Support
UK

 

[sem]

How about setting job_queue_processes to 0?

Regards, Dima

http://seminihin.narod.ru

 

[MCubitt]

Dima,

Please expand on this.

How do I do that?

Are you saying I should add it to the start of my script?

Won't the Db starting kick in the job queues before the job_queue_processes is set to 0?

Sorry if I missed the point completely.

thanks



Applications Support
UK

 

[sem]

I may set it in init.ora. If you use spfile you may specify that pfile during startup.


Regards, Dima

http://seminihin.narod.ru

 

[MCubitt]

Hmm, not really ideal. I don't want to mess with init.ora since this is purely a DB data copy and other processes should run.

I guess I will just have to put the update at the top of my script and keep my fingers crossed!





Applications Support
UK

 

[sem]

There's nothing dangerous in editing init.ora. Moreover it's possible to have multiple files for single instance working in different modes, suppose as OLTP during a day time and as a DSS at night. So I'm still sure that editing single parameter is much better than making unnecessary updates.

Regards, Dima

http://seminihin.narod.ru