I'm upgrading all our databases to 11.3.2 (windows) The problem is that when the adminserver has a java out of memory issue, i have to restart the adminservice with the -keepservers option. After that all database are running unmanaged. I was hoping that the databases would reregister themself with the adminservice, but that doesn't happen. Is there a way to force a re-register? Or is there a parameter that influences this re-registering? The real problem ofcourse is the adminservice running out of memory. I'm hoping the serviceack 11.3.3 brings some stability. (I have oem installed.)
Did you increase -Xmx in AdminSeverplugin.properties? This is a must for OEM and the more resources you monitor the higher it should be. 1024m is a good start.
Please talk to tech support and make sure you have the hotfix for PSC00285790 for 11.3.2. In the meantime you can edit $DLC/properties/management.properties and set allowDiscovery = false. There is a memory leak that has been present forever that only occurs due to a race which can be triggered by the internal eventing caused by this feature. This won't fix the issue, but it normally alleviates it until you can install the hotfix.
And do increase the default memory size as suggested by Paul, since the defaults are fairly conservative
Please talk to tech support and make sure you have the hotfix for PSC00285790 for 11.3.2. In the meantime you can edit $DLC/properties/management.properties and set allowDiscovery = false. This won't fix the issue without the hotfix, but it normally alleviates it until you can install the hotfix.
Flag this post as spam/abuse.
FYI: the "-keepservers option" is for stopping the adminserver not starting it
it's to allow any ubrokers currently running to remain running when the adminserver is stopped:
proadsv -stop -keepservers
Then re-register (the same way databases 'should' do) when the adminserver is restarted.
You mention that the databases don't re-register, what about the running ubrokers .. do they remain running and re-register when the adminserver is restarted?
Once you have the HF mentioned above, let the support engineer know if the problem persists.
FYI: the "-keepservers option" is for stopping the adminserver not starting it
it's to allow any ubrokers currently running to remain running when the adminserver is stopped:
proadsv -stop -keepservers
Then re-register (the same way databases 'should' do) when the adminserver is restarted.
You mention that the databases don't re-register, what about the running ubrokers .. do they remain running and re-register when the adminserver is restarted?
Once you have the HF mentioned above, let the support engineer know if the problem persists.
Flag this post as spam/abuse.