Home » RDBMS Server » Security » URGENT!!!! SYS PASSWORD AND 9i!!!
URGENT!!!! SYS PASSWORD AND 9i!!! [message #72216] Tue, 15 April 2003 15:21 Go to next message
newbie2
Messages: 8
Registered: October 2002
Junior Member
How do you change the sys password in 9i?
It is still saying it is "change_on_install".

I logged in as sys/change_on_install as sysdba and then made and alter statement.
Re: URGENT!!!! SYS PASSWORD AND 9i!!! [message #72217 is a reply to message #72216] Tue, 15 April 2003 16:05 Go to previous messageGo to next message
Anand
Messages: 161
Registered: August 1999
Senior Member
Login as SYS ...

$ sqlplus /nolog
SQL> CONN SYS AS SYSDBA
Enter password: ***
Connected.
SQL> SHO USER
USER is "SYS"
SQL> ALTER USER sys IDENTIFIED BY ora9i;
SQL>

That's it... you are all set.Logout and login again, if needed.

A
Re: URGENT!!!! SYS PASSWORD AND 9i!!! [message #72218 is a reply to message #72216] Tue, 15 April 2003 16:20 Go to previous messageGo to next message
newbie2
Messages: 8
Registered: October 2002
Junior Member
Anand,

Thanks for your reply.

Here is the log file from what I have done:

SQL> set echo on
SQL> connect sys@imrs_test as sysdba
Connected.
SQL> sho user
USER is "SYS"
SQL> alter user sys identified by gondola;

User altered.

SQL> connect sys/gondola@imrs_test as sysdba
ERROR:
ORA-01017: invalid username/password; logon denied

Warning: You are no longer connected to ORACLE.
SQL> spool off
Re: URGENT!!!! SYS PASSWORD AND 9i!!! [message #72222 is a reply to message #72218] Wed, 16 April 2003 09:28 Go to previous messageGo to next message
Anand
Messages: 161
Registered: August 1999
Senior Member
================================================================
ORA-01017 on CONNECT INTERNAL or AS SYSDBA When Using Password File Validation
==============================================================================
Contents
--------
1) You are not providing the correct password or you have forgotten the password.
2) Are you connecting to the correct instance?
3) You might have reset the password by dropping the old password file or
recreating the instance with ORADIMxx, but you still are not able to connect
and get the error ORA-01017.
4) After deleting and recreating the instance with ORADIMxx.
5) The Password file might be corrupt.
6) The password of SYS has changed.
1) You are not providing the correct password or have forgotten the password
-------------------------------------------------------------------------
If you receive this error while trying to connect as internal or as SYSDBA
in svrmgrxx or sqlplus, it generally means that the password you are
providing is not the correct one.
SVRMGR> connect internal/wrong_password
ORA-01017: invalid username/password; logon denied
If you forgot the password of INTERNAL, or do not know it at all, you can
reset the password of INTERNAL in several ways. See [[NOTE:114384.1]] <ml2_documents.showDocument?p_id=114384.1&p_database_id=NOT>
WIN: Checklist for Resolving CONNECT AS SYSDBA (INTERNAL)
2) Are you connecting to the correct instance?
-------------------------------------------
If you have multiple instances with different passwords for INTERNAL on your
server, check if you are connecting to correct instance.
Verify if the parameter 'LOCAL' is not set in the registry or environment to
another instance name.
If not, set the environment variable ORACLE_SID to the correct instance name,
before launching svrmgrxx or sqlplus :
c:Orant> Set ORACLE_SID=<SID> !!!no blanks around the equal sign
c:Orant> svrmgrxx
3) You might have already reset the password by dropping the old password file
or recreated the instance with ORADIMxx, but still are not able to connect
and get the error ORA-01017
---------------------------------------------------------------------------
Check which password file is used by checking the value of ORA_<SID>_PWFILE
in the correct registry key.
If the parameter is set in the registry, you might be using another password
file than the one you just dropped and recreated.
[[NOTE:77412.1]] <ml2_documents.showDocument?p_id=77412.1&p_database_id=NOT> How To Identify Which Registry Hive Is Used By A Specific Oracle Executable
Default home: HkeyLocalMachineSoftwareOracle
Not Default home: HkeyLocalMachineSoftwareOracleHomex
If the parameter is not set, it is the password file in the default location
(%ORACLE_HOME%Database) with its default name (PWD<SID>.ORA) that is used,
otherwise it is the file specified by ORA_<SID>_PWFILE that is being used.
In that case, you should reset that parameter or drop and recreate that
specific password file.
4) After deleting and recreating the instance with ORADIMxx
--------------------------------------------------------
As from Oracle 8.0.5, 'ORADIMxx -delete' does not remove the password file.
Therefore after using 'ORADIMxx -new', the old password is still kept.
Example: you forgot or do not know the INTERNAL password. You reset it by
deleting and recreating the service with
ORADIMxx -delete -sid <sid>
ORADIMxx -new -sid <sid> -intpwd <password> -startmode auto -pfile <initsid.ora>
But when you try to connect as INTERNAL with the new <password> to the newly
created service, you still receive
ORA-01017: invalid username/password; logon denied
Solution : after 'ORADIMxx -delete', delete the password file.
The password file is by default situated in the Oracle Homedatabase
directory and might by a hidden file, visible by the DOS-prompt command:
d:Orantdatabase> dir /A:H
5) The Password file might be corrupt
----------------------------------
When you try to connect as INTERNAL or SYS, you receive the following error:
ORA-1017: invalid username/password; logon denied
You can connect as SYSTEM and if you attempt to change the password for SYS,
and you receive error:
ORA-3113: end of file on communication channel.
Passwords for SYS and INTERNAL are held externally in the pwd<sid>.ora file.
This file has been corrupted: dropping it and recreating it by using ORAPWDxx
might be not enough.
Occasionally, you need to bring the instance up by stopping the services and
restarting it.
[[NOTE:114384.1]] <ml2_documents.showDocument?p_id=114384.1&p_database_id=NOT> WIN: Checklist for Resolving CONNECT AS SYSDBA (INTERNAL)
6) The password of SYS has changed
-------------------------------
The password for INTERNAL appears to be changed. This always worked before
and you are certain that nobody has changed the INTERNAL password by
recreating the passwordfile.
On connection to Server Manager or SQL*Plus, you always receive the following error:
ORA-01017: invalid username/password; logon denied
You can connect as INTERNAL using the new password of SYS although the
password for the user SYS is different from the password for INTERNAL :
SVRMGR> connect internal/<password for sys>
This behavior depends on the instance parameter REMOTE_LOGIN_PASSWORDFILE.
a. REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
b. SQL> alter user sys identified by <password>;
c. SQL> connect sys/<password> AS SYSDBA
d. SQL> connect sys/<password_for_sysdba> AS SYSDBA
ERROR:
ORA-01017: invalid username/password; logon denied
If REMOTE_LOGIN_PASSWORDFILE=SHARED, a subsequent "alter user SYS identified
..." does not affect the password of INTERNAL.
Re: URGENT!!!! SYS PASSWORD AND 9i!!! [message #72246 is a reply to message #72218] Wed, 23 April 2003 10:28 Go to previous messageGo to next message
Anand
Messages: 161
Registered: August 1999
Senior Member
Check-out this link...

http://asktom.oracle.com/pls/ask/f?p=4950:8:77786801098946130::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:670117794561,

This may help resolve your problem
Re: URGENT!!!! SYS PASSWORD AND 9i!!! [message #73023 is a reply to message #72246] Sun, 18 January 2004 22:32 Go to previous messageGo to next message
Naresh
Messages: 27
Registered: March 2001
Junior Member
sir
if i am conencting :sys/passward@service as sysdba then it conenct to databace

if i am connecting as sys/passward@service
then it show err ora01017
invalid username passward

pls help
Re: URGENT!!!! SYS PASSWORD AND 9i!!! [message #73037 is a reply to message #73023] Wed, 21 January 2004 22:44 Go to previous message
Barbara Boehmer
Messages: 8922
Registered: November 2002
Location: California, USA
Senior Member
Oracle 9i requires that sys or system be connected as sysdba or sysuser.
Previous Topic: auditing of the db
Next Topic: access control
Goto Forum:
  


Current Time: Sat Aug 15 14:38:04 CDT 2020