- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: RMAN and SAP Oracle Databases
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2006 03:29 AM
тАО06-26-2006 03:29 AM
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)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2006 06:59 AM
тАО06-26-2006 06:59 AM
SolutionI 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2006 07:19 AM
тАО06-26-2006 07:19 AM
Re: RMAN and SAP Oracle Databases
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2006 08:49 AM
тАО06-26-2006 08:49 AM
Re: RMAN and SAP Oracle Databases
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2006 08:05 PM
тАО06-26-2006 08:05 PM
Re: RMAN and SAP Oracle Databases
Thanks again! Share and Enjoy! Ian