Operating System - HP-UX
1752339 Members
5576 Online
108787 Solutions
New Discussion юеВ

Re: Oracle operation problem

 
T G Manikandan
Honored Contributor

Re: Oracle operation problem

Andreas,

GReat to see you again after a long time.

Welcome back.
Expecting great answers as usual.


Thanks
Andreas D. Skjervold
Honored Contributor

Re: Oracle operation problem

Hi TG

Nice to have been missed! Been kinda busy lately.

rgds
Andreas
Only by ignoring what everyone think is important, can you be aware of what everyone ignores!
KY.Chuang
Advisor

Re: Oracle operation problem

Dear all,
I create the orapw file with orapw.
And also add
(remote_login_passwordfile = exclusive) to init.ora file.

When I login SYSDBA with sys/, It fail.(ORA-01017 invalid username/passowrd) which I execute Oracle DBA Studio in Remote.
But I login oracle with svrmgrl(connect sys/ as sysdba) in locale, It could.
Why?

Service is King
Yogeeraj_1
Honored Contributor

Re: Oracle operation problem

hi,

quote from above:


$ svrmgrl

SVRMGR> connect internal
Connected.

SVRMGR> connect sys/change_on_install@ora817dev
Connected.

that works OK, lets try as sysdba:

SVRMGR> connect sys/change_on_install@ora817dev as sysdba;
ORA-01017: invalid username/password; logon denied

there I got your error. My SYS password is change_on_install but the password file has yog in it. SYS is special -- sys connecting as sysdba is like internal -- you have to use the password file password!

Lets try that:

SVRMGR> connect sys/yog@ora817dev as sysdba;
Connected.


the sysdba trick is generally used to allow other NON-SYS users to connect. BTW, it is recommended that you use your OWN account that has been granted sysdba!




most probably, you are not connecting as sysdba in the DBA studio, hence the error!

i suggest, you connect using the svrmgrl and change the sys password using:

alter user sys identified by ;

Again, avoid using the sys account and create your own as i mentioned in my previous post.

Best Regards
Yogeeraj

No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Andreas D. Skjervold
Honored Contributor

Re: Oracle operation problem

Hi again Ky

Perhaps silly, but remember to bounce your database after updating the init.ora file.

rgds
Andreas
Only by ignoring what everyone think is important, can you be aware of what everyone ignores!
Massimo Bianchi
Honored Contributor

Re: Oracle operation problem

Hi,
there is also another point:
AFTER you created the password file you have to grant the sysdba and sysoper role to the user.


Yuo define one user in the file (user=) and his/her password (password=), after that you will have to re-grant the permission to that user.

svrmgrl> grant sysoper, sysdba to XXXXX ;
svrmgrl> commit;

HTH,
Massimo