Prev: MSACCES.EXE to ORACLE via odbc implicit float number conversion
Next: Patching terminology
From: NetComrade on 28 Apr 2010 09:52
I have multiple databases writing to NFS for backups, and the NFS will
be going down for MW.
Is there any way to suspend RMAN jobs w/o downtiming all the
databases, or w/o suspending individual backup jobs?
From: John Hurley on 28 Apr 2010 14:52
NetComrade:

> I have multiple databases writing to NFS for backups, and the NFS will
> be going down for MW.
> Is there any way to suspend RMAN jobs w/o downtiming all the
> databases, or w/o suspending individual backup jobs?

Put em in cron! Or some kind of external scheduler!

Let's see ... if your datbase is having issues and you have something
that is supposed to run but depends on the database ... hmmm ...

If you have something outside the database that doesn't depend on the
database can you put together something that does some checking and
alerting when needed ... hmmm ...
From: Mladen Gogala on 28 Apr 2010 15:25
On Wed, 28 Apr 2010 06:52:36 -0700, NetComrade wrote:

> I have multiple databases writing to NFS for backups, and the NFS will
> be going down for MW.
> Is there any way to suspend RMAN jobs w/o downtiming all the databases,
> or w/o suspending individual backup jobs?


I use the following "kill 'em all" snippet:


declare
cursor csr(usr varchar2) is select sid,serial# from v$session
where username=usr and
status != 'KILLED';
cmd varchar2(40):='alter system kill session ''';
err_msg varchar2(80);
begin
for c in csr(upper('&usr')) loop
begin
execute immediate cmd||c.sid||','||c.serial#||'''';
exception
when others then
dbms_output.put_line('Killing of the SID:'||c.sid||' failed.');
err_msg:=substr(SQLERRM,1,80);
dbms_output.put_line(err_msg);
end;
end loop;
end;
/

It shouldn't be a problem to modify it to fit your purpose. I named this
little snippet "cnorris.sql" because it delivers the fatal roundhouse
kick to the all sessions belonging to the targeted user.

--
http://mgogala.byethost5.com
From: NetComrade on 28 Apr 2010 16:39
On Apr 28, 2:52 pm, John Hurley <hurleyjo...(a)yahoo.com> wrote:
> NetComrade:
>
> > I have multiple databases writing to NFS for backups, and the NFS will
> > be going down for MW.
> > Is there any way to suspend RMAN jobs w/o downtiming all the
> > databases, or w/o suspending individual backup jobs?
>
> Put em in cron!  Or some kind of external scheduler!
>
> Let's see ... if your datbase is having issues and you have something
> that is supposed to run but depends on the database ... hmmm ...
>
> If you have something outside the database that doesn't depend on the
> database can you put together something that does some checking and
> alerting when needed ... hmmm ...


We do all oracle related jobs through grid control, including custom
monitoring scripts, that way we don't have to hunt down outputs from
cron.
If my database is having issues, my grid has nothing to do with it,
it's on different host and a different database.
If my database is not available we fail back to prompt to toubleshoot
it, but we ensure our alerting works otherwise.
With 20-30 databases to track all over the place, cron is really not a
good option. Plus, how is modifying cron on 2-3 dozen hosts easier
then clicking through a few jobs in a single interface?
From: NetComrade on 28 Apr 2010 16:40
On Apr 28, 3:25 pm, Mladen Gogala <n...(a)email.here.invalid> wrote:
> On Wed, 28 Apr 2010 06:52:36 -0700, NetComrade wrote:
> > I have multiple databases writing to NFS for backups, and the NFS will
> > be going down for MW.
> > Is there any way to suspend RMAN jobs w/o downtiming all the databases,
> > or w/o suspending individual backup jobs?
>
> I use the following "kill 'em all" snippet:
>
> declare
> cursor csr(usr varchar2) is select sid,serial# from v$session
>                             where username=usr and
>                             status != 'KILLED';
> cmd varchar2(40):='alter system kill session ''';
> err_msg varchar2(80);
> begin
> for c in csr(upper('&usr')) loop
>    begin
>       execute immediate cmd||c.sid||','||c.serial#||'''';
>    exception
>       when others then
>          dbms_output.put_line('Killing of the SID:'||c.sid||' failed.');
>          err_msg:=substr(SQLERRM,1,80);
>          dbms_output.put_line(err_msg);
>     end;
> end loop;
> end;
> /
>
> It shouldn't be a problem to modify it to fit your purpose. I named this
> little snippet "cnorris.sql" because it delivers the fatal roundhouse
> kick to the all sessions belonging to the targeted user.
>
> --http://mgogala.byethost5.com

Well, this is killing sessions per a certain criteria. What I want to
do is suspend all jobs.. I guess downtiming databases will be the way
to go, or identifying all jobs that should run during a MW
 |  Next  |  Last
Pages: 1 2
Prev: MSACCES.EXE to ORACLE via odbc implicit float number conversion
Next: Patching terminology