Unable to start TIBCO iProcess Engine or execute any command such as swsvrmgr, plist, swadm
Article ID: KB0078550
Updated On:
| Products | Versions |
|---|---|
| TIBCO Process Engine (Oracle) | All supported versions |
Description
All environment variables are defined correctly and it is possible to connect to Oracle correctly using the database background and foreground users.
The utility tnsping reports a successful test, for example:
tnsping TEST
TNS Ping Utility for Linux: Version 12.1.0.2.0 - Production on 12-APR-2019 13:11:36
Copyright (c) 1997, 2014, Oracle. All rights reserved.
Used parameter files:
/oracle/client/12.1.0.2/network/admin/sqlnet.ora
Used LDAP adapter to resolve the alias
Attempting to contact (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=test.one.com)(PORT=1928))(CONNECT_DATA=(SERVICE_NAME=TEST.ONE.COM)))
OK (10 msec)
The utility tnsping reports a successful test, for example:
tnsping TEST
TNS Ping Utility for Linux: Version 12.1.0.2.0 - Production on 12-APR-2019 13:11:36
Copyright (c) 1997, 2014, Oracle. All rights reserved.
Used parameter files:
/oracle/client/12.1.0.2/network/admin/sqlnet.ora
Used LDAP adapter to resolve the alias
Attempting to contact (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=test.one.com)(PORT=1928))(CONNECT_DATA=(SERVICE_NAME=TEST.ONE.COM)))
OK (10 msec)
Issue/Introduction
Unable to start TIBCO iProcess Engine or execute any command such as swsvrmgr, plist, swadm
Environment
Unix / Linux
Resolution
The problem is caused by LDAP being used to resolve the alias as seen in the output from tnsping,
Used LDAP adapter to resolve the alias
The iProcess Engine is expecting to use TNSNAMES,
Used TNSNAMES adapter to resolve the alias
LDAP is currently not supported for the database resolution.
Update the configuration to change the database resolution method to be TNSNAMES rather than LDAP.
If other applications need the LDAP resolution method install a new Oracle client that does not use the LDAP resolution and point iProcess Engine to use that $ORACLE_HOME instead.
Used LDAP adapter to resolve the alias
The iProcess Engine is expecting to use TNSNAMES,
Used TNSNAMES adapter to resolve the alias
LDAP is currently not supported for the database resolution.
Update the configuration to change the database resolution method to be TNSNAMES rather than LDAP.
If other applications need the LDAP resolution method install a new Oracle client that does not use the LDAP resolution and point iProcess Engine to use that $ORACLE_HOME instead.
Feedback
Yes
No
Powered by
