Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBIEE managed server not starting

llo All,
We have manually stopped it once and after that it is not starting ..... Failed when we tried to start from console.
when we trid to start
Erro Message in Biserver1
[2017-08-20T09:40:15.620+03:00] [bi_server1] [ERROR] [WSM-02313] [oracle.wsm.resources.policymanager] [tid: [STANDBY].ExecuteThread: '37' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 49c292fc-1154-4acb-8468-9b8302a9ecfd-00000333,0] [APP: bicomposer] [partition-name: DOMAIN] [tenant-name: GLOBAL] The documents used by a policy subject cannot be recorded due to underlying error "Exception during invoke."[[
java.rmi.NoSuchObjectException: Exception during invoke.
Answers
-
May be is it due to the order of startup?
Should i start the managed server before Nodemanagers and other servers?
0 -
Hi,
What version are you talking about?
If it's 12c (that's my guess at least) you must not start things randomly by hand, you have a start.sh and stop.sh script provided which make everything in the right order. And talking about the order if you look at the script it's nodemanager, weblogic admin server, weblogic managed server, obiee services.
0 -
its 12c. starting in admin mode ...
Error messages in managed server log.
0 -
Hi,
The error screenshot you provided was it found in bi_server1.log?
Thanks & Regards,
RCB
0 -
Yes. My managed server name is Bi_Server1
0 -
Was there any changes performed related to HTTP/HTTPS for managed server as there are couple of known issue related to same error as yours, check below KM documents for more information on same.
OBIEE 12c: After Disabling SSL For Internal Communications The Managed Server does Not Start (Doc ID 2191153.1)
OBIEE 12c: After Implementing SSL In a Clustered Environment, The Managed Server Fails To Start with Error: java.lang.AssertionError: No replication server channel for bi_server1 (Doc ID 2287661.1)
0 -
Tried configuring SSL few weeks ago, and reverted the changes. Dont have access to those support docs it seems.
0 -
Now since you don't have SSL configured anymore, Just Login into console and make sure SSL is disabled for Admin Server(AdminServer), Managed Server(bi_server1) and then disable Replication for Managed Server.
Follow below steps and see if it helps resolve your issue:
a. Stop BIEE Services(obips1,obis1,obiccs1,obisch1,obijh1) and Managed Server(bi_server1) but keep Admin Server UP and RUNNING.
You can do the same executing below command from command console(Putty etc..) from following location <DOMAIN_HOME>\bitools\bin
./stop.sh -i obis1,obiccs1,obips1,obisch1,obijh1,bi_server1
b. Next from following location <DOMAIN_HOME>\config backup file named config.xml, this will help you restore back to previous configuration in case below steps result into some issue.
c. Login to WebLogic Admin console.d. Click Lock and Edit.
e. Select Environment-->Servers.For each server(AdminServer and bi_server1) one after the another:
f. On the main Configuration tab, make sure SSL Listen Port Enabled is unchecked and non-SSL Listen Port Enabled is checked
g. Click Save.
Do not Activate Changes yet , make another change related to Managed Server(bi_server1):
h. Select Environment, Clusters, and bi_cluster.
i. Select Configuration, and the Replication tab. '
j. Uncheck the option secure replication enabled.
If you do not do this, the managed servers will fail to startup, remaining in admin mode. This prevents the start scripts from running.
k. Click Save.
l. Now under change center click Activate Changes.
m. Now stop Admin Server
You can do the same executing below command from command console(Putty etc..) from following location <DOMAIN_HOME>\bitools\bin
./stop.sh -i AdminServer
n. Now start your server and services back.
You can do the same executing below command from command console(Putty etc..) from following location <DOMAIN_HOME>\bitools\bin
./start.sh
0 -
Let me check and will update the progress. Anyway thanks alot.
0 -
Now other servers are not starting
Error message seems to socket already in use.
0