Unable to start NodeManager [message #674572] |
Mon, 04 February 2019 02:54 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](http://www.gravatar.com/avatar/d8049923f90321c2f651dd696c6cde60?s=64&d=mm&r=g) |
bosekamineni
Messages: 2 Registered: February 2019
|
Junior Member |
|
|
Installed WebLogic Server 12.2.1.2.0 for Microsoft Windows x64 on Windows 2012 server
Oracle Forms 12.2.1.2.0 for Microsoft Windows x64 (64-bit) V789400-01
Oracle Reports 12.2.1.2.0 for Microsoft Windows x64 (64-bit) V789400-01
Oracle Fusion Middleware 12c Infrastructure 12.2.1.2.0 for Microsoft Windows x64 (64-bit) V779122-01
Oracle WebLogic Server 12.2.1.2.0 for Microsoft Windows x64 (64-bit) V779119-01
when starting nodemanager
D:\Oracle\Middleware\user_projects\domains\FRDomain\bin>startNodeManager.cmd
'ocom5' is not recognized as an internal or external command, operable program or batch file.
could not find logfile
|
|
|
|
|
Re: Unable to start NodeManager [message #674584 is a reply to message #674580] |
Mon, 04 February 2019 06:05 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
John Watson
Messages: 8938 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
I find WebLogic awful to work with for exactly this sort of reason. There are scripts calling scripts calling scripts, and horribly confused environment variables.
One thing I have found is that it is best to use short,simple directory names (definitely no spaces) and passwords that have only "normal" characters.
(As a scientist, I don't believe in luck. But with WebLogic, you may need it.)
|
|
|