List a complete directory tree

List a complete directory tree

You can use the tree command. If tree command does not exist in your system use the following

find . -type d -print | sed -e 's;[^/]*/;|____;g;s;____|; |;g'

Reference: http://www.unix.com/shell-programming-scripting/20702-tree-unix.html

Enable client tracing in SQLNET

add in the %ORACLE_HOME%\network\admin\sqlnet.ora

TRACE_UNIQUE_CLIENT = ON
TRACE_LEVEL_CLIENT = 16
TRACE_DIRECTORY_CLIENT = C:\temp
TRACE_FILE_CLIENT = SQLNetTrace
TRACE_TIMESTAMP_CLIENT = ON

Configure RMAN to use all RAC nodes (Parallel backups)

Consider a two-node rac with 1 cpu per node.

CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;

CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'sys/oracle@rt1';

CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'sys/oracle@rt2';

RMAN> show all;

RMAN configuration parameters are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';

CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/product/10.2.0/db_1/dbs/snapcf_RT2.f'; # default

RMAN> backup database plus archivelog;

Starting backup at 04-JUL-11

current log archived

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid=143 instance=RT1 devtype=DISK

allocated channel: ORA_DISK_2

channel ORA_DISK_2: sid=132 instance=RT2 devtype=DISK

channel ORA_DISK_1: starting compressed archive log backupset

channel ORA_DISK_1: specifying archive log(s) in backup set

input archive log thread=1 sequence=10 recid=6 stamp=755647649

input archive log thread=1 sequence=11 recid=10 stamp=755648045

input archive log thread=1 sequence=12 recid=14 stamp=755648207

input archive log thread=1 sequence=13 recid=16 stamp=755648344

input archive log thread=1 sequence=14 recid=22 stamp=755648490

input archive log thread=1 sequence=15 recid=26 stamp=755648538

input archive log thread=1 sequence=16 recid=30 stamp=755648596

input archive log thread=2 sequence=12 recid=2 stamp=755647601

channel ORA_DISK_1: starting piece 1 at 04-JUL-11

channel ORA_DISK_2: starting compressed archive log backupset

channel ORA_DISK_2: specifying archive log(s) in backup set

input archive log thread=2 sequence=13 recid=4 stamp=755647644

input archive log thread=2 sequence=14 recid=8 stamp=755648043

input archive log thread=2 sequence=15 recid=12 stamp=755648206

input archive log thread=2 sequence=16 recid=18 stamp=755648344

input archive log thread=2 sequence=17 recid=20 stamp=755648488

input archive log thread=2 sequence=18 recid=24 stamp=755648536

input archive log thread=2 sequence=19 recid=28 stamp=755648594

channel ORA_DISK_2: starting piece 1 at 04-JUL-11

channel ORA_DISK_1: finished piece 1 at 04-JUL-11

piece handle=+DISKGROUP01/rt/backupset/2011_07_04/annnf0_tag20110704t222317_0.314.755648601 tag=TAG20110704T222317 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07

channel ORA_DISK_2: finished piece 1 at 04-JUL-11

piece handle=+DISKGROUP01/rt/backupset/2011_07_04/annnf0_tag20110704t222317_0.315.755648603 tag=TAG20110704T222317 comment=NONE

channel ORA_DISK_2: backup set complete, elapsed time: 00:00:07

Finished backup at 04-JUL-11

Starting backup at 04-JUL-11

using channel ORA_DISK_2

using channel ORA_DISK_1

....

Reference : http://oraclehandson.wordpress.com/2008/01/10/parallel-backup-using-rman-in-rac-environment/

....

Migrating Existing Backups to ASM Flash Recovery Area

Migrating Existing Backups to ASM Flash Recovery Area

This article coming from http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmasm.htm

In this example, it is assumed that you have already set the initialization parameters for a flash recovery area in ASM storage, using the process in "Setting Initialization Parameters for Flash Recovery Area in ASM".

Note:

After you configure the database to change the location of the flash recovery area, backups created in the old flash recovery area location remain in their old location, still count against the total disk quota of the flash recovery area, are deleted from the old flash recovery area as space is required for other files, and can still be managed by RMAN and used in RMAN recovery operations. There is no need to move existing backups to the new ASM flash recovery area, unless you need the disk space used by those files for other purposes.

If you do need to free the space taken up by leftover non-ASM flash recovery area files, your options include backing them up to tape (for example, by using BACKUP RECOVERY AREA DELETE INPUT) or moving the backups from the old flash recovery area location to the new one, as described in this section.

To back up the existing archived redo log files to the new flash recovery area, use this command:

RMAN> BACKUP AS COPY ARCHIVELOG ALL DELETE INPUT;

To move backup sets to the new flash recovery area, use this command:

RMAN> BACKUP DEVICE TYPE DISK BACKUPSET ALL DELETE INPUT;

To move all datafile copies to the new flash recovery area location, use this command:

RMAN> BACKUP AS COPY DATAFILECOPY ALL DELETE INPUT;