Databases
cancel
Showing results for 
Search instead for 
Did you mean: 

RMAN and SAP Oracle Databases

SOLVED
Go to solution
Ian Dennison_1
Honored Contributor

RMAN and SAP Oracle Databases

This is a weird one. I register normal Oracle Databases in RMAN using "oracle8.exe" and get a unique DBID. I do the same for SAP / Oracle Databases and get the same DBID for each Database on the same server.

here's the rman userid showing the same DBID for 4 database on the same server.

Has anyone seen this before? Know the work-around? Share and Enjoy! Ian

export COLUMNS LINES;
$ rman target system/******@FR3

Recovery Manager: Release 9.2.0.6.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: FR3 (DBID=1177527126)

RMAN> exit


Recovery Manager complete.
$ rman target system/******@FM3

Recovery Manager: Release 9.2.0.6.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: FM3 (DBID=1177527126)

RMAN> exit


Recovery Manager complete.
$ rman target system/******@UK3

Recovery Manager: Release 9.2.0.6.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: UK3 (DBID=1177527126)

RMAN> exit


Recovery Manager complete.
$ rman target system/******@SA3

Recovery Manager: Release 9.2.0.6.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: SA3 (DBID=1177527126)
Building a dumber user
4 REPLIES
Volker Borowski
Honored Contributor
Solution

Re: RMAN and SAP Oracle Databases

Hi Ian,

I think the DBID is unique within the create database statement.
When you do a DBCOPY to a diffrent SID using backup/restore and
CREATE CONTROLFILE
the DBIDs will always be the same.
So if the DBs on this servers all have the same copy source, this seems to be likely.

You need to use RMAN to re-incarnate the DB when doing a DBCOPY (only read about this, but never did this myself). As long as you already have diffrent DBs with the same ID you are stuck.

Since you run Oracle 9 (SAP) there is an Option to rebuild the SYSTEM tablespace with quite new BRTOOLS from SAP. Basicly it does the following:
- deatch tablespaces from database (transportable tablespace feature)
- drop database
- create new database (this should give you a new DBID)
- re-attach tablespaces to DB
This feature is used by SAP to migrate the SYSTEM TS from dictionary managed to LMTS.
There are a couple of OSS notes about this and there are OSS notes about some bugs with this feature as well, so ensure you are on current oracle patches.

Keep a good backup the old fashioned way (i.e. offline file copy) until everything is migrated and dbverified and "validate sturcture cascade"d.

Hope this helps
Volker



TwoProc
Honored Contributor

Re: RMAN and SAP Oracle Databases

I suspect your DBID are all the same because you've cloned the databases from a single database at one point in time or another.

You don't need to rebuild the system area.

Anyway, to regenerate your DBID:

a) backup your controlfile to trace and save it.
b) switch through your logfiles (enough to cycle through ALL of your redos +1 ) - just to be sure.
c) shutdown the database
d) From "startup mount"ed database:
execute sys.dbms_backup_restore.zerodbid(0);
e) shutdown and rebuild your controlfile;
f) login to rman (from target instance), and run "register database"
g) grant connect, resource sysdba to [whatever your backup admin account is]
on your SAP database.

We are the people our parents warned us about --Jimmy Buffett
TwoProc
Honored Contributor

Re: RMAN and SAP Oracle Databases

I noticed I was a little light in step e).

After rebuilding the controlfile, you'll have to open the database with "resetlogs" (which is why I asked you to switch through all logs +1).

e)
create control file set database "URDBASENAME" RESETLOGS ...
e.i) alter database open resetlogs;

Anyways, I just wanted to point out not to forget that step e.i) and why should go ahead an manually cycle through the log files. I know that if you "read the books" on this, you really shouldn't need to. HOWEVER, I've personally had committed data not show up in a cloned database, even though it was properly shutdown before cloning. It was obviously a bug in some version(s), but you can avoid this by manually switching through all of your redo logs just before your cloning procedure. Although you're not cloning here, you're close enough to cause concern, and you will be blowing away the redos.
We are the people our parents warned us about --Jimmy Buffett
Ian Dennison_1
Honored Contributor

Re: RMAN and SAP Oracle Databases

Thank you both for the solutions provided. You picked up on the fact that this database was cloned several times, which it was. I will arrange to re-create the DBID for each Database.

Thanks again! Share and Enjoy! Ian
Building a dumber user