DP sends the commands from the script (provided in the backup spec) sequentially via. DP Integration to RMAN to start Offline backup of Oracle database as follows.
RMAN> CONNECT TARGET *
2> CONNECT CATALOG *
3> HOST 'exit';
4> run {
5> shutdown immediate;
6> startup mount;
7> allocate channel 'dev_0' type
'sbt_tape'
8> parms
'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=oradb101,OB2BARLIST=Oracle_DB_Spec01)';
9>
10> send device type 'sbt_tape'
'OB2BARHOSTNAME=Orasrv01';
11> backup incremental level 0
12> format 'Oracle_DB_Spec01<oradb101_%s:%t:%p>.dbf'
13> database;
14> backup
15> format 'Oracle_DB_Spec01<oradb101_%s:%t:%p>.dbf'
16> current controlfile;
17> alter database open;
18> }
19> EXIT
RMAN-06005: connected to target database:
oradb101 (DBID=101)
RMAN-06008: connected to recovery
catalog database
RMAN-00571:
==================================================
RMAN-00569: ========= ERROR
MESSAGE STACK FOLLOWS =========
RMAN-00571: ==================================================
RMAN-03002: failure of shutdown command
at 03/02/2014 09:31:22
ORA-01013: user requested cancel of
current operation
Recovery Manager complete.
[Major] From: ob2rman@Orasrv01 "oradb101"
Time: 03/02/14 09:31:22
External utility
reported error.
Execution of the
script starts and there was connection established between DP and the Oracle
database via. DP Integration. Eventually, once the backup goes smooth the script would bring the database online and complete, if not continue reading the post till end.
The backup has error messages:
RMAN-03002: failure of shutdown command
at 03/02/2014 09:31:22
ORA-01013: user
requested cancel of current operation
Here, the database is refusing the shutdown command issued
by the backup script. Offline backup requires database to be in down and
mounted status. Check if the database is engaged by long running tasks if any.
That's right, when we checked the database was busy with long running oracle jobs which was the root cause to override the shutdown command. Try running the backup when the DB is free from jobs/tasks and during non-business/less or no traffic to DB, after all it's an offline backup.
