Re: Big company, little error

It's not a database error. It's just a example when unnx it's little confused. I forget "" --> "little error"

Have a nice day,
Dan

Pete Finnigan <plsql_at_petefinnigan.com> wrote in message news:<AyxMmgB+JFbBRx9q_at_peterfinnigan.demon.co.uk>...
> Hi,
>
> I would say that this is not an error. The error you get is because the
> user unnx does not have the CREATE SESSION privilege. This means he
> cannot connect. This is what the error message says. This is unconnected
> to changing a users password. The same example could be done as follows:
 

  It's not a database error, it's just a intresting message.

> Connected to:
> Personal Oracle9i Release 9.2.0.1.0 - Production
> With the Partitioning, OLAP and Oracle Data Mining options
> JServer Release 9.2.0.1.0 - Production
>
> SQL> connect sys/a_at_sans as sysdba
> Connected.
> SQL> create user unnx identified by unnx password expire;
>
> User created.
> SQL> alter user unnx identified by unnx2;
>
> User altered.
>
> SQL> connect unnx/unnx2
> ERROR:
> ORA-01045: user UNNX lacks CREATE SESSION privilege; logon denied
>
>
> Warning: You are no longer connected to ORACLE.
> SQL> connect sys/a_at_sans as sysdba
> Connected.
> SQL> grant create session to unnx;
>
> Grant succeeded.
>
> SQL> connect unnx/unnx2
> Connected.
> SQL>
>
> Instead here the user SYS changes the user UNNX's password and then the
> user UNNX tries to connect (I realise this is concocted and the purpose
> of expiring the password is to make the user change it on his next
> connection) and receives the "LACK OF CREATE SESSION privilege" error.
> This shows that changing the password is unconnected to the lack of
> create session privilege.
>
> BUT, you are right to make people aware of this, some may assume that
> the password change was rolled back (so to speak) when in fact it was
> not. but not a bug in the database.
>
> kind regards
>
> Pete
Received on Wed Oct 13 2004 - 03:25:24 CDT