Seems your script assumes that the database isn't open -- odd
assumption for an RMAN script - especially one that looks to be doing
hot backups. I'm not sure there's any reason to have the "alter
database open;" line in the script, unless you've got something
shutting down your database and bringing it partly up before the
script runs.

I don't know if you're reading the "hangs" correctly. RMAN output
tends to start a backup piece and output all of the data files that
are going into that backup piece, then start feeding those to tape.
It's in a proprietary format so it's reading the datafiles from
multiple points and interleaving them is some fashion that it knows
how to decipher later. What you're probably seeing is the beginning of
a new backup piece each time there's log output. More interesting
would be to watch your tape/network IO and see that there is actually
data flowing freely.

-Charlie

On 10/24/05, Nigel Phillips <NIGELPHI AT uk.ibm DOT com> wrote:
>
> Hi guys,
>
> Anyone seen this type of problem before - using old version 3.4 on HP
> servers in an SSO environment all fibre connected to 20 x 9840c drives in a
> L700e library. Problem I'm getting only affects oracle backups using rman,
> SAP and standard backups no issues. What I see in  the rman backup log is
> the data getting written then hangs then more data written hangs etc till it
> gets to the point of opening database and then hangs again. These hangs can
> be anything from 10 to over 60mins each time. Example of main part of rman
> rcv script which is basically the same across the servers.
>
> run
> {
>    allocate channel t1 type 'SBT_TAPE';
>    allocate channel t2 type 'SBT_TAPE';
>    allocate channel t3 type 'SBT_TAPE';
>    setlimit channel t1 kbytes 2097150;
>    setlimit channel t2 kbytes 2097150;
>    setlimit channel t3 kbytes 2097150;
>
>    backup
>      incremental level 0
>      filesperset 10
>      database
>      format '%U' ;
>
>    # now that the backup is complete, open the db.
>    alter database open;
> }
> allocate channel for delete type 'sbt_tape';
> crosscheck backup of database completed before 'SYSDATE-70';
> delete expired backup of database completed before 'SYSDATE-70';
> release channel;
>
>
> Also the crosscheck seems very slow. I am not a dba (black art like
> networks) but i assume nothing if wrong with the above script. What gets me
> is the part where it says it is opening the database and nothing happens for
> ages - talked to dba's but got nowhere they say they have no problem with
> rman catalog and problem is netbackup, yet the physical data is written
> quickly (checked NB logs for this)  but the bells and whistles around rman
> can take an eternity. Any help comments will be appreciated.
>
> By the way if Mark Donaldson reads this post you are the dog's danglies your
> scripts and comments rock.
>
> Nigel