Rman Backup set specification slowness. [message #650790] |
Wed, 04 May 2016 00:38 |
muktha_22
Messages: 527 Registered: December 2009
|
Senior Member |
|
|
Hi All,
Need a guidance,
We have setup the RMAN Backup as mentioned below.
connect target sys/password
connect catalog <username/password>@<connect string>
alter session set nls_date_format='dd-mon-yyyy hh24:mi';
set echo on;
run
{
allocate channel dev1 type disk format '<path>\db_t%t_s%s_p%p';
select current_timestamp from dual;
allocate channel dev2 type disk format '<path>\db_t%t_s%s_p%p';
select current_timestamp from dual;
BACKUP archivelog all ;
select current_timestamp from dual;
delete noprompt archivelog all completed before 'sysdate-1';
select current_timestamp from dual;
release channel dev1 ;
select current_timestamp from dual;
release channel dev2 ;
select current_timestamp from dual;
}
Analyzing the LOG FILE after finding the tremendous slowness in the performance gives the below
Between the below mentioned process taken 1.5 Hours:
channel dev1: specifying archived log(s) in backup set
and
channel dev1: starting piece 1 at <date and time>
But the backup set got finished within 4 mins.
Kindly guide me, where the problem resides.
Thanks and Regards
Muktha
|
|
|
|
|
|
|
|
|
Re: Rman Backup set specification slowness. [message #650798 is a reply to message #650797] |
Wed, 04 May 2016 01:30 |
muktha_22
Messages: 527 Registered: December 2009
|
Senior Member |
|
|
Hi Michel, Mahesh,
Thanks for the help.
1) I have modified the date and the deleted the rows after the problematic BACKUP SET finished successfully.
2) I don't think the issue is connecting to the CATALOG server, as the time shown in the log, the below statement executed in few seconds.
connected to target database: <name> (DBID=<Number>)
connected to recovery catalog database
3) And the below line also executed in few seconds.
allocated channel: dev1
channel dev1: SID=<ID> device type=DISK
Starting backup at <Date> 12:33:16
current log archived
channel dev1: starting archived log backup set
Which means, connection to the Remote catalog server is fine.
Connecting to the RMAN Client and the Oracle Instance is fine.
4) But the problem is resides in the line of, which takes 1.5 Hours.
channel dev1: specifying archived log(s) in backup set
5)And this happened only to the First TIME SPECIFICATION of the CHANNEL 1.
It never gives the problem on further consequence of CHANNEL 2 or another CHANNEL Backup set 3, 4 5 etc..
Thanks and Regards
Muktha
|
|
|
|