RE: allowing developers to create guaranteed restore point

From: Fergal Taheny <ftaheny_at_gmail.com>
Date: Tue, 3 Dec 2013 23:19:02 +0000
Message-ID: <CAOuMUT5Ku++Z3W6++S8z261S_wSWuOkiosO0XtJXiphCC9pqdQ_at_mail.gmail.com>



Hi Chris,

I implemented this with a couple of database procs. One runs as sys from a datatabase job every minute. It checks a table for a request and if one exists, it creates the restore point and places a response in the table. Another proc is run by the developers which places the request in the table then polls the table every few seconds untils the response is found and then exits successfully.

I'll send you the code if you want to go this way.

Regards,
Fergal
On 3 Dec 2013 19:37, "Stephens, Chris" <Chris.Stephens_at_adm.com> wrote:

> That seems much more appropriate. I forgot you could execute shell
> scripts through dbms_scheduler.
>
>
>
> Using external tables to do this felt like poor way to get this done.
>
>
>
> Thanks!
>
>
>
> *From:* rjamya [mailto:rjamya_at_gmail.com]
> *Sent:* Tuesday, December 03, 2013 1:31 PM
> *To:* Stephens, Chris; oracle-l_at_freelists.org
> *Subject:* Re: allowing developers to create guaranteed restore point
>
>
>
> Chris,
>
>
>
> We do this using external job. restore point is taken via a shell script,
> this shell script is called via dbms_scheduler job. If you set it up like
> this, you can give execute on a procedure (in sys schema) to developers.
> This procedure will run the scheduler job and your requirements will be
> met.
>
>
>
> We recently extended this to our release management, it takes a restore
> point before release begins, so if something goes wrong, we have that
> restore point as a failback. Since it is all automated via liquibase, it is
> hands off for us.
>
>
>
> Raj
>
> CONFIDENTIALITY NOTICE:
> This message is intended for the use of the individual or entity to which
> it is addressed and may contain information that is privileged,
> confidential and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient or the employee or agent
> responsible for delivering this message to the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, please notify us immediately by email reply.
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Dec 04 2013 - 00:19:02 CET

Original text of this message