Hi All,
We are working on a POC for OBIEE 12c on a windows 2012 server machine. node manager, adminserver and managed server are on the same machine.
I am trying to create windows services just like we did in 11g.
I was able to get all 3: Nodemanager, AdminServer and Managed Server (bi_server1 in my case) started via services.
However, I can't seem to get any of the bi components up in EM.
The managed and adminserver are up and show green in both em and console.
I am attaching few errors below.
If you need some more information let me know.
Thanks
Marwin
The error I see at a lot of places is:
Starting server obis1 ...
This Exception occurred at Fri Feb 19 16:22:13 IST 2016.
weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Server start command for OBIS server 'obis1' failed due to: [Server failed to start up but NodeManager was not aware of the reason]. Please check Node Manager log and/or server 'obis1' log for detailed information.]. Please check NodeManager log for details.Error: Error occurred while performing nmStart : Error Starting server obis1 : Received error message from Node Manager Server: [Server start command for OBIS server 'obis1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'obis1' log for detailed information.]. Please check Node Manager log for details.
The node manager logs don't really say much:
<Feb 19, 2016 4:35:13 PM IST> <INFO> <bi> <obis1> <Startup configuration properties saved to "C:\Obiee12c\home\Oracle\user_projects\domains\bi\system_components\OBIS\obis1\data\nodemanager\startup.properties">
<Feb 19, 2016 4:35:19 PM IST> <INFO> <bi> <obis1> <The server 'obis1' with process id 7944 is no longer alive; waiting for the process to die.>
<Feb 19, 2016 4:35:19 PM IST> <INFO> <bi> <obis1> <Server failed during startup. It may be retried according to the auto restart configuration.>
<Feb 19, 2016 4:35:19 PM IST> <INFO> <bi> <obis1> <Server failed so attempting to restart (restart count = 1)>
<Feb 19, 2016 4:35:23 PM IST> <INFO> <bi> <obis1> <The server 'obis1' with process id 7888 is no longer alive; waiting for the process to die.>
<Feb 19, 2016 4:35:23 PM IST> <INFO> <bi> <obis1> <Server failed during startup. It may be retried according to the auto restart configuration.>
<Feb 19, 2016 4:35:23 PM IST> <INFO> <bi> <obis1> <Server failed so attempting to restart (restart count = 2)>
<Feb 19, 2016 4:35:27 PM IST> <INFO> <bi> <obis1> <The server 'obis1' with process id 9420 is no longer alive; waiting for the process to die.>
<Feb 19, 2016 4:35:27 PM IST> <INFO> <bi> <obis1> <Server failed during startup. It may be retried according to the auto restart configuration.>
<Feb 19, 2016 4:35:27 PM IST> <INFO> <bi> <obis1> <Server failed but will not be restarted because the maximum number of restart attempts has been exceeded>
<Feb 19, 2016 4:35:27 PM IST> <WARNING> <Server start command for OBIS server 'obis1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'obis1' log for detailed information.>
EM:
Unable to start the server obis1 : Received error message from Node Manager Server: [Server start command for OBIS server 'obis1' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'obis1' log for detailed information.]. Please check Node Manager log for details.
| Can not start selected component. |
| oracle.sysman.emai.model.bi.ModelException: Failed to start the component
at oracle.sysman.emai.model.bi.mbean.AvailabilityAssistant.processComponent(AvailabilityAssistant.java:1111)
at oracle.sysman.emai.model.bi.mbean.AvailabilityAssistant.startComponent(AvailabilityAssistant.java:967)
at oracle.sysman.emai.view.bi.AvailabilityView.startComponent(AvailabilityView.java:876)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at oracle.sysman.emInternalSDK.sdkas.general.pojo.progress.WorkWrapper.run(WorkWrapper.java:113)
at java.lang.Thread.run(Thread.java:745) |
| WorkWrapper caught exception: |
| oracle.sysman.emSDK.app.exception.EMSystemException
at oracle.sysman.emai.view.bi.AvailabilityView.startComponent(AvailabilityView.java:881)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at oracle.sysman.emInternalSDK.sdkas.general.pojo.progress.WorkWrapper.run(WorkWrapper.java:113)
at java.lang.Thread.run(Thread.java:745)
Caused by: oracle.sysman.emai.model.bi.ModelException: Failed to start the component
at oracle.sysman.emai.model.bi.mbean.AvailabilityAssistant.processComponent(AvailabilityAssistant.java:1111)
at oracle.sysman.emai.model.bi.mbean.AvailabilityAssistant.startComponent(AvailabilityAssistant.java:967)
at oracle.sysman.emai.view.bi.AvailabilityView.startComponent(AvailabilityView.java:876)
... 6 more
|