Problem:
ORA-12162 errors on application (.exe) startup ONLY when .exe file was launched from certain directories, NOT from others
Client Platform: NT4 (SP6)
Server: Oracle 8.1.5
Repeatable: Yes
Commonality:
Error occurred when full path of .exe contained closed-paren character ")".
Example from sqlnet.log -
test program full name and path is "C:\(PAREN)\PROGRAM.EXE"
****************************************
Fatal NI connect error 12162, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=ORACLEDM)(PORT=1234)))(CONNECT_DATA=(SERVICE_NAME=ORACLE.WORLD)(CID=(PROGRAM=C:\(PAREN)\PROGRAM.EXE)(HOST=WK1)(USER=johndoe) )))
Possible Cause:
Oracle8 parsing algorithm misreads embedded closed-paren as end of PROGRAM= parameter.
Note:
Application whose full path contains open-paren character(s) but no closed-paren characters WILL startup, but with unknown effect on stability/performance (did not test).
Workaround:
Removed all closed-paren characters from file name and path- i.e., renamed .exe file and all parent directories to names NOT containing closed-paren characters; out of prudence, also removed all open-paren characters from file name and path.
Per this example, renamed program full name and path is now "C:\PAREN\PROGRAM.EXE"
ORA-12162 errors on application (.exe) startup ONLY when .exe file was launched from certain directories, NOT from others
Client Platform: NT4 (SP6)
Server: Oracle 8.1.5
Repeatable: Yes
Commonality:
Error occurred when full path of .exe contained closed-paren character ")".
Example from sqlnet.log -
test program full name and path is "C:\(PAREN)\PROGRAM.EXE"
****************************************
Fatal NI connect error 12162, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=ORACLEDM)(PORT=1234)))(CONNECT_DATA=(SERVICE_NAME=ORACLE.WORLD)(CID=(PROGRAM=C:\(PAREN)\PROGRAM.EXE)(HOST=WK1)(USER=johndoe) )))
Possible Cause:
Oracle8 parsing algorithm misreads embedded closed-paren as end of PROGRAM= parameter.
Note:
Application whose full path contains open-paren character(s) but no closed-paren characters WILL startup, but with unknown effect on stability/performance (did not test).
Workaround:
Removed all closed-paren characters from file name and path- i.e., renamed .exe file and all parent directories to names NOT containing closed-paren characters; out of prudence, also removed all open-paren characters from file name and path.
Per this example, renamed program full name and path is now "C:\PAREN\PROGRAM.EXE"
