Exitcode -11113

[Former Member]

Hello,

I had tried to configurate a datasource with the admintool but after a restart the J2EE Server does not start up. Has anyone an idea how I can fix this?

Here is a summary from the logfile "std_server0.out"

Thanks for help.

-

---

stdout/stderr redirect

-

---

node name : server0

pid : 3700

system name : J2E

system nr. : 00

started at : Tue Jan 17 08:32:24 2006

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude iaik/security/md/SHA a

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...

Loading: LogManager ... 16303 ms.

Loading: PoolManager ... 16 ms.

Loading: ApplicationThreadManager ... 249 ms.

Loading: ThreadManager ... 47 ms.

Loading: IpVerificationManager ... 46 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... 343 ms.

Loading: LockingManager ... 155 ms.

Loading: ConfigurationManager ... 1293 ms.

Loading: LicensingManager ... 62 ms.

Loading: ServiceManager ...

0.000: [GC 0.000: [ParNew: 43519K->2612K(65280K), 0.0438155 secs] 43519K->2612K(502528K), 0.0438913 secs]

Loading services.:

Service memory started. (78 ms).

Service runtimeinfo started. (62 ms).

Service timeout started. (78 ms).

Service cross started. (1153 ms).

Service file started. (343 ms).

Service jmx_notification started. (62 ms).

Service trex.service started. (63 ms).

Service p4 started. (482 ms).

Service classpath_resolver started. (78 ms).

16.142: [GC 16.142: [ParNew: 46132K->4355K(65280K), 0.0294726 secs] 46132K->4355K(502528K), 0.0295444 secs]

Service tc_secwssec~service started. (2663 ms).

Service userstore started. (15 ms).

Service tc_secvsi~service started. (389 ms).

23.743: [GC 23.743: [ParNew: 47875K->6123K(65280K), 0.0277173 secs] 47875K->6123K(502528K), 0.0277743 secs]

Service log_configurator started. (17954 ms).

Service locking started. (46 ms).

Service naming started. (825 ms).

Service ts started. (124 ms).

Service deploy started. (13983 ms).

Service licensing started. (16 ms).

Service appclient started. (109 ms).

Service failover started. (32 ms).

Service jmsconnector started. (47 ms).

Service javamail started. (872 ms).

Service http started. (872 ms).

30.790: [GC 30.790: [ParNew: 49643K->7626K(65280K), 0.0348315 secs] 49643K->7626K(502528K), 0.0348999 secs]

Service apptracing started. (638 ms).

Service connector started. (218 ms).

Service webservices started. (2258 ms).

Service configuration started. (109 ms).

35.111: [GC 35.111: [ParNew: 51146K->8123K(65280K), 0.0309683 secs] 51146K->8123K(502528K), 0.0310251 secs]

Service dbpool started. (5294 ms).

Jan 17, 2006 8:33:56 AM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_15] Fatal: Initialization of UME persistence adapter "PRIVATE_DATASOURCE" failed.

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:60)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:689)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)

... 6 more

com.sap.engine.frame.ServiceException: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:531)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:201)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:60)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

ume.db.connection_pool_type=SAP/BC_UME

ume.db.connection_pool.j2ee.xatransactions_used=FALSE

ume.db.connection_pool.j2ee.is_unicode=FALSE

ume.db.connection_pool.j2ee.oracle_native_driver_used=false: ConnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:689)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:280)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:224)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:528)

... 6 more

[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Jan 17, 2006 8:33:57 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_15] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

-

---

[Former Member]

I am also encountering this error. PLEASE HELP ME! I WILL DEFINITELY AWARD POINTS FOR THOSE WHO WILL HELP ME!

[Former Member]

Hi, check if you have maintained <SID> in global server configuration / services / dbpool

[Former Member]

Hai,

Check you ume.persistance.data_source_configuration in the configtool and also check the diskspace or filesystems space of the /usr/sap/<SID> directory......

Thanks and Regards,

[Former Member]

Hello Jan,

Your solution helped my problem. I want to give points to you but dont know how. many thanks to you.

Regards,

Krishna.

[Former Member]

hi Manuel

Now to change UME Setting do the following step.

Run configtool

<drive:\>\usr\sap\sid\JC<InstanceNumber>\J2EE\

configtool\configtool.bat

Under Clustre Data -> Global Server Configuration -> Services -> com.sap.security.cor.ume.services

Now find the key :- ume.persistence.data_source_configuration

And chnge to default

The default was: - dataSourceConfiguration_database_only.xml

click on set and from file -> apply

Now start the server hope it's works

regards,

kaushal

[Former Member]

Hi manual,

I encountered this problem recently. I applied the Portal License and the problem solved.

Hope this helps.

Rgds,

Hapizorr Rozi Alias

[Former Member]

Hi Manuel,

Looks like you are missing SAP/BC_UME ConnectionFactory in your DB Pool. To fix it, you need to define SAP/BC_UME as an alias for the SAP<SID>DB DataSource in the JDBC Connector service for your J2EE server.

Regards,

Mike

[deidre_logan]

We had the same problem and it was an issue with the number of oracle threads that we had defined. In the log /usr/sap/XC0/D73/j2ee/cluster/bootstrap/system.log we found the error

#1.5#00306E4B487900000000000A00005CAF0004133E736CD3A1#1147058852253#/System/Data

base/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory#######Thread[main,5,main

]##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#co

m.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={

0,number,integer}, state="", message="".#5#20#61000#ORA-00020: maximum num

ber of processes (80) exceeded

the oracle DBA increased the number or oracle threads to 400 and we restarted the Central instance and application server and all came up without issue.