Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Installation/Configurations10g

October 1, 2017 RMAN backup and logical backup With Different User
Installation/Configurations10gInstallation/Configurations11gInstallation/Configurations12cOracle Database Material

RMAN backup and logical backup With Different User

Step 1: Create the user

CREATE USER bkp_user IDENTIFIED BY bkp_user DEFAULT TABLESPACE users TEMPORARY 
TABLESPACE temp PROFILE DEFAULT; 
GRANT CONNECT TO bkp_user; 
GRANT exp_full_database TO bkp_user; 
GRANT imp_full_database TO bkp_user; 
GRANT recovery_catalog_owner TO bkp_user; 
GRANT select_catalog_role TO bkp_user; 
GRANT CREATE SESSION TO bkp_user; 

Step 2: Connect RMAN with the Above Created User

$ rman

RMAN> connect target bkp_user/bkp_user

RMAN> backup database;

Note: Script can be written and job can be scheduled to take backup.

 

September 1, 2017 Oracle RMAN Commands List
Installation/Configurations10gInstallation/Configurations11gInstallation/Configurations12cOracle Database Material

Oracle RMAN Commands List

Here is the list of key most RMAN commands that are used for Backup and related activities:

 

LIST Commands

LIST Commands are generic RMAN commands that will show/list various types of information when executed within RMAN utility.

RMAN> list backup;

It lists all the backups taken using RMAN utility.

RMAN> list backup of database;

The above command lists out all the (individual) files that are in the backup.

RMAN> list backup of tablespace system;

The above command lists out all the files that are in the backup that belong to the tablespace ‘system’.

RMAN> list backup of control file;

The above command lists out all backups of the control file.

 

CONFIGURE Commands

CONFIGURE commands in RMAN are used to configure/setup various initial settings:

RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY2;

The above commands indicates how many days the backup copies need to be retained. Default is 1 day.

RMAN> CONFIGURE RETENTION POLICY CLEAR;

The above command resets the Retention policy to the default value of 1 day.

CONFIGURE BACKUP OPTIMIZATION ON;

The above command verifies to make sure that identical files are NOT backed up to the device specified.

CONFIGURE BACKUP OPTIMIZATION CLEAR;

The above command resets the Optimization option to the default value.

 

SHOW Commands

Show commands are used to show/display the configuration setting values.

RMAN> show all;

The above command shows all the current configuration settings on the screen.

RMAN> show retention policy;

The above command shows the current retention policy.

RMAN> show default device type;

The above command shows the default device type configured for backups.

RMAN> show datafile backup copies;

The above command shows the number of backup copies available in the target database.

 

BACKUP Commands

Backup commands are the real commands which do the actual backup work.

RMAN> backup database;

The above command backs up the database (target).

RMAN> backup database include current controlfile plus archive log;

The above command backs up the target database and the current control file and archive log files.

 

REPORT Commands

Report commands list/report specific information. The difference between report and list command is report command output is in a better format.

RMAN> report obsolete;

The above command reports which backups can be deleted.

 

DELETE Commands

Delete commands delete/remove specific items from the server, repository catalog.

RMAN> delete obsolete;

The above command deletes all the backups that are older based on the retention policy setup.

 

 

September 1, 2017 RAC Voting Disk
Installation/Configurations10gInstallation/Configurations11gInstallation/Configurations12cOracle Database Material

Rac Voting Disk

The Voting Disk File is a file on the shared cluster system or a shared raw device file.

Voting disk a key component of clusterware and its failure can lead to inoperability of the cluster.

In RAC at any point in time the clusterware must know which nodes are member of the rso that

  • it can perform load balancing
  • In case a node fails, it can perform failover of resources as defined in the resource profiles
  • If a node joins, it can start resources on it as defined in OCR/OLR
  • If a node joins, it can assign VIP to it in case GNS is in use
  • If a node fails, it can execute callouts if defined

Adding

crsctl add css votedisk <file>

deleting

crsctl delete css votedisk <file>

querying

crsctl query css votedisk

 

 

September 1, 2017 RAC Management Commands
Installation/Configurations10g

Basic RAC Management Commands

 

Cluster Related Commands

crs_stat -t Shows HA resource status (hard to read)
crsstat Ouptut of crs_stat -t formatted nicely
ps -ef|grep d.bin crsd.bin evmd.bin ocssd.bin
crsctl check crs CSS,CRS,EVM appears healthy
crsctl stop crs Stop crs and all other services
crsctl disable crs* Prevents CRS from starting on reboot
crsctl enable crs* Enables CRS start on reboot
crs_stop -all Stops all registered resources
crs_start -all Starts all registered resources

* These commands update the file /etc/oracle/scls_scr/<node>/root/crsstart which contains the string “enable” or “disable” as appropriate.

Database Related Commands

srvctl start instance -d <db_name> -i <inst_name> Starts an instance
srvctl start database -d <db_name> Starts all instances
srvctl stop database -d <db_name> Stops all instances, closes database
srvctl stop instance -d <db_name> -i <inst_name> Stops an instance
srvctl start service -d <db_name> -s <service_name> Starts a service
srvctl stop service -d <db_name> -s <service_name> Stops a service
srvctl status service -d <db_name> Checks status of a service
srvctl status instance -d <db_name> -i <inst_name> Checks an individual instance
srvctl status database -d <db_name> Checks status of all instances
srvctl start nodeapps -n <node_name> Starts gsd, vip, listener, and ons
srvctl stop nodeapps -n <node_name> Stops gsd, vip and listener