-
Dropping RMAN schema
Hi,
In order to test recovery using RMAN, i've created another user called RMANTEMP to do a recovery of my database (target database) on a separate host (catalog server). After a successful recovery, i intend to remove the RMANTEMP user.
Do i need to execute 'drop catalog' on my catalog server? Will this affect RMAN's catalog?
Do i also need to execute 'drop catalog' on my target database?
Thanks in advance!!!
-
Hi
You dont need to execute the drop catalog on the target database.
If you have created a catalog on another catalog log database then you cna drop it while you are logged in as RMANTEMP
While logged in as RMANTEMP onto the catalog database from RMAN prompt you can say DROP CATALOG.
regards
Hrishy
-
Thanks hrishy!!
Is it neccessary to drop the user RMANTEMP in both the target and catalog server then?
I was worried that there is any side effects since my target database is registered to 2 catalog servers.
-
Hi
I dont see any issues of dropping the RMANTEMP user from both the catalog and target database.
Did i forgot to tell you to take a export backup of RMANTEMP user in both catalog and target database just case before you drop :-)
regards
Hrishy
-
Thanks alot Hrishy!
According to what i've picked up from the online documentation, i've come to believe that as compared to unregistering my target database, dropping RMANTEMP will perhaps save some space in my database. Both will actually have the same end results in that i can no longer do backup or recovery using RMANTEMP. Is this correct?
Regards,
gxangel
-
Hi
Yes your understanding is correct once you drop the rmantemp user and its catalog you wont be able to backup the target database using that id.
However you have another user called RMAN and you can use that for your backup and recovery needs
regards
Hrishy
-
Thanks again!!!
In this case, does dropping user RMANTEMP drop its catalog too?
Or do we need to specifically drop its catalog before dropping RMANTEMP user?
Regards,
gxangel
-
Hi
Logged in as user RMANTEMP first drop the catalog and then logged in as a user with dba privileges drop the user rmantemp
regards
Hrishy
-
-
Hi,
Will the target server contain any information on the user RMANTEMP and it's catalog if i executed DROP CATALOG followed by DROP USER RMANTEMP at the catalog server only?
Do i need to do any cleanup here since DROP CATALOG is not executed at the target server?
-
Hi
You need to do logged in as rmantemp user on the catalog database
DROP CATALOG and
then with a user having DBA privileges to
DROP USER RMANTEMP;
After that you should log into target database with DBA privileges and then do a drop user rmantemp
regards
Hrishy
-
Hi Hrishy,
I don't get the part of dropping user RMANTEMP at the target database.
The user RMANTEMP was created at the catalog server only. After which i log in using RMANTEMP at the target database to register the database.The subsequent recovery was done on the catalog server.
In this case, won't dropping the user RMANTEMP at the target database be erroneous?
Regards,
gxangel
-
Hi
While doing a backup don't you connect simultaneously too catalog as well as target database ?
How do you do your backup ?
regards
Hrishy
-
Hi Hrishy,
My backup was done on the target server. The backup files are then copied over to the catalog server using data pump
-
Hi
I am sorry rman and datapump dont think so are related i did not understand what you are trying to say
regards
Hrishy
-
Hi,
Sorry if i confused you.
I have both physical and logical backup of my database.
The physical backup was done at my catalog database using RMAN.
-
Hi
How do you connect to target and catalog using rman temp ?
post the commands here
whats the output of
select username from dba_users
where username ='RMANTEMP'
in catalog and target databases
regards
Hris
-
Hi,
This is how i connect to RMANTEMP at both my target and catalog servers
HTML Code:
rman target /
RMAN> connect catalog rmantemp/password@rman
Output of select query at both servers
HTML Code:
SQL> select username from dba_users where username='RMANTEMP';
no rows selected
Thanks alot Hrishy!
-
Hi
I am sorry i don't understand
what i was thinking was something like this
rmantemp /target
rman>connect catalog rmantemp/password@rman
So your rmantemp user should exist in both the catalog and target database.
The fact that you can do this
Code:
RMAN> connect catalog rmantemp/password@rman
Tells me that you have user called rmantemp in catalog database which you should drop using drop user rmantemp in catalog database
regards
Hrishy
-
I see!
Thanks alot Hrishy!