11g Managed Server bi_server1 Fails To Start With Error "java.lang.OutOfMemoryError: PermGen Space" In bi_server1.log File - Need To Increase The Java Heap Size (Doc ID 1622182.1)

Last updated on OCTOBER 03, 2016

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.6.12 and later
Information in this document applies to any platform.

Symptoms

Upgrading OBIEE  from 11.1.1.6.12 version to 11.1.1.7.1.

After running Start BI Services, found managed server bi_server1 failed to start in Weblogic Console, when attempting to bi_server1 from weblogic console,
the following error occurs.

ERROR
-----------------------

See the following error:
####<Feb 3, 2014 7:39:13 PM EST> <Error> <JMX> <SVR-BI-PROD> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1391474353548> <BEA-149501> <An exception occurred while registering the MBean com.bea:Name=AdminServer,Type=WebServiceBuffering,Server=AdminServer,WebService=AdminServer at property WebServiceRequestBufferingQueue.
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:295)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.management.provider.internal.BeanInfoAccessImpl$BeanInfoFactoryList.loadBeanInfoFactory(BeanInfoAccessImpl.java:564)
at weblogic.management.provider.internal.BeanInfoAccessImpl$BeanInfoFactoryList.loadBeanInfoFactories(BeanInfoAccessImpl.java:546)
at weblogic.management.provider.internal.BeanInfoAccessImpl$BeanInfoFactoryList.getFactories(BeanInfoAccessImpl.java:527)
at weblogic.management.provider.internal.BeanInfoAccessImpl$BeanInterfaceClasses.load(BeanInfoAccessImpl.java:626)
at weblogic.management.provider.internal.BeanInfoAccessImpl$BeanInterfaceClasses.initialize(BeanInfoAccessImpl.java:621)
at weblogic.management.provider.internal.BeanInfoAccessImpl$BeanInterfaceClasses.contains(BeanInfoAccessImpl.java:589)
at weblogic.management.provider.internal.BeanInfoAccessImpl.hasBeanInfo(BeanInfoAccessImpl.java:198)
at weblogic.management.mbeanservers.internal.WLSObjectNameManager.isClassMapped(WLSObjectNameManager.java:85)
at weblogic.management.jmx.modelmbean.WLSModelMBeanContext.isContainedBean(WLSModelMBeanContext.java:220)
at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:140)
at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:166)
at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:166)
at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:166)
at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:153)
at weblogic.management.mbeanservers.runtime.internal.RuntimeServerService.registerAllMBeans(RuntimeServerService.java:220)
at weblogic.management.mbeanservers.runtime.internal.RuntimeServerService.access$100(RuntimeServerService.java:45)
at weblogic.management.mbeanservers.runtime.internal.RuntimeServerService$1$1$1.run(RuntimeServerService.java:240)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. run start BI Services
2. Login to weblogic console, seen Admin Server is in running status, but bi_server is in starting status and stays in this status
3. stop bi_server1 from console, then start it again, found above error in bi_server1.log, and status stays in STARTING again.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get BIEE login screen

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms