Archive

Archive for the ‘RMAN’ Category

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

June 20, 2012 Leave a comment

Today, I clone a 11gR2.0.3 database at the same database server. Once I start rman, I get the ORA errors message below

[oracle@ycsdb01 dbs]$ rman target / nocatalog auxiliary sys/12345@spbpro

Recovery Manager: Release 11.2.0.3.0 – Production on Wed Jun 20 17:13:06 2012

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

connected to target database: CSPRO (DBID=3560463483)
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
[oracle@ycsdb01 dbs]$ cd $ORACLE_HOME/network/admin

Solution

Then, I add the option “(UR=A)”  in tnsnames.ora as below. The problem is fixed.

SPBPRO =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = scan.springboard.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = spbpro)(UR=A)
)
)

 

 

Categories: ORA-XXX, RMAN, TNS

RMAN-04014: startup failed: ORA-09925: Unable to create audit trail file

May 2, 2012 1 comment

After restoring spfile and controlfile from the backup, I start the database instance in nomount, the below message shows

RMAN> startup nomount;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 05/02/2012 11:41:14
RMAN-04014: startup failed: ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9925

Since I restore the database backup into another 11gR2 cluster server, I forget create audit files for it. After creating the files and directories as below, it works

[oracle@wcsvmuatdb01 cspro]$  mkdir adump dpdump hdump pfile
[oracle@wcsvmuatdb01 cspro]$ rman target /

Recovery Manager: Release 11.2.0.3.0 – Production on Wed May 2 11:52:53 2012

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

connected to target database: CSPRO (not mounted)

Categories: RMAN

RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter REMOTE_LISTENER

May 2, 2012 Leave a comment

I restore a  11gR2 database into a testing 11gR2 cluster database, after restoring the spfile from backup and starting it up by RMAN, I get the messages below

RMAN> startup nomount;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 05/02/2012 11:23:56
RMAN-04014: startup failed: ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax error or unresolved network name ‘scan.csportal.com:1521’

Since the testing server can look DNS up, I have added the scan.csportal.com into /etc/hosts. The problem is workaround.

#SCAN Entry
10.193.42.100   scan.springbroad.com   scan <– this testing db scan IP
10.193.42.100   scan.csportal.com <– the restoring database

 

Regards /Jeff Wong

 

Categories: RMAN

ORA-16072: a minimum of one standby database destination is required

February 29, 2012 Leave a comment

Today, I try to restore a production database to a testing server. When I opened the database, it showed the ERRORS below

“ORA-16072: a minimum of one standby database destination is required”.

Since there is no standby in testing environment, I try to workaround as the following

SQL> startup mount;
ORACLE instance started.

Database mounted.
SQL> alter database set standby database to maximize performance;

Database altered.

SQL> alter database open ; <– I successfully open the database

Database altered.

Categories: ORA-XXX, RMAN, Standby database

ORA-01180: can not create datafile 1

May 11, 2011 Leave a comment

Symptoms

I moved the backup sets  from a production 10g database into a development server for restoration. I could restore spfile and control files. Once  I started the database in mount mode and restore database. It returned the following errors.

creating datafile fno=1 name=/u01/oradata/videv/system01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/10/2011 22:32:23
ORA-01180: can not create datafile 1
ORA-01110: data file 1: ‘/u01/oradata/videv/system01.dbf’

Fix

Then I cataloged the backup sets, it worked as the following

RMAN> catalog start with ‘/u01/oracle/instance/bkup_VIDEV_3509_1_750301226.dat’;

using target database control file instead of recovery catalog
searching for all files that match the pattern /u01/oracle/instance/bkup_VIDEV_3509_1_750301226.dat

List of Files Unknown to the Database
=====================================
File Name: /u01/oracle/instance/bkup_VIDEV_3509_1_750301226.dat

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files…
cataloging done

List of Cataloged Files
=======================
File Name: /u01/oracle/instance/bkup_VIDEV_3509_1_750301226.dat

RMAN> restore database;

Starting restore at 10-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=2193 devtype=DISK

channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/oradata/videv/system01.dbf
restoring datafile 00002 to /u01/oradata/videv/undotbs01.dbf
restoring datafile 00003 to /u01/oradata/videv/sysaux01.dbf
restoring datafile 00004 to /u01/oradata/videv/users01.dbf
restoring datafile 00005 to /u01/oradata/videv/vi_tbs_dat01_01.dbf
restoring datafile 00006 to /u01/oradata/videv/vi_tbs_dat02_01.dbf
restoring datafile 00007 to /u01/oradata/videv/vi_tbs_dat03_01.dbf
restoring datafile 00008 to /u01/oradata/videv/vi_tbs_idx01_01.dbf
restoring datafile 00009 to /u01/oradata/videv/vi_tbs_idx02_01.dbf
restoring datafile 00010 to /u01/oradata/videv/vi_tbs_idx03_01.dbf
channel ORA_DISK_1: reading from backup piece /u01/oracle/instance/bkup_VIDEV_3509_1_750301226.dat

channel ORA_DISK_1: restored backup piece 1
piece handle=/u01/oracle/instance/bkup_VIDEV_3509_1_750301226.dat tag=TAG20110505T010026
channel ORA_DISK_1: restore complete, elapsed time: 00:09:09
Finished restore at 10-MAY-11

Categories: RMAN

RMAN-06207: WARNING: 20 objects could not be deleted for DISK channel(s)

April 8, 2011 Leave a comment

Symptoms

RMAN-06207: WARNING: 20 objects could not be deleted for DISK channel(s) due RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status RMAN-06210: List of Mismatched objects RMAN-06211: ========================== RMAN-06212: Object Type Filename/Handle RMAN-06213: ————— ————————————————— RMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4710_1_746949640.dat RMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4711_1_746949640.dat RMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4712_1_746951040.dat RMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4713_1_746951067.dat RMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4714_1_746952417.datRMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4715_1_746952475.dat RMAN-06214: Backup Piece /rcdb/oracle/bkup/viqa/bkup_VI_4716_1_746953824.dat

Cause

This was caused by removing the backupset in OS before, so RMAN reported mismatched status due to the backupsets were missing.

Fix Procedures

Do crosscheck the missing backupsets to update RMAN catalog. The following is example

RMAN>  CROSSCHECK  backupset;

using channel ORA_DISK_1
using channel ORA_DISK_2
crosschecked backup piece: found to be ‘AVAILABLE’
backup piece handle=/rcdb/oracle/bkup/viqa/bkup_VI_4863_1_747834472.dat recid=4850 stamp=747834474
crosschecked backup piece: found to be ‘AVAILABLE’
backup piece handle=/rcdb/oracle/bkup/viqa/bkup_VI_4862_1_747834472.dat recid=4851 stamp=747834474
crosschecked backup piece: found to be ‘AVAILABLE’
backup piece handle=/rcdb/oracle/bkup/viqa/bkup_VI_4864_1_747836002.dat recid=4852 stamp=747836004
crosschecked backup piece: found to be ‘AVAILABLE’

RMAN> delete obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
using channel ORA_DISK_2
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
——————– —— —————— ——————–
Backup Set           4706   28-MAR-11
Backup Piece       4706   28-MAR-11          /rcdb/oracle/bkup/viqa/bkup_VI_4710_1_746949640.dat
Backup Set           4707   28-MAR-11
Backup Piece       4707   28-MAR-11          /rcdb/oracle/bkup/viqa/bkup_VI_4711_1_746949640.dat
Backup Set           4708   28-MAR-11
Backup Piece       4708   28-MAR-11          /rcdb/oracle/bkup/viqa/bkup_VI_4712_1_746951040.dat
Backup Set           4709   28-MAR-11

Categories: RMAN, Uncategorized Tags: