No domains accessible to the user logged in while logging to BPEL Console
Problem:
“No domains accessible to the users” message is displayed while logging to the
bpel console.
We tried to create the domains using create domain link, we found from the error
Messages that it is using a different port. And also the bpel user account is
getting locked.
Cause:
The console is not able to find the default domains in the database
Solution:
1) Check the database is up and running or not. if not, make it up otherwise check the error and follow point 2
2) We changed the URL which it is trying to connect while creating a new domain
In the following path:
EM console OC4J Home Click Administration tab In Services Go To
JDBC Resources in Connection Pools Click
BPELPM_CONNECTION_POOL In the URL box edit the URL and
revert the change.
We edited the port and remaining is to resolve bpeluser account locking.
We proceeded with the following (Source Google)
Recently we’ve had quite a few migrations to 10g Release 2 and several times been hit by one issue – some users consistently get locked with status LOCKED(TIMED). One good example is with the DBSNMP and SYSMAN users, but more important are locked production accounts.
It turned out that the FAILED_LOGIN_ATTEMPTS attribute for the DEFAULT profile has been changed in 10.2.0.2 (actually 10.2.0.1 and above) from UNLIMITED to the value of 10. Well, that’s good from security point of view. On the other hand, this is really dangerous, especially during or after migrations while chances are high that some process will try to connect with wrong credentials. This can easily end up with a service outage because an application can’t connect.
One way to resolve it is to change the DEFAULT profile. However, I would recommend leaving it 10 by default and, instead, create a new profile and assign the critical production users to this profile:
CREATE PROFILE DEFAULT_10GR1
LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;
ALTER USER [USERNAME] PROFILE DEFAULT_10GR1;
After this we tested the connection by clicking test connection option in the following path
EM console OC4J Home Click Administration tab In Services Go To
JDBC Resources in Connection Pools Click
BPELPM_CONNECTION_POOL Test Connection.
The Test was successful and this time we are able to see the default domain after logging PEL Console.
“No domains accessible to the users” message is displayed while logging to the
bpel console.
We tried to create the domains using create domain link, we found from the error
Messages that it is using a different port. And also the bpel user account is
getting locked.
Cause:
The console is not able to find the default domains in the database
Solution:
1) Check the database is up and running or not. if not, make it up otherwise check the error and follow point 2
2) We changed the URL which it is trying to connect while creating a new domain
In the following path:
EM console OC4J Home Click Administration tab In Services Go To
JDBC Resources in Connection Pools Click
BPELPM_CONNECTION_POOL In the URL box edit the URL and
revert the change.
We edited the port and remaining is to resolve bpeluser account locking.
We proceeded with the following (Source Google)
Recently we’ve had quite a few migrations to 10g Release 2 and several times been hit by one issue – some users consistently get locked with status LOCKED(TIMED). One good example is with the DBSNMP and SYSMAN users, but more important are locked production accounts.
It turned out that the FAILED_LOGIN_ATTEMPTS attribute for the DEFAULT profile has been changed in 10.2.0.2 (actually 10.2.0.1 and above) from UNLIMITED to the value of 10. Well, that’s good from security point of view. On the other hand, this is really dangerous, especially during or after migrations while chances are high that some process will try to connect with wrong credentials. This can easily end up with a service outage because an application can’t connect.
One way to resolve it is to change the DEFAULT profile. However, I would recommend leaving it 10 by default and, instead, create a new profile and assign the critical production users to this profile:
CREATE PROFILE DEFAULT_10GR1
LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;
ALTER USER [USERNAME] PROFILE DEFAULT_10GR1;
After this we tested the connection by clicking test connection option in the following path
EM console OC4J Home Click Administration tab In Services Go To
JDBC Resources in Connection Pools Click
BPELPM_CONNECTION_POOL Test Connection.
The Test was successful and this time we are able to see the default domain after logging PEL Console.
Comments