Today we will discuss about the issue during the oracle database startup.
Symptoms For Error 2EETW169 no connect possible:
Oracle doesn’t start & R3trans -d throws error as
“No connect possible
2EETW169 no connect possible: “DBMS = ORACLE— dbs_ora_tnsname = ‘DEV'”
Solution:
We analyzed many logs and few of the steps we performed to rectify the issue are as below:
- We have checked listener which was working fine
- Checked if the database is in open state.
- Finally, when we checked the dev_W* logs which is showing the below that it is due to locking of user account SAPDEV:
- We checked if any database user was locked using the query:
Select username,ACCOUNT_STATUS from dba_users;
Here SAPDEV user was locked, oracle unlock account should be performed to solve the issue using the command:
SQL> alter user <USER> account unlock;
<USER>=SAPDEV in our case
Reason and Prerequisites for 2EETW169 no connect possible:
what is ORA-28000 and when it occurs?
There are two situations when your account could be locked and to get ORA-28000 error.
- Failed Login Attempts:
Default profile in oracle Database Management Software has 10 failed login attempts and after that it locks the user account. So, need to unlock this.
SQL> select * from dba_profiles where resource_name like 'FAILED_LOGIN_ATTEMPTS%';
Results:
PROFILE | RESOURCE_NAME | RESOURCE | LIMIT |
DEFAULT | FAILED_LOGIN_ATTEMPTS | PASSWORD | 10 |
MONITORING_PROFILE | FAILED_LOGIN_ATTEMPTS | PASSWORD | UNLIMITED |
- New Database Creation:
When you create a new database all default accounts are “EXPIRED & LOCKED” except SYS and SYSTEM. So, you need to unlock and change password to use them.
SQL> select username,account_status from dba_users;
USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
SYS OPEN
SYSTEM OPEN
SAPDEV EXPIRED & LOCKED
OUTLN EXPIRED & LOCKED