J2EE Engine start problem Exit Code

[Former Member]

Hi all,

I have a problem with the J2EE server initialization: server0 doesn't starts. I've checked the aliases and there isn't any problem. I saw several messages where people could solve it, but they no explain how.

¿Any ideas?

Regards,

Emanuel

This is the log file:

-

-

---

stdout/stderr redirect

-

-

---

node name : server0

pid : 4992

system name : J2E

system nr. : 00

started at : Mon Feb 06 15:03:47 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 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 100627.313 is starting...

Loading: LogManager ... 2937 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 188 ms.

Loading: ThreadManager ... 93 ms.

Loading: IpVerificationManager ... 32 ms.

Loading: ClassLoaderManager ... 125 ms.

Loading: ClusterManager ... 1250 ms.

Loading: LockingManager ... 109 ms.

Loading: ConfigurationManager ...

6531 ms.

Loading: LicensingManager ... 125 ms.

Loading: ServiceManager ...

Loading services.:

Service cross started. (16 ms).

Service memory started. (16 ms).

Service file started. (156 ms).

Service trex.service started. (672 ms).

Service runtimeinfo started. (0 ms).

Service timeout started. (234 ms).

Service userstore started. (110 ms).

Service jmx_notification started. (1515 ms).

Service p4 started. (859 ms).

Service classpath_resolver started. (31 ms).

Service log_configurator started. (11375 ms).

Service locking started. (15 ms).

Service naming started. (1187 ms).

Service appclient started. (688 ms).

Service http started. (1938 ms).

Service failover started. (1047 ms).

Service jmsconnector started. (1219 ms).

Service javamail started. (2531 ms).

Service ts started. (2109 ms).

Service licensing started. (63 ms).

Service connector started. (1688 ms).

Service webservices started. (3125 ms).

Service deploy started. (16110 ms).

Service configuration started. (375 ms).

service MobileSetupGeneration ================= ERROR =================

Service MobileArchiveContainer started. (484 ms).

Service dbpool started. (4172 ms).

Feb 6, 2006 3:04:52 PM (PrincipalDatabagFactoryInstance.java:283)

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

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

... 6 more

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

Feb 6, 2006 3:04:52 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_19] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

-

-

---

stdout/stderr redirect

-

-

---

node name : server0

pid : 4992

system name : J2E

system nr. : 00

started at : Mon Feb 06 15:04:54 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 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 100627.313 is starting...

Loading: LogManager ... 1093 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 187 ms.

Loading: ThreadManager ... 31 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 47 ms.

Loading: ClusterManager ... 297 ms.

Loading: LockingManager ... 156 ms.

Loading: ConfigurationManager ...

4609 ms.

Loading: LicensingManager ... 47 ms.

Loading: ServiceManager ...

Loading services.:

Service memory started. (31 ms).

Service cross started. (47 ms).

Service file started. (266 ms).

Service runtimeinfo started. (234 ms).

Service trex.service started. (500 ms).

Service userstore started. (157 ms).

Service timeout started. (265 ms).

Service p4 started. (625 ms).

Service classpath_resolver started. (47 ms).

Service jmx_notification started. (4188 ms).

Service log_configurator started. (12968 ms).

Service locking started. (15 ms).

Service naming started. (1250 ms).

Service appclient started. (344 ms).

Service failover started. (469 ms).

Service javamail started. (672 ms).

Service jmsconnector started. (641 ms).

Service http started. (2000 ms).

Service deploy started. (14172 ms).

Service ts started. (1063 ms).

Service licensing started. (47 ms).

Service connector started. (1188 ms).

Service configuration started. (313 ms).

service MobileSetupGeneration ================= ERROR =================

Service MobileArchiveContainer started. (234 ms).

Service webservices started. (3172 ms).

Service dbpool started. (4687 ms).

Feb 6, 2006 3:05:36 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_26] 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:573)

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

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

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

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

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

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

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:690)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.(PrincipalDatabagFactoryInstance.java:283)

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

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

... 6 more

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

Feb 6, 2006 3:05:36 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_26] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

-

-

---

stdout/stderr redirect

-

-

---

node name : server0

pid : 4992

system name : J2E

system nr. : 00

started at : Mon Feb 06 15:05:39 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 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 100627.313 is starting...

Loading: LogManager ... 1562 ms.

Loading: PoolManager ... 16 ms.

Loading: ApplicationThreadManager ... 219 ms.

Loading: ThreadManager ... 31 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 46 ms.

Loading: ClusterManager ... 797 ms.

Loading: LockingManager ... 235 ms.

Loading: ConfigurationManager ...

3609 ms.

Loading: LicensingManager ... 31 ms.

Loading: ServiceManager ...

Loading services.:

Service memory started. (32 ms).

Service cross started. (453 ms).

Service file started. (531 ms).

Service runtimeinfo started. (297 ms).

Service timeout started. (375 ms).

Service trex.service started. (828 ms).

Service userstore started. (109 ms).

Service p4 started. (797 ms).

Service classpath_resolver started. (31 ms).

Service jmx_notification started. (4954 ms).

Service log_configurator started. (10203 ms).

Service locking started. (32 ms).

Service naming started. (1281 ms).

Service appclient started. (328 ms).

Service javamail started. (625 ms).

Service failover started. (500 ms).

Service jmsconnector started. (812 ms).

Service http started. (2250 ms).

Service ts started. (1141 ms).

Service licensing started. (15 ms).

Service connector started. (906 ms).

Service webservices started. (2688 ms).

Service deploy started. (13516 ms).

Service configuration started. (78 ms).

Service MobileArchiveContainer started. (813 ms).

service MobileSetupGeneration ================= ERROR =================

Service dbpool started. (5734 ms).

Feb 6, 2006 3:06:20 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_27] 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:573)

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

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

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

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

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

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

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:690)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.(PrincipalDatabagFactoryInstance.java:283)

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

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

... 6 more

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

Feb 6, 2006 3:06:20 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_27] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

-

-

---

stdout/stderr redirect

-

-

---

node name : server0

pid : 4992

system name : J2E

system nr. : 00

started at : Mon Feb 06 15:06:22 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 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 100627.313 is starting...

Loading: LogManager ... 1219 ms.

Loading: PoolManager ... 0 ms.

Loading: ApplicationThreadManager ... 266 ms.

Loading: ThreadManager ... 31 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ClassLoaderManager ... 31 ms.

Loading: ClusterManager ... 359 ms.

Loading: LockingManager ... 610 ms.

Loading: ConfigurationManager ...

4625 ms.

Loading: LicensingManager ... 47 ms.

Loading: ServiceManager ...

Loading services.:

Service runtimeinfo started. (93 ms).

Service cross started. (625 ms).

Service file started. (641 ms).

Service memory started. (703 ms).

Service trex.service started. (672 ms).

Service timeout started. (407 ms).

Service userstore started. (140 ms).

Service p4 started. (625 ms).

Service classpath_resolver started. (15 ms).

Service jmx_notification started. (2985 ms).

Service log_configurator started. (12203 ms).

Service locking started. (32 ms).

Service naming started. (2391 ms).

Service appclient started. (531 ms).

Service failover started. (547 ms).

Service http started. (3282 ms).

Service javamail started. (969 ms).

Service jmsconnector started. (1094 ms).

Service ts started. (1407 ms).

Service licensing started. (172 ms).

Service deploy started. (15641 ms).

Service connector started. (1719 ms).

Service configuration started. (313 ms).

Service MobileArchiveContainer started. (266 ms).

service MobileSetupGeneration ================= ERROR =================

Service webservices started. (3891 ms).

Service dbpool started. (4203 ms).

Feb 6, 2006 3:07:04 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_26] 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:573)

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

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

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

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

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

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

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:690)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.(PrincipalDatabagFactoryInstance.java:283)

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

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

... 6 more

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

Feb 6, 2006 3:07:04 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_26] Fatal: Critical shutdown was invoked.

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

Reserved 1610612736 (0x60000000) bytes before loading DLLs.

[Former Member · Accepted solution]

Hi,

Please check if there's a problem is with the database.

Check for any SQL exceptions like max no. of work

processes exceeded.

Also check the datasource name.

Hope it helps.

Regards

Srikishan

[Former Member · Accepted solution]

Hi!,

Thanks for the answers. There is no problem with aliases, and because of I'm working with SP15, the notes doesn't apply. I forgot mention that.

How I check for SQL exceptions?

Any other idea?

Thanks a lot!,

Emanuel

[deidre_logan · Accepted solution]

We have the same error when trying to install a dialog Abap + Java addin server. We are on support pack 14.

here is a portion of the log file std_server1.out

Service dbpool started. (2070 ms).

Feb 8, 2006 1:50:39 PM com.sap.security.core.persistence [SAPEngine_Sys

tem_Thread[impl:5]_48] 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 sta

rted.

com.sap.engine.frame.ServiceException: ConnectionFactory "SAP/BC_UME" does not e

xist. 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: ConnectionF

actory "SAP/BC_UME" does not exist. Possible reasons: the connector in which Con

nectionFactory "SAP/BC_UME" is defined is not deployed or not started.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMESer

viceFrame.java:573)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAd

aptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicati

onServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRun

ner.java:142)

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

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.ja

va:74)

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

41)

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Co

nnectionFactory "SAP/BC_UME" does not exist. Possible reasons: the connector in

which ConnectionFactory "SAP/BC_UME" is defined is not deployed or not started.

any insight on how to correct the issue. We have the Central instance up and running with the java addin server. This is an SAP XI system.

Thanks,

Dede

[Former Member · Accepted solution]

hi ,

The problem with the sevlet enging i guess, better you install and configure the Tomcat server or any other server.

Security Issues

Several security issues affect X server, including:

General issues of program security

Access to the display device

Access to the X server itself

go thru this link , sure it helps you

http://developers.sun.com/solaris/articles/solaris_graphics.html

Thanks

Varun

[Former Member · Accepted solution]

Thanks all for answer. The problem is that you need a Fully Qualified Domain Name to access portal. For more information, see SAP Note 654982.

Thaks all,

Emanuel

[deidre_logan · Accepted solution]

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.

[Former Member]

Hi Emanuel

I think this problem occured when u tried to create a new datasource in visual admin. If its so then,

It was caused by a missing SAP/BC_UME ConnectionFactory in the DB Pool. To fix it, you need to define SAP/BC_UME as an alias for the SAPDB DataSource in the JDBC Connector service for your J2EE server.

For this,

Open the configtool (\usr\sap\IN<no>\JC00\j2ee\configtool\configtool.bat).

In the configtool select dbpool.

Set the sysDSaliases to the default value, SAP/bc_UME.

Restart the engine.

Hope it works for u.

Regards

Sasha.

[Former Member]

hi Emanuel,

Check these SAP Notes 795362 & 685230. This might help you to solve the problem.

Regards

Arun