[Veritas-bu] Any help on an RMAN error message?

thanks to all who responded to me - we tracked our problem down to an 
apparnent NBU misconfiguration:

In spite of the nature of the errors we were seeing (I was growing 
certain the problem was in our RMAN configuration, or an RMAN 
bug...), the problem was eventually solved by correcting the hostname 
of the client in our NBU class.

we were using a technically valid (or at least ping-able from the 
master) hostname for the client, but in the larger enterprise network 
there was a different naming convention required for correct 
communication between the NBU server and the NBU client.

again, thanks for your responses,
rob



>>-----Original Message-----
>>From: Rob Worman [mailto:rob AT colltech DOT com]
>>Sent: Wednesday, August 09, 2000 12:26 PM
>>To: veritas-bu AT mailman.eng.auburn DOT edu
>>Subject: [Veritas-bu] Any help on an RMAN error message?
>>
>>
>>In setting up a new RMAN configuration, there's an error that I can't
>>track down - the text below should hold all the needed clues, I hope.
>>
>>NBU 3.2 patch 412 running on Solaris 7
>>Oracle/RMAN 8.0.6
>>
>>Our backup class is calling an RMAN wrapper script, and here is the
>>relevant bit of that shell script.  (you may safely assume that all
>>the variables are properly defined previous to this code block)
>>
>>----  rman_wrapper.sh  -----
>>su - $ORACLE_USER -c "
>>ORACLE_HOME=/app/oracle/product/8.0.6
>>export ORACLE_HOME
>>ORACLE_SID=test
>>export ORACLE_SID
>>${ORACLE_HOME}/bin/$RMAN TARGET $USER/$PASS@test RCVCAT
>>$USER2/$PASS2@rcat806 cmdfile "$CMDFILE"
>>"
>>RETURN_STATUS=$?
>>----------------------------
>>
>>and here are the actual RMAN commands contained in $CMDFILE:
>>
>>------  rman.rcv  ----------
>>run {
>># Hot database level 0 whole backup
>>allocate channel t1 type 'SBT_TAPE';
>>#allocate channel t2 type 'SBT_TAPE';
>>backup
>>    incremental level 0
>>    skip inaccessible
>>    tag hot_db_bk_level0
>>    filesperset 5
>>    # recommended format
>>    format 'bk_%s_%p_%t'
>>      (database);
>>    sql 'alter system archive log current';
>>    # backup all archive logs
>>    backup
>>     filesperset 20
>>     format 'al_%s_%p_%t'
>>     (archivelog all
>>      delete input);
>>}
>>------------------------------
>>
>>and when I kick off a manual backup of this class, things start out nicely:
>>
>>     1-the manual job goes active in the job monitor
>>     2-one user-initiated job appears
>>     3-the user-initiated job mounts a tape and writes 600k of data
>>     4-the user-initiated job finishes with an exit status of 0
>>
>>but then the manual job finishes with an exit status of 1
>>
>>(this test database should be more like 600MB of data, BTW)
>>
>>so what is going wrong?
>>the interesting part of the rman output looks like this:
>>
>>-----  rman_wrapper.sh.out  --------
>>RMAN-03022: compiling command: allocate
>>RMAN-03023: executing command: allocate
>>RMAN-08030: allocated channel: t1
>>RMAN-08500: channel t1: sid=9 devtype=SBT_TAPE
>>
>>RMAN-03022: compiling command: backup
>>RMAN-03025: performing implicit partial resync of recovery catalog
>>RMAN-03023: executing command: partial resync
>>RMAN-08003: starting partial resync of recovery catalog
>>RMAN-08005: partial resync complete
>>RMAN-03023: executing command: backup
>>RMAN-08008: channel t1: starting datafile backupset
>>RMAN-08502: set_count=2 set_stamp=405165707
>>RMAN-08010: channel t1: including datafile 2 in backupset
>>RMAN-08010: channel t1: including datafile 3 in backupset
>>RMAN-08010: channel t1: including datafile 6 in backupset
>>RMAN-08010: channel t1: including datafile 7 in backupset
>>RMAN-08010: channel t1: including datafile 5 in backupset
>>RMAN-03026: error recovery releasing channel resources
>>RMAN-08031: released channel: t1
>>RMAN-00569: ================error message stack follows================
>>RMAN-03006: non-retryable error occurred during execution of command: backup
>>RMAN-07004: unhandled exception during command execution on channel t1
>>RMAN-10035: exception raised in RPC: ORA-19583: conversation
>>terminated due to error
>>ORA-27016: skgfcls: sbtinfo returned error
>>SVR4 Error: 17469124: Unknown system error
>>Additional information: -12709556
>>ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 408
>>RMAN-10031: ORA-19583 occurred during call to
>>DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
>>---------------------------------------
>>
>>and the client's /usr/openv/netbackup/logs/bphdb log looks like this:
>>
>>-----  bphdb log  ---------
>>10:44:05 [22731] <2> logparams: -sb -rdbms oracle -S kan-sol-prod3
>>-to 300 -c dtsc2_test_rman -s full_test -FULL
>>10:44:05 [22731] <4> bphdb: INF - setenv NB_ORA_MODE=B
>>10:44:05 [22731] <4> bphdb: INF - NB_ORA_CLASS=dtsc2_test_rman
>>10:44:05 [22731] <4> bphdb: INF - NB_ORA_SCHED not defined.
>>10:44:05 [22731] <4> bphdb: INF - NB_ORA_PC_SCHED=full_test
>>10:44:05 [22731] <4> bphdb: INF - NB_ORA_SERV=kan-sol-prod3
>>10:44:05 [22731] <4> bphdb: INF - setenv NB_ORA_FULL=1
>>10:44:05 [22731] <4> bphdb: INF - setenv NB_ORA_INCR=0
>>10:44:05 [22731] <4> bphdb: INF - setenv NB_ORA_CINC=0
>>10:44:05 [22731] <4> bphdb: INF - setenv NB_ORA_USER_INITIATED=0
>>10:44:05 [22731] <4> bphdb: INF - setenv NB_ORA_SCHEDULED=1
>>10:44:05 [22731] <4> bphdb: INF - BACKUP START
>>10:44:05 [22731] <4> bphdb: INF - CONTINUE BACKUP message received.
>>10:44:05 [22731] <4> bphdb: INF - Processing
>>/usr/local/openv/scripts/hot_database_backup_test.sh
>>10:44:05 [22731] <4> bphdb: INF - bphdb still working.
>>10:44:05 [22731] <4> bphdb: INF - Keepalives will be sent every 150 seconds.
>>10:44:05 [22731] <4> bphdb: INF - Waiting for the child status.
>>10:44:05 [22732] <4> bphdb: INF - Child executing
>>/usr/local/openv/scripts/hot_database_backup_test.sh
>>10:44:34 [22731] <16> bphdb: ERR - Script exited with status = 1
>>10:44:34 [22731] <4> bphdb: file /tmp/obackup_class deleted.
>>10:44:34 [22731] <16> bphdb: ERR - bphdb exit status = 1: the
>>requested operation was partially successful
>>
>>10:44:34 [22731] <4> bphdb: INF - EXIT STATUS 1: the requested
>>operation was partially successful
>>----------------------------
>>
>>
>>
>>and it looks to me like this is an RMAN error (most likely
>>configuration, as I don't claim to be an RMAN expert) but I'm not
>>sure what else to look at/for.
>>
>>any help out there?
>>
>>TiA
>>rob
>>_______________________________________________
>>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>--
>Rob Worman, Consultant
>Collective Technologies           cell: 612/802-6850
>"The Power of Many Minds"         alpha page: 1-800-946-4646, pin=1422494

--
Rob Worman, Consultant
Collective Technologies           cell: 612/802-6850
"The Power of Many Minds"         alpha page: 1-800-946-4646, pin=1422494