Skip to main content

Sample RMAN backup script



	
#!/bin/bash
#Declare your environment variables
#export ORACLE_SID=
#export ORACLE_HOME=
#export PATH=$PATH:${ORACLE_HOME}/bin
#export LD_LIBRARY_PATH=${ORACLE_HOME}/bin/lib

dd=`date '+%d-%h-%Y'`
mkdir -p /backup_location/$dd
touch /backup_location/$dd/rmanbkup_$dd.log
echo rman backup for PROD started `date` > /backup_location/$dd/rmanbkup_$dd.log

/oracle/db_software/bin/rman target=/ << EOF >> /backup_location/$dd/rmanbkup_$dd.log
CONFIGURE CONTROLFILE AUTOBACKUP ON;
allocate channel for maintenance type disk;
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup_location/$dd/autobackup_control_file%F';
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH02 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH03 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH04 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH05 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH06 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH07 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH08 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH09 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH10 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH11 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH12 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH13 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH14 TYPE DISK;
ALLOCATE CHANNEL RMAN_BACK_CH15 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/backup_location/$dd/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/backup_location/$dd/archivelogs_%d_%u_%s_%T';
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/backup_location/$dd/controlfile_%d_%u_%s_%T';
RELEASE CHANNEL RMAN_BACK_CH01;
RELEASE CHANNEL RMAN_BACK_CH02;
RELEASE CHANNEL RMAN_BACK_CH03;
RELEASE CHANNEL RMAN_BACK_CH04;
RELEASE CHANNEL RMAN_BACK_CH05;
RELEASE CHANNEL RMAN_BACK_CH06;
RELEASE CHANNEL RMAN_BACK_CH07;
RELEASE CHANNEL RMAN_BACK_CH08;
RELEASE CHANNEL RMAN_BACK_CH9;
RELEASE CHANNEL RMAN_BACK_CH10;
RELEASE CHANNEL RMAN_BACK_CH11;
RELEASE CHANNEL RMAN_BACK_CH12;
RELEASE CHANNEL RMAN_BACK_CH13;
RELEASE CHANNEL RMAN_BACK_CH14;
RELEASE CHANNEL RMAN_BACK_CH15;
}
EXIT;
EOF

    




Comments

Popular posts from this blog

Data Safe - Introduction

Oracle Data Safe - Practical Guide Oracle Data Safe learner guide Oracle Data Safe Assess risk, discover sensitive data, audit activity, and mask safely It focuses on what Data Safe helps you do operationally: review security posture, find risky identities, centralize auditing, locate sensitive data, and produce safer non-production copies. Contents 01 Why Data Safe matters 02 Where it fits 03 Capability map 04 Assessments 05 Activity Auditing 06 Discovery and Masking 07 Operating model 08 First 30 days 09 Knowledge check Section 01 Why Data Safe matters Database security work is often fragmented. One process checks configuration drift, another stores audit logs, another team scans for PII, and another team writes masking logic for test refreshes. Data Safe is useful because it turns those separate jobs into one security workflow. Key idea The best way to think about Data Safe is as a control plane for database security posture: assess the target, identify risky accounts, d...

Testing Different Access Paths : Concatenated Index

Oracle Concatenated Indexes - Practical Deep Dive Oracle concatenated index deep dive Concatenated Indexes How composite indexes really work, why column order matters, and when skip scan changes the story Concatenated indexes, also called composite indexes, are easy to explain badly and surprisingly rich to explain well. The usual summary is “Oracle can use the index only when the leading column is present,” but that is only the starting point. To design them properly, you need to think about leading portions, equality versus range predicates, ordering requirements, skip scan eligibility, covering behavior, and whether one composite index can replace several single-column indexes in a given workload. Contents 01 What concatenated indexes are 02 Leading edge and leading portion 03 Why column order matters 04 Skip scan and when it helps 05 Access patterns and plan reading 06 Covering and sort elimination 07 Design rules that actually hold 08 Common mistakes 09 End-to-end demo 1...

Database Replay - Real Application Testing (RAT)

Oracle Database Replay and RAT - Practical Deep Dive Oracle Database Replay deep dive Database Replay and Real Application Testing How to validate upgrades, patches, migrations, and risky changes with real workload behavior Database Replay is one of the most practical risk-reduction tools in the Oracle DBA toolbox. Instead of trusting synthetic benchmarks, isolated SQL tests, or intuition, you capture a real production workload, restore a test system to the same logical starting point, replay that workload, and analyze whether performance, errors, timing, and transactional behavior still look safe. Contents 01 What RAT actually is 02 Why Database Replay matters 03 End-to-end workflow 04 Capture design and prerequisites 05 Preprocess, calibrate, replay 06 Reading the results well 07 Pitfalls and unreplayable work 08 Database Replay vs SPA 09 Practical playbooks 10 Knowledge check Section 01 What Real Application Testing actually is Real Application Testing, usually shortened...