Re: tuning advisor for an insert statement

It’s unlikely a rollback will kill your system, the rollback will be done in one process. If your system can’t handle one process doing work, you have bigger problems.

I’ve rolled back multiple GB transactions and the only things that cares are the sessions that we’re waiting for the locked resources in the first place.

SQL tuning advisor is by no means the perfect solution, but if you are paying for it then why would you not try to use it. Of course, you can do any analysis on a separate system and apply the findings to your PROD instance (after testing elsewhere).

Regards,
Andy

On Tue, 22 Oct 2019 at 04:42, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

>
> On 10/21/19 4:26 PM, Sayan Malakshinov wrote:
> > Hi Jeffrey,
> >
> > Yes, as far as I remember it executes DML, but then it executes rollback.
> >
> In other words, it kills your system dead. Insert of a few GB into a
> large table, followed by an equally humongous rollback is a nice prank,
> if executed on the database owned by somebody else. Alternatively, it's
> a great way of convincing your boss that you need Exadata. However, that
> strategy might backfire if you don't work in Dilbert-like environment.
> That is why there is SQL trace. Tuning advisor sounds like a really,
> really bad idea in this case.
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l