password value in dba_users

[CONCLUSION]
Same encrypted password string (PASSWORD column) in dba_users doesn't mean the actual password are the same. USERNAME looks the key to encrypt the password.
Below is the experiment.

SQL> select password, username from dba_users where username in ('LIQY');

PASSWORD USERNAME
------------------------------ ------------------------------
B68901BE8B75A6BA LIQY

SQL> create user liqy1 identified by values 'B68901BE8B75A6BA';

User created.

SQL> grant create session to liqy1;

Grant succeeded.

SQL> sers where username in ('LIQY','LIQY1'); <> connect liqy1/liqyliqy;
ERROR:
ORA-01017: invalid username/password; logon denied


Warning: You are no longer connected to ORACLE.
SQL> connect liqy/liqyliqy;
Connected.


SQL> connect /
Connected.
SQL> alter user liqy identified by liqyliqy;

User altered.

SQL> s where username in ('LIQY','LIQY1'); <> connect /
Connected.
SQL> alter user liqy1 identified by liqyliqy;

User altered.

SQL> select password, username from dba_users where username in ('LIQY','LIQY>

PASSWORD USERNAME
------------------------------ ------------------------------
B68901BE8B75A6BA LIQY
56775B8ACC3F0E97 LIQY1

Internal error:ulnail: bad row out of bounds [21]

Problem:

8i SQL*Loader failed with error message SQL*Loader-704:Internal error:ulnail: bad row out of bounds [21]. Target database is 10g.

Troubleshooting:

Tried option DIRECT=TURE but failed as 10g database doesn't support such option from 8i client.

Solution:

Add parameter bindsize=500000 and succeed.

No trigger body in dba_source

[The problem]

Can see trigger body with dbms_metadata.get_ddl, but can't see in dba_source or dba_triggers. Moreover, the trigger functions well.

[Root Cause]
This is due to a bug in Oracle version 8. For my case , this database was upgraded from 8.0 to 8i to 9i eventually.

To rectify it, just recompile it.


select TRIGGER_BODY from dba_triggers where trigger_name='IVOC_SP_CONTACT3';