Netweaver 7.3 installation error while starting dispatcher

Question

Hi Experts
I am installing PI 7.3 on a distributive host Linux RHEL 5.7 & Oracle 11.2g
I have installed ASCS & SCS and DB instance and now i am installing CI while installing CI its stuck while starting dispatcher
Please see the below logs
dev_disp trace
pTraceWpStatus: child (pid=9939) exited with exit code 255
DpUnlockWpAdm: force unlock of wp_adm mutex W12
DpProcFreeBlks: free blocks for WORK_PROCESS (pid=9939; flags=3)
DpListRemove: remove elem 12 from wpadm_btc_list
DpListRemove: 0 elems in wpadm_btc_list
DpListRemove: elem 12 not in wpadm_free_btc_list
DpHdlDeadWp: handling of W12 o.k.
DpGetMsgTypes: my types = MS_DIA,MS_VB,MS_BTC,MS_SPO,MS_VB2,MS_ICMAN
DpGetMsgTypes: my types = MS_DIA,MS_VB,MS_BTC,MS_SPO,MS_VB2,MS_ICMAN
DpGetMsgTypes: my types = MS_DIA,MS_VB,MS_BTC,MS_SPO,MS_VB2,MS_ICMAN
DpGetMsgTypes: my types = MS_DIA,MS_VB,MS_BTC,MS_SPO,MS_VB2,MS_ICMAN
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN
dev_w0 trace
ERROR => Invalid profile parameter dbms/type (or environment variable dbms_type) = <undef>, cannot load DB library
[dbcon.c      5081]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 008192)
I already have a dbms_type=ORA set , R3trans -D works fine .
i have checked many posts here but its not helping me .
I have restarted the server and done the cleanipc as well
Any help will be much appreciated.
Thanks
dEE

Answer 1

ORA-12154:
TNS:could not resolve the connect identifier specified
Cause:      A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Action:     
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.