Atikh's DBA blog
  • Home
  • Oracle
  • MySQL
  • MongoDB
  • PostgreSQL
  • Snowflake
  • About Me
  • Contact Us

Introduction to PostgreSQL

 Atikh Shaikh     PostgreSQL     1 comment   

techondba-postgreSQL-introduction

PostgreSQL is powerful open source RDBMS. It has gained strong confidence for reliability, data integrity and correctness.
It is known for most advanced open source database system.
It runs on all major operating system like Linux, UNIX, and Windows.

PostgreSQL includes most number of datatypes like INT, NUM, BOOLEAN, CHAR, VARCHAR, DATE, INTERVAL, TIMESTAMP etc. It also supports binary large objects. One can define his own datatypes.

Total cost of implementation is very less as maintenance efforts are very minimum due to its stability feature.

PostgreSQL features: 
  • User defined types
  • Table inheritance
  • Foreign key referential integrity
  • Views, rules, subqueries
  • Sophisticated locking system
  • Nested transaction.
  • Multi Version concurrently control(MVCC)
  • Tablespaces
  • Point in time recovery
Architectural fundamentals of PostgreSQL

PostgreSQL is first database system that implemented multi-version concurrency control (MVCC)
Recent version comes with support for NoSQL as well.

Useful constraints in PostgreSQL

NOT NULL, UNIQUE, PRIMARY KEY, CHECK, Foreign Key

PostgreSQL is based on client-server architecture

PostgreSQL structure consist of shared memory, few background process and datafiles present in data directory

Shared Memory: shared memory consist of shared buffer and wal buffer, memory used for transaction caching and database caching

PostgreSQL Processes:

techondba-postgreSQL-process structure


Daemon Process: First process starts when we start PostgreSQL. Performs recovery, memory allocation and start background process

Background process: logger, checkpointer, writer, wal writer, archiver, stats collector

Backend Process: backend process performs sorting, query execution and transferring results to user process

Client Process: client process is request coming from user

You may also like to see introduction to mongodb


Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit

Introduction to MongoDB

 Atikh Shaikh     MongoDB     3 comments   

NoSQL

Before starting with the MongoDB introduction, let’s discuss NoSQL
  • NoSQL (Not Only SQL) was started in 2009 and then rapidly started growing.
  • It provides support to the storage and retrieval of data other than tabular relations.
  • Currently there are more than 160 NoSQL databases. MongoDB is the leading NoSQL database

  • NoSQL databases allow storing of data without any predefined schemas
  • Primary goal of NoSQL databases is to provide horizontal scalability i.e. we can add a number of servers to handle large traffic.
  • Relational     database (SQL) database use SQL to define and manipulate data whereas NoSQL uses unstructured query language such as JSON
  • SQL databases: Oracle, MySQL, PostgreSQL etc.
  • NoSQL databases: MongoDB, BigTable, Redis, RavenDb, Cassandra
  • It is easy to store hierarchical data in NoSQL, Let’s discuss more MongoDB

MongoDB

  • MongoDB is an open-source document-oriented NoSQL database that provides high performance, high availability, and automatic scaling
  • This has been written in C++ and its created by 10 gen. The name MongoDB came from the word humongous means huge data.
  • MongoDB works on concepts of collection and document. It stores data as a collection of name-value pairs. And it is a schema-less database
Example 
{“john”:1, “smith”: 2}

techondba-mongodb

MongoDB uses BSON data format which is binary JSON (JavaScript Object Notion) for data storage and data transfer, BSON provides additional DATATypes

JSON is the syntax for storing and exchanging data, an alternative for XML, Language independent, and self-describing. JSON is built based on two structures
  1.  Collection of name-value pair
  2.  An ordered list of values
Example of document
     { rno : 1234
       name : Chris
       aggregate: 75
     }

MongoDBDatatypes

MongoDB supports a number of datatypes likes STRING, NUMBER, BOOLEAN, DATE, NULL, ARRAY, FLOAT,
Mapping of terms with RDBMS DB



techondba-mongodba-mapping of terms-document-collection

Now we will look for more details on Documents and collection

Documents: 


  • Document is a set of name-value pairs which can have dynamic schema
  • MongoDB documents are BSON documents i.e. binary representation of JSON
  • MongoDB instance may have zero or more documents
  • Document is equivalent to RDBMS row 

Collection:


The collection is equivalent to RDBMS tables; one can have zero or more collections
A collection is group of documents
collection is schema-free.

Why MongoDB (Features of MongoDB)

With the use document instead of a relation database row, it’s very simple to represent complex hierarchical relationships with a single record (document).

No predefined schema, documents keys, and values not of fixed sizes.

 Easy scaling - as the amount of data is growing day by day it’s important to scale databases/servers. MongoDB was designed to scale out (sharing data across machines); MongoDB makes it easier to scale up data using multiple servers

 Supports Indexing, aggregation, special collection types, file storage (GRIDFS), replication, sharding (storing data across machines), auto-balancing of data across machines 

 Advantages over RDBMS

  • schema-free
  • no joins required
  • relationship between objects not required
  • easy to scale
  • uses internal memory for operations which enables fast retrieval of data
watch out this space for more articles coming on MongoDB
Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit

Switching between ARCHIVELOG Mode and NOARCHIVELOG mode Oracle Database

 Atikh Shaikh     oracle     No comments   

In this post we are going to discuss about how to convert no ARCHIVELOG mode database to archive lo mode and vice versa.
techondba-oracle-archivelog-noarchivelog
archivelog-noarchivelog

Archive log mode verification using ARCHIVELOG list method, below we can database is in archive log mode with current and oldest log sequence.

SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/arch/techon_db
Oldest online log sequence     8485
Next log sequence to archive   8490

Current log sequence           8490

Below are steps to convert database to NOARCHIVELOG mode


--clean shutdown the database

SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> 

--startup database in mount mode
SQL> startup mount;
ORACLE instance started.

Total System Global Area 1811910416 bytes
Fixed Size                   732944 bytes
Variable Size            1056964608 bytes
Database Buffers          738197504 bytes
Redo Buffers               16015360 bytes

Database mounted.
SQL>

--alter database to NOARCHIVELOG
SQL> alter database noarchivelog;

Database altered.

--open the database
SQL> alter database open;

Database altered.

SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Enabled
Archive destination            /u01/arch/techon_db
Oldest online log sequence     8485
Current log sequence           8490

Now we will convert database to NOARCHIVELOG mode. Follow the same method as above. Use alter database ARCHIVELOG instead of alter database NOARCHIVELOG
We need to set below parameters before converting it to ARCHIVELOG. Make it through either pfile or spfile (using alter system command)


log_archive_dest='/u01/arch/techon_db'
log_archive_format='%t_%s_%r.arc'
log_archive_start=true

SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1811910416 bytes
Fixed Size                   732944 bytes
Variable Size            1056964608 bytes
Database Buffers          738197504 bytes
Redo Buffers               16015360 bytes
Database mounted.

SQL> alter database archivelog;

Database altered.

SQL> alter database open;

Database altered.

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/arch/techon_db
Oldest online log sequence     8485
Next log sequence to archive   8490
Current log sequence           8490

Verify if ARCHIVELOG is working fine by issue switch log.

SQL> alter system switch logfile;

System altered.

SQL> /

System altered.

SQL> /

System altered.

SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/arch/techon_db
Oldest online log sequence     8488
Next log sequence to archive   8493
Current log sequence           8493


Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit

Create MySQL Database Backup | mysqldump mysqlbackup

 Atikh Shaikh     mysql, mysqlbackup, mysqldump     No comments   

Here, we are going to discuss about creating mysql database backup including table backup, backup of all database 


mysqldump-mysqlbackup
mysqldump and mysqlbackup


Physical and Logical backup

Physical backup is taking backup of database directories while database is closed (cold backup) or open (hot backup)
Logical backup is more of extracting SQL statements of INSERT, CREATE, and ALTER etc. statements. 

Below we are going to discuss about logical backup methods mysqldump and mysqlbackup (Enterprise) 

MYSQLDUMP: 


Using mysqldump one take backup of single database, multiple databases, all databases, single table or multiple tables. 

one disadvantage with mysqldump is that it takes lot of time to restore as it have created and insert statements.



Syntax
mysqldump -u <username> -p --all-databases --single-transaction > all_databases.sql

above command will help to take backup of all databases.

Taking backup of single database

mysqldump -u root -p adminDB > adminDB_bckup_dump.sql

Taking backup of mysql table 

mysqldump -u root -p  adminDB UserInfo > table_UserInfo_bckup_dump.sql

Backing up multiple tables 

mysqldump -u root -p  adminDB UserInfo AdminElement> table_UserInfo_bckup_dump.sql

Where adminDB is database and UserInfo and AdminElement are tables

Backup database is compress it using zip or gzip 

mysqldump -u root -p adminDB |gzip > adminDB_bckup_dump.sql.gzip

MYSQLBACKUP:

Below privileges are required to run mysqlbackup command.

GRANT RELOAD ON *.* TO 'test_usr'@'localhost';
GRANT CREATE, INSERT, DROP ON mysql.ibbackup_binlog_marker TO 'test_usr'@'localhost';
GRANT CREATE, INSERT, DROP ON mysql.backup_progress TO 'test_usr'@'localhost';
GRANT CREATE, INSERT, SELECT, DROP ON mysql.backup_history TO 'test_usr'@'localhost';
GRANT REPLICATION CLIENT ON *.* TO 'test_usr'@'localhost';
GRANT SUPER ON *.* TO 'test_usr'@'localhost';
GRANT CREATE TEMPORARY TABLES ON `mysql.*` TO 'test_usr'@'localhost';
FLUSH PRIVILEGES;

In below example we are using root user so not required to grant anything.
Syntax:  
$ mysqlbackup --port=3306 --protocol=tcp --user=<user> --password=<password> --with-timestamp --backup-dir=/u01/backup_t backup-and-apply-log

For example: 
mysqlbackup --port=3306 --protocol=tcp --user=root --password=DexRt#75 --with-timestamp --backup-dir=/u01/backup_t backup-and-apply-log

Where 
--user--> is account having all privileges to perform mysqlbackup operation
--with-timestamp--> this will create sub directory under backup directory mentioned in options
--backup-dir--> is directory where backup needs to take.

--backup-and-apply--> this will bring all tables up to date with changes occurred during backup in short it will take consistent backup.





Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit

Difference Between User, Service account and Schema in Oracle Database

 Atikh Shaikh     oracle     No comments   

Every DBA must have come through terminologies like user account,service account, schema account. We will see these terminology below



user-account-service-account-schema-account-oracle-mysql

User : 

User account is account created in database for individual use. if employees name is John then account with his name will be personal account. Ideally DBA will set some profile to personal user account which forces to reset password after certain period say 90 days or 180 days. ideally it will have only read only access on certain objects or certain schemas, it depends on requirements.
This will only limited some quota defined on USERS tablespaces. 
for example : john01
techondba-user-account-oracle

Service account : 

Service account is account created in database for the purpose of accessing certain schemas by group of people using same account to avoid individual logins. Service account don't own any objects under it, but it can have certain synonyms for security purpose and ease of use.
This will have read only and or read write access on certain schemas according to requirements.
for example : appdata_ro, appdata_rw
techondba-service-account-oracle

Schema account : 

Schema account is account created in database to own objects like tables, index, materialized views, views, procedure, functions etc. Schema account will have its individual tablespace granted.schema account will have its own objects and will be able perform all operations on it.Generally this account will have non expiry password profile.
for example : appdata


consider below scenario

   database :           asgard
   schema :             appdata
   service account :  appdata_ro
   user account :      john01

john01 will have read only access on appdata schema and service account appdata_ro will have read only access on schema appdata in database asgard. service account appdata_ro can be used by number of users with same credentials.

comment below in case of any issues or help.

you may also like to see create database user, Oracle Database schema refresh 

Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit

RMAN Backup of Single Datafile and List Backup

 Atikh Shaikh     oracle, RMAN     2 comments   

This post will discuss about taking backup of single datafile, provided database is in archive log mode.

Check if ARCHIVELOG mode is on

SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/ASGARD/arch
Oldest online log sequence     404
Next log sequence to archive   406
Current log sequence           406

Take backup of datafile system_01.dbf


$ rman target / nocatalog
Recovery Manager: Release 11.2.0.4.0 - Production on Tue Nov 20 02:35:57 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: ASGARD (DBID=2227813556)

using target database control file instead of recovery catalog

RMAN> run
{
allocate channel ch1 type disk format '/u01/rman_backup/rman_datafile_backup_%U';
backup datafile '/u01/ASGARD/data/system_01.dbf';
release channel ch1;
}2> 3> 4> 5> 6>

allocated channel: ch1
channel ch1: SID=133 device type=DISK

Starting backup at 20-NOV-18
channel ch1: starting full datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/ASGARD/data/system_01.dbf
channel ch1: starting piece 1 at 20-NOV-18
channel ch1: finished piece 1 at 20-NOV-18
piece handle=/u01/rman_backup/rman_datafile_backup_vdtilht7_1_1 tag=TAG20181120T024247 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:07
channel ch1: starting full datafile backup set
channel ch1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ch1: starting piece 1 at 20-NOV-18
channel ch1: finished piece 1 at 20-NOV-18
piece handle=/u01/rman_backup/rman_datafile_backup_vetilhte_1_1 tag=TAG20181120T024247 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 20-NOV-18
released channel: ch1

RMAN>

List/Report backup of above datafile


RMAN> list backup of datafile '/u01/ASGARD/data/system_01.dbf';
 List of Backup Sets
===================
  List of Datafiles in backup set 19110
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 14718266653698 20-NOV-18 /u01/ASGARD/data/system_01.dbf
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19112   Full    405.02M    DISK        00:00:05     20-NOV-18
        BP Key: 19112   Status: AVAILABLE  Compressed: NO  Tag: TAG20181120T024247
        Piece Name: /u01/rman_backup/rman_datafile_backup_vdtilht7_1_1
  List of Datafiles in backup set 19112
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 14718266653802 20-NOV-18 /u01/ASGARD/data/system_01.dbf


you may also want to check this rman-disk-backup-and-list-or-report
Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit

RMAN Disk backup and List or Report RMAN Backup

 Atikh Shaikh     oracle, RMAN     No comments   

In this post we are going to discuss RMAN disk backup and how to list the same.
consider database name is :ASGARD

We will see example how to take RMAN full backup of database with archive log mode on.

Check if ARCHIVELOG mode is on

SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/ASGARD/arch
Oldest online log sequence     404
Next log sequence to archive   406
Current log sequence           406

We need to create command file(rcv) and shell script to call command file

First create commandfile (this will take backup of datafiles, controlfile and archivelogs as well)

vi rman_disk_bkp_ASGARD_20Nov2018.rcv

run
{
allocate channel ch1 type disk format '/u01/rman_backup/full_rman_disk1_ASGARD_%U.bck' maxpiecesize 10240M;
allocate channel ch2 type disk format '/u01/rman_backup/full_rman_disk2_ASGARD_%U.bck' maxpiecesize 10240M;
backup incremental level 0 database tag = full_rman_disk;
sql 'alter system archive log current';
release channel ch1;
release channel ch2;
allocate channel ch3 type disk format '/u01/rman_backup/arch_backup_disk3_ASGARD_%U.bck' maxpiecesize 10240M;
backup archivelog from logseq 404;
backup current controlfile format '/u01/rman_backup/ctrl_backup_disk4_ASGARD_%U.bck';
release channel ch3;

}

shell script to call above command file

vi rman_disk_bkp_ASGARD_20Nov2018.sh 

rman target / cmdfile=rman_disk_bkp_ASGARD_20Nov2018.rcv  log=rman_disk_bkp_ASGARD_20Nov2018.log


Check if any syntactical error


$ rman checksyntax@rman_disk_bkp_ASGARD_20Nov2018.rcv

Recovery Manager: Release 11.2.0.4.0 - Production on Tue Nov 20 02:25:58 2018


Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.


RMAN> run

2> {
3> allocate channel ch1 type disk format '/u01/rman_backup/full_rman_disk1_ASGARD_%U.bck' maxpiecesize 10240M;
4> allocate channel ch2 type disk format '/u01/rman_backup/full_rman_disk2_ASGARD_%U.bck' maxpiecesize 10240M;
5> backup incremental level 0 database tag = full_rman_disk;
6> sql 'alter system archive log current';
7> release channel ch1;
8> release channel ch2;
9> allocate channel ch3 type disk format '/u01/rman_backup/arch_backup_disk3_ASGARD_%U.bck' maxpiecesize 10240M;
10> backup archivelog from logseq 12404;
11> backup current controlfile format '/u01/rman_backup/ctrl_backup_disk4_ASGARD_%U.bck';
12> release channel ch3;
13> }
14>
The cmdfile has no syntax errors

Recovery Manager complete.

$

Now we need just need to execute the sh file.


$sh rman_disk_bkp_ASGARD_20Nov2018.sh  &

once this backup is completed, we can check the same in RMAN client 



$ rman target / nocatalog

Recovery Manager: Release 11.2.0.4.0 - Production on Tue Nov 20 02:35:57 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: ASGARD (DBID=2227813556)
using target database control file instead of recovery catalog

RMAN> LIST BACKUPSET TAG 'full_open_backup_disk';


List of Backup Sets
===================


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19089   Incr 0  7.70M      DISK        00:00:02     20-NOV-18
        BP Key: 19089   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup2_ASGARD_992656989_19415_1_untilfit_1_1.bck
  List of Datafiles in backup set 19089
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  5    0  Incr 14718266652218 20-NOV-18 /u02/ASGARD/data/undotbs1_02.dbf
  7    0  Incr 14718266652218 20-NOV-18 /u02/ASGARD/data/tools_01.dbf
  9    0  Incr 14718266652218 20-NOV-18 /u02/ASGARD/data/perfstats_i1_01.dbf
  10   0  Incr 14718266652218 20-NOV-18 /u02/ASGARD/data/sys_audit_d1_01.dbf
  11   0  Incr 14718266652218 20-NOV-18 /u02/ASGARD/data/db_qts01.dbf
  12   0  Incr 14718266652218 20-NOV-18 /u02/ASGARD/data/db_qts02.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19090   Incr 0  46.39M     DISK        00:00:02     20-NOV-18
        BP Key: 19090   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup2_ASGARD_992656993_19416_1_uotilfj1_1_1.bck
  Control File Included: Ckp SCN: 14718266652220   Ckp time: 20-NOV-18

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19091   Incr 0  80.00K     DISK        00:00:00     20-NOV-18
        BP Key: 19091   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup2_ASGARD_992656997_19417_1_uptilfj5_1_1.bck
  SPFILE Included: Modification time: 11-JUL-18
  SPFILE db_unique_name: ASGARD

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19092   Incr 0  7.86G      DISK        00:01:54     20-NOV-18
        BP Key: 19092   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup1_ASGARD_992656989_19414_1_umtilfit_1_1.bck
  List of Datafiles in backup set 19092
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1    0  Incr 14718266652216 20-NOV-18 /u01/ASGARD/data/system_01.dbf
  2    0  Incr 14718266652216 20-NOV-18 /u02/ASGARD/data/sysaux_01.dbf
  3    0  Incr 14718266652216 20-NOV-18 /u03/ASGARD/data/sysaux_02.dbf
  4    0  Incr 14718266652216 20-NOV-18 /u01/ASGARD/data/undotbs1_01.dbf
  6    0  Incr 14718266652216 20-NOV-18 /u01/ASGARD/data/users_01.dbf
  8    0  Incr 14718266652216 20-NOV-18 /u03/ASGARD/data/perfstats_d1_01.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19095   Incr 0  7.70M      DISK        00:00:00     20-NOV-18
        BP Key: 19095   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup2_992657412_19421_1_uttilg04_1_1.bck
  List of Datafiles in backup set 19095
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  5    0  Incr 14718266652461 20-NOV-18 /u02/ASGARD/data/undotbs1_02.dbf
  7    0  Incr 14718266652461 20-NOV-18 /u02/ASGARD/data/tools_01.dbf
  9    0  Incr 14718266652461 20-NOV-18 /u04/ASGARD/data/perfstats_i1_01.dbf
  10   0  Incr 14718266652461 20-NOV-18 /u01/ASGARD/data/sys_audit_d1_01.dbf
  11   0  Incr 14718266652461 20-NOV-18 /u01/ASGARD/data/db_qts01.dbf
  12   0  Incr 14718266652461 20-NOV-18 /u01/ASGARD/data/db_qts02.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19096   Incr 0  46.39M     DISK        00:00:02     20-NOV-18
        BP Key: 19096   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup2_ASGARD_992657413_19422_1_uutilg05_1_1.bck
  Control File Included: Ckp SCN: 14718266652462   Ckp time: 20-NOV-18

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19097   Incr 0  80.00K     DISK        00:00:01     20-NOV-18
        BP Key: 19097   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup2_ASGARD_992657417_19423_1_uvtilg09_1_1.bck
  SPFILE Included: Modification time: 11-JUL-18
  SPFILE db_unique_name: ASGARD

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19098   Incr 0  7.86G      DISK        00:01:14     20-NOV-18
        BP Key: 19098   Status: AVAILABLE  Compressed: NO  Tag: FULL_OPEN_BACKUP_DISK
        Piece Name: /u01/rman_backup/rman_full_open_backup1_ASGARD_992657412_19420_1_ustilg04_1_1.bck
  List of Datafiles in backup set 19098
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1    0  Incr 14718266652459 20-NOV-18 /u01/ASGARD/data/system_01.dbf
  2    0  Incr 14718266652459 20-NOV-18 /u02/ASGARD/data/sysaux_01.dbf
  3    0  Incr 14718266652459 20-NOV-18 /u03/ASGARD/data/sysaux_02.dbf
  4    0  Incr 14718266652459 20-NOV-18 /u01/ASGARD/data/undotbs1_01.dbf
  6    0  Incr 14718266652459 20-NOV-18 /u01/ASGARD/data/users_01.dbf
  8    0  Incr 14718266652459 20-NOV-18 /u03/ASGARD/data/perfstats_d1_01.dbf

RMAN>




Comment below if you need any additional info.
also check rman-backup-single-datafile-and-list




Read More
  • Share This:  
  •  Facebook
  •  Twitter
  •  Instagram
  •  Pin
  •  linkedin
  •  reddit
Newer Posts Older Posts Home

Author

Atikh Shaikh
View my complete profile

Categories

  • MongoDB (18)
  • Oracle 12c (30)
  • Oracle12cR2 New Feature (3)
  • PostgreSQL (20)
  • RMAN (10)
  • Snowflake (8)
  • mysql (23)
  • oracle (74)

Blog Archive

  • ►  2018 (38)
    • ►  November (25)
    • ►  December (13)
  • ►  2019 (33)
    • ►  January (15)
    • ►  February (6)
    • ►  March (2)
    • ►  April (5)
    • ►  May (5)
  • ►  2020 (5)
    • ►  April (1)
    • ►  May (2)
    • ►  July (2)
  • ►  2021 (8)
    • ►  June (3)
    • ►  July (3)
    • ►  August (1)
    • ►  December (1)
  • ►  2022 (33)
    • ►  May (3)
    • ►  June (10)
    • ►  July (3)
    • ►  August (4)
    • ►  September (8)
    • ►  October (3)
    • ►  November (2)
  • ►  2023 (14)
    • ►  February (1)
    • ►  April (5)
    • ►  May (2)
    • ►  June (1)
    • ►  September (1)
    • ►  October (1)
    • ►  December (3)
  • ►  2024 (5)
    • ►  January (2)
    • ►  March (3)
  • ▼  2025 (6)
    • ►  March (1)
    • ►  April (3)
    • ▼  May (2)
      • Oracle 23ai : The all new Hybrid Read-Only for plu...
      • Oracle Active Data Guard Features and Benefits

Popular Posts

  • ORA-29283: invalid file operation: unexpected "LFI" error (1509)[29437]
    I was trying to export the schema in my windows PC, it got stuck with below error    C:\Users\shaik\Videos\technodba exp>expdp userid...
  • PostgreSQL : How to get data directory location for PostgreSQL instance
    Sometimes, you start working on a PostgreSQL instance but forget about the data directory, here we will discuss different methods to know th...
  • Oracle 23ai : Use of NOVALIDATE Constraints in IMPDP
    While performing impdp operations in the Oracle database, Oracle performs validation checks for every constraint on the imported table, that...
  • ERROR 1221 (HY000): Incorrect usage of DB GRANT and GLOBAL PRIVILEGES
    In previous articles, we have learned about user creation and grants  in MySQL in detail, but there are a few privileges called global priv...
  • Oracle Dataguard Broker Configuration (DGMGRL)
    Data Guard Broker is a command-line interface that makes managing primary and standby databases easy. DBA can use a single command to switch...

Labels

oracle Oracle 12c mysql PostgreSQL MongoDB oracle 19c Oracle23c oracle19c Orale PDB-CDB oracle12c python AWS Oracle ASM Virtualbox pluggable database storage engine

Pages

  • Disclaimer
  • Privacy Policy

Follow TechnoDBA

Copyright © Atikh's DBA blog | Powered by Blogger