Skip to content

Category: RMAN Basics

Physical and Logical Block Corruption in Oracle Database

Block corruptions are one of the common source of database outages. A database block is corrupted when its content has changed from what Oracle Database expects. Correcting block corruptions can prove to be a lengthy and costly exercise and requires good expertise 0n the DBA part.

Block Corruption can happen at Logical level or Physical level. Also, such corruption can impact a single block or huge number of blocks in the database.

[Post Views: 6]

Leave a Comment

Oracle ASM – ORA-19504: failed to create file – SVR4 Error: 13: Permission denied

During one of our 11gR2 database restore activity we found below error message in the RMAN “duplicate database command”

channel aux4: ORA-19870: error while restoring backup piece /oraclone/ORCL/rman_clone/ORCL_F_20170605_c1s60alv_1_1
ORA-19504: failed to create file "+DATA3"
ORA-15045: ASM file name '+DATA3' is not in reference form
ORA-17502: ksfdcre:5 Failed to create file +DATA3
ORA-15081: failed to submit an I/O operation to a disk
ORA-27091: unable to queue I/O
ORA-27041: unable to open file
SVR4 Error: 13: Permission denied

[Post Views: 255]

Leave a Comment

RMAN : CONFIGURE YOUR RMAN ENVIRONMENT

To work with RMAN, you must configure several things, which can be default backup type (disk or tape), the number of channels you want to use, and the degree of parallelism.

When you are testing it on your personal system, you probably can get by with RMAN’s default configuration settings. However, for production jobs involving sophisticated backup strategies, you need to customize RMAN’s configuration settings to fulfill all your requirement. You can configure different backup retention policies, for example, for different databases.

[Post Views: 3932]

Leave a Comment
error: Alert: Content is protected !!