Migrate database from one RMAN catalog to another RMAN catalog
Tuesday, June 14, 2016
Moving from one RMAN catalog to another RMAN catalog
Excerpt from Chennai:
In a nut shell It is nothing but importing a CATALOG from one database to another, or in other words, "moving" or "migrating" CATALOG.
We can see GGDB1 is also registered to this CATALOG.
Wednesday, July 30, 2014
Migrate database from one RMAN catalog to another RMAN catalog
IMPORT CATALOG
is a new feature of RMAN in Oracle 11g. We can move or merge schemas of
different RECOVERY CATALOG of different databases into a centralized
repository.
In a nut shell It is nothing but importing a CATALOG from one database to another, or in other words, "moving" or "migrating" CATALOG.
SOURCE DATABASE - GGDB1
TARGET DATABASE - GGDB2
ORACLE VERSION - 11.2.0.3.0
OS VERSION - Linux 6.0 X86_64
The below scenario describes the steps to move a CATALOG from GGDB1 (Source) to GGDB2 (Target).
In GGDB1 - The catalog is registered.
In GGDB2 - Check the CATALOG for the registered database.
In GGDB2 - Connect to the destination database that will receive the new CATALOG data.
Issue the IMPORT CATALOG command specifying the owner of the source catalog and Check the registered database in the catalog in GGDB2 (Target database).
We can see GGDB1 is also registered to this CATALOG.
In GGDB1 - Check the source catalog (GGDB1) for the registered database.,
On the Source Catalog, the database will be automatically Unregistered after the IMPORT CATALOG.
If you need to retain the catalog on the source side even after the import then a keyword should be added to the IMPORT CATALOG command.
Connect to the RMAN prompt and issue the IMPORT CATALOG command with the keyword NO UNREGISTER.,
Check whether the source database (GGDB1) is registered to the New target catalog database (GGDB2).
Now check on the Source (GGDB1) side whether the imported database exists.
You can clearly see that the database is not Unregistered from the Source side.
Thursday, May 12, 2016
Change unknown SYSMAN password on #EM12c
Change unknown SYSMAN password on #EM12c
When I normally start work on a new EM 12c environment, I would request to have a userid created; however, I don’t have a userid in this environment and I need access EM 12c as SYSMAN. Without knowing the password for SYSMAN, how can I access the EM 12c interface? The short answer is that I can change the SYSMAN password from the OS where EM 12c is running.Note:
Before changing the SYSMAN password for EM 12c, make sure to understand the following:
- SYSMAN is used by the OMS to login to the OMR to store and query all activity
- SYSMAN password has to be changed at both the OMS and OMR to EM 12c to work correctly
- Do not modify the SYSMAN or any other repository user at the OMR level (not recommended)
Tip: Make sure you know what the SYS password is for the OMR. It will be needed to reset SYSMAN.
1. Stop all OMS processes
cd <oms home>/bin
emctl stop oms
Image 1:
2. Change the SYSMAN password
cd <oms home>/bin
emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd <sys password> -new_pwd <new sysman password>
In Image 2, notice that I didn’t pass the password for SYS or SYSMAN on the command line. EMCTL will ask you to provide the password if you don’t put it on the command line.
Image 2:
3. Stop the Admin Server on the primary OMS and restart OMS
cd <oms home>/bin
emctl stop oms -all
emctl start oms
Image 3:
4. Verify that all of OMS is up and running
cd <oms home>/bin
emctl status oms -details
Image 4:
After verifying that the OMS is backup, I can now try to login to the OMS interface.
Image 5:
As we can see, I’m able to access OEM as SYSMAN now with the new SYSMAN password.
Enjoy!!
Re-creating Oracle Enterprise Manager's Console Repository
| Mandalika's scratchpad | [ Work blog @Oracle | Stock Market Notes | My Music Compositions ] |
Old Posts:
09.04
10.04
11.04
12.04
01.05
02.05
03.05
04.05
05.05
06.05
07.05
08.05
09.05
10.05
11.05
12.05
01.06
02.06
03.06
04.06
05.06
06.06
07.06
08.06
09.06
10.06
11.06
12.06
01.07
02.07
03.07
04.07
05.07
06.07
08.07
09.07
10.07
11.07
12.07
01.08
02.08
03.08
04.08
05.08
06.08
07.08
08.08
09.08
10.08
11.08
12.08
01.09
02.09
03.09
04.09
05.09
06.09
07.09
08.09
09.09
10.09
11.09
12.09
01.10
02.10
03.10
04.10
05.10
06.10
07.10
08.10
09.10
10.10
11.10
12.10
01.11
02.11
03.11
04.11
05.11
07.11
08.11
09.11
10.11
11.11
12.11
01.12
02.12
03.12
04.12
05.12
06.12
07.12
08.12
09.12
10.12
11.12
12.12
01.13
02.13
03.13
04.13
05.13
06.13
07.13
08.13
09.13
10.13
11.13
12.13
01.14
02.14
03.14
04.14
05.14
06.14
07.14
09.14
10.14
11.14
12.14
01.15
02.15
03.15
04.15
06.15
09.15
12.15
01.16
03.16
04.16
05.16
Thursday, August 28, 2008
Re-creating Oracle Enterprise Manager's Console Repository
An earlier blog post, Oracle 10g: Setting up The Oracle Enterprise Manager Console, has the detailed instructions for setting up the Oracle 10g
OEM console. However if the database along with the RDBMS server was
moved (copied over) to a different host, Oracle Enterprise Manager (OEM)
refuses to start. In such cases, the error message will be similar to
the following.
One simple solution (there might be many) to fix this issue is to re-create the repository for the OEM console. The steps are as follows.
You are done. As simple as that.
_______________
% emctl start dbconsole
OC4J Configuration issue. /export/pspp/oracle/oc4j/j2ee/OC4J_DBConsole_localhost_test not found.
One simple solution (there might be many) to fix this issue is to re-create the repository for the OEM console. The steps are as follows.
- Make sure the database instance and the listener are up.
- Unlock
sysmanandsysuser accounts if not unlocked already.
eg.,% sqlplus / as sysdba SQL*Plus: Release 10.2.0.3.0 - Production on Thu Aug 27 23:42:24 2008 Copyright (c) 1982, 2006, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the Partitioning, OLAP and Data Mining options SQL> alter user sysman identified by manager account unlock; User altered. SQL> alter user sys identified by manager account unlock; User altered. SQL> quit
- Re-create the repository.
eg.,% emca -config dbcontrol db -repos recreate STARTED EMCA at Aug 27, 2008 11:43:09 PM EM Configuration Assistant, Version 10.2.0.1.0 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: test Listener port number: 1521 Password for SYS user: manager Password for DBSNMP user: dbsnmp Password for SYSMAN user: manager Email address for notifications (optional): Outgoing Mail (SMTP) server for notifications (optional): ----------------------------------------------------------------- You have specified the following settings Database ORACLE_HOME ................ /export/pspp/oracle Database hostname ................ matrix Listener port number ................ 1521 Database SID ................ test Email address for notifications ............... Outgoing Mail (SMTP) server for notifications ............... ----------------------------------------------------------------- Do you wish to continue? [yes(Y)/no(N)]: Y Aug 27, 2008 11:43:28 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /export/pspp/oracle/cfgtoollogs/emca/test/emca_2008-08-27_11-43-09-PM.log. Aug 27, 2008 11:43:31 PM oracle.sysman.emcp.EMReposConfig dropRepository INFO: Dropping the EM repository (this may take a while) ... ... ...
You are done. As simple as that.
_______________
| 2004-2016 |  |
Subscribe to:
Posts (Atom)