I am sorry that this thread has botherred you. I have been using TOAD to login DB to do some DBA work with different version of Oracle DB on different platform. Recently I switched to a new comapny as DBA. I used TOAD 9.5 to login DB as sysdba (in TOAD there are 3 login modes - sysdba, sysoper and normal). In begining, I logged in and did some work successfully. Then one day, I could not login with ORA-01017 error. Then I went to server and login as: conn / as sysdba successfully. Then I tried login as conn sys/password@DBSID as sysdba successfully. Then I queryed by : select * from v$pwfile_users; , I got sys.
From above trials, it seems that password file is fine. My oracle client is still in 10.2.0.1 version and DB has been patched (done by previoue DBA) to 10.2.0.3 patch2. TOAD use tnsnames and sqlnet from local oracle client home to connect to DB on server remotely. Is this the reason to cause ORA-01017? Then I used: alter user system identified by new_password;. Then login as system in normal mode successfully even client tool is still in 10.2.0.1 and DB on server is 10.2.0.3 patch2.
I just want to idenfy the problem and still login with TOAD as sysdba to do some work. However, I will never give up login with / as sysdba to do most DBA work on server side. Please advise. Thanks.
QUOTE (burleson @ Jul 23 2008, 04:27 PM)
>> But we are talking about apple and banana here.
I read this, and I don't understand your question.
In your first post, you asked why TOAD threw an error. Who knows?
Can you please re-state your question, please?