|
|
Please tell me why
|
|
Environment : Oracle816 for RedHat6.2 + Oracle816 Client
21:30:03 SQL> connect sys@linux as sysdba
Password : Attention duty announcers, please input
ERROR :
ORA-28000 : the account is locked
Warning : You no longer connect to Oracle.
21:30:19 SQL> connect sys/change_on_install@linux as sysdba
Has been connected.
21:30:24 SQL>
The first two days ago suddenly SYS users not directly connected, as sysdba must remember that a lot of people were off this trick wonder : ORACLE a backdoor)
Second, it is necessary to connect codes such as the above, say ORA-28000, who can tell me how else child?
Thank you
*******************
World in a Grain of Sand
A paradise for water
|
|
|
|
Can connect sys/change_on_install@linux ah!
|
|
Windows Client Server Environment is my ORACLE8.1.6+RH62
AS SYSDBA can not be increased landing
Allocation may be? PFILE, such NET8
. . . . . . . . Peregrine Road unpaid days. . . . . . . . .
|
|
|
|
Re : Please tell me why
|
|
Sys users to check the configuration file to see the setup parameters
|
|
|
|
Re : Please tell me why
|
|
Easyfree sys SYSDBA not only can you use internal SYSDBA identity landing.
|
|
|
|
Re : Please tell me why
|
|
Sys as sysdba=internal
|
|
|
|
Re : Please tell me why
|
|
ZALBB :
Look at what parameters you? Last time you used the SYS SYSDBA registered users can then how to solve?
*******************
World in a Grain of Sand
A paradise for water
|
|
|
|
Re : Please tell me why
|
|
I do not like the situation you. Check it out for you view dba_users
And its profile, and then look dba_profiles.
|
|
|
|
Re : Please tell me why
|
|
I checked the profile of sys, it was the default parameter profiles and its was the following :
PROFILE RESOURCE_NAME RESOURCE_TYPE LIMIT
---------- ------------------------------ ---------------- ----------
DEFAULT COMPOSITE_LIMIT KERNEL UNLIMITED
DEFAULT FAILED_LOGIN_ATTEMPTS PASSWORD 3
DEFAULT PASSWORD_LIFE_TIME PASSWORD 3
DEFAULT PASSWORD_REUSE_TIME PASSWORD UNLIMITED
DEFAULT PASSWORD_REUSE_MAX PASSWORD UNLIMITED
DEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD UNLIMITED
DEFAULT PASSWORD_LOCK_TIME PASSWORD. 0006
DEFAULT PASSWORD_GRACE_TIME PASSWORD 10
DEFAULT PRIVATE_SGA KERNEL UNLIMITED
DEFAULT CONNECT_TIME KERNEL UNLIMITED
DEFAULT IDLE_TIME KERNEL UNLIMITED
DEFAULT LOGICAL_READS_PER_CALL KERNEL UNLIMITED
DEFAULT LOGICAL_READS_PER_SESSION KERNEL UNLIMITED
DEFAULT CPU_PER_CALL KERNEL UNLIMITED
DEFAULT CPU_PER_SESSION KERNEL UNLIMITED
DEFAULT SESSIONS_PER_USER KERNEL UNLIMITED
What is the problem? I do not have any way to reform
*******************
World in a Grain of Sand
A paradise for water
|
|
|
|
Re : Please tell me why
|
|
CONNECT INTERNAL SQL>
Enter password :
Connected.
SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LOCK_TIME 0.0001;
SYS AGAIN AS THEN TRY TO CONNECT
|
|
|
|
Re : Please tell me why
|
|
You solve the problem?
|
|
|
|
Re : Please tell me why
|
|
Or not, eh :
17:47:23 SQL> connect internal@linux as sysdba
Password : Please input ******
ERROR :
ORA-01031 insufficient privileges :
17:47:54 SQL> connect internal/A2345@linux
Has been connected.
17:48:00 SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LOCK_TIME 0.0001;
Configuration file has been changed
17:48:18 SQL> connect sys@linux as sysdba
Password : Please input ******
ERROR :
ORA-01017 : invalid logon denied username/password;
Warning : You no longer connect to Oracle.
17:48:31 SQL> connect sys/A2345@linux as sysdba
Has been connected.
17:48:47 SQL>
28,000 but not wrong, but I have certainly not wrong password, it is also wrong to say users and password, can be directly written
But strangely, I could be in another machine, some of the nuances of suspected version of the Client
*******************
World in a Grain of Sand
A paradise for water
|
|
|
|
Re : Please tell me why
|
|
Unfortunately, I do not have Linux to simulate the environment in your situation NT
You may not succeed, I succeed.
|
|
|
|
Re : Please tell me why
|
|
Last resort if these values have changed unlimited :
Alter profile profile limit failed_login_attempts null;
|
|
|
|
Re : Please tell me why
|
|
Easyfree you look into database-driven parameter value is not EXCLUSIVE REMOTE_LOGIN_PASSWORDFILE, if not change, then you see is what you can to solve the problem.
|
|
|
|
Re : Please tell me why
|
|
View V$PWFILE_USRS you look into it to see if there is SYSDBA sys whether the authority.
|
|
|
|
Re : Please tell me why
|
|
Sys never have sysdba competence.
|
|
|
|
Re : Please tell me why
|
|
CHENQI :
I have read that you said that there would be no problem, in fact I said in front of the other machines can be, suspected CLIENTįĢ¯ the problem rather than the problem itself database
Thank you two
*******************
World in a Grain of Sand
A paradise for water
|
