Archive for the ‘rman’ Category

As per http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmmaint.htm :

The CATALOG command enables you to add records about RMAN and user-managed backups that are currently not recorded in the RMAN repository, or to remove records for backups that are recorded.

Which, though I find the usage of “catalog” a bit unfortunate given the fact that there is also a repository referred to as a “catalog”, the command is quite handy.

Unfortunately, all Oracle references I have found only provide instructions for disk backups. Today though, I came across a post referring to an undocumented method of performing the needed actions with a tape backup.

Essentially, one just needs to configure a tape channel and run the command. For me, this was:

RMAN> configure channel device type ‘SBT_TAPE’
2> parms ‘ENV=(NB_ORA_CLIENT=myserver01),SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64’;

followed by the command:

RMAN> catalog device type ‘SBT_TAPE’ backuppiece ‘mydb_al_reog5k26_1_1_822267974’;

and poof, the backup piece was registered and available to use for a restore.

As this is an undocumented route, i don’t know the deeper implications of it (if any) and thus would not run straight to it as a first step in a prod restore. But, for the test situations I have run so far, it has performed eloquently.

Read Full Post »

While testing a new NetBackup client installation on a server, I received the error:

ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSACreateObject: Failed with error:
Server Status:  Communication with the server has not been initiated or the server status has not been retrieved from the serve

A version of the issue is listed here: http://www.symantec.com/business/support/index?page=content&id=TECH51356

It ends up, with the install, the logs directory was overlooked. (And just creating a ‘logs’ directory isn’t enough, it needs to have the full/proper expected structure.) Once I created that, the backup carried on.

Read Full Post »

After migrating a database to a new server via a restore (which included an ‘open resetlogs’), I attempted to verify the configuration parameters with a ‘show all’. This resulted in the following error:

RMAN-03002: failure of show command at 02/26/2012 15:23:08
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog

The fix:

RMAN> reset database;

new incarnation of database registered in recovery catalog
starting full resync of recovery catalog
full resync complete


More info:


Read Full Post »

Just ran a test on 11g active duplication. How horribly easy it is..if you take into account the fact that you need not perform a backup first, it is about 10x easier than a standard duplication.

In order to duplicate (using testdb and prod as example db names):

-create auxiliary db’s password file

$> cd $ORACLE_HOME/dbs

$> orapwd file=orapwtestdb

-create oracle net connection

add info to listener.ora

reload listener

-create (s)pfile and appropriate directories for auxiliary

include db_file_name_convert and log_file_name_convert

-start auxiliary db

SQL> connect sys@testdb as sysdba

SQL> startup nomount;

connect with rman:

auxiliary database Password: password
connected to auxiliary database: TESTDB (not mounted)
target database Password: password
connected to target database: PROD (DBID=123456789)

run the duplicate command:

RMAN> duplicate target database
to testdb
from active database;

So very, very easy.

Of course there are other options and one can include the db_File_name_convert in the RMAN command, or use a catalog, or… But I reckon this plain and simple version is what I’ll be using most of the time.

More info: http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmdupdb.htm#i1008564

Read Full Post »