Noticed it first with 5.1.

Currently we're running 6.0 MP4.   Now that you mention it I won't swear
I've seen it since we went to 6.0 MP4.  (But I also won't swear I
haven't either.)   Since it wasn't an every day occurrence we wouldn't
have noticed it "going away" after the 6.0 MP4 upgrade.   

It was just something we saw once in a while we would live with it until
end of a week when we could bounce daemons on the master.

One thing we did notice with 6.0 MP4 in relation to RMAN - we had
upgraded the master but not one client on one DB server we were backing
up with RMAN.  We were seeing things like 25 (communication error) and
52 (tape error) on occasion.  Updating the client to 6.0 MP4 on the
database server being backed up seems to have stopped those.  (The 52
was really odd because we were actually using a DSSU rather than a tape
as the backup device and had never seen a 52 on that before the upgrade
to 6.0 on the master.)  Before the upgrade of the client backups were
completing most days so it was totally incompatible.

-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com] 
Sent: Friday, September 21, 2007 5:39 PM
To: Jeff Lightner
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Odd ball Oracle RMAN backup problem.



On Fri, 21 Sep 2007, Jeff Lightner wrote:

> We see this on occasion for RMAN and also for other client initiated
> backups (as opposed to those we initiate from the master server
> scheduler).
>
> It appears that what occurs is the client process that started the job
> died for whatever reason (sometimes it is a timeout at the client
which
> what we initially saw on RMAN).   When this occurs the master server
> isn't told the job isn't going to complete so shows it "queued".   The
> only way we've found to clear this is to bounce the daemons on the
> master server.   However, it doesn't actually hurt anything since it
> isn't doing anything - it's just an annoyance to see it in the
activity
> monitor.
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin
> Piszcz
> Sent: Friday, September 21, 2007 12:53 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Odd ball Oracle RMAN backup problem.
>
> We have Oracle databases that backup using the RMAN agent.
>
> Every once and awhile with 6.0MP4 we see jobs QUEUED forever, other
jobs
>
> run fine or when the job on the client re-runs it is fine, but every
so
> often there is 1 (or more) jobs that stay queued until you right click
> and
> kill (or bpbdbjos -cancel) them, has anyone seen this before?
>
> I have a case open currently but they are talking to me like they have
> never seen it before?
>
> Justin.
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> ----------------------------------
>
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or
confidential information and is for the sole use of the intended
recipient(s). If you are not the intended recipient, any disclosure,
copying, distribution, or use of the contents of this information is
prohibited and may be unlawful. If you have received this electronic
transmission in error, please reply immediately to the sender that you
have received the message in error, and delete it. Thank you.
>
> ----------------------------------
>
>

What version are you running?

Does it occur with 6.0MP5/6.5.x?

Justin.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu