Problem connecting to the target using RMAN [message #310203] |
Mon, 31 March 2008 09:58 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
Hello,
I have a problem in connecting to the target database from the auxiliary... say from the (auxiliary) standby database server i issue the following commands..the previous DBA has quit his job before a month i joined...Now I need to perform a RMAN backup of the prod and then duplicate the database on the standby...
/opt/oracle>rman catalog rman/rcvy10g@rman target sys/oracle@prod.oracle.com auxiliary /
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Mar 31 06:48:54 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01017: invalid username/password; logon denied
Is there a problem with SYS password..Does the host connects to the target via pwd file..I am not sure about the SYS password too as there is no password maintained by the previous DBA at job.
In the listener file there is a password set with logging on.. Does it stop me connecting to the target(prod) database from the standby(auxiliary)...
Please share your knowledge...
|
|
|
|
|
Re: Problem connecting to the target using RMAN [message #310233 is a reply to message #310209] |
Mon, 31 March 2008 11:37 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
Brian,
Either I couldnot connect with sqlplus.
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Mar 31 09:21:48 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: sys@prod.oracle.com
Enter password:
ERROR:
ORA-01017: invalid username/password; logon denied
In this case should I change the sys password and recreate the pwd file with the sys pwd in primary as well as the standby databases.. We have 3 standby databases. and also should I need to change anything in the RMAN catalog database..
I am here with attaching the tnsnames entries also for your reference..
prod.oracle.com=
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = prod.alprod-priv.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = edc.oracle.com)
(SID=edc)
)
)
Please let me know whether changing the SYS password and recreating the passwd file in all instances (primary & standby) will solve the issue..whether there will be any business impact in changing the SYS password..
Thank You...
|
|
|
|
|
|
|
|
Re: Problem connecting to the target using RMAN [message #311204 is a reply to message #310247] |
Thu, 03 April 2008 12:51 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
Brian/Michel,
Does recreating the pwd file on standby's affect the standby databases during switch over..How does the pwd file work..
Does it not directly dependent on the SYS password.. since I could not change the SYS password in standby..
how do I change it.Should I stop the log shipping to standby using defer, then bring then recover the standby db's and shutdown.. then change SYS password same as primary and bring back standby..
|
|
|
|
|
|
|
|
Re: Problem connecting to the target using RMAN [message #311263 is a reply to message #311261] |
Thu, 03 April 2008 19:37 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
I was unable to connect to the primary thru RMAN and so I have changed the SYS passwd.. and recreated the passwd file with same SYS password on all databases(primary & standby).. Now I need to keep the same SYS passwd for the standby also right..
Here is where I am struck with...If the pwd file takes care of log shipping then if want to switchover to the primary how will the database react...
|
|
|
|
|
|
Re: Problem connecting to the target using RMAN [message #311268 is a reply to message #311267] |
Thu, 03 April 2008 20:00 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
Yeah you missed my query. To summarize the problem..
1.I had problems in connecting to primary database through RMAN to create a duplicate database.
2.I have reset the SYS password in the primary DB and also recreated the password file..after which I can able to connect to target from the auxiliary
3.then I recreated the pwd file in standby as well and the log shipping was happening ...
4.At this point since I must have the same SYS password in standby databases i tried to reset them..
Let me know if you have any queries...
|
|
|
|
Re: Problem connecting to the target using RMAN [message #311270 is a reply to message #311269] |
Thu, 03 April 2008 20:14 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
Thank you.. Since I have reset the password to the older one I was able to do all stuffs .. If I have changed to a new password then how to go about in changing the same in standby...
Should I stop the log shipping , open the standby and change the SYS pwd to match the primary and then put back in standby..
Michel, You said that pwd file over takes the database SYS pwd.. Do you have any suggestions..
|
|
|
|
|
Re: Problem connecting to the target using RMAN [message #313140 is a reply to message #311291] |
Thu, 10 April 2008 17:50 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
Thanks Brian/Michele,
I would like to change the listener password in the current env, Does it have any impact on the OEM agent or the application connectivity to the database.. Or it is simply used to prevent database from the hackers..What will happen setting the ADMIN_RESTRICTIONS_LISTENER = ON in the listener..Please let me know your views..
|
|
|
|
|
Re: Problem connecting to the target using RMAN [message #313394 is a reply to message #313189] |
Fri, 11 April 2008 11:37 |
Nick_01
Messages: 36 Registered: March 2008
|
Member |
|
|
The RMAN issues no more exists..I just wanted to know whether I need to reload the listener after changing the listener password ..
And to make sure that listener password is only to prevent hackers and it doesnot affect the application access to the database..
|
|
|
|
|
|