Shulou(Shulou.com)06/01 Report--

Technology usage scenario: today, when troubleshooting a system problem, there is no problem at the application level. There is no way to think that the corresponding user of the database has been modified, so check whether the corresponding database account has been modified. (this scenario is executed without knowing the database password. If you know the password of the database, just run sqlplus login directly.)

View table USER$

SQL > desc user$

Name Null? Type

-

USER# NOT NULL NUMBER

NAME NOT NULL VARCHAR2 (30)

TYPE# NOT NULL NUMBER

PASSWORD VARCHAR2 (30)

DATATS# NOT NULL NUMBER

TEMPTS# NOT NULL NUMBER

CTIME NOT NULL DATE creation time

PTIME DATE modification time

EXPTIME DATE expiration time

LTIME DATE Lock time

RESOURCE$ NOT NULL NUMBER

AUDIT$ VARCHAR2 (38)

DEFROLE NOT NULL NUMBER

DEFGRP# NUMBER

DEFGRP_SEQ# NUMBER

ASTATUS NOT NULL NUMBER

LCOUNT NOT NULL NUMBER

DEFSCHCLASS VARCHAR2 (30)

EXT_USERNAME VARCHAR2 (4000)

SPARE1 NUMBER

SPARE2 NUMBER

SPARE3 NUMBER

SPARE4 VARCHAR2 (1000)

SPARE5 VARCHAR2 (1000)

SPARE6 DATE

Query statement: select USER#, NAME,PTIME from user$

Query again after changing the password

Change it to the current date immediately

In addition: some friends on the Internet have explained that you can modify the user name in the user$ table to change the display name. It is recommended not to modify the digital dictionary under sys. The unknown risk is great.

+

Author: JOHN

ORACLE technology blog: ORACLE hunter's note database technology group: 367875324 (please note ORACLE management)

+

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.