Shulou(Shulou.com)05/31 Report--

Editor to share with you how to solve ORA-00245 and RMAN-08132 problems, I believe that most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

Starting with Oracle11gR2, you no longer need to lock controlfile enqueue when backing up control files. For non-RAC databases, there is no change, but for RAC databases, any instance in the cluster can need to be written to the snapshot control file because of the change in the control file backup mechanism, so the snapshot controlfile needs to be visible to all instances.

In the RAC environment, if the snapshot controlfile is not in the shared location, any form of control file may report an error in ORA-245.

The snapshot control file must be accessible to all nodes, and if the snapshot control is not stored on a shared device, an error will be reported when RMAN makes a snapshot backup of the control file.

Changes

RAC Database release 11.2

Cause

The error description is:

00245, 00000, "control file backup failed; target is likely on a local file system"

/ / * Cause: Failed to create a control file backup because some process

/ / signaled an error during backup creation. This is likely caused

/ / by the backup target being on a local file system so it could not

/ / be accessed by other instances. It can also be caused by other

/ / I/O errors to the backup target. Any process of any instance that

/ / starts a read/write control file transaction must have access

/ / to the backup control file during backup creation.

/ / * Action: Check alert files of all instances for further information.

RMAN creates a copy of the controlfile for read consistency, this is the snapshot controlfile.

Due to the changes made to the controlfile backup mechanism in 11gR2 any instances

In the cluster may write to the snapshot controlfile. Therefore

The snapshot controlfile file needs to be visible to all instances.

The same happens when a backup of the controlfile is

Created directly from sqlplus any instance in the cluster may write to the backup controfile file.

In 11gR2 onwards, the controlfile backup happens without holding the controlfile enqueue.

For non-RAC database, this doesn't change anything.

But, for RAC database, the snapshot controlfile location must be

In a shared file system that will be accessible from all the nodes.

The snapshot controlfile MUST be accessible by all nodes of a RAC database.

Solution

The snapshot controlfile MUST be accessible by all nodes of a RAC database

If the snapshot controlfile does not reside in on a shared device this error will raise.

1. Check the snapshot controlfile location:

RMAN > show all

2. Configure the snapshot controlfile to a shared disk:

Solution:

Configure snapshot controlfile to a shared location

CONFIGURE SNAPSHOT CONTROLFILENAME TO'/ snapcf_.f'

If ASM is used, specify to the corresponding ASM disk group:

CONFIGURE SNAPSHOT CONTROLFILENAME TO'+ / snapcf_.f'

Example:

RMAN > show all

2 >

Using target database control file instead of recovery catalog

RMAN configuration parameters for database with db_unique_name RACDB are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 14

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'% favored; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

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

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

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE' DEFAULT' OPTIMIZE FOR LOAD TRUE; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'/ u01qoracleq11g default; # oracleUniverse; # oracle

RMAN > CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA1/snapcf_RACBD.F'

Old RMAN configuration parameters:

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA1/snapcf.f'

New RMAN configuration parameters:

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA1/snapcf_RACBD.F'

New RMAN configuration parameters are successfully stored

RMAN > show all

RMAN configuration parameters for database with db_unique_name RACDB are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 14

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'% favored; # default

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default

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

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

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE' DEFAULT' OPTIMIZE FOR LOAD TRUE; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO'+ DATA1/snapcf_RACBD.F'

The above is all the contents of the article "how to solve the ORA-00245 and RMAN-08132 problems". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.