com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnec tion(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.

masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:05:988#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060550000309A#8263150000000492#redwood.com

/scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:05:988#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060560000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:05:988#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060580000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:05:988#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000605A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:05:988#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000605B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678)

at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:05:989#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000605C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:05:989#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000605E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no

t enough for current load.# #2.0 #2013 06 08 18:03:05:989#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060600000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:05:989#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060610000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:104#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060630000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:104#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060640000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION]

com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio

n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060650000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti

ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060680000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000606A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000606B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a

pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000606C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:105#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc

eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000606E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:106#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060700000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:106#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060710000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL

ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:125#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002300000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain##

Attempting recovery# #2.0 #2013 06 08 18:03:06:125#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C019300 0002320000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers] #Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:138#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0193000002340000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSer ver: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:138#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0193000002350000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Application ServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU

serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getMonitorNodeIn tByParentName(BaseSchedulerSessionImpl.java:18412) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.getSapMo nitorRoot(MonitorUtils.java:188) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:227) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:219) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.updateAppServerInfo(ApplicationServerLoadMonitori ngComponent.java:237) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:231) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 35 more # #2.0 #2013 06 08 18:03:06:138#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0193000002360000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Applic ationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:139#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002370000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions.

BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:139#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0193000002390000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationSer verLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:139#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01930000023B0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringC omponent for PI1 \#16,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:06:139#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01930000023C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getMonitorNodeIn

tByParentName(BaseSchedulerSessionImpl.java:18412) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.getSapMo nitorRoot(MonitorUtils.java:188) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:227) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:219) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.updateAppServerInfo(ApplicationServerLoadMonitori ngComponent.java:237) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:231) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 28 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 31 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152)

... 32 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 35 more # #2.0 #2013 06 08 18:03:06:140#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01930000023D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:140#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR

H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C01930000023F0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMon itoringComponent for PI1 \#16,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:140#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002400000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:06:140#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0193000002420000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringCo mponent for PI1 \#16,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:06:221#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060730000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus

ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:221#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060740000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)

at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:221#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060750000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:221#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060760000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get

Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060780000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000607A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000607B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000607C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007

e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000607E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060800000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#

#2.0 #2013 06 08 18:03:06:222#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060810000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load.

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:337#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060830000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:337#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060840000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460)

at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:337#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060850000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress

.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060880000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java

x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000608A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000608B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load.

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000608C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000608E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu

m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060900000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060910000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached

. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:454#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060930000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:454#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060940000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS

ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:454#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060950000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:454#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:454#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060980000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n##

SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:455#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000609A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:455#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000609B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU

serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000609C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000609E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo

d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060A00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met

hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284)

at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:473#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:473#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve

ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:473#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018400 0005230000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:473#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018500 0005230000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI _ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:487#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0184000005250000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSer ver: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:487#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0184000005260000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchr onizerComponent for PI1 \#17,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:06:487#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0184000005270000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventS ynchronizerComponent for PI1 \#17,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:487#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005280000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions.

BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:487#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C01840000052A0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchroni zerComponent for PI1 \#17,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:488#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01840000052C0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for P I1 \#17,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:06:488#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01840000052D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB

yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 25 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 28 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 29 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:06:488#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01840000052E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:488#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0184000005300000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerCompone nt for PI1 \#17,5,Workers]#Plain##

Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:488#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0184000005330000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for PI 1 \#17,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0185000005250000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0185000005260000309A#8263150000000492#

redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchr onizerComponent for PBI \#1b,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0185000005270000309A#8263150000000492#redwood.com

/scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventS ynchronizerComponent for PBI \#1b,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005280000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C01850000052A0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchroni zerComponent for PBI \#1b,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01850000052C0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for P BI \#1b,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:489#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01850000052D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR

ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 25 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:221) ... 28 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 29 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:06:490#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01850000052E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba

d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:490#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0185000005300000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerCompone nt for PBI \#1b,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:490#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:06:490#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0185000005330000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for PB

I \#1b,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:06:570#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060A30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:570#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060A40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:570#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060A50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .#

#2.0 #2013 06 08 18:03:06:570#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060A60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060A80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000060AA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060AB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060AC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000060AE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong

or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060B00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:571#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060B10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne

ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060B30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060B40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261)

... 15 more # #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060B50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060B60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060B80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000060BA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:686#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060BB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:687#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060BC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:687#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000060BE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock

PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:687#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060C00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:687#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason

s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139)

at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060C30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060C40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05

111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060C50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060C80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000060CA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:802#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060CB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2)

Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139)

at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:803#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 18:03:06:803#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000060CE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:803#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060D00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:803#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060D10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti

on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E

xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:06:815#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0183000000140000309A#8 263150000001327##com.sap.sql.connect.datasource.DBDataSourceImpl####9D0B8A31D051 11E28FB80050568C5F4A#9d0b8a31d05111e28fb80050568c5f4a#9d0b8a31d05111e28fb8005056 8c5f4a#0#Thread[Timer-4,5,SystemThreadGroup]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:815#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0183000000150000309A#8263150000001327# #com.sap.sql.connect.datasource.DBDataSourceImpl####9D0B8A31D05111E28FB80050568C 5F4A#9d0b8a31d05111e28fb80050568c5f4a#9d0b8a31d05111e28fb80050568c5f4a#0#Thread[ Timer-4,5,SystemThreadGroup]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:295) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.sap.uddi.helpers.database.util.UDDIDbUtil.getConnection(UDDIDbUti l.java:135) at com.sap.uddi.sql.SqlDatabase.myGetTransaction(SqlDatabase.java:297) at com.sap.uddi.sql.SqlDatabase.getTransactionAtIsolationLevel(SqlDataba se.java:309) at com.sap.uddi.server.STRunnable$Starter.run(STRunnable.java:409) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505)

at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 13 more # #2.0 #2013 06 08 18:03:06:815#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0183000000160000309A#8263150000001327##com.sap.en gine.services.dbpool.spi.ManagedConnectionFactoryImpl####9D0B8A31D05111E28FB8005 0568C5F4A#9d0b8a31d05111e28fb80050568c5f4a#9d0b8a31d05111e28fb80050568c5f4a#0#Th read[Timer-4,5,SystemThreadGroup]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:815#0-700#Fatal#com.sap.uddi.helpers.database.util.UDDID bUtil# #BC-ESI-UDDI#tc~esi~uddi~server~core~service#C0000ADCD98C0183000000170000309A#82 63150000001327##com.sap.uddi.helpers.database.util.UDDIDbUtil####9D0B8A31D05111E 28FB80050568C5F4A#9d0b8a31d05111e28fb80050568c5f4a#9d0b8a31d05111e28fb80050568c5 f4a#0#Thread[Timer-4,5,SystemThreadGroup]#Plain## Fatal Error trying to get a connection from datasource: null [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.sap.uddi.helpers.database.util.UDDIDbUtil.getConnection(UDDIDbUti l.java:135)

at com.sap.uddi.sql.SqlDatabase.myGetTransaction(SqlDatabase.java:297) at com.sap.uddi.sql.SqlDatabase.getTransactionAtIsolationLevel(SqlDataba se.java:309) at com.sap.uddi.server.STRunnable$Starter.run(STRunnable.java:409) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:295) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 6 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 9 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 10 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 13 more # #2.0 #2013 06 08 18:03:06:823#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004D40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:823#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004700 0004D60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:836#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0047000004D80000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:836#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0047000004D90000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH SUX17 \#9,5,Workers]#Plain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155)

at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate

.java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:06:837#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0047000004DA0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHSUX17 \#9,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:837#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:06:837#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0047000004DD0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX 17 \#9,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:837#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0047000004DF0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]# Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:837#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004E00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#

abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess

age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:06:838#0-700#Error#com.redwood.scheduler.persistence.recove

ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:838#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0047000004E30000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,W orkers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:838#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004E40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28# #2.0 #2013 06 08 18:03:06:838#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28#XX-PART-REDWOOD#redwood.com/s

cheduler-ear#C0000ADCD98C0047000004E60000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#P lain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28# #2.0 #2013 06 08 18:03:06:918#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060D30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:06:918#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060D40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97)

at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:918#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060D50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty

pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:918#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060D60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:918#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060D80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:919#0-700#Error#com.redwood.scheduler.persistence.persis

tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000060DA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:919#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re

solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:919#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060DC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:919#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000060DE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:06:919#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect

ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060E00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:06:919#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc

e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:06:922#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004D30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:922#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C00 0004D50000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI _ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:935#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018C000004D70000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..#

#2.0 #2013 06 08 18:03:06:935#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018C000004D80000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitori ngComponent for PBI \#18,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper.

wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo

rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:06:935#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018C000004D90000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMon itoringComponent for PBI \#18,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:06:935#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004DA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:936#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect

ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018C000004DC0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringC omponent for PBI \#18,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:936#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018C000004DE0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \ #18,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:936#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004DF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load.

[EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82)

at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 34 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 37 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 38 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:06:936#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004E00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:937#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018C000004E20000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0

5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent f or PBI \#18,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:06:937#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004E30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28# #2.0 #2013 06 08 18:03:06:937#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018C000004E50000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \# 18,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28# #2.0 #2013 06 08 18:03:06:987#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:06:987#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00

0004030000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:988#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004A70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:06:988#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004200 0004A90000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:001#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004AB0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:001#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004050000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:002#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004060000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep

tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39)

at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:07:002#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004AC0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH S95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95)

at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:07:002#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0042000004AD0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHS95549 \#3,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:002#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F000004070000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:002#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004080000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:002#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004AE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:003#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F0000040A0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain##

SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:003#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0042000004B00000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95 549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:003#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0042000004B20000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]

#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:003#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F0000040C0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:003#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000040D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare

Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC

onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:07:003#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004B30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper.

wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora

ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000040E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F000004100000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004B40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to

DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=17# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0042000004B60000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5, Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=17#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F000004130000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load.) in 1000ms, index=17# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004B70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=23# #2.0 #2013 06 08 18:03:07:004#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=23#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0042000004B90000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]# Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=23# #2.0 #2013 06 08 18:03:07:034#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060E30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:034#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060E40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo

wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:035#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060E50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:035#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:035#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions.

BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060E80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:035#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000060EA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:035#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060EB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc

curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152)

... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:036#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:036#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock

PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000060EE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:036#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060F00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:036#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c

heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:151#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060F30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS

ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:151#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000060F40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:151#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000060F50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:151#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect

ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:151#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000060F80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:152#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000060FA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:07:152#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060FB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:152#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000060FC0000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:152#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000060FE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:152#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l

oad.# #2.0 #2013 06 08 18:03:07:152#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re

solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:267#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061030000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:267#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061040000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97)

at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:267#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061050000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty

pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061080000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.persistence.persis

tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000610A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000610B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re

solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000610C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000610E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect

ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061100000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:268#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc

e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:384#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061130000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:384#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061140000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.

java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:385#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061150000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:385#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061160000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:385#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061180000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111

e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:385#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000611A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:385#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000611B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto

ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000611C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000611E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch

eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061200000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736)

Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:419#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]# Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:419#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005000 0006430000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.

persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Compone nt \#11,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:432#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0050000006450000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,W orkers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:432#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0050000006460000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR

ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.action.ActionComponent.processMessages(ActionCo mponent.java:219) at com.redwood.scheduler.action.ActionComponent.onMessage(ActionComponen t.java:183) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736)

Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 43 more # #2.0 #2013 06 08 18:03:07:433#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0050000006470000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]#Pla in## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:433#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006480000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Worker s]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:433#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C00500000064A0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:433#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00500000064C0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Action Component \#11,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:433#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00500000064D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Worker s]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460)

at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.action.ActionComponent.processMessages(ActionCo mponent.java:219) at com.redwood.scheduler.action.ActionComponent.onMessage(ActionComponen t.java:183) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 36 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 39 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 40 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 43 more # #2.0 #2013 06 08 18:03:07:434#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00500000064E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover

y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]# Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:434#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0050000006500000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:434#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006510000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]# Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34# #2.0 #2013 06 08 18:03:07:434#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34#XX-PART-REDWOOD#redwood.com/ scheduler-ear#C0000ADCD98C0050000006530000309A#8263150000000492#redwood.com/sche duler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Action Component \#11,5,Workers]#Plain##

Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34# #2.0 #2013 06 08 18:03:07:501#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061230000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:501#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061240000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061250000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061260000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061280000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000612A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000612B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC

onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000612C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:502#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000612E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:503#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l

oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061300000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:503#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:618#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061330000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:618#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061340000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:07:618#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061350000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061380000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000613A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000613B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000613C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000613E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061400000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:619#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note

719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:734#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061430000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:734#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061440000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P

lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:735#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061450000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:735#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061460000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:735#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061480000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:735#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000614A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:735#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000614B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect

ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:736#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000614C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 18:03:07:736#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000614E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:736#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061500000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:736#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061510000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory

Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init

ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:851#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061530000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:851#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061540000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:851#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061550000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061560000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061580000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000615A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000615B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init

ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000615C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000615E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061600000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu

m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:852#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061610000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:920#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01820000052A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:920#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018200 00052C0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:928#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004D20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:928#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D00 0004D40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:07:933#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C01820000052E0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav

a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:933#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C01820000052F0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchr onizerComponent for PC1 \#1f,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re

tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261)

... 32 more # #2.0 #2013 06 08 18:03:07:934#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0182000005300000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventS ynchronizerComponent for PC1 \#1f,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:934#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:934#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0182000005330000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchroni zerComponent for PC1 \#1f,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:934#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0182000005350000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for P C1 \#1f,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:934#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460)

at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 25 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE

xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 28 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 29 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more

# #2.0 #2013 06 08 18:03:07:935#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005370000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:935#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0182000005390000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerCompone nt for PC1 \#1f,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:935#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01820000053A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:07:935#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can

apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01820000053C0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for PC 1 \#1f,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:07:941#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018D000004D60000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:941#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018D000004D70000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitori ngComponent for PC1 \#1c,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor

ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:07:941#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018D000004D80000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMon itoringComponent for PC1 \#1c,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:941#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004D90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:942#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018D000004DB0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringC omponent for PC1 \#1c,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:942#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018D000004DD0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \ #1c,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:942#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004DE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466)

at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 34 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE

xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 37 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 38 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more

# #2.0 #2013 06 08 18:03:07:943#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004DF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:943#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018D000004E10000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent f or PC1 \#1c,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:943#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004E20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28# #2.0 #2013 06 08 18:03:07:943#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can

apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018D000004E40000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \# 1c,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=28# #2.0 #2013 06 08 18:03:07:967#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061630000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:07:967#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061640000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:967#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061650000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone

nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:07:967#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061680000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000616A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000616B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736)

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000616C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000616E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061700000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:07:968#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061710000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116)

... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:007#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004BA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:08:007#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004140000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:08:007#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004200 0004BC0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery#

#2.0 #2013 06 08 18:03:08:007#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 0004160000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:08:021#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004180000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:021#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004190000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect

(OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)

at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:08:021#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F0000041A0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:021#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000041B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get

Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:022#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F0000041D0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:022#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F0000041F0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:022#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004200000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252)

at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152)

... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:08:022#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:023#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR

H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F000004230000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:023#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004240000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=18# #2.0 #2013 06 08 18:03:08:023#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=18#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F000004260000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=18# #2.0 #2013 06 08 18:03:08:029#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004BE0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav

a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:029#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004BF0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH S95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re

tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736)

Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:08:030#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0042000004C00000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHS95549 \#3,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:030#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:030#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0042000004C30000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95 549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:031#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0042000004C50000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers] #Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java

x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:031#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:08:032#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004C70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:032#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0042000004C90000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5, Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:032#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004CA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load.) in 1000ms, index=24# #2.0 #2013 06 08 18:03:08:032#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=24#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0042000004CC0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]# Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=24# #2.0 #2013 06 08 18:03:08:083#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061730000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:083#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061740000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:08:083#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061750000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061760000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061780000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000617A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000617B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000617C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000617E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu

rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061800000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:084#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061810000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E

IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:200#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061830000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:200#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061840000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:200#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061850000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2)

Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061880000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000618A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000618B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load.

[EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000618C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000618E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061900000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:201#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061910000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db

pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:317#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl#

com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061930000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:317#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061940000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:318#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061950000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:318#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:318#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061980000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:318#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000619A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:318#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000619B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:318#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000619C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:319#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000619E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:319#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061A00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in

order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:319#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA

S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37)

at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:378#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers] #Plain## Attempting recovery# #2.0 #2013 06 08 18:03:08:378#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200 0008DD0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Compon ent \#13,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:08:391#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0052000008DF0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5, Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:391#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0052000008E00000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeQuery(Schedul erSessionImpl.java:707) at com.redwood.scheduler.monitor.MonitorComponent.handleLoad(MonitorComp onent.java:818) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:754) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j

ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 30 more # #2.0 #2013 06 08 18:03:08:392#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0052000008E10000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:392#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008E20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Worke rs]#Plain##

SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:392#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0052000008E40000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:392#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0052000008E60000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java

x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:392#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008E70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Worke rs]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeQuery(Schedul erSessionImpl.java:707) at com.redwood.scheduler.monitor.MonitorComponent.handleLoad(MonitorComp onent.java:818) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:754) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 23 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 26 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 27 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at at at at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica

te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 30 more # #2.0 #2013 06 08 18:03:08:393#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008E80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers] #Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:393#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0052000008EA0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain##

Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:393#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008EB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers] #Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34# #2.0 #2013 06 08 18:03:08:393#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34#XX-PART-REDWOOD#redwood.com/ scheduler-ear#C0000ADCD98C0052000008ED0000309A#8263150000000492#redwood.com/sche duler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34# #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061A30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061A40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest#

0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061A50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061A60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061A80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000061AA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:434#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061AB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS

ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:435#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061AC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no

t enough for current load.# #2.0 #2013 06 08 18:03:08:435#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000061AE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:435#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061B00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:435#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061B10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo

d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE

xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:08:550#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061B30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:550#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061B40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49)

at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:550#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061B50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:550#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061B60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc

eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:550#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061B80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:551#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000061BA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java

x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:551#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061BB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE

xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:08:551#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061BC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:551#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000061BE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:551#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061C00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect

ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:551#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo

rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061C30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061C40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo

cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061C50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G

uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061C80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti

ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000061CA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:666#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061CB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster

Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo

rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:667#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:667#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000061CE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 18:03:08:667#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061D00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:667#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061D10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129)

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:782#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061D30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:782#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061D40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep

tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:782#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061D50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:782#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061D60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and

resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061D80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000061DA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur

ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061DC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss

ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000061DE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061E00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:783#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152)

at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061E30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav

a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061E40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061E50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti

ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061E80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000061EA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:08:898#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061EB0000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:08:899#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain##

Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:899#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000061EE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:08:899#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061F00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:08:899#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:014#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061F30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:014#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000061F40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000061F50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .#

#2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000061F80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000061FA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061FB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000061FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000061FE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:015#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong

or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:016#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne

ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:026#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004270000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:09:026#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 0004290000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:09:034#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004CD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:09:034#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004200 0004CF0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain##

Attempting recovery# #2.0 #2013 06 08 18:03:09:040#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F0000042B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:040#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F0000042C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521)

at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:09:040#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F0000042D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:040#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000042E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:041#0-700#Error#com.redwood.scheduler.persistence.persis

tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F000004300000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:041#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F000004320000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:041#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004330000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess

age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)

at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:09:041#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004340000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:041#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F000004360000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000

007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:042#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004370000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=19# #2.0 #2013 06 08 18:03:09:042#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=19#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F000004390000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=19# #2.0 #2013 06 08 18:03:09:047#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004D10000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:047#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004D20000309A#8263150000000492#

redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH S95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at at at at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica

te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:09:047#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0042000004D30000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHS95549 \#3,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:047#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004D40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:047#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0042000004D60000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95 549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:048#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0042000004D80000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers] #Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:048#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004D90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag

(BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more

Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more

# #2.0 #2013 06 08 18:03:09:048#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004DA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:049#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0042000004DC0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5, Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:049#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004DD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=25# #2.0 #2013 06 08 18:03:09:049#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P

ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=25#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0042000004DF0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]# Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=25# #2.0 #2013 06 08 18:03:09:131#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062030000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:131#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062040000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54)

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:131#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062050000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e

84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:131#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:131#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062080000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and

resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:132#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000620A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:132#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000620B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49)

at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:132#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000620C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:132#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000620E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 18:03:09:132#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062100000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:132#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL

ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:247#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062130000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:247#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062140000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062150000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062160000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062180000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000621A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000621B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000621C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:248#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app

ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000621E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:249#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062200000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:249#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005470000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Worke rs]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:09:249#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti

on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E

xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:09:249#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018600 0005490000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor U pdater \#10,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:09:262#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C01860000054B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10 ,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:262#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C01860000054C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plai n## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:195) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.rethrowException(OuterPersistenceUnitOfWorkManager.java:91) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:43) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:37) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.core.CoreMonitorUpdater.onMessage(CoreMonitorUp dater.java:175) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 28 more # #2.0 #2013 06 08 18:03:09:263#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C01860000054D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:263#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000054E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Wo rkers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:263#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and

resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0186000005500000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:263#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0186000005520000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:263#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005530000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Wo rkers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:195) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.rethrowException(OuterPersistenceUnitOfWorkManager.java:91) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:43) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:37) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.core.CoreMonitorUpdater.onMessage(CoreMonitorUp dater.java:175) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 21 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E

xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 24 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 25 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 28 more #

#2.0 #2013 06 08 18:03:09:264#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005540000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Worke rs]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:264#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0186000005560000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:264#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005570000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Worke rs]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34# #2.0 #2013 06 08 18:03:09:264#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load.) in 60000ms, index=34#XX-PART-REDWOOD#redwood.com/ scheduler-ear#C0000ADCD98C0186000005590000309A#8263150000000492#redwood.com/sche duler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 60000ms, index=34# #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062230000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062240000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97)

at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062250000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty

pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062260000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062280000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.redwood.scheduler.persistence.persis

tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000622A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:364#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000622B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re

solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:365#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000622C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:365#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000622E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:365#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect

ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062300000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:365#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc

e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:480#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062330000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:480#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062340000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.

java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062350000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062380000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111

e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000623A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000623B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto

ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000623C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:481#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000623E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch

eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:482#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062400000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:482#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736)

Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:597#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062430000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:597#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062440000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:597#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062450000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:597#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062460000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.persistence.persis

tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062480000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000624A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000624B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc

eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000624C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss

ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000624E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062500000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:598#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062510000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain##

Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261)

... 15 more # #2.0 #2013 06 08 18:03:09:713#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062530000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:713#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062540000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration(

ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:714#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062550000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:714#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062560000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#

abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:714#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062580000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:714#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000625A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB

E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:714#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000625B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261)

... 15 more # #2.0 #2013 06 08 18:03:09:714#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000625C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:715#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000625E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:715#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062600000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5

,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:715#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062610000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97)

at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:830#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062630000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:830#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062640000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:831#0-700#Error#com.sap.engine.services.dbpool.spi.Manag

edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062650000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:831#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:831#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062680000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions.

BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:831#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000626A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:831#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000626B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116)

at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:831#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000626C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:832#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000626E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app

ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:832#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062700000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:832#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062710000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more

Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062730000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062740000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress

.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062750000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062760000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get

Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062780000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000627A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:09:948#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000627B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE

xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more

Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:09:949#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000627C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:949#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000627E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:09:949#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062800000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:09:949#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062810000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS

is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:044#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000043A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba

d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:10:044#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 00043C0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:052#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004E00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:052#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004200 0004E20000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:058#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F0000043E0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:059#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F0000043F0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.

java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess

age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:10:059#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F000004400000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain#

# ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:059#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:059#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F000004430000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:10:059#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F000004450000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:060#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004460000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE

xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more

# #2.0 #2013 06 08 18:03:10:060#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004470000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:060#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F000004490000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:060#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000044A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=20# #2.0 #2013 06 08 18:03:10:060#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu

ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=20#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F0000044C0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=20# #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062830000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062840000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto

ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062850000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi

le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062880000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:10:064#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004E40000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000628A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000628B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:064#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004E50000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH S95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41)

at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more #

#2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000628C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0042000004E60000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHS95549 \#3,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000628E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004E70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist

ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062900000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0042000004E90000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95 549 \#3,5,Workers]#Plain##

SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062910000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0042000004EB0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers] #Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:065#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION]

com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept

ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:10:066#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004ED0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to

DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:066#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0042000004EF0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5, Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:067#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004F00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=26# #2.0 #2013 06 08 18:03:10:067#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=26#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0042000004F20000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]# Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu

ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=26# #2.0 #2013 06 08 18:03:10:180#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062930000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:180#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062940000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678)

at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:180#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062950000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C

omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062980000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000629A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee

#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000629B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000629C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000629E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062A00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain##

com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:181#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU

serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062A30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062A40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC

onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl#

#BC-JAS-TRH#dbpool#C0000ADCD98C0034000062A50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062A60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062A80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get

Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000062AA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:298#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062AB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration(

ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:299#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062AC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:299#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000062AE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat

ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:299#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062B00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:299#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062B10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:414#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062B30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:414#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062B40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..

[EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37)

at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:414#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062B50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062B60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062B80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000062BA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062BB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po

ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062BC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu

rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000062BE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062C00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:415#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:531#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062C30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus

ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:531#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062C40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)

at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:531#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062C50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:531#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get

Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062C80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000062CA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062CB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007

e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000062CE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062D00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#

#2.0 #2013 06 08 18:03:10:532#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062D10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load.

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:600#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Job MonitoringComponent for PI1 \#14,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:600#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B00 0004E80000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:613#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018B000004EA0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSer ver: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:613#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018B000004EB0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMonitori ngComponent for PI1 \#14,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284)

at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54)

at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:10:614#0-700#Error#com.sap.engine.services.dbpool.spi.Manag

edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018B000004EC0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMon itoringComponent for PI1 \#14,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:614#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004ED0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:614#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018B000004EF0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringC omponent for PI1 \#14,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions.

BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:614#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018B000004F10000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \ #14,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:614#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004F20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare

Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections

to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 34 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 37 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 38 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio

n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:10:615#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004F30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Job MonitoringComponent for PI1 \#14,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:615#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018B000004F50000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent f or PI1 \#14,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:615#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Job MonitoringComponent for PI1 \#14,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o

ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:10:615#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018B000004F80000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \# 14,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:10:635#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX05 \#7,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:635#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004600 0005230000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062D30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062D40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062D50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062D60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.redwood.scheduler.persistence.persis

tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062D80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000062DA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:648#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc

eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:649#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062DC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss

ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:649#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000062DE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:649#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062E00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:649#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0046000005250000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:649#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:649#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0046000005260000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH SUX05 \#7,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR

ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler.

handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:10:650#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0046000005270000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHSUX05 \#7,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or

shutdown in progress .# #2.0 #2013 06 08 18:03:10:650#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005280000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:650#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C00460000052A0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX 05 \#7,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:650#0-700#Error#com.redwood.scheduler.persistence.persis tence#

ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00460000052C0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]# Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:650#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00460000052D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91)

at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:10:651#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00460000052E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX05 \#7,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:651#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0046000005300000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,W orkers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:651#0-700#Error#com.redwood.scheduler.persistence.recove

ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX05 \#7,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:10:651#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0046000005330000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#P lain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=32# #2.0 #2013 06 08 18:03:10:764#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062E30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:764#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062E40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION]

com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio

n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062E50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti

ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062E80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000062EA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062EB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a

pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc

eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000062EE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:765#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062F00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:766#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL

ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:881#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062F30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:881#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000062F40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at at at at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica

te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:881#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000062F50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:10:881#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:881#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000062F80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:882#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000062FA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:882#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062FB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:882#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000062FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu

ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:882#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000062FE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:882#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:882#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:997#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063030000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:10:997#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063040000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:997#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063050000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .#

#2.0 #2013 06 08 18:03:10:997#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063080000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c

reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000630A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000630B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000630C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000630E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in

order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063100000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:10:998#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks.

2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate

.java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:062#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000044D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:11:062#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 00044F0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:070#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004F30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:070#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004200 0004F50000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent

Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:075#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004510000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:075#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004520000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ

uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:11:076#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F000004530000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:076#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004540000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:11:076#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F000004560000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:076#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F000004580000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:076#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004590000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc

eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100)

at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:11:077#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000045A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:077#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F0000045C0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0

5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:077#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000045D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=21# #2.0 #2013 06 08 18:03:11:077#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=21#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F0000045F0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=21# #2.0 #2013 06 08 18:03:11:082#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004F70000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:082#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl#

#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0042000004F80000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH S95549 \#3,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana

ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)

at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:11:083#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0042000004F90000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHS95549 \#3,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:083#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004FA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get

Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:083#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0042000004FC0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95 549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:083#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0042000004FE0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers] #Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 18:03:11:083#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000004FF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404)

at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more

# #2.0 #2013 06 08 18:03:11:084#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000005000000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:084#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0042000005020000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5, Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:084#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000005030000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=27# #2.0 #2013 06 08 18:03:11:084#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource

Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=27#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0042000005050000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]# Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=27# #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063130000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063140000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo

cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063150000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G

uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063160000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063180000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti

ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000631A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:113#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000631B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster

Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo

rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:114#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000631C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:114#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000631E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 18:03:11:114#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063200000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:114#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129)

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:142#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002430000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:142#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C019300 0002450000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers] #Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:155#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0193000002470000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSer

ver: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:155#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0193000002480000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Application ServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec

ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getMonitorNodeIn tByParentName(BaseSchedulerSessionImpl.java:18412) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.getSapMo nitorRoot(MonitorUtils.java:188) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:227) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:219) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.updateAppServerInfo(ApplicationServerLoadMonitori ngComponent.java:237) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:231) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37)

at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 35 more # #2.0 #2013 06 08 18:03:11:155#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0193000002490000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Applic ationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:156#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01930000024A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:156#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C01930000024C0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationSer verLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:156#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01930000024E0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringC omponent for PI1 \#16,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:156#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01930000024F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE

xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getMonitorNodeIn tByParentName(BaseSchedulerSessionImpl.java:18412) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.getSapMo nitorRoot(MonitorUtils.java:188) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:227) at com.redwood.scheduler.connector.sap.rfc.monitor.MonitorUtils.initSapI nstanceMonitorRoot(MonitorUtils.java:219) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.updateAppServerInfo(ApplicationServerLoadMonitori ngComponent.java:237) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:231) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115)

at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 28 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 31 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 32 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 35 more # #2.0 #2013 06 08 18:03:11:157#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002500000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:157#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0193000002520000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMon itoringComponent for PI1 \#16,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:157#0-700#Error#com.redwood.scheduler.persistence.recove

ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002530000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=30# #2.0 #2013 06 08 18:03:11:157#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=30#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0193000002550000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PI1_ProcessServer: ApplicationServerLoadMonitoringCo mponent for PI1 \#16,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=30# #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063230000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063240000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION]

com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio

n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063250000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063260000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti

ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063280000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000632A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:229#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000632B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a

pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:230#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000632C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:230#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc

eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000632E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:230#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063300000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:230#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL

ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:345#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063330000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:345#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063340000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at at at at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica

te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:346#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063350000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:346#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:346#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063380000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:346#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000633A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:346#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000633B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221)

... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:346#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000633C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu

ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:347#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000633E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:347#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063400000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:347#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:462#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063430000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:462#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063440000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:463#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063450000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .#

#2.0 #2013 06 08 18:03:11:463#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063460000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:463#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063480000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:463#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c

reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000634A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:463#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000634B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect

ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:464#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000634C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:464#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000634E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:464#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in

order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063500000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:464#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063510000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks.

2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate

.java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:490#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005340000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:490#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018400 0005360000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:492#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005340000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:492#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018500 0005360000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI

_ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:504#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0184000005380000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSer ver: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:504#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0185000005380000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:504#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0184000005390000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchr onizerComponent for PI1 \#17,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate

.java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:11:504#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0185000005390000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchr onizerComponent for PBI \#1b,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate

.java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:11:504#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C01850000053A0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventS ynchronizerComponent for PBI \#1b,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:504#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C01840000053A0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventS ynchronizerComponent for PI1 \#17,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01840000053B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain##

SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01850000053B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C01840000053D0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchroni zerComponent for PI1 \#17,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2)

Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C01850000053D0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchroni zerComponent for PBI \#1b,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01840000053F0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for P I1 \#17,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01850000053F0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for P BI \#1b,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005400000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ

uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 25 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 28 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 29 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:11:505#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005400000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain##

SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone

nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 25 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 28 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 29 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv

e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0185000005430000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerCompone nt for PBI \#1b,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0184000005430000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerCompone nt for PI1 \#17,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005440000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005440000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o

ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0184000005460000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PI1_ProcessServer: EventSynchronizerComponent for PI 1 \#17,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33# #2.0 #2013 06 08 18:03:11:506#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0185000005460000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PBI_ProcessServer: EventSynchronizerComponent for PB I \#1b,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33# #2.0 #2013 06 08 18:03:11:580#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063530000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo

wn in progress ..# #2.0 #2013 06 08 18:03:11:580#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063540000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505)

at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:580#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063550000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:580#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063560000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and

resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063580000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000635A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000635B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist

ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov

erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000635C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock

PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000635E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063600000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:581#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063610000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC

onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:696#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063630000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:696#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063640000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:697#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063650000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:697#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:697#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063680000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:697#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000636A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:697#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000636B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC

onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:697#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000636C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:698#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000636E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:698#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l

oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063700000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:698#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063710000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063730000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063740000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063750000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063760000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063780000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000637A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:814#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000637B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:815#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000637C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:815#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000637E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:815#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063800000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:815#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063810000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note

719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:840#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004E70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:840#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004700 0004E90000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Attempting recovery#

#2.0 #2013 06 08 18:03:11:853#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0047000004EB0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Ha ndler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:853#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0047000004EC0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASH SUX17 \#9,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat

abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ

est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:11:854#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0047000004ED0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBA L.ASHSUX17 \#9,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:854#0-700#Error#com.redwood.scheduler.persistence.persis

tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004EE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:854#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0047000004F00000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX 17 \#9,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:854#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0047000004F20000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]# Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:854#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004F30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466)

at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:41) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140)

at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 42 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 45 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 46 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 49 more # #2.0 #2013 06 08 18:03:11:855#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004F40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:855#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C0047000004F60000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,W orkers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:855#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004F70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba

d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:11:856#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0047000004F90000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#P lain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:11:930#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063830000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:930#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063840000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:931#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063850000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:931#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:931#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063880000309A#8263150000000492#r

edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:931#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000638A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:931#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000638B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)

at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:932#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000638C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:932#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no

t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000638E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:11:932#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063900000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:11:932#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063910000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster

Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress .

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:11:940#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:940#0-700#Error#com.redwood.scheduler.persistence.recove ry#

Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C00 0004E80000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI _ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:11:953#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018C000004EA0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:11:953#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018C000004EB0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitori ngComponent for PBI \#18,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69)

at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:11:954#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018C000004EC0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMon itoringComponent for PBI \#18,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:11:954#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004ED0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:954#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018C000004EF0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringC omponent for PBI \#18,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:954#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018C000004F10000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \ #18,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c

reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:954#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004F20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut

eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 34 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 37 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 38 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:11:955#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004F30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain##

Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:955#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018C000004F50000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent f or PBI \#18,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:11:955#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:11:956#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018C000004F80000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \# 18,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o

ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:12:048#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063930000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:048#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063940000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129)

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063950000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063980000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable.

3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000639A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000639B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000639C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:049#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000639E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:050#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063A00000309A#

8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:050#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:079#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004600000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:12:079#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 0004620000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:12:093#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004640000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:093#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004650000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155)

at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.

java:261) ... 38 more # #2.0 #2013 06 08 18:03:12:093#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F000004660000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:093#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004670000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:094#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F000004690000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.

ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:094#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F0000046B0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:094#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000046C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora

ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:12:094#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000046D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:094#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F0000046F0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:095#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004700000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can

apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=22# #2.0 #2013 06 08 18:03:12:095#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=22#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F000004720000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=22# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063A30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063A40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063A50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063A60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063A80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000063AA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:166#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063AB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:167#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063AC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:167#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000063AE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:167#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063B00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:167#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063B10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note

719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063B30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063B40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P

lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063B50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063B60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063B80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000063BA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:283#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063BB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect

ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:284#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063BC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 18:03:12:284#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000063BE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:284#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063C00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:284#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory

Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init

ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:399#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063C30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:399#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063C40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:400#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063C50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:400#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:400#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063C80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:400#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000063CA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:400#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063CB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init

ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:12:401#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:401#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000063CE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:401#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063D00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu

m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:401#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063D10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:516#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063D30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:516#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063D40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:517#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063D50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone

nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:517#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063D60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:517#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063D80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:517#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000063DA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:517#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736)

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:517#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063DC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:518#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000063DE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:518#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063E00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:518#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116)

... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:633#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063E30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:634#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063E40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress .

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:634#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063E50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:634#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:634#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO

OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063E80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:634#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000063EA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:634#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063EB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:635#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:635#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat

ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000063EE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:635#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063F00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:635#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678)

at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:751#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063F30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress

..# #2.0 #2013 06 08 18:03:12:751#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000063F40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:752#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000063F50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:752#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:752#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000063F80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:752#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000063FA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:752#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063FB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#

abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:753#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000063FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:753#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000063FE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:753#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:753#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast

erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064030000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064040000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129)

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064050000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064080000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable.

3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000640A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:869#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000640B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:870#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000640C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:870#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000640E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:870#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064100000309A#

8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:870#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:937#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01820000053D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:12:937#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018200 00053F0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:12:946#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004E50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:12:946#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D00 0004E70000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Attempting recovery#

#2.0 #2013 06 08 18:03:12:951#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0182000005410000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:951#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0182000005420000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchr onizerComponent for PC1 \#1f,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat

abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm

pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:12:951#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0182000005430000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventS ynchronizerComponent for PC1 \#1f,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:951#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005440000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:951#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0182000005460000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchroni zerComponent for PC1 \#1f,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:952#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0182000005480000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for P C1 \#1f,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:952#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005490000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur

ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 25 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 28 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 29 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 32 more # #2.0 #2013 06 08 18:03:12:952#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01820000054A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:952#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C01820000054C0000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerCompone nt for PC1 \#1f,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:952#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01820000054D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load.) in 5000ms, index=33# #2.0 #2013 06 08 18:03:12:953#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01820000054F0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PC1_ProcessServer: EventSynchronizerComponent for PC 1 \#1f,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=33# #2.0 #2013 06 08 18:03:12:959#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018D000004E90000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:959#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018D000004EA0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitori ngComponent for PC1 \#1c,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept

ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:12:960#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018D000004EB0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMon

itoringComponent for PC1 \#1c,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:960#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:960#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018D000004EE0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringC omponent for PC1 \#1c,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:960#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018D000004F00000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \ #1c,5,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:960#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521)

at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:264) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 34 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 37 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 38 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43)

at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 41 more # #2.0 #2013 06 08 18:03:12:961#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004F20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:961#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018D000004F40000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent f or PC1 \#1c,5,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:961#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004F50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are

not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:12:961#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018D000004F70000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \# 1c,5,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 5000ms, index=29# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064130000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064140000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064150000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064160000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064180000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000641A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:12:986#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000641B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:12:987#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000641C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:987#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000641E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu

rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:12:987#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064200000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:12:987#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E

IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:097#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004730000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:13:097#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 0004750000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:13:103#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064230000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:103#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064240000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:103#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064250000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:103#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064260000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:103#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064280000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:104#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000642A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:104#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000642B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init

ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:13:104#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000642C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:104#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000642E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:104#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064300000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu

m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:104#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064310000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:111#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004770000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:111#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F000004780000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149)

at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:13:111#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F000004790000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:111#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000047A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc

eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:111#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F0000047C0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:112#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F0000047E0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c

reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:112#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000047F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut

eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.

java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:13:112#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004800000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u

nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:112#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F000004820000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:112#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004830000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=23# #2.0 #2013 06 08 18:03:13:113#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=23#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F000004850000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=23# #2.0 #2013 06 08 18:03:13:220#0-700#Error#com.sap.sql.connect.datasource.DBDataSou

rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064330000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:220#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064340000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or

shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:220#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064350000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:220#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne

ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:220#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064380000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:221#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000643A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:221#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000643B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init

ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more #

#2.0 #2013 06 08 18:03:13:221#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000643C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:221#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000643E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:221#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064400000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu

m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:221#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064410000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:336#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064430000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:337#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064440000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:337#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064450000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone

nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:337#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064460000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:337#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064480000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:337#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000644A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:337#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000644B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736)

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000644C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000644E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064500000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:338#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064510000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116)

... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:454#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064530000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:454#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064540000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress .

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:454#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064550000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:454#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064560000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO

OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064580000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000645A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000645B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000645C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat

ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000645E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064600000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:455#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064610000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678)

at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:571#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064630000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress

..# #2.0 #2013 06 08 18:03:13:571#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064640000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:571#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064650000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:571#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064680000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000646A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000646B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#

abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000646C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000646E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064700000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:572#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064710000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast

erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064730000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064740000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129)

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064750000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064760000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064780000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable.

3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000647A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:689#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000647B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:690#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000647C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:690#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000647E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:690#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064800000309A#

8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:690#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064810000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064830000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064840000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064850000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064880000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000648A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:806#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000648B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:807#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000648C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:807#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000648E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu

rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:807#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064900000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:807#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064910000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E

IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:922#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064930000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:13:922#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064940000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:923#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064950000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:13:923#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:923#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2)

Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064980000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:923#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000649A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:13:923#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000649B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load.

[EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:13:923#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000649C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:924#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000649E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:13:924#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064A00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:13:924#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db

pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl#

com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064A30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064A40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064A50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064A60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064A80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000064AA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio

n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:040#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064AB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:041#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064AC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:041#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000064AE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:041#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064B00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in

order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:041#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064B10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA

S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37)

at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:114#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:14:114#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 0004880000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:14:128#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F0000048A0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Work ers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:128#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C018F0000048B0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess

ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more # #2.0 #2013 06 08 18:03:14:128#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C018F0000048C0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G

uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain# # ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:128#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000048D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:129#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C018F0000048F0000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and

resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:129#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C018F000004910000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:129#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004920000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]# Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521)

at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageIntBy Tag(BaseSchedulerSessionImpl.java:15404) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getLanguageByTag (BaseSchedulerSessionImpl.java:15252) at com.redwood.scheduler.apissf.ExceptionTranslationSource.<init>(Except ionTranslationSource.java:39) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:203) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess ageStatic(ModelExceptionFormatter.java:100) at com.redwood.scheduler.apissf.ModelExceptionFormatter.getLocalizedMess age(ModelExceptionFormatter.java:54) at com.redwood.scheduler.infrastructure.exception.ExceptionLocalizerHelp er.getLocalizedMessage(ExceptionLocalizerHelper.java:29) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getLocalizedMessage(SchedulerRuntimeException.java:82) at com.redwood.scheduler.infrastructure.exception.SchedulerRuntimeExcept ion.getMessage(SchedulerRuntimeException.java:77) at com.redwood.scheduler.infrastructure.logging.SAPLoggingShim.log(SAPLo ggingShim.java:152) at com.redwood.scheduler.infrastructure.logging.DynamicLogger.log(Dynami cLogger.java:114) at com.redwood.scheduler.infrastructure.logging.WriterLogger.error(Write rLogger.java:109) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:149) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

... 31 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 34 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 35 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 38 more

# #2.0 #2013 06 08 18:03:14:129#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004930000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:129#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redw ood.com/scheduler-ear#C0000ADCD98C018F000004950000309A#8263150000000492#redwood. com/scheduler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D0 5111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000 007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=0, STA TE=08003): ResourceException occurred in method ConnectionFactoryImpl.getConnect ion(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TR H) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolv e connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary u nreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:130#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=24# #2.0 #2013 06 08 18:03:14:130#0-700#Error#com.redwood.scheduler.persistence.recove ry# Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P

ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=24#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C018F000004980000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.recovery#Guest#0##ABAD0E84D05111E2CBE 10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee# 0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Will attempt recovery of SQLException (CODE=0, STATE=08003): ResourceException o ccurred in method ConnectionFactoryImpl.getConnection(): javax.resource.Resource Exception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. P ossible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configu ration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.) in 1000ms, index=24# #2.0 #2013 06 08 18:03:14:156#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064B30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:156#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064B40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:157#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064B50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone

nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:157#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064B60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:157#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064B80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:157#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000064BA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:157#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064BB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736)

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo

nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:157#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064BC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:158#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000064BE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:158#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064C00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:158#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116)

... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:273#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064C30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:273#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064C40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress .

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995)

at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:274#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064C50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:274#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:274#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO

OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064C80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:274#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000064CA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:274#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064CB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:275#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:275#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat

ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000064CE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:275#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064D00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:275#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064D10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678)

at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:390#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064D30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress

..# #2.0 #2013 06 08 18:03:14:390#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064D40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:391#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064D50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:391#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064D60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp

orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:391#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064D80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:391#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000064DA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:391#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#

abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress

. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:392#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064DC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException

$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:392#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000064DE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:392#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064E00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:392#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast

erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:507#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064E30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:508#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064E40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129)

at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:508#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064E50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:508#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064E60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:508#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064E80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:508#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable.

3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000064EA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:508#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064EB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95)

at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:509#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064EC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:509#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000064EE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:509#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064F00000309A#

8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:509#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:624#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064F30000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:624#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000064F40000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more

# #2.0 #2013 06 08 18:03:14:624#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000064F50000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:624#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:624#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000064F80000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached.

You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:625#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000064FA0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:625#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064FB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl

.getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:

552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:625#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000064FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:625#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000064FE0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu

rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:625#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:625#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E

IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:740#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065030000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress ..# #2.0 #2013 06 08 18:03:14:740#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065040000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain##

Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdo wn in progress .. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:741#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000065050000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: ORA-01033: ORACLE initialization or shutdown in progress .# #2.0 #2013 06 08 18:03:14:741#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:741#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2)

Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065080000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:741#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C00340000650A0000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 18:03:14:741#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000650B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load.

[EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36)

at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:14:742#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000650C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:742#0-700#Error#com.redwood.scheduler.cluster.ClusterMas

terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C00340000650E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 18:03:14:742#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065100000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 18:03:14:742#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db

pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01033: ORACLE init ialization or shutdown in progress

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01033: ORACLE initialization or shutdown in progress . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more # #2.0 #2013 06 08 18:03:15:132#0-700#Error#com.redwood.scheduler.persistence.recove ry#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004990000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Attempting recovery# #2.0 #2013 06 08 18:03:15:132#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F00 00049B0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:15:618#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004F90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Job MonitoringComponent for PI1 \#14,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:15:618#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B00 0004FB0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:15:654#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005340000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX05 \#7,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:15:654#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004600 0005360000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:15:797#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005370000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX05 \#7,5,Workers]#Plain## Recovered#

#2.0 #2013 06 08 18:03:15:797#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Job MonitoringComponent for PI1 \#14,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:15:797#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000049C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Recovered# #2.0 #2013 06 08 18:03:15:797#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005390000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message H andler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:15:797#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000004FE0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSe rver: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:15:797#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F0000049E0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Wor kers]#Plain## Recovered# #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.connector.sap.rfc. service.components.JobMonitoringComponentImpl# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000005000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.r fc.service.components.JobMonitoringComponentImpl#Guest#0##ABAD0E84D05111E2CBE100 00007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#T hread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \#14, 5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager#

JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00460000053B0000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.Un itOfWorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe100 00007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Mess age Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.infrastructure.wor k.WorkerImpl# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004A00000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.infrastructure. work.WorkerImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe100 00007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f, 8,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00460000053C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## Unable to perform persist, and a SchedulerApiRuntimeException occurred; notifyin g worker. [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107)

at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 20 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.connector.sap.rfc. service.components.JobMonitoringComponentImpl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000005010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.s ervice.components.JobMonitoringComponentImpl#Guest#0##ABAD0E84D05111E2CBE1000000 7E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Threa d[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Wo rkers]#Plain## JMC for PI1: exception while updating jobs [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.getConsoleBwChains(JobMonitoringComponentImpl.java:832) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.processConsoleBWChains(JobMonitoringComponentImpl.java:636) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:251) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71)

at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52)

... 26 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 29 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 30 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 33 more # #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.infrastructure.wor k.WorkerImpl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.infrastructure.work .WorkerImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Wo rkers]#Plain## Worker Job Dispatcher has thrown an Exception [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.core.JobLocker.refreshLockedLocks(JobLocker.jav a:212) at com.redwood.scheduler.core.DispatcherAgent.onMessage(DispatcherAgent. java:300) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 6 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load.

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 11 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 24 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 27 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory .

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 28 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 31 more # #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000005020000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method#

#2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004A20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreContextImp l#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Dispatcher error JCS-122036: An exception occurred during the execution of a per sistence layer method# #2.0 #2013 06 08 18:03:15:932#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B0000050 40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.conne ctor.sap.rfc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE1000000 7E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Threa d[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Wo rkers]#Plain## Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method# #2.0 #2013 06 08 18:03:15:933#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# Dispatcher error JCS-122036: An exception occurred during the execution of a per sistence layer method#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F 000004A40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.schedule r.core.CoreContextImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e 2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatch er \#f,8,Workers]#Plain## Dispatcher error JCS-122036: An exception occurred during the execution of a per sistence layer method# #2.0 #2013 06 08 18:03:15:934#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000005060000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.r fc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#aba d0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Pla in## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:15:934#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018B000005070000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PI1_ProcessServer: JobMonitoringComponent for PI1 \#14,5,Workers]#Plain## Exception [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080)

at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.getConsoleBwChains(JobMonitoringComponentImpl.java:832) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.processConsoleBWChains(JobMonitoringComponentImpl.java:636) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:251) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut

eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 26 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 29 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 30 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at at at at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica

te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 33 more # #2.0 #2013 06 08 18:03:15:934#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00460000053D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:15:935#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method#XX-PART-REDWOOD#redwood. com/scheduler-ear#C0000ADCD98C00460000053F0000309A#8263150000000492#redwood.com/ scheduler-ear#com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandl er#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#ab ad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler G LOBAL.ASHSUX05 \#7,5,Workers]#Plain##

Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:15:936#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004A60000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreContex tImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee #abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers] #Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:15:936#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018F000004A70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreContextImp l#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Job Dispatcher \#f,8,Workers]#Pla in## Dispatcher error [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.core.JobLocker.refreshLockedLocks(JobLocker.jav a:212) at com.redwood.scheduler.core.DispatcherAgent.onMessage(DispatcherAgent. java:300) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc

e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 6 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 11 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 24 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory

. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 27 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 28 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 31 more #

#2.0 #2013 06 08 18:03:15:936#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005410000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remo te.PlatformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e 84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Pla tform Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:15:936#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0046000005420000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHSUX05 \#7,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> [EXCEPTION] JCS-122035: Unable to persist: JCS-122036: An exception occurred during the exec ution of a persistence layer method at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:36) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$

1.performWork(UpdateMonitorHandler.java:181) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) ... 12 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74)

... 20 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:15:937#0-700#Error#com.redwood.scheduler.infrastructure.wor k.WorkerImpl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003E000000090000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.infrastructure.work .WorkerImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Component \#1,5,Wo rkers]#Plain## Worker Core Component has thrown an Exception java.lang.RuntimeException: Core c omponent needs to restart as a component has died.# #2.0 #2013 06 08 18:03:15:937#0-700#Error#com.redwood.scheduler.infrastructure.wor k.WorkerImpl# Worker Core Component has thrown an Exception java.lang.RuntimeException: Core c omponent needs to restart as a component has died.#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C003E0000000B0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.infrastructure.work.WorkerImpl#Guest#0##ABAD0E84D 05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe1000 0007e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Plain## Worker Core Component has thrown an Exception java.lang.RuntimeException: Core c omponent needs to restart as a component has died.# #2.0 #2013 06 08 18:03:15:937#0-700#Error#com.redwood.scheduler.infrastructure.wor k.WorkerImpl# Core component needs to restart as a component has died.#XX-PART-REDWOOD#redwood .com/scheduler-ear#C0000ADCD98C003E0000000D0000309A#8263150000000492#redwood.com /scheduler-ear#com.redwood.scheduler.infrastructure.work.WorkerImpl#Guest#0##ABA D0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2c be10000007e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Plain## Core component needs to restart as a component has died.# #2.0 #2013 06 08 18:03:15:937#0-700#Error#com.redwood.scheduler.infrastructure.wor k.WorkerImpl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003E0000000E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.infrastructure.work .WorkerImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Component \#1,5,Wo rkers]#Plain## Worker Core Component has thrown an Exception

[EXCEPTION] java.lang.RuntimeException: Core component needs to restart as a component has d ied. at com.redwood.scheduler.core.CoreContextImpl.onMessage(CoreContextImpl. java:425) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.core.JobLocker.refreshLockedLocks(JobLocker.jav a:212) at com.redwood.scheduler.core.DispatcherAgent.onMessage(DispatcherAgent. java:300) ... 3 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 6 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare

Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 11 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 24 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 27 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 28 more

Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 31 more # #2.0 #2013 06 08 18:03:15:942#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000055A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Worke rs]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:15:942#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018600 00055C0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor U pdater \#10,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:054#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedSt atement# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C01860000055E0000309A#8

263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonPrepared Statement#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10 ,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Failed to set the par ameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REM OTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LAS TMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? , ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used i f the corresponding column is nullable. .# #2.0 #2013 06 08 18:03:16:054#0-700#Error#com.sap.sql.jdbc.common.CommonPreparedSt atement# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C01860000055F0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonPreparedStatement#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plai n## Exception of type com.sap.sql.log.OpenSQLException caught: Failed to set the par ameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REM OTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LAS TMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? , ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used i f the corresponding column is nullable. . [EXCEPTION] com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A _CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_ SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cann ot assign NULL. The setNull() method can only be used if the corresponding colum n is nullable. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.jdbc.common.CommonPreparedStatement.handleSetterException (CommonPreparedStatement.java:420) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:415) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setN ull(PreparedStatementWrapper.java:570) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.setRealP reparedStatementParameters(PreparedStatementImpl.java:179) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.execute( PreparedStatementImpl.java:429) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:906) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sCreation(LowLevelPersistenceImpl.java:776) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:288) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74)

at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.rethrowException(OuterPersistenceUnitOfWorkManager.java:91) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:43) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:37) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.core.CoreMonitorUpdater.onMessage(CoreMonitorUp dater.java:175) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.sql.check.ValueCheckerException: Cannot assign NULL. The setN ull() method can only be used if the corresponding column is nullable. at com.sap.sql.jdbc.common.dispatch.AbstractHostvariableSetter.setNull(A bstractHostvariableSetter.java:268) at com.sap.sql.jdbc.common.dispatch.SetterDispatcherImpl.setNull(SetterD ispatcherImpl.java:244) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:413) ... 23 more # #2.0 #2013 06 08 18:03:16:054#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005600000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Wo rkers]#Plain## SQL Error: SQLException (CODE=1001152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHA VIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSU B, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. com.sap.sql.log.OpenSQLException: Failed to s et the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_A CTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_N AME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGR OUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. # #2.0 #2013 06 08 18:03:16:054#0-700#Error#com.redwood.scheduler.persistence.persis tence#

SQL Error: SQLException (CODE=1001152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHA VIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSU B, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. com.sap.sql.log.OpenSQLException: Failed to s et the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_A CTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_N AME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGR OUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. #XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C0186000005620000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2 CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15 ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## SQL Error: SQLException (CODE=1001152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHA VIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSU B, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. com.sap.sql.log.OpenSQLException: Failed to s et the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_A CTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_N AME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGR OUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.persis tence# Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPV ERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTM ODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZO NE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() meth od can only be used if the corresponding column is nullable. #XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0186000005640000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0 E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe 10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPV ERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTM ODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZO NE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() meth od can only be used if the corresponding column is nullable. # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005650000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Wo rkers]#Plain## SQL Error: SQLException (CODE=1001152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHA VIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID,

A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSU B, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. [EXCEPTION] com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A _CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_ SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cann ot assign NULL. The setNull() method can only be used if the corresponding colum n is nullable. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.jdbc.common.CommonPreparedStatement.handleSetterException (CommonPreparedStatement.java:420) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:415) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setN ull(PreparedStatementWrapper.java:570) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.setRealP reparedStatementParameters(PreparedStatementImpl.java:179) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.execute( PreparedStatementImpl.java:429) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:906) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sCreation(LowLevelPersistenceImpl.java:776) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:288) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.rethrowException(OuterPersistenceUnitOfWorkManager.java:91) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:43) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:37) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.core.CoreMonitorUpdater.onMessage(CoreMonitorUp dater.java:175) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107)

at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.sql.check.ValueCheckerException: Cannot assign NULL. The setN ull() method can only be used if the corresponding column is nullable. at com.sap.sql.jdbc.common.dispatch.AbstractHostvariableSetter.setNull(A bstractHostvariableSetter.java:268) at com.sap.sql.jdbc.common.dispatch.SetterDispatcherImpl.setNull(SetterD ispatcherImpl.java:244) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:413) ... 23 more # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## Start Transaction id=76804068 contains 3 objects. Error: : SQLException (CODE=10 01152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert int o JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A _DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A _UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NUL L. The setNull() method can only be used if the corresponding column is nullable . com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of the statem ent >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT , A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNO DE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: C annot assign NULL. The setNull() method can only be used if the corresponding co lumn is nullable. # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76804068 contains 3 objects. Error: : SQLException (CODE=10 01152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert int o JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A _DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A _UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NUL L. The setNull() method can only be used if the corresponding column is nullable . com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of the statem ent >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT , A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNO DE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: C annot assign NULL. The setNull() method can only be used if the corresponding co lumn is nullable. #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000 005680000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.p ersistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10 000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updat er \#10,5,Workers]#Plain## Start Transaction id=76804068 contains 3 objects. Error: : SQLException (CODE=10 01152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert int o JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A _DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A _UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?,

?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NUL L. The setNull() method can only be used if the corresponding column is nullable . com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of the statem ent >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT , A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNO DE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: C annot assign NULL. The setNull() method can only be used if the corresponding co lumn is nullable. # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.tdump# Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPV ERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTM ODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZO NE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() meth od can only be used if the corresponding column is nullable. #XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C01860000056A0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPV ERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTM ODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZO NE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() meth od can only be used if the corresponding column is nullable. # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000056B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## Start Transaction id=76804068 contains 3 objects. Error: : SQLException (CODE=10 01152, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert int o JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A _DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A _UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NUL L. The setNull() method can only be used if the corresponding column is nullable . [EXCEPTION] com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A _CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_ SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cann ot assign NULL. The setNull() method can only be used if the corresponding colum n is nullable. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.jdbc.common.CommonPreparedStatement.handleSetterException (CommonPreparedStatement.java:420) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:415) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setN ull(PreparedStatementWrapper.java:570) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.setRealP reparedStatementParameters(PreparedStatementImpl.java:179)

at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.execute( PreparedStatementImpl.java:429) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:906) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sCreation(LowLevelPersistenceImpl.java:776) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:288) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.rethrowException(OuterPersistenceUnitOfWorkManager.java:91) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:43) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:37) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.core.CoreMonitorUpdater.onMessage(CoreMonitorUp dater.java:175) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.sql.check.ValueCheckerException: Cannot assign NULL. The setN ull() method can only be used if the corresponding column is nullable. at com.sap.sql.jdbc.common.dispatch.AbstractHostvariableSetter.setNull(A bstractHostvariableSetter.java:268) at com.sap.sql.jdbc.common.dispatch.SetterDispatcherImpl.setNull(SetterD ispatcherImpl.java:244) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:413) ... 23 more # #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000056C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## dirtyObject: [x] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n

ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<System>> RemoteId=<null> RemoteSystem=<null> SearchNam e=<<null>,<SYSTEM>> UniqueId=<<null>,<11213009>> CreationTimeZone=<null> Isolati onGroup=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode=<null># #2.0 #2013 06 08 18:03:16:055#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<System>> RemoteId=<null> RemoteSystem=<null> SearchNam e=<<null>,<SYSTEM>> UniqueId=<<null>,<11213009>> CreationTimeZone=<null> Isolati onGroup=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode=<null>#XX-PART -REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000056E0000309A#826315000000 0492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## dirtyObject: [x] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<System>> RemoteId=<null> RemoteSystem=<null> SearchNam e=<<null>,<SYSTEM>> UniqueId=<<null>,<11213009>> CreationTimeZone=<null> Isolati onGroup=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode=<null># #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000056F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## dirtyObject: [ ] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<Queue>> RemoteId=<null> RemoteSystem=<null> SearchName =<<null>,<QUEUE>> UniqueId=<<null>,<11213010>> CreationTimeZone=<null> Isolation Group=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode=<<null>,<1121300 9>># #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<Queue>> RemoteId=<null> RemoteSystem=<null> SearchName =<<null>,<QUEUE>> UniqueId=<<null>,<11213010>> CreationTimeZone=<null> Isolation Group=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode=<<null>,<1121300 9>>#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005710000309A#8 263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdum p#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Worke rs]#Plain## dirtyObject: [ ] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<Queue>> RemoteId=<null> RemoteSystem=<null> SearchName =<<null>,<QUEUE>> UniqueId=<<null>,<11213010>> CreationTimeZone=<null> Isolation Group=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode=<<null>,<1121300 9>># #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005720000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## dirtyObject: [ ] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification

Time=<null> Name=<<null>,<ProcessServer>> RemoteId=<null> RemoteSystem=<null> Se archName=<<null>,<PROCESSSERVER>> UniqueId=<<null>,<11213011>> CreationTimeZone= <null> IsolationGroup=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode= <<null>,<11213009>># #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<ProcessServer>> RemoteId=<null> RemoteSystem=<null> Se archName=<<null>,<PROCESSSERVER>> UniqueId=<<null>,<11213011>> CreationTimeZone= <null> IsolationGroup=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode= <<null>,<11213009>>#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018600 0005740000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1 0000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Upda ter \#10,5,Workers]#Plain## dirtyObject: [ ] C MonitorNode:v<null> ActualSeverity=<<null>,<-1>> Behavior=<<n ull>,<0>> Comment=<null> CreationTime=<null> Description=<null> LastModification Time=<null> Name=<<null>,<ProcessServer>> RemoteId=<null> RemoteSystem=<null> Se archName=<<null>,<PROCESSSERVER>> UniqueId=<<null>,<11213011>> CreationTimeZone= <null> IsolationGroup=<<null>,<3>> LastModifierSubject=<null> ParentMonitorNode= <<null>,<11213009>># #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005750000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers] #Plain## End Transaction id=76804068# #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76804068#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0186000005770000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Moni tor Updater \#10,5,Workers]#Plain## End Transaction id=76804068# #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005780000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Worke rs]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=100115 2, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JC S_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DES CRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNI QUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. T he setNull() method can only be used if the corresponding column is nullable. # #2.0 #2013 06 08 18:03:16:056#0-700#Error#com.redwood.scheduler.persistence.recove ry# Exception during recovery, will attempt recovery again SQLException (CODE=100115 2, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JC S_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DES CRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNI

QUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. T he setNull() method can only be used if the corresponding column is nullable. #X X-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000057A0000309A#826315 0000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recovery# Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0 e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers ]#Plain## Exception during recovery, will attempt recovery again SQLException (CODE=100115 2, STATE=SAP06): Failed to set the parameter 5 of the statement >>insert into JC S_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DES CRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNI QUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. T he setNull() method can only be used if the corresponding column is nullable. # #2.0 #2013 06 08 18:03:16:057#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000057B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \# 10,5,Workers]#Plain## Unable to perform persist; notifying worker. JCS-122035: Unable to persist: JCSXXXXX: Recovery failed: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS , A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME , A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nulla ble. # #2.0 #2013 06 08 18:03:16:057#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# Unable to perform persist; notifying worker. JCS-122035: Unable to persist: JCSXXXXX: Recovery failed: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS , A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME , A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nulla ble. #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01860000057D0000309A #8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.U nitOfWorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10 000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updat er \#10,5,Workers]#Plain## Unable to perform persist; notifying worker. JCS-122035: Unable to persist: JCSXXXXX: Recovery failed: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS , A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME , A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nulla ble. # #2.0 #2013 06 08 18:03:16:086#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000005060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba

d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:086#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004200 0005080000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:135#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000005090000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHS95549 \#3,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:135#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00420000050B0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message H andler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:137#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00420000050D0000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.Un itOfWorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe100 00007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Mess age Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:16:137#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00420000050E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Unable to perform persist, and a SchedulerApiRuntimeException occurred; notifyin g worker. [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181)

at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 20 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio

n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:16:140#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00420000050F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:16:141#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler#

Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method#XX-PART-REDWOOD#redwood. com/scheduler-ear#C0000ADCD98C0042000005110000309A#8263150000000492#redwood.com/ scheduler-ear#com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandl er#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#ab ad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler G LOBAL.ASHS95549 \#3,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:16:156#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# JCS-122035: Unable to persist: JCS-XXXXX: @locale2@:(com.redwood.scheduler.excep tion.Class.persistence.api.PersistenceException$RecoveryFailedException 'Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_I SOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. ')#XX-PART-REDWOOD#redwood .com/scheduler-ear#C0000ADCD98C01860000057F0000309A#8263150000000492#redwood.com /scheduler-ear#com.redwood.scheduler.apiint.model.UnitOfWorkManager#Guest#0##ABA D0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2c be10000007e15ee#0#Thread[Redwood Core Monitor Updater \#10,5,Workers]#Plain## JCS-122035: Unable to persist: JCS-XXXXX: @locale2@:(com.redwood.scheduler.excep tion.Class.persistence.api.PersistenceException$RecoveryFailedException 'Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_I SOGROUP, F_LASTMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the corresponding column is nullable. ')# #2.0 #2013 06 08 18:03:16:156#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0186000005800000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Monitor Updater \# 10,5,Workers]#Plain## Unable to perform persist; notifying worker. [EXCEPTION] JCS-122035: Unable to persist: JCS-XXXXX: Recovery failed: Failed to set the par ameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REM OTEID, A_REMOTESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LAS TMODSUB, F_PARENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? , ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used i f the corresponding column is nullable. at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(

SchedulerSessionImpl.java:931) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:37) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.core.CoreMonitorUpdater.onMessage(CoreMonitorUp dater.java:175) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: Failed to set the parameter 5 of the statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A_C OMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOTES YSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PAREN TMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )<<: Cannot assign NULL. The setNull() method can only be used if the correspond ing column is nullable. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.rethrowException(OuterPersistenceUnitOfWorkManager.java:91) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:43) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) ... 7 more Caused by: com.sap.sql.log.OpenSQLException: Failed to set the parameter 5 of th e statement >>insert into JCS_MONNODE0(A_LLPVERSION, A_ACTUALSEV, A_BEHAVIOUR, A _COMMENT, A_CREATEDTS, A_DESCRIPTION, A_LASTMODIFTS, A_NAME, A_REMOTEID, A_REMOT ESYSTEM, A_SEARCHNAME, A_UNIQUEID, F_CRTIMEZONE, F_ISOGROUP, F_LASTMODSUB, F_PAR ENTMONNODE) values ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)<<: Cannot assign NULL. The setNull() method can only be used if the correspo nding column is nullable. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.jdbc.common.CommonPreparedStatement.handleSetterException (CommonPreparedStatement.java:420) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:415) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setN ull(PreparedStatementWrapper.java:570) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.setRealP reparedStatementParameters(PreparedStatementImpl.java:179) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.execute( PreparedStatementImpl.java:429) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:906) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sCreation(LowLevelPersistenceImpl.java:776)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:288) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: com.sap.sql.check.ValueCheckerException: Cannot assign NULL. The setN ull() method can only be used if the corresponding column is nullable. at com.sap.sql.jdbc.common.dispatch.AbstractHostvariableSetter.setNull(A bstractHostvariableSetter.java:268) at com.sap.sql.jdbc.common.dispatch.SetterDispatcherImpl.setNull(SetterD ispatcherImpl.java:244) at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPrepare dStatement.java:413) ... 23 more # #2.0 #2013 06 08 18:03:16:185#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002560000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:185#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C019300 0002580000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers] #Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:185#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000005130000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remo te.PlatformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e 84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Pla tform Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:16:185#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0042000005140000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHS95549 \#3,5,Workers]#Plain##

Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>17</monitor-value> </update-monitor> [EXCEPTION] JCS-122035: Unable to persist: JCS-122036: An exception occurred during the exec ution of a persistence layer method at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:36) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) ... 12 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut

eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 20 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more

# #2.0 #2013 06 08 18:03:16:243#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0193000002590000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: App licationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:243#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01930000025B0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSe rver: ApplicationServerLoadMonitoringComponent for PI1 \#16,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:508#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0184000005470000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:508#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018400 0005490000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1 _ProcessServer: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:509#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0185000005470000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:509#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018500 0005490000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI _ProcessServer: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:595#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01840000054A0000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Eve ntSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:595#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01850000054A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Eve ntSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:595#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01850000054C0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSe rver: EventSynchronizerComponent for PBI \#1b,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:595#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01840000054C0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSe rver: EventSynchronizerComponent for PI1 \#17,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:857#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004FA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:857#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004700 0004FC0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:858#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004FD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX17 \#9,5,Workers]#Plain## Recovered#

#2.0 #2013 06 08 18:03:16:858#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000004FF0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message H andler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:860#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000005010000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.Un itOfWorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe100 00007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Mess age Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:16:860#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000005020000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Unable to perform persist, and a SchedulerApiRuntimeException occurred; notifyin g worker. [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107)

at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 20 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:16:862#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000005030000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>3</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:16:862#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>3</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method#XX-PART-REDWOOD#redwood. com/scheduler-ear#C0000ADCD98C0047000005050000309A#8263150000000492#redwood.com/ scheduler-ear#com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandl er#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#ab ad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler G LOBAL.ASHSUX17 \#9,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>3</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:16:865#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler#

JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000005070000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remo te.PlatformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e 84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Pla tform Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:16:865#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0047000005080000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHSUX17 \#9,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>3</monitor-value> </update-monitor> [EXCEPTION] JCS-122035: Unable to persist: JCS-122036: An exception occurred during the exec ution of a persistence layer method at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:36) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20)

... 12 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 20 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections

to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)

at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:16:958#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004F90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:958#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C00 0004FB0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI _ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:16:958#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Job MonitoringComponent for PBI \#18,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:958#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000004FE0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSe rver: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:16:962#0-700#Error#com.redwood.scheduler.connector.sap.rfc. service.components.JobMonitoringComponentImpl# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000005000000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.r

fc.service.components.JobMonitoringComponentImpl#Guest#0##ABAD0E84D05111E2CBE100 00007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#T hread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18, 5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:16:962#0-700#Error#com.redwood.scheduler.connector.sap.rfc. service.components.JobMonitoringComponentImpl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000005010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.s ervice.components.JobMonitoringComponentImpl#Guest#0##ABAD0E84D05111E2CBE1000000 7E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Threa d[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Wo rkers]#Plain## JMC for PBI: exception while updating jobs [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.getConsoleBwChains(JobMonitoringComponentImpl.java:832) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.processConsoleBWChains(JobMonitoringComponentImpl.java:636) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:251) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con

nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 26 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 29 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov

erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 30 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 33 more # #2.0 #2013 06 08 18:03:16:962#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000005020000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS

ervice PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method# #2.0 #2013 06 08 18:03:16:963#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C0000050 40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.conne ctor.sap.rfc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE1000000 7E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Threa d[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Wo rkers]#Plain## Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method# #2.0 #2013 06 08 18:03:16:967#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000005060000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.r fc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#aba d0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Pla in## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:16:967#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018C000005070000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PBI_ProcessServer: JobMonitoringComponent for PBI \#18,5,Workers]#Plain## Exception [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.getConsoleBwChains(JobMonitoringComponentImpl.java:832) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.processConsoleBWChains(JobMonitoringComponentImpl.java:636) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:251) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1

)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 26 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 29 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 30 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio

n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 33 more # #2.0 #2013 06 08 18:03:17:954#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005500000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:17:954#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018200 0005520000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:17:955#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005530000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Eve ntSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:17:955#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0182000005550000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSe rver: EventSynchronizerComponent for PC1 \#1f,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:17:964#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004F80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:17:964#0-700#Error#com.redwood.scheduler.persistence.recove

ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D00 0004FA0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:17:964#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004FB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Job MonitoringComponent for PC1 \#1c,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:17:964#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004FD0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSe rver: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:17:966#0-700#Error#com.redwood.scheduler.connector.sap.rfc. service.components.JobMonitoringComponentImpl# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000004FF0000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.r fc.service.components.JobMonitoringComponentImpl#Guest#0##ABAD0E84D05111E2CBE100 00007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#T hread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c, 5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:17:966#0-700#Error#com.redwood.scheduler.connector.sap.rfc. service.components.JobMonitoringComponentImpl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000005000000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.s ervice.components.JobMonitoringComponentImpl#Guest#0##ABAD0E84D05111E2CBE1000000 7E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Threa d[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Wo rkers]#Plain## JMC for PC1: exception while updating jobs [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.getConsoleBwChains(JobMonitoringComponentImpl.java:832) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.processConsoleBWChains(JobMonitoringComponentImpl.java:636) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:251)

at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re

tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 26 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 29 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 30 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 33 more # #2.0 #2013 06 08 18:03:17:966#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000005010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method# #2.0 #2013 06 08 18:03:17:966#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D0000050 30000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.conne ctor.sap.rfc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE1000000 7E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Threa d[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Wo rkers]#Plain## Exception JCS-122036: An exception occurred during the execution of a persistenc e layer method# #2.0 #2013 06 08 18:03:17:968#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000005050000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.r fc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#aba d0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Pla in## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:17:968#0-700#Error#com.redwood.scheduler.connector.sap.rfc.

components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C018D000005060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PC1_ProcessServer: JobMonitoringComponent for PC1 \#1c,5,Workers]#Plain## Exception [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.getConsoleBwChains(JobMonitoringComponentImpl.java:832) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.processConsoleBWChains(JobMonitoringComponentImpl.java:636) at com.redwood.scheduler.connector.sap.rfc.service.components.JobMonitor ingComponentImpl.execute(JobMonitoringComponentImpl.java:251) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU

serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 13 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 26 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 29 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS

ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 30 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 33 more # #2.0 #2013 06 08 18:03:19:342#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0190000002A20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Xbp SynchronizerComponent for PI1 \#15,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:19:342#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C019000 0002A40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1

_ProcessServer: XbpSynchronizerComponent for PI1 \#15,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:19:342#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0190000002A50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessServer: Xbp SynchronizerComponent for PI1 \#15,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:19:342#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0190000002A70000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PI1_ProcessSe rver: XbpSynchronizerComponent for PI1 \#15,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:19:826#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0191000002A20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Xbp SynchronizerComponent for PBI \#19,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:19:826#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C019100 0002A40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI _ProcessServer: XbpSynchronizerComponent for PBI \#19,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:19:826#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0191000002A50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: Xbp SynchronizerComponent for PBI \#19,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:19:827#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0191000002A70000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSe rver: XbpSynchronizerComponent for PBI \#19,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:20:344#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0192000002A20000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Xbp SynchronizerComponent for PC1 \#1d,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:20:344#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C019200 0002A40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1 _ProcessServer: XbpSynchronizerComponent for PC1 \#1d,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:20:344#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0192000002A50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessServer: Xbp SynchronizerComponent for PC1 \#1d,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:20:344#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0192000002A70000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSe rver: XbpSynchronizerComponent for PC1 \#1d,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:46:455#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C017A000000280000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService P01_ProcessServer: EventSynchronizerComponent for P01 \#23,5,Wor kers]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

# #2.0 #2013 06 08 18:03:46:455#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:03:36 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 60 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C017A0000002A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService P01_ProcessServer: EventSynchronizerComponent for P01 \#23,5,Wor kers]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

#2.0 #2013 06 08 18:03:46:455#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720

COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 60 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C017A0000002C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService P01_ProcessServer: EventSynchronizerComponent for P01 \#23,5,Wor kers]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

#2.0 #2013 06 08 18:03:46:455#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C017A0000002D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService P01_ProcessServer: EventSynchronizerComponent for P01 \#23,5,Wor kers]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300

SYSTEM CALL ERRNO ERRNO TEXT COUNTER

connect 111 Connection refused 60

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

.perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:03:36 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 18:03:48:633#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0045000005590000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX02 \#5,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:48:633#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C004500 00055B0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:03:48:634#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00450000055C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GL OBAL.ASHSUX02 \#5,5,Workers]#Plain##

Recovered# #2.0 #2013 06 08 18:03:48:634#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00450000055E0000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message H andler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:03:48:635#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0045000005600000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.Un itOfWorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe100 00007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Mess age Handler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:48:635#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0045000005610000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## Unable to perform persist, and a SchedulerApiRuntimeException occurred; notifyin g worker. [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91)

at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover(

RetryThenFailAction.java:74) ... 20 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:48:637#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0045000005620000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>5</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method# #2.0 #2013 06 08 18:03:48:637#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>5</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method#XX-PART-REDWOOD#redwood. com/scheduler-ear#C0000ADCD98C0045000005640000309A#8263150000000492#redwood.com/ scheduler-ear#com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandl er#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#ab ad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platform Agent Message Handler G LOBAL.ASHSUX02 \#5,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>5</monitor-value> </update-monitor> JCS-122035: Unable to persist: JCS-122036: An exception occu rred during the execution of a persistence layer method#

#2.0 #2013 06 08 18:03:48:639#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0045000005660000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remo te.PlatformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e 84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Pla tform Agent Message Handler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:03:48:639#0-700#Error#com.redwood.scheduler.jobservice.remote. PlatformAgentReplyXmlHandler# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0045000005670000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.jobservice.remote.P latformAgentReplyXmlHandler#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0 5111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Platfor m Agent Message Handler GLOBAL.ASHSUX02 \#5,5,Workers]#Plain## Error handling call UpdateMonitor XML follows <update-monitor> <monitor-path>CPUBusy</monitor-path> <monitor-value>5</monitor-value> </update-monitor> [EXCEPTION] JCS-122035: Unable to persist: JCS-122036: An exception occurred during the exec ution of a persistence layer method at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:36) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.jobservice.remote.ElementHandlerContextImpl.per form(ElementHandlerContextImpl.java:62) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler. handle(UpdateMonitorHandler.java:170) at com.redwood.scheduler.jobservice.remote.handler.CallDispatcher.handle (CallDispatcher.java:438) at com.redwood.scheduler.servicemessage.messages.UpdateMonitor.handle(Up dateMonitor.java:78) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyXmlHandler. handleCalls(PlatformAgentReplyXmlHandler.java:52) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.proc essResponse(PlatformAgentReplyPoller.java:178) at com.redwood.scheduler.jobservice.remote.PlatformAgentService.sendRequ est(PlatformAgentService.java:1534) at com.redwood.scheduler.jobservice.remote.PlatformAgentReplyPoller.onMe ssage(PlatformAgentReplyPoller.java:91) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.jobservice.remote.handler.UpdateMonitorHandler$ 1.performWork(UpdateMonitorHandler.java:181)

at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) ... 12 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 15 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 20 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 33 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 36 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 37 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio

n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 40 more # #2.0 #2013 06 08 18:03:53:419#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003E0000000F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreContextImp l#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Pla in## Core Context error java.lang.RuntimeException: Core component needs to restart a s a component has died.# #2.0 #2013 06 08 18:03:53:419#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# Core Context error java.lang.RuntimeException: Core component needs to restart a s a component has died.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00 3E000000110000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.schedu ler.core.CoreContextImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0511 1e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Compo nent \#1,5,Workers]#Plain## Core Context error java.lang.RuntimeException: Core component needs to restart a s a component has died.# #2.0 #2013 06 08 18:03:53:419#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# Core component needs to restart as a component has died.#XX-PART-REDWOOD#redwood .com/scheduler-ear#C0000ADCD98C003E000000130000309A#8263150000000492#redwood.com /scheduler-ear#com.redwood.scheduler.core.CoreContextImpl#Guest#0##ABAD0E84D0511 1E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007 e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Plain## Core component needs to restart as a component has died.# #2.0 #2013 06 08 18:03:53:419#0-700#Error#com.redwood.scheduler.core.CoreContextIm pl# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003E000000140000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreContextImp l#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Pla in## Core Context error [EXCEPTION]

java.lang.RuntimeException: Core component needs to restart as a component has d ied. at com.redwood.scheduler.core.CoreContextImpl.onMessage(CoreContextImpl. java:425) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.core.JobLocker.refreshLockedLocks(JobLocker.jav a:212) at com.redwood.scheduler.core.DispatcherAgent.onMessage(DispatcherAgent. java:300) ... 3 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 6 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339)

at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 11 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 24 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 27 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 28 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 31 more # #2.0 #2013 06 08 18:03:53:429#0-700#Error#com.redwood.scheduler.core.CoreComponent # #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003E000000150000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreComponent# Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0 e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Plain ## Core Component stopped java.lang.RuntimeException: Core component needs to resta rt as a component has died.# #2.0 #2013 06 08 18:03:53:430#0-700#Error#com.redwood.scheduler.core.CoreComponent # Core Component stopped java.lang.RuntimeException: Core component needs to resta rt as a component has died.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C003E000000170000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.core.CoreComponent#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Com ponent \#1,5,Workers]#Plain## Core Component stopped java.lang.RuntimeException: Core component needs to resta rt as a component has died.# #2.0 #2013 06 08 18:03:53:430#0-700#Error#com.redwood.scheduler.core.CoreComponent

# Core component needs to restart as a component has died.#XX-PART-REDWOOD#redwood .com/scheduler-ear#C0000ADCD98C003E000000190000309A#8263150000000492#redwood.com /scheduler-ear#com.redwood.scheduler.core.CoreComponent#Guest#0##ABAD0E84D05111E 2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e1 5ee#0#Thread[Redwood Core Component \#1,5,Workers]#Plain## Core component needs to restart as a component has died.# #2.0 #2013 06 08 18:03:53:430#0-700#Error#com.redwood.scheduler.core.CoreComponent # #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003E0000001A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.core.CoreComponent# Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0 e84d05111e2cbe10000007e15ee#0#Thread[Redwood Core Component \#1,5,Workers]#Plain ## Core Component stopped [EXCEPTION] java.lang.RuntimeException: Core component needs to restart as a component has d ied. at com.redwood.scheduler.core.CoreContextImpl.onMessage(CoreContextImpl. java:425) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.core.JobLocker.refreshLockedLocks(JobLocker.jav a:212) at com.redwood.scheduler.core.DispatcherAgent.onMessage(DispatcherAgent. java:300) ... 3 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 6 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc

e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 11 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 24 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 27 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 28 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 31 more # #2.0 #2013 06 08 18:04:06:771#0-700#Fatal#com.sap.uddi.server.STRunnable# #BC-ESI-UDDI#tc~esi~uddi~server~core~service#C0000ADCD98C0183000000180000309A#82 63150000001327##com.sap.uddi.server.STRunnable####9D0B8A31D05111E28FB80050568C5F 4A#9d0b8a31d05111e28fb80050568c5f4a#9d0b8a31d05111e28fb80050568c5f4a#0#Thread[Ti mer-4,5,SystemThreadGroup]#Plain##

run() Database is back up. # #2.0 #2013 06 08 18:04:07:446#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006540000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]# Plain## Attempting recovery# #2.0 #2013 06 08 18:04:07:446#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005000 0006560000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Compone nt \#11,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:04:07:447#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006570000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]# Plain## Recovered# #2.0 #2013 06 08 18:04:07:447#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006590000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5, Workers]#Plain## Recovered# #2.0 #2013 06 08 18:04:07:448#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00500000065B0000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.Un itOfWorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe100 00007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \# 11,5,Workers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:04:07:448#0-700#Error#com.redwood.scheduler.apiint.model.UnitO fWorkManager# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00500000065C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.apiint.model.UnitOf WorkManager#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000000 7e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5 ,Workers]#Plain## Unable to perform persist, and a SchedulerApiRuntimeException occurred; notifyin g worker. [EXCEPTION] JCS-122036: An exception occurred during the execution of a persistence layer me

thod at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.action.ActionComponent$4.performWork(ActionComp onent.java:224) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.action.ActionComponent.processMessages(ActionCo mponent.java:219) at com.redwood.scheduler.action.ActionComponent.onMessage(ActionComponen t.java:183) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 9 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339)

at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 14 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 27 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 30 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 31 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 34 more # #2.0 #2013 06 08 18:04:07:450#0-700#Error#com.redwood.scheduler.action.ActionCompo nent# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00500000065D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.action.ActionCompon ent#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#a bad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers ]#Plain## Error processing messages JCS-122035: Unable to persist: JCS-122036: An exceptio n occurred during the execution of a persistence layer method# #2.0 #2013 06 08 18:04:07:450#0-700#Error#com.redwood.scheduler.action.ActionCompo nent# Error processing messages JCS-122035: Unable to persist: JCS-122036: An exceptio n occurred during the execution of a persistence layer method#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C00500000065F0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.action.ActionComponent#Guest#0##ABAD0E 84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe1 0000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers]#Plain## Error processing messages JCS-122035: Unable to persist: JCS-122036: An exceptio n occurred during the execution of a persistence layer method# #2.0 #2013 06 08 18:04:07:452#0-700#Error#com.redwood.scheduler.action.ActionCompo

nent# JCS-122036: An exception occurred during the execution of a persistence layer me thod#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006610000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.action.ActionCo mponent#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15 ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Wor kers]#Plain## JCS-122036: An exception occurred during the execution of a persistence layer me thod# #2.0 #2013 06 08 18:04:07:452#0-700#Error#com.redwood.scheduler.action.ActionCompo nent# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0050000006620000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.action.ActionCompon ent#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#a bad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Action Component \#11,5,Workers ]#Plain## Error processing messages [EXCEPTION] JCS-122035: Unable to persist: JCS-122036: An exception occurred during the exec ution of a persistence layer method at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:36) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:9) at com.redwood.scheduler.action.ActionComponent.processMessages(ActionCo mponent.java:219) at com.redwood.scheduler.action.ActionComponent.onMessage(ActionComponen t.java:183) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: JCS-122036: An exception occurred during the execution of a persisten ce layer method at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1097) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1080) at com.redwood.scheduler.action.ActionComponent$4.performWork(ActionComp onent.java:224) at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWo rkManager.java:20) ... 6 more Caused by: com.redwood.scheduler.persistence.api.PersistenceException$RecoveryFa iledException: JCS-XXXXX: Recovery failed: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1 )Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719 778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS i s wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for cu rrent load. at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:71) at com.redwood.scheduler.persistence.helper.RecoverySQLExceptionWrapper. wrapSQLException(RecoverySQLExceptionWrapper.java:95) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:45) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut

eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.SchedulerSessionImpl.executeObjectQuery(S chedulerSessionImpl.java:1093) ... 9 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.retry(Re tryThenFailAction.java:88) at com.redwood.scheduler.persistence.helper.RetryThenFailAction.recover( RetryThenFailAction.java:74) ... 14 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 27 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 30 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory . at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 31 more Caused by: java.sql.SQLRecoverableException: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthentica te.java:441) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:505) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate .java:404) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:402) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 34 more

# #2.0 #2013 06 08 18:04:08:406#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008EE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers] #Plain## Attempting recovery# #2.0 #2013 06 08 18:04:08:406#0-700#Error#com.redwood.scheduler.persistence.recove ry# Attempting recovery#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200 0008F00000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. persistence.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2c be10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Compon ent \#13,5,Workers]#Plain## Attempting recovery# #2.0 #2013 06 08 18:04:08:408#0-700#Error#com.redwood.scheduler.persistence.recove ry# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008F10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.recover y#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#aba d0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers] #Plain## Recovered# #2.0 #2013 06 08 18:04:08:408#0-700#Error#com.redwood.scheduler.persistence.recove ry# Recovered#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008F30000 309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistenc e.recovery#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5 ,Workers]#Plain## Recovered# #2.0 #2013 06 08 18:04:53:912#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000020000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:04:43 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 10

#2.0 #2013 06 08 18:04:53:912#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:04:43 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 10 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000040000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:04:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 10

#2.0 #2013 06 08 18:04:53:913#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00

PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:04:43 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 10 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:04:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 10

#2.0 #2013 06 08 18:04:53:913#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000070000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:04:43 2013 720

COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 10

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:04:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 10

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:04:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 10

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:06:23:961#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000000D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:06:13 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286

DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 20

#2.0 #2013 06 08 18:06:23:961#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:06:13 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 20 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000000F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:06:13 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 20

#2.0 #2013 06 08 18:06:23:961#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:06:13 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 20 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:06:13 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 20

#2.0 #2013 06 08 18:06:23:961#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000120000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:06:13 2013 720 NI (network interface)

VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 20

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:06:13 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 20

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:06:13 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 20

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008F40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76806089 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,806,089# #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76806089 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,806,089#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000008F60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76806089 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,806,089# #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump#

JCS-123100: 0 rows updated in tid=76,806,089#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000008F80000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,806,089# #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008F90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76806089 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,806,089 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008FA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76806088> UniqueId=<11213402># #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump#

dirtyObject: [ ] D MonitorMessage:v<76806088> UniqueId=<11213402>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000008FC0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76806088> UniqueId=<11213402># #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000008FD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76805960> UniqueId=<632090># #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76805960> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000008FF0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76805960> UniqueId=<632090># #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009000000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76806089# #2.0 #2013 06 08 18:07:25:914#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76806089#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009020000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76806089# #2.0 #2013 06 08 18:07:53:987#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000180000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:07:43 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 30

#2.0 #2013 06 08 18:07:53:987#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:07:43 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 30 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000001A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:07:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 30

#2.0 #2013 06 08 18:07:53:987#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00

PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:07:43 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 30 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000001C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:07:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 30

#2.0 #2013 06 08 18:07:53:988#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000001D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:07:43 2013 720

COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 30

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:07:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 30

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:07:43 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 30

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:09:24:014#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000230000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:09:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286

DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 40

#2.0 #2013 06 08 18:09:24:014#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:09:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 40 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000250000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:09:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 40

#2.0 #2013 06 08 18:09:24:014#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:09:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 40 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000270000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:09:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 40

#2.0 #2013 06 08 18:09:24:014#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000280000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:09:14 2013 720 NI (network interface)

VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 40

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:09:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 40

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:09:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 40

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:10:54:041#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000002E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:10:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300

SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

connect 111 Connection refused 50

#2.0 #2013 06 08 18:10:54:041#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:10:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 50 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000300000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:10:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 50

#2.0 #2013 06 08 18:10:54:041#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:10:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 50 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000320000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:10:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 50

#2.0 #2013 06 08 18:10:54:041#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000330000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:10:44 2013 720 NI (network interface) 40

RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

-10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 50

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:10:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 50

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:10:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 50

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:12:24:069#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000390000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:12:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect

ERRNO 111 ERRNO TEXT Connection refused COUNTER 60 # #2.0 #2013 06 08 18:12:24:069#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:12:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 60 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000003B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:12:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

#2.0 #2013 06 08 18:12:24:069#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:12:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 60 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000003D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:12:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

#2.0 #2013 06 08 18:12:24:069#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000003E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:12:14 2013 720 NI (network interface) 40 -10

MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:12:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

.perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:12:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 60

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:13:54:096#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000440000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:13:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111

ERRNO TEXT Connection refused COUNTER 70 # #2.0 #2013 06 08 18:13:54:096#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:13:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 70 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000460000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:13:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 70

#2.0 #2013 06 08 18:13:54:096#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached

TIME Sat Jun 8 18:13:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 70 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000480000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:13:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 70

#2.0 #2013 06 08 18:13:54:096#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000490000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:13:44 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 70

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:13:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 70

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:13:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 70

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:15:24:124#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000004F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused

COUNTER #

80

#2.0 #2013 06 08 18:15:24:124#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:15:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 80 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000510000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 80

#2.0 #2013 06 08 18:15:24:124#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013

RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 80 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000530000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 80

#2.0 #2013 06 08 18:15:24:124#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000540000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286

DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 80

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 80

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:15:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 80

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009030000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76809602 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,809,602# #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76809602 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,809,602#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009050000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76809602 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,809,602# #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,809,602#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009070000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[

Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,809,602# #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009080000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76809602 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,809,602 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009090000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76809601> UniqueId=<11213784># #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76809601> UniqueId=<11213784>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C00520000090B0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10

000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76809601> UniqueId=<11213784># #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000090C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76809388> UniqueId=<662183># #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76809388> UniqueId=<662183>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C00520000090E0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76809388> UniqueId=<662183># #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000090F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76809602# #2.0 #2013 06 08 18:16:31:270#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76809602#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009110000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76809602# #2.0 #2013 06 08 18:16:54:152#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000005A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:16:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111

ERRNO TEXT Connection refused COUNTER 90 # #2.0 #2013 06 08 18:16:54:152#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:16:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 90 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000005C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:16:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 90

#2.0 #2013 06 08 18:16:54:152#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached

TIME Sat Jun 8 18:16:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 90 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000005E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:16:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 90

#2.0 #2013 06 08 18:16:54:152#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000005F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:16:44 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 90

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:16:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 90

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:16:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 90

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009120000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76810128 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,810,128# #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76810128 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,810,128#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009140000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76810128 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,810,128# #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,810,128#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009160000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E

15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,810,128# #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009170000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76810128 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,810,128 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009180000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76810127> UniqueId=<11213831># #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76810127> UniqueId=<11213831>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C00520000091A0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8

4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76810127> UniqueId=<11213831># #2.0 #2013 06 08 18:18:02:194#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000091B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76809971> UniqueId=<632090># #2.0 #2013 06 08 18:18:02:195#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76809971> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C00520000091D0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76809971> UniqueId=<632090># #2.0 #2013 06 08 18:18:02:195#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000091E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76810128# #2.0 #2013 06 08 18:18:02:195#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76810128#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009200000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76810128# #2.0 #2013 06 08 18:18:24:180#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000650000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:18:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect

ERRNO 111 ERRNO TEXT Connection refused COUNTER 100 # #2.0 #2013 06 08 18:18:24:180#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:18:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 100 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000670000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:18:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 100

#2.0 #2013 06 08 18:18:24:180#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:18:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 100 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000690000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:18:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 100

#2.0 #2013 06 08 18:18:24:180#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000006A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:18:14 2013 720 NI (network interface) 40 -10

MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 100

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:18:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 100

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

.perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:18:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 100

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:19:54:208#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000700000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:19:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111

ERRNO TEXT Connection refused COUNTER 110 # #2.0 #2013 06 08 18:19:54:208#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:19:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 110 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000720000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:19:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 110

#2.0 #2013 06 08 18:19:54:208#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached

TIME Sat Jun 8 18:19:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 110 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000740000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:19:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 110

#2.0 #2013 06 08 18:19:54:208#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000750000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:19:44 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 110

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:19:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 110

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:19:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 110

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:21:24:237#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000007B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused

COUNTER #

120

#2.0 #2013 06 08 18:21:24:237#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:21:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 120 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000007D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 120

#2.0 #2013 06 08 18:21:24:237#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013

RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 120 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000007F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 120

#2.0 #2013 06 08 18:21:24:237#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000800000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286

DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER

NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 120

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 120

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:21:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 120

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:22:54:264#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000860000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 130

# #2.0 #2013 06 08 18:22:54:264#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:22:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 130 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000880000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 130

#2.0 #2013 06 08 18:22:54:264#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720

COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 130 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000008A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 130

#2.0 #2013 06 08 18:22:54:264#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000008B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300

SYSTEM CALL ERRNO ERRNO TEXT COUNTER

connect 111 Connection refused 130

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 130

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:22:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 130

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:24:24:292#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000910000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 140

#2.0 #2013 06 08 18:24:24:293#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:24:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 140 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000930000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 140

#2.0 #2013 06 08 18:24:24:293#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface)

VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 140 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000950000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 140

#2.0 #2013 06 08 18:24:24:293#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect

ERRNO 111 ERRNO TEXT Connection refused COUNTER 140 at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 140

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:24:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 140

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009210000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76812564 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,812,564# #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76812564 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,812,564#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009230000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76812564 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,812,564# #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,812,564#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009250000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,812,564#

#2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009260000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76812564 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,812,564 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009270000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76812563> UniqueId=<11214068># #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76812563> UniqueId=<11214068>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009290000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76812563> UniqueId=<11214068>#

#2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000092A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76812346> UniqueId=<665675># #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76812346> UniqueId=<665675>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C00520000092C0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76812346> UniqueId=<665675># #2.0 #2013 06 08 18:24:36:093#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000092D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76812564# #2.0 #2013 06 08 18:24:36:094#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76812564#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C00520000092F0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76812564# #2.0 #2013 06 08 18:25:54:320#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000009C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 150

# #2.0 #2013 06 08 18:25:54:320#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:25:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 150 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000009E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 150

#2.0 #2013 06 08 18:25:54:320#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720

COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 150 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000A00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 150

#2.0 #2013 06 08 18:25:54:320#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000A10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300

SYSTEM CALL ERRNO ERRNO TEXT COUNTER

connect 111 Connection refused 150

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 150

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:25:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 150

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:27:24:347#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000A70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 160

#2.0 #2013 06 08 18:27:24:348#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:27:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 160 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000A90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 160

#2.0 #2013 06 08 18:27:24:348#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface)

VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 160 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000AB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 160

#2.0 #2013 06 08 18:27:24:348#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000AC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect

ERRNO 111 ERRNO TEXT Connection refused COUNTER 160 at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 160

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:27:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 160

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:28:54:376#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000B20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 170

#2.0 #2013 06 08 18:28:54:376#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:28:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 170 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000B40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 170

#2.0 #2013 06 08 18:28:54:376#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40

RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 170 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000B60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 170

#2.0 #2013 06 08 18:28:54:376#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000B70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111

ERRNO TEXT Connection refused COUNTER 170 at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 170

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:28:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 170

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:30:24:403#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000BD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 180

#2.0 #2013 06 08 18:30:24:404#0-700#Error#com.redwood.scheduler.connector.sap.rfc.

connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:30:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 180 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000BF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 180

#2.0 #2013 06 08 18:30:24:404#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10

MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 180 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000C10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 180

#2.0 #2013 06 08 18:30:24:404#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000C20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused

COUNTER

180

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 180

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:30:14 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 180

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:31:20:778#0-700#Error#com.redwood.scheduler.ui.theme.ResourceS ervlet# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01CA000000000000309A#8263 150000000004#redwood.com/scheduler-ear#com.redwood.scheduler.ui.theme.ResourceSe rvlet#jcarlson#4##40A8B96AD0A411E28AFE0000007E15EE#49d604f3d0a411e2905e0000007e1 5ee#49d604f3d0a411e2905e0000007e15ee#0#Thread[HTTP Worker [@1699906070],5,Dedica ted_Application_Thread]#Plain## Unable to find /black/javascript/clear.cache.gif# #2.0 #2013 06 08 18:31:20:779#0-700#Error#com.redwood.scheduler.ui.theme.ResourceS ervlet# Unable to find /black/javascript/clear.cache.gif#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01CA000000020000309A#8263150000000004#redwood.com/schedul er-ear#com.redwood.scheduler.ui.theme.ResourceServlet#jcarlson#4##40A8B96AD0A411 E28AFE0000007E15EE#49d604f3d0a411e2905e0000007e15ee#49d604f3d0a411e2905e0000007e 15ee#0#Thread[HTTP Worker [@1699906070],5,Dedicated_Application_Thread]#Plain## Unable to find /black/javascript/clear.cache.gif# #2.0 #2013 06 08 18:31:54:431#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000C80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:31:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 190

#2.0 #2013 06 08 18:31:54:431#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:31:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 190 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000CA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:31:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111

ERRNO TEXT Connection refused COUNTER 190 # #2.0 #2013 06 08 18:31:54:431#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:31:44 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 190 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:31:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 190

#2.0 #2013 06 08 18:31:54:431#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000CD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION]

Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:31:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 190

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:31:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 190

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:31:44 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 190

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:32:32:007#0-700#Error#com.redwood.scheduler.ui.theme.ResourceS ervlet# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01D0000000000000309A#8263 150000000004#redwood.com/scheduler-ear#com.redwood.scheduler.ui.theme.ResourceSe rvlet#jcarlson#5##540B351AD0A411E29BD50000007E15EE#71109040d0a411e280bf0000007e1 5ee#71109040d0a411e280bf0000007e15ee#0#Thread[HTTP Worker [@1632377357],5,Dedica ted_Application_Thread]#Plain## Unable to find /black/javascript/clear.cache.gif# #2.0 #2013 06 08 18:32:32:007#0-700#Error#com.redwood.scheduler.ui.theme.ResourceS ervlet# Unable to find /black/javascript/clear.cache.gif#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01D0000000020000309A#8263150000000004#redwood.com/schedul er-ear#com.redwood.scheduler.ui.theme.ResourceServlet#jcarlson#5##540B351AD0A411

E29BD50000007E15EE#71109040d0a411e280bf0000007e15ee#71109040d0a411e280bf0000007e 15ee#0#Thread[HTTP Worker [@1632377357],5,Dedicated_Application_Thread]#Plain## Unable to find /black/javascript/clear.cache.gif# #2.0 #2013 06 08 18:32:41:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009300000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76815586 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,815,586# #2.0 #2013 06 08 18:32:41:401#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76815586 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,815,586#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009320000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76815586 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,815,586# #2.0 #2013 06 08 18:32:41:401#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,815,586#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009340000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,815,586# #2.0 #2013 06 08 18:32:41:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009350000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76815586 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,815,586 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)

at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:32:41:402#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76815585> UniqueId=<11214444># #2.0 #2013 06 08 18:32:41:402#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76815585> UniqueId=<11214444>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009380000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76815585> UniqueId=<11214444># #2.0 #2013 06 08 18:32:41:402#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009390000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76815467> UniqueId=<837591># #2.0 #2013 06 08 18:32:41:402#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76815467> UniqueId=<837591>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C00520000093B0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76815467> UniqueId=<837591># #2.0 #2013 06 08 18:32:41:402#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000093C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76815586# #2.0 #2013 06 08 18:32:41:402#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76815586#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9

8C00520000093E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76815586# #2.0 #2013 06 08 18:38:24:523#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000D30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:38:14 2013 720 NI (network interface) 40 -10 nibuf.cpp 4658 NiBufIConnect: connection pending after 60000ms connect 115 Operation now in progress 200

#2.0 #2013 06 08 18:38:24:523#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:38:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nibuf.cpp LINE 4658 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 115 ERRNO TEXT Operation now in progress COUNTER 200 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000D50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser

vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:38:14 2013 720 NI (network interface) 40 -10 nibuf.cpp 4658 NiBufIConnect: connection pending after 60000ms connect 115 Operation now in progress 200

#2.0 #2013 06 08 18:38:24:523#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:38:14 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nibuf.cpp LINE 4658 DETAIL NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO 115 ERRNO TEXT Operation now in progress COUNTER 200 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000D70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:38:14 2013 720 NI (network interface) 40 -10

MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

nibuf.cpp 4658 NiBufIConnect: connection pending after 60000ms connect 115 Operation now in progress 200

#2.0 #2013 06 08 18:38:24:523#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000D80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:38:14 2013 720 NI (network interface) 40 -10 nibuf.cpp 4658 NiBufIConnect: connection pending after 60000ms connect 115 Operation now in progress 200

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:38:14 2013 720 NI (network interface) 40 -10 nibuf.cpp 4658 NiBufIConnect: connection pending after 60000ms connect 115 Operation now in progress 200

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:38:14 2013 720 NI (network interface) 40 -10 nibuf.cpp 4658 NiBufIConnect: connection pending after 60000ms connect 115 Operation now in progress 200

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092

) ... 14 more # #2.0 #2013 06 08 18:40:15:549#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000DE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:40:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 210

#2.0 #2013 06 08 18:40:15:550#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:40:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 210 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000E00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5

,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:40:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 210

#2.0 #2013 06 08 18:40:15:550#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:40:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 210 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000E20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:40:05 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 210

#2.0 #2013 06 08 18:40:15:550#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000E30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:40:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 210

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:40:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 210

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:40:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 210

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 )

... 14 more # #2.0 #2013 06 08 18:40:46:185#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000093F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76817917 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,817,917# #2.0 #2013 06 08 18:40:46:185#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76817917 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,817,917#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009410000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76817917 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,817,917# #2.0 #2013 06 08 18:40:46:185#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,817,917#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009430000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,817,917# #2.0 #2013 06 08 18:40:46:185#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009440000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76817917 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,817,917 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)

at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:40:46:186#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009450000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76817916> UniqueId=<11214681># #2.0 #2013 06 08 18:40:46:186#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76817916> UniqueId=<11214681>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009470000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76817916> UniqueId=<11214681># #2.0 #2013 06 08 18:40:46:186#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009480000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76817687> UniqueId=<665675># #2.0 #2013 06 08 18:40:46:186#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76817687> UniqueId=<665675>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C00520000094A0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76817687> UniqueId=<665675># #2.0 #2013 06 08 18:40:46:186#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000094B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76817917# #2.0 #2013 06 08 18:40:46:186#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76817917#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9

8C00520000094D0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76817917# #2.0 #2013 06 08 18:41:45:575#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000E90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:41:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 220

#2.0 #2013 06 08 18:41:45:575#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:41:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 220 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000EB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser

vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:41:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 220

#2.0 #2013 06 08 18:41:45:575#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:41:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 220 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000ED0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:41:35 2013 720 NI (network interface) 40 -10

MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 220

#2.0 #2013 06 08 18:41:45:575#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000EE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:41:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 220

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:41:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 220

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:41:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 220

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092

) ... 14 more # #2.0 #2013 06 08 18:42:47:388#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000094E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76818477 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,818,477# #2.0 #2013 06 08 18:42:47:388#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76818477 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,818,477#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009500000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76818477 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,818,477# #2.0 #2013 06 08 18:42:47:388#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,818,477#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009520000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,818,477# #2.0 #2013 06 08 18:42:47:388#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009530000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76818477 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,818,477 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc

e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:42:47:388#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009540000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76818476> UniqueId=<11214741># #2.0 #2013 06 08 18:42:47:389#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76818476> UniqueId=<11214741>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009560000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76818476> UniqueId=<11214741># #2.0 #2013 06 08 18:42:47:389#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009570000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76818246> UniqueId=<632090># #2.0 #2013 06 08 18:42:47:389#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76818246> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009590000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76818246> UniqueId=<632090># #2.0 #2013 06 08 18:42:47:389#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000095A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76818477# #2.0 #2013 06 08 18:42:47:389#0-700#Error#com.redwood.scheduler.persistence.tdump#

End Transaction id=76818477#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C00520000095C0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76818477# #2.0 #2013 06 08 18:43:15:604#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000F40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:43:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 230

#2.0 #2013 06 08 18:43:15:605#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:43:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 230 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000F60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E

E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:43:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 230

#2.0 #2013 06 08 18:43:15:605#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:43:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 230 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000F80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:43:05 2013 720 NI (network interface) 40

RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

-10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 230

#2.0 #2013 06 08 18:43:15:605#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000F90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:43:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 230

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00

PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:43:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 230 CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:43:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 230

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more # #2.0 #2013 06 08 18:44:45:631#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000000FF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:44:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 240

#2.0 #2013 06 08 18:44:45:631#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:44:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 240 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser

vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:44:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 240

#2.0 #2013 06 08 18:44:45:631#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:44:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 240 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001030000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:44:35 2013 720 NI (network interface) 40 -10

MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 240

#2.0 #2013 06 08 18:44:45:631#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001040000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:44:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 240

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:44:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 240

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:44:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 240

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092

) ... 14 more # #2.0 #2013 06 08 18:46:15:657#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000010A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:46:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 250

#2.0 #2013 06 08 18:46:15:658#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:46:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 250 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000010C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5

,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:46:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 250

#2.0 #2013 06 08 18:46:15:658#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:46:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 250 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000010E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:46:05 2013 720 NI (network interface) 40 -10 nixxi.cpp

LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 250

#2.0 #2013 06 08 18:46:15:658#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000010F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:46:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 250

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1

LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:46:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 250

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:46:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 250

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 )

... 14 more # #2.0 #2013 06 08 18:47:45:684#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001150000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:47:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 260

#2.0 #2013 06 08 18:47:45:684#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:47:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 260 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001170000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain##

Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:47:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 260

#2.0 #2013 06 08 18:47:45:684#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:47:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 260 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001190000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:47:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286

DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 260

#2.0 #2013 06 08 18:47:45:684#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000011A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:47:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 260

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:47:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 260

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:47:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 260

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more

# #2.0 #2013 06 08 18:49:15:716#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001200000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:49:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 270

#2.0 #2013 06 08 18:49:15:717#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:49:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 270 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001220000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway

failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:49:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 270

#2.0 #2013 06 08 18:49:15:717#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:49:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 270 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001240000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:49:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300

SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

connect 111 Connection refused 270

#2.0 #2013 06 08 18:49:15:717#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001250000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:49:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 270

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached

TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

Sat Jun 8 18:49:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 270

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:49:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 270

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more

# #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000095D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76820497 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,820,497# #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76820497 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,820,497#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C00520000095F0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76820497 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,820,497# #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,820,497#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009610000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,820,497# #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009620000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76820497 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,820,497 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910)

at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009630000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76820496> UniqueId=<11214985># #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76820496> UniqueId=<11214985>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009650000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76820496> UniqueId=<11214985># #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009660000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76820265> UniqueId=<660760># #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76820265> UniqueId=<660760>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009680000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76820265> UniqueId=<660760># #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009690000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76820497# #2.0 #2013 06 08 18:49:51:401#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76820497#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C00520000096B0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051

11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76820497# #2.0 #2013 06 08 18:50:45:743#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000012B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:50:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 280

#2.0 #2013 06 08 18:50:45:743#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:50:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 280 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000012D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain##

Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:50:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 280

#2.0 #2013 06 08 18:50:45:743#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:50:35 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 280 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000012F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:50:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286

DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 280

#2.0 #2013 06 08 18:50:45:743#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001300000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:50:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 280

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:50:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 280

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:50:35 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 280

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more

# #2.0 #2013 06 08 18:52:15:770#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001360000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:52:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 290

#2.0 #2013 06 08 18:52:15:770#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:52:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 290 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A4000001380000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system Exception: 102: Connect to SAP gateway

failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER # CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:52:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 290

#2.0 #2013 06 08 18:52:15:771#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.220.162.190:sapgw00' not reached TIME Sat Jun 8 18:52:05 2013 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 3286 DETAIL NiPConnect2: 10.220.162.190:3300 SYSTEM CALL connect ERRNO 111 ERRNO TEXT Connection refused COUNTER 290 #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000013A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:52:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300

SYSTEM CALL ERRNO ERRNO TEXT COUNTER #

connect 111 Connection refused 290

#2.0 #2013 06 08 18:52:15:771#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01A40000013B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Ser vice starter: SAP Service for instance P01 on process server P01_ProcessServer,5 ,SAP Services]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:52:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 290

at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.connection.impl.AbstractRfcCo nnectionPoolManager.getConnectionPool(AbstractRfcConnectionPoolManager.java:143) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eConnectionPool(SapComponent.java:212) at com.redwood.scheduler.connector.sap.rfc.connection.SapComponent.creat eXbpConnectionPool(SapComponent.java:156) at com.redwood.scheduler.connector.sap.rfc.service.SapService$SapService Startup.run(SapService.java:187) Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached

TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER a:557)

Sat Jun 8 18:52:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 290

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 8 more Caused by: RfcException: message: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=/H/ASHSUX02 SYSNR=00 GWHOST=/H/ASHSUX02 GWSERV=sapgw00 PCS=1 LOCATION ERROR TIME RELEASE COMPONENT VERSION RC MODULE LINE DETAIL SYSTEM CALL ERRNO ERRNO TEXT COUNTER CPIC (TCP/IP) on local host with Unicode partner '10.220.162.190:sapgw00' not reached Sat Jun 8 18:52:05 2013 720 NI (network interface) 40 -10 nixxi.cpp 3286 NiPConnect2: 10.220.162.190:3300 connect 111 Connection refused 290

Return code: RFC_FAILURE(1) error group: 102 key: RFC_ERROR_COMMUNICATION at com.sap.mw.rfc.engine.RfcIoControl.error_end(RfcIoControl.java:348) at com.sap.mw.rfc.engine.RfcIoControl.ab_rfcopen(RfcIoControl.java:152) at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:712) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 14 more

# #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000096C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76821899 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,821,899# #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76821899 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,821,899#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C00520000096E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76821899 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,821,899# #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,821,899#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009700000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,821,899# #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009710000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76821899 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,821,899 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910)

at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009720000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76821898> UniqueId=<11215166># #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76821898> UniqueId=<11215166>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009740000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76821898> UniqueId=<11215166># #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009750000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76821668> UniqueId=<632090># #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76821668> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009770000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76821668> UniqueId=<632090># #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009780000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76821899# #2.0 #2013 06 08 18:54:54:336#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76821899#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C00520000097A0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051

11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76821899# #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000097B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76821940 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,821,940# #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76821940 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,821,940#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C00520000097D0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76821940 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,821,940# #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,821,940#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C00520000097F0000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,821,940# #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009800000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76821940 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,821,940 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90)

at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009810000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76821939> UniqueId=<11215172># #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76821939> UniqueId=<11215172>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009830000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76821939> UniqueId=<11215172># #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009840000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76821893> UniqueId=<665675># #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76821893> UniqueId=<665675>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009860000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76821893> UniqueId=<665675># #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009870000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76821940# #2.0 #2013 06 08 18:55:24:583#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76821940#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9

8C0052000009890000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76821940# #2.0 #2013 06 08 18:59:01:835#0-700#Error#com.redwood.scheduler.ui.theme.ResourceS ervlet# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01E3000000000000309A#8263 150000000004#redwood.com/scheduler-ear#com.redwood.scheduler.ui.theme.ResourceSe rvlet#tbudinav#6##0B585766D0A811E29B660000007E15EE#24498a6bd0a811e2a4c70000007e1 5ee#24498a6bd0a811e2a4c70000007e15ee#0#Thread[HTTP Worker [@1811723112],5,Dedica ted_Application_Thread]#Plain## Unable to find /black/javascript/clear.cache.gif# #2.0 #2013 06 08 18:59:01:835#0-700#Error#com.redwood.scheduler.ui.theme.ResourceS ervlet# Unable to find /black/javascript/clear.cache.gif#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C01E3000000020000309A#8263150000000004#redwood.com/schedul er-ear#com.redwood.scheduler.ui.theme.ResourceServlet#tbudinav#6##0B585766D0A811 E29B660000007E15EE#24498a6bd0a811e2a4c70000007e15ee#24498a6bd0a811e2a4c70000007e 15ee#0#Thread[HTTP Worker [@1811723112],5,Dedicated_Application_Thread]#Plain## Unable to find /black/javascript/clear.cache.gif# #2.0 #2013 06 08 19:05:30:302#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000098A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76824855 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,824,855# #2.0 #2013 06 08 19:05:30:302#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76824855 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,824,855#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C00520000098C0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76824855 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,824,855# #2.0 #2013 06 08 19:05:30:302#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,824,855#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C00520000098E0000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,824,855# #2.0 #2013 06 08 19:05:30:302#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000098F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain##

Start Transaction id=76824855 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,824,855 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:05:30:303#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009900000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76824854> UniqueId=<11215556># #2.0 #2013 06 08 19:05:30:303#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76824854> UniqueId=<11215556>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009920000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76824854> UniqueId=<11215556># #2.0 #2013 06 08 19:05:30:303#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009930000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain##

dirtyObject: [x] V MonitorCheck:v<76824821> UniqueId=<662183># #2.0 #2013 06 08 19:05:30:303#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76824821> UniqueId=<662183>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009950000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76824821> UniqueId=<662183># #2.0 #2013 06 08 19:05:30:303#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009960000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76824855# #2.0 #2013 06 08 19:05:30:303#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76824855#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009980000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76824855# #2.0 #2013 06 08 19:10:33:147#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009990000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76826321 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,826,321# #2.0 #2013 06 08 19:10:33:147#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76826321 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,826,321#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C00520000099B0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76826321 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,826,321# #2.0 #2013 06 08 19:10:33:147#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,826,321#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C00520000099D0000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,826,321# #2.0 #2013 06 08 19:10:33:147#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000099E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e

84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76826321 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,826,321 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:10:33:147#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00520000099F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76826320> UniqueId=<11215702># #2.0 #2013 06 08 19:10:33:148#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76826320> UniqueId=<11215702>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009A10000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76826320> UniqueId=<11215702># #2.0 #2013 06 08 19:10:33:148#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009A20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e

84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76826199> UniqueId=<662538># #2.0 #2013 06 08 19:10:33:148#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76826199> UniqueId=<662538>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009A40000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76826199> UniqueId=<662538># #2.0 #2013 06 08 19:10:33:148#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009A50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76826321# #2.0 #2013 06 08 19:10:33:148#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76826321#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009A70000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76826321# #2.0 #2013 06 08 19:10:33:157#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009A80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76826324 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,826,324# #2.0 #2013 06 08 19:10:33:157#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76826324 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,826,324#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009AA0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76826324 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,826,324# #2.0 #2013 06 08 19:10:33:157#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,826,324#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009AC0000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,826,324# #2.0 #2013 06 08 19:10:33:157#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009AD0000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76826324 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,826,324 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:10:33:157#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009AE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76826322> UniqueId=<11215703># #2.0 #2013 06 08 19:10:33:158#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76826322> UniqueId=<11215703>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009B00000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76826322> UniqueId=<11215703># #2.0 #2013 06 08 19:10:33:158#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009B10000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76826201> UniqueId=<665675># #2.0 #2013 06 08 19:10:33:158#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76826201> UniqueId=<665675>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009B30000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76826201> UniqueId=<665675># #2.0 #2013 06 08 19:10:33:158#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009B40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76826324# #2.0 #2013 06 08 19:10:33:158#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76826324#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009B60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76826324# #2.0 #2013 06 08 19:30:48:999#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F6000000010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PC1_ProcessServer: ApplicationServerLoadMonitoringComponent for PC1 \#3d, 5,Workers]#Plain## Exception Exception: 104: 00024No connect to database, session terminated??????? ???????????????????# #2.0 #2013 06 08 19:30:48:999#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# Exception Exception: 104: 00024No connect to database, session terminated??????? ???????????????????#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F600 0000030000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. connector.sap.rfc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood SapService PC1_ProcessServer: ApplicationServerLoadMonitoringComp onent for PC1 \#3d,5,Workers]#Plain## Exception Exception: 104: 00024No connect to database, session terminated??????? ???????????????????# #2.0 #2013 06 08 19:30:48:999#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F6000000050000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.componen ts.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111 e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService

PC1_ProcessServer: ApplicationServerLoadMonitoringComponent for PC1 \#3d,5,Worke rs]#Plain## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:30:48:999#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F6000000060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PC1_ProcessServer: ApplicationServerLoadMonitoringComponent for PC1 \#3d, 5,Workers]#Plain## Exception [EXCEPTION] Exception: 104: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:222) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.execute(AbstractRfcConnection.java:294) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunct ionModuleWrapper.execute(SapFunctionModuleWrapper.java:200) at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule .execute(AbstractSapFunctionModule.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:195) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: Exception while calling BAPI_XBP_GET_CURR_BP_RESOURCES: 104: 00024No connect to database, session terminated?????????????????????????? at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientCo nnectionImpl.call(ClientConnectionImpl.java:492) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$4.doPerform(AbstractRfcConnection.java:301) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: 00024No connect to database, session terminated?????????????????????????? (raised by sy stem PC1|ashs91271) at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:555) at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1526 ) at com.sap.mw.jco.JCO$Client.execute(JCO.java:4401) at com.sap.mw.jco.JCO$Client.execute(JCO.java:3917) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientCo nnectionImpl.call(ClientConnectionImpl.java:463) ... 12 more

Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_SYS_EXCEPTION(3) error group: 104 key: RFC_ERROR_SYSTEM_FAILURE Exception raised by PC1|ashs91271 at com.sap.mw.rfc.api.RfcApi.RfcReceive(RfcApi.java:1134) at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1496 ) ... 15 more # #2.0 #2013 06 08 19:30:57:424#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000010000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35, 5,Workers]#Plain## Exception Exception: 104: 00024No connect to database, session terminated??????? ???????????????????# #2.0 #2013 06 08 19:30:57:424#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# Exception Exception: 104: 00024No connect to database, session terminated??????? ???????????????????#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F700 0000030000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler. connector.sap.rfc.components.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComp onent for PBI \#35,5,Workers]#Plain## Exception Exception: 104: 00024No connect to database, session terminated??????? ???????????????????# #2.0 #2013 06 08 19:30:57:425#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000050000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.componen ts.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111 e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Worke rs]#Plain## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:30:57:425#0-700#Error#com.redwood.scheduler.connector.sap.rfc. components.AbstractSapInterface# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000060000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c omponents.AbstractSapInterface#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e8 4d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapS ervice PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35, 5,Workers]#Plain## Exception [EXCEPTION] Exception: 104: 00024No connect to database, session terminated?????????????????

????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:222) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.execute(AbstractRfcConnection.java:294) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunct ionModuleWrapper.execute(SapFunctionModuleWrapper.java:200) at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule .execute(AbstractSapFunctionModule.java:109) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:195) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: Exception while calling BAPI_XBP_GET_CURR_BP_RESOURCES: 104: 00024No connect to database, session terminated?????????????????????????? at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientCo nnectionImpl.call(ClientConnectionImpl.java:492) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$4.doPerform(AbstractRfcConnection.java:301) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: 00024No connect to database, session terminated?????????????????????????? (raised by sy stem PBW|ashs91274) at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:555) at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1526 ) at com.sap.mw.jco.JCO$Client.execute(JCO.java:4401) at com.sap.mw.jco.JCO$Client.execute(JCO.java:3917) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientCo nnectionImpl.call(ClientConnectionImpl.java:463) ... 12 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_SYS_EXCEPTION(3) error group: 104 key: RFC_ERROR_SYSTEM_FAILURE Exception raised by PBW|ashs91274 at com.sap.mw.rfc.api.RfcApi.RfcReceive(RfcApi.java:1134) at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1496 ) ... 15 more #

#2.0 #2013 06 08 19:33:19:734#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F6000000070000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: ApplicationServerLoadMonitoringComponent for PC1 \#3d,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:33:19:734#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F6000000090000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: ApplicationServerLoadMonitoringComponent for PC1 \#3d,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:33:19:735#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F60000000B0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PC1_ProcessServer: ApplicationServerLoadMonitoringComponent for PC1 \#3 d,5,Workers]#Plain## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:33:19:735#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F60000000C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: ApplicationServerLoadMonitoringComponent for PC1 \#3d,5,Workers]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:186) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio

nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:33:37:828#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000070000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:33:37:829#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F7000000090000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer

ver: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:33:37:829#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F70000000B0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#3 5,5,Workers]#Plain## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:33:37:829#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F70000000C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.monitorLoad(ApplicationServerLoadMonitoringCompon ent.java:186) at com.redwood.scheduler.connector.sap.rfc.service.components.Applicatio nServerLoadMonitoringComponent.execute(ApplicationServerLoadMonitoringComponent. java:134) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect

ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:34:58:024#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000000000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:34:58:024#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F8000000020000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:34:58:024#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000040000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Pla in## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:34:58:024#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000050000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c

onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more #

#2.0 #2013 06 08 19:35:26:269#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000000000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:35:26:269#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F9000000020000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#33,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:35:26:269#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000040000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers]#Plain ## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:35:26:269#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000050000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo

nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:35:47:638#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009B70000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76833527 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,833,527# #2.0 #2013 06 08 19:35:47:638#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76833527 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,833,527#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009B90000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76833527 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro

ws updated in tid=76,833,527# #2.0 #2013 06 08 19:35:47:638#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,833,527#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009BB0000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,833,527# #2.0 #2013 06 08 19:35:47:638#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009BC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76833527 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,833,527 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:35:47:638#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009BD0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain##

dirtyObject: [ ] D MonitorMessage:v<76833526> UniqueId=<11216551># #2.0 #2013 06 08 19:35:47:639#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76833526> UniqueId=<11216551>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009BF0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76833526> UniqueId=<11216551># #2.0 #2013 06 08 19:35:47:639#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009C00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76833297> UniqueId=<632090># #2.0 #2013 06 08 19:35:47:639#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76833297> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009C20000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76833297> UniqueId=<632090># #2.0 #2013 06 08 19:35:47:639#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009C30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76833527# #2.0 #2013 06 08 19:35:47:639#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76833527#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009C50000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76833527# #2.0 #2013 06 08 19:36:48:409#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009C60000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76833798 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,833,798# #2.0 #2013 06 08 19:36:48:409#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76833798 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,833,798#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009C80000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain##

Start Transaction id=76833798 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,833,798# #2.0 #2013 06 08 19:36:48:409#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,833,798#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009CA0000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,833,798# #2.0 #2013 06 08 19:36:48:409#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009CB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76833798 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,833,798 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:36:48:410#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009CC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e

84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76833797> UniqueId=<11216576># #2.0 #2013 06 08 19:36:48:410#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76833797> UniqueId=<11216576>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009CE0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76833797> UniqueId=<11216576># #2.0 #2013 06 08 19:36:48:410#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009CF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76833572> UniqueId=<660760># #2.0 #2013 06 08 19:36:48:410#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76833572> UniqueId=<660760>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009D10000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76833572> UniqueId=<660760># #2.0 #2013 06 08 19:36:48:410#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009D20000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76833798# #2.0 #2013 06 08 19:36:48:410#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76833798#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009D40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76833798# #2.0 #2013 06 08 19:37:38:915#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000080000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:37:38:915#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F80000000A0000309A#8263150000000492#redwood.com/sched

uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:37:38:915#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F80000000C0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Pla in## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:37:38:915#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F80000000D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130)

at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:38:20:008#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000080000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:38:20:008#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F90000000A0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#33,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:38:20:008#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F90000000C0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers]#Plain ## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:38:20:008#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F90000000D0000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more

# #2.0 #2013 06 08 19:40:19:747#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000100000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:40:19:747#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F8000000120000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:40:19:747#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000140000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Pla in## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:40:19:747#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000150000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167)

at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:41:08:176#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000100000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:41:08:176#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F9000000120000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer

ver: JobMonitoringComponent for PBI \#33,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:41:08:176#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000140000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers]#Plain ## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:41:08:176#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000150000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository

Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009D50000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76834939 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,939# #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76834939 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,939#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009D70000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76834939 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,939# #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,834,939#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009D90000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,834,939# #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009DA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76834939 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,834,939

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009DB0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76834938> UniqueId=<11216698># #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76834938> UniqueId=<11216698>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009DD0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76834938> UniqueId=<11216698># #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009DE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76834893> UniqueId=<662538># #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76834893> UniqueId=<662538>#XX-PART-REDWOOD#re

dwood.com/scheduler-ear#C0000ADCD98C0052000009E00000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76834893> UniqueId=<662538># #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009E10000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76834939# #2.0 #2013 06 08 19:41:21:056#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76834939#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009E30000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76834939# #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009E40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76834948 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,948# #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76834948 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,948#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009E60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76834948 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,948# #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,834,948#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009E80000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,834,948# #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009E90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76834948 contains 2 objects. Persistence Error: [EXCEPTION]

com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,834,948 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009EA0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76834947> UniqueId=<11216702># #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76834947> UniqueId=<11216702>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009EC0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76834947> UniqueId=<11216702># #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009ED0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76834901> UniqueId=<632090>#

#2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76834901> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009EF0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76834901> UniqueId=<632090># #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009F00000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76834948# #2.0 #2013 06 08 19:41:21:109#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76834948#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C0052000009F20000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76834948# #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009F30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76834951 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,951# #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76834951 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,951#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C0052000009F50000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76834951 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,834,951# #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,834,951#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C0052000009F70000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,834,951# #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009F80000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain##

Start Transaction id=76834951 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,834,951 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009F90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76834950> UniqueId=<11216703># #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76834950> UniqueId=<11216703>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C0052000009FB0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76834950> UniqueId=<11216703># #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009FC0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain##

dirtyObject: [x] V MonitorCheck:v<76834903> UniqueId=<662183># #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76834903> UniqueId=<662183>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C0052000009FE0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76834903> UniqueId=<662183># #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0052000009FF0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76834951# #2.0 #2013 06 08 19:41:21:125#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76834951#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C005200000A010000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76834951# #2.0 #2013 06 08 19:43:00:595#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F8000000180000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:43:00:596#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F80000001A0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PC1_ProcessSer ver: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:43:00:596#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F80000001C0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Workers]#Pla in## 00024No connect to database, session terminated??????????????????????????#

#2.0 #2013 06 08 19:43:00:596#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F80000001D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PC1_ProcessServer: XbpSynchronizerComponent for PC1 \#3c,5,Worke rs]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092

) ... 16 more # #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A020000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76835741 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,835,741# #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76835741 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,835,741#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C005200000A040000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76835741 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,835,741# #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,835,741#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C005200000A060000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,835,741# #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A070000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76835741 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,835,741 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc

e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A080000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76835740> UniqueId=<11216831># #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76835740> UniqueId=<11216831>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C005200000A0A0000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76835740> UniqueId=<11216831># #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A0B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76835500> UniqueId=<837591># #2.0 #2013 06 08 19:43:52:664#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76835500> UniqueId=<837591>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C005200000A0D0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76835500> UniqueId=<837591># #2.0 #2013 06 08 19:43:52:665#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A0E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76835741# #2.0 #2013 06 08 19:43:52:665#0-700#Error#com.redwood.scheduler.persistence.tdump#

End Transaction id=76835741#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C005200000A100000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76835741# #2.0 #2013 06 08 19:43:52:752#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A110000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76835752 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,835,752# #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76835752 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,835,752#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C005200000A130000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76835752 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,835,752# #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,835,752#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C005200000A150000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,835,752# #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A160000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76835752 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,835,752 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD

irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A170000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76835751> UniqueId=<11216843># #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76835751> UniqueId=<11216843>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C005200000A190000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76835751> UniqueId=<11216843># #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A1A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76835510> UniqueId=<632090># #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76835510> UniqueId=<632090>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C005200000A1C0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76835510> UniqueId=<632090># #2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A1D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76835752#

#2.0 #2013 06 08 19:43:52:753#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76835752#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C005200000A1F0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76835752# #2.0 #2013 06 08 19:44:01:601#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000180000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:44:01:601#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F90000001A0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#33,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:44:01:601#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F90000001C0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers]#Plain ## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:44:01:601#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F90000001D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect

ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:46:49:271#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000200000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:46:49:271#0-700#Error#com.redwood.scheduler.connector.sap.rfc.

connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F9000000220000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#33,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:46:49:271#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000240000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers]#Plain ## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:46:49:271#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000250000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099

) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:49:29:769#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F9000000280000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:49:29:770#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F90000002A0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: JobMonitoringComponent for PBI \#33,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:49:29:770#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F90000002C0000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers]#Plain ## 00024No connect to database, session terminated??????????????????????????#

#2.0 #2013 06 08 19:49:29:770#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F90000002D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: JobMonitoringComponent for PBI \#33,5,Workers ]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:49:56:203#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A200000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76837503 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,837,503# #2.0 #2013 06 08 19:49:56:203#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76837503 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,837,503#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C005200000A220000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76837503 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,837,503# #2.0 #2013 06 08 19:49:56:203#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,837,503#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C005200000A240000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,837,503# #2.0 #2013 06 08 19:49:56:203#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A250000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76837503 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,837,503 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160)

at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:49:56:203#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A260000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76837502> UniqueId=<11217072># #2.0 #2013 06 08 19:49:56:204#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76837502> UniqueId=<11217072>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C005200000A280000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76837502> UniqueId=<11217072># #2.0 #2013 06 08 19:49:56:204#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A290000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76837258> UniqueId=<665675># #2.0 #2013 06 08 19:49:56:204#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76837258> UniqueId=<665675>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C005200000A2B0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76837258> UniqueId=<665675># #2.0 #2013 06 08 19:49:56:204#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A2C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76837503#

#2.0 #2013 06 08 19:49:56:204#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76837503#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C005200000A2E0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76837503# #2.0 #2013 06 08 19:52:19:451#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F70000000D0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:52:19:452#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F70000000F0000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:52:19:452#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000110000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#3 5,5,Workers]#Plain## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:52:19:452#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000120000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447)

at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 ) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:54:59:042#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000150000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:54:59:042#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool#

Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????#XX-PART-REDWOOD#redwood.com/s cheduler-ear#C0000ADCD98C01F7000000170000309A#8263150000000492#redwood.com/sched uler-ear#com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiConne ctionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService PBI_ProcessSer ver: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system Exception: 102: 00024No connect to data base, session terminated??????????????????????????# #2.0 #2013 06 08 19:54:59:043#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# 00024No connect to database, session terminated??????????????????????????#XX-PAR T-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F7000000190000309A#82631500000 00492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.connecti on.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0 e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Sa pService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#3 5,5,Workers]#Plain## 00024No connect to database, session terminated??????????????????????????# #2.0 #2013 06 08 19:54:59:043#0-700#Error#com.redwood.scheduler.connector.sap.rfc. connection.xmi.AbstractXmiConnectionPool# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C01F70000001A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.connector.sap.rfc.c onnection.xmi.AbstractXmiConnectionPool#Guest#0##ABAD0E84D05111E2CBE10000007E15E E#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Red wood SapService PBI_ProcessServer: ApplicationServerLoadMonitoringComponent for PBI \#35,5,Workers]#Plain## Exception while connecting to SAP system [EXCEPTION] Exception: 102: 00024No connect to database, session terminated????????????????? ????????? at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:250) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.perform(AbstractRfcConnection.java:472) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion.doConnect(AbstractRfcConnection.java:447) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nection.connect(AbstractXmiConnection.java:64) at com.redwood.scheduler.connector.sap.rfc.connection.xmi.AbstractXmiCon nectionPool.borrowConnection(AbstractXmiConnectionPool.java:188) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapInterfa ce.checkRfcConnection(AbstractSapInterface.java:167) at com.redwood.scheduler.connector.sap.rfc.service.SapService.checkRfcCo nnection(SapService.java:1847) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:97) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated?????????????????????????? at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.jav a:557) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1099 )

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3644) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.createJCoClient(ClientConnectionFactoryImpl.java:130) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.ClientConnect ionFactoryImpl.connect(ClientConnectionFactoryImpl.java:45) at com.redwood.scheduler.connector.sap.rfc.jco2.connection.RfcRepository Impl.connect(RfcRepositoryImpl.java:119) at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnect ion$5.doPerform(AbstractRfcConnection.java:452) at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall .perform(RemoteFunctionCall.java:147) ... 10 more Caused by: RfcException: message: 00024No connect to database, session terminated???????????????????? ?????? Return code: RFC_FAILURE(1) error group: 103 key: RFC_ERROR_LOGON_FAILURE at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:831) at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1092 ) ... 16 more # #2.0 #2013 06 08 19:58:31:754#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A2F0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76839746 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,839,746# #2.0 #2013 06 08 19:58:31:754#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76839746 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,839,746#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C005200000A310000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76839746 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,839,746# #2.0 #2013 06 08 19:58:31:754#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,839,746#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C005200000A330000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,839,746# #2.0 #2013 06 08 19:58:31:754#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A340000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e

84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76839746 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,839,746 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:58:31:755#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A350000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76839745> UniqueId=<11217323># #2.0 #2013 06 08 19:58:31:755#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76839745> UniqueId=<11217323>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C005200000A370000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76839745> UniqueId=<11217323># #2.0 #2013 06 08 19:58:31:755#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A380000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e

84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76839711> UniqueId=<662538># #2.0 #2013 06 08 19:58:31:755#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76839711> UniqueId=<662538>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C005200000A3A0000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76839711> UniqueId=<662538># #2.0 #2013 06 08 19:58:31:755#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A3B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76839746# #2.0 #2013 06 08 19:58:31:755#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76839746#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C005200000A3D0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76839746# #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A3E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76839749 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,839,749# #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# Start Transaction id=76839749 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,839,749#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD 98C005200000A400000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.s cheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05 111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## Start Transaction id=76839749 contains 2 objects. Persistence Error: com.redwoo d.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-123100: 0 ro ws updated in tid=76,839,749# #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# JCS-123100: 0 rows updated in tid=76,839,749#XX-PART-REDWOOD#redwood.com/schedul er-ear#C0000ADCD98C005200000A420000309A#8263150000000492#redwood.com/scheduler-e ar#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E 15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[ Redwood Monitor Component \#13,5,Workers]#Plain## JCS-123100: 0 rows updated in tid=76,839,749# #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A430000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## Start Transaction id=76839749 contains 2 objects. Persistence Error: [EXCEPTION] com.redwood.scheduler.persistence.api.PersistenceException$NoRowsUpdated: JCS-12 3100: 0 rows updated in tid=76,839,749 at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.popula teAndExecute(LowLevelPersistenceImpl.java:920) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.proces sSelect(LowLevelPersistenceImpl.java:805) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectListRetry(LowLevelPersistenceImpl.java:303) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $0(LowLevelPersistenceImpl.java:164) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteD irtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:103) at com.redwood.scheduler.persistence.impl.OuterPersistenceUnitOfWorkMana ger.execute(OuterPersistenceUnitOfWorkManager.java:38) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeD irtyObjectList(LowLevelPersistenceImpl.java:160) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.writeDirtyObjectList(ClusteredLowLevelPersistence.java:90) at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal( SchedulerSessionImpl.java:910) at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSes sionImpl.java:872) at com.redwood.scheduler.monitor.MonitorComponent.handleMessageBatch(Mon itorComponent.java:372) at com.redwood.scheduler.monitor.MonitorComponent.handleDatabaseMessages (MonitorComponent.java:784) at com.redwood.scheduler.monitor.MonitorComponent.onMessage(MonitorCompo nent.java:739) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A440000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [ ] D MonitorMessage:v<76839747> UniqueId=<11217324># #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [ ] D MonitorMessage:v<76839747> UniqueId=<11217324>#XX-PART-REDWOO D#redwood.com/scheduler-ear#C0000ADCD98C005200000A460000309A#8263150000000492#re dwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E8 4D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10 000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [ ] D MonitorMessage:v<76839747> UniqueId=<11217324># #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A470000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## dirtyObject: [x] V MonitorCheck:v<76839713> UniqueId=<665675># #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# dirtyObject: [x] V MonitorCheck:v<76839713> UniqueId=<665675>#XX-PART-REDWOOD#re dwood.com/scheduler-ear#C0000ADCD98C005200000A490000309A#8263150000000492#redwoo d.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#Guest#0##ABAD0E84D05 111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe100000 07e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Plain## dirtyObject: [x] V MonitorCheck:v<76839713> UniqueId=<665675># #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C005200000A4A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.tdump#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor Component \#13,5,Workers]#Pl ain## End Transaction id=76839749# #2.0 #2013 06 08 19:58:31:764#0-700#Error#com.redwood.scheduler.persistence.tdump# End Transaction id=76839749#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD9 8C005200000A4C0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sc heduler.persistence.tdump#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d051 11e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Monitor C omponent \#13,5,Workers]#Plain## End Transaction id=76839749# #2.0 #2013 06 08 20:00:12:841#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065130000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPrepared Statement#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')".# #2.0 #2013 06 08 20:00:12:841#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065140000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')". [EXCEPTION] java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:12:842#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065150000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:12:842#0-700#Error#com.redwood.scheduler.persistence.lockin g# SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C0034000065170000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#

Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:12:842#0-700#Error#com.redwood.scheduler.persistence.lockin g# No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C0034000065190000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:12:842#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000651A0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] [EXCEPTION] com.sap.sql.exception.OpenSQLRecoverableException: No more data to read from soc ket OpenSQLExceptionCategories: [RECOVERABLE] at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLE xceptionFactory.java:146) at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQL ExceptionFactory.java:72) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJav a6(DirectPooledConnection.java:1000) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(Di rectPooledConnection.java:926) at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectCo nnection.java:1544) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:375) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: No more data to read from socket

at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) ... 9 more # #2.0 #2013 06 08 20:00:12:843#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000651C0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnecti onImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15e e#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@ee819f0 has already been closed becaus e of a fatal connection error..# #2.0 #2013 06 08 20:00:12:843#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000651D0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnectionImpl#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@ee819f0 has already been closed becaus e of a fatal connection error.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.common.Comm onConnectionImpl@ee819f0 has already been closed because of a fatal connection e rror. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(

ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:12:843#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000651E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@ee819f0 has already been closed b ecause of a fatal connection error.# #2.0 #2013 06 08 20:00:12:844#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@ee819f0 has already been closed b ecause of a fatal connection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0 000ADCD98C0034000065200000309A#8263150000000492#redwood.com/scheduler-ear#com.re dwood.scheduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE100000 07E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thre ad[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec

t com.sap.sql.jdbc.common.CommonConnectionImpl@ee819f0 has already been closed b ecause of a fatal connection error.# #2.0 #2013 06 08 20:00:12:844#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@ee819f0 has already been closed because of a fatal conn ection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C003400006522 0000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluste r.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111 e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@ee819f0 has already been closed because of a fatal conn ection error.# #2.0 #2013 06 08 20:00:12:844#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065230000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.common.Common ConnectionImpl@ee819f0 has already been closed because of a fatal connection err or. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:102) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.s ql.jdbc.common.CommonConnectionImpl@ee819f0 has already been closed because of a fatal connection error. at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:111) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr

esh(GlobalPersistenceLockImpl.java:98) ... 4 more Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc. common.CommonConnectionImpl@ee819f0 has already been closed because of a fatal c onnection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) ... 11 more # #2.0 #2013 06 08 20:00:12:946#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065250000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPrepared Statement#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')".# #2.0 #2013 06 08 20:00:12:946#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065260000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')". [EXCEPTION] java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207)

at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:12:947#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065270000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:12:947#0-700#Error#com.redwood.scheduler.persistence.lockin g# SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C0034000065290000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR

ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:12:947#0-700#Error#com.redwood.scheduler.persistence.lockin g# No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C00340000652B0000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:12:947#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000652C0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] [EXCEPTION] com.sap.sql.exception.OpenSQLRecoverableException: No more data to read from soc ket OpenSQLExceptionCategories: [RECOVERABLE] at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLE xceptionFactory.java:146) at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQL ExceptionFactory.java:72) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJav a6(DirectPooledConnection.java:1000) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(Di rectPooledConnection.java:926) at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectCo nnection.java:1544) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:375) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223)

at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) ... 9 more # #2.0 #2013 06 08 20:00:12:948#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000652E0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnecti onImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15e e#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@512301ef has already been closed becau se of a fatal connection error..# #2.0 #2013 06 08 20:00:12:948#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000652F0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnectionImpl#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@512301ef has already been closed becau se of a fatal connection error.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.common.Comm onConnectionImpl@512301ef has already been closed because of a fatal connection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340)

at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:12:948#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065300000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@512301ef has already been closed because of a fatal connection error.# #2.0 #2013 06 08 20:00:12:948#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@512301ef has already been closed because of a fatal connection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C 0000ADCD98C0034000065320000309A#8263150000000492#redwood.com/scheduler-ear#com.r edwood.scheduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000 007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thr ead[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@512301ef has already been closed because of a fatal connection error.#

#2.0 #2013 06 08 20:00:12:948#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@512301ef has already been closed because of a fatal con nection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000653 40000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.clust er.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0511 1e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Pol l Thread,5,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@512301ef has already been closed because of a fatal con nection error.# #2.0 #2013 06 08 20:00:12:948#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065350000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.common.Common ConnectionImpl@512301ef has already been closed because of a fatal connection er ror. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:102) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.s ql.jdbc.common.CommonConnectionImpl@512301ef has already been closed because of a fatal connection error. at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:111) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) ... 4 more Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.

common.CommonConnectionImpl@512301ef has already been closed because of a fatal connection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) ... 11 more # #2.0 #2013 06 08 20:00:13:050#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065370000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPrepared Statement#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')".# #2.0 #2013 06 08 20:00:13:050#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065380000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')". [EXCEPTION] java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme

nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:13:051#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065390000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:13:051#0-700#Error#com.redwood.scheduler.persistence.lockin g# SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C00340000653B0000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#

#2.0 #2013 06 08 20:00:13:051#0-700#Error#com.redwood.scheduler.persistence.lockin g# No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C00340000653D0000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:13:051#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000653E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] [EXCEPTION] com.sap.sql.exception.OpenSQLRecoverableException: No more data to read from soc ket OpenSQLExceptionCategories: [RECOVERABLE] at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLE xceptionFactory.java:146) at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQL ExceptionFactory.java:72) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJav a6(DirectPooledConnection.java:1000) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(Di rectPooledConnection.java:926) at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectCo nnection.java:1544) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:375) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207)

at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) ... 9 more # #2.0 #2013 06 08 20:00:13:051#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065400000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnecti onImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15e e#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@1581d444 has already been closed becau se of a fatal connection error..# #2.0 #2013 06 08 20:00:13:051#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065410000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnectionImpl#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@1581d444 has already been closed becau se of a fatal connection error.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.common.Comm onConnectionImpl@1581d444 has already been closed because of a fatal connection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ

uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:13:052#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065420000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@1581d444 has already been closed because of a fatal connection error.# #2.0 #2013 06 08 20:00:13:052#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@1581d444 has already been closed because of a fatal connection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C 0000ADCD98C0034000065440000309A#8263150000000492#redwood.com/scheduler-ear#com.r edwood.scheduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000 007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thr ead[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@1581d444 has already been closed because of a fatal connection error.# #2.0 #2013 06 08 20:00:13:052#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX:

SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@1581d444 has already been closed because of a fatal con nection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000654 60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.clust er.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0511 1e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Pol l Thread,5,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@1581d444 has already been closed because of a fatal con nection error.# #2.0 #2013 06 08 20:00:13:052#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065470000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.common.Common ConnectionImpl@1581d444 has already been closed because of a fatal connection er ror. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:102) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.s ql.jdbc.common.CommonConnectionImpl@1581d444 has already been closed because of a fatal connection error. at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:111) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) ... 4 more Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc. common.CommonConnectionImpl@1581d444 has already been closed because of a fatal connection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) ... 11 more # #2.0 #2013 06 08 20:00:13:155#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# com.sap.sql_0025#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065490000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPrepared Statement#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')".# #2.0 #2013 06 08 20:00:13:155#0-700#Error#com.sap.sql.jdbc.direct.DirectPreparedSt atement# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000654A0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## FATAL SQL error occurred on connection ashs95548:CPP:SAPSR3DB: code=17,410, stat e="08000", message="No more data to read from socket"; SQL statement is "UPDATE "JCS_LOCK0" SET "A_OWNER" = ?,"A_LTIME" = ?,"A_STATUS" = 'L' WHERE "A_NAME" = ? AND ("A_OWNER" = ? AND "A_STATUS" = 'L' OR "A_STATUS" = ' ')". [EXCEPTION] java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584)

at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:13:156#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000654B0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:13:156#0-700#Error#com.redwood.scheduler.persistence.lockin g# SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C00340000654D0000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] com.sap.sql.exception.OpenSQLR ecoverableException: No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:13:156#0-700#Error#com.redwood.scheduler.persistence.lockin g# No more data to read from socket

OpenSQLExceptionCategories: [RECOVERABLE]#XX-PART-REDWOOD#redwood.com/sc heduler-ear#C0000ADCD98C00340000654F0000309A#8263150000000492#redwood.com/schedu ler-ear#com.redwood.scheduler.persistence.locking#Guest#0##ABAD0E84D05111E2CBE10 000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0# Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE]# #2.0 #2013 06 08 20:00:13:156#0-700#Error#com.redwood.scheduler.persistence.lockin g# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065500000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.locking #Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad 0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compo nent]#Plain## SQLException (CODE=17410, STATE=08000): No more data to read from socket OpenSQLExceptionCategories: [RECOVERABLE] [EXCEPTION] com.sap.sql.exception.OpenSQLRecoverableException: No more data to read from soc ket OpenSQLExceptionCategories: [RECOVERABLE] at com.sap.sql.exception.SQLExceptionFactory.createOpenSQLException(SQLE xceptionFactory.java:146) at com.sap.sql.exception.SQLExceptionFactory.wrapChainedSQLException(SQL ExceptionFactory.java:72) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLExceptionJav a6(DirectPooledConnection.java:1000) at com.sap.sql.jdbc.direct.DirectPooledConnection.processSQLException(Di rectPooledConnection.java:926) at com.sap.sql.jdbc.direct.DirectConnection.processSQLException(DirectCo nnection.java:1544) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:375) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonP reparedStatement.java:354) at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.exec uteUpdate(PreparedStatementWrapper.java:397) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeU pdate(PreparedStatementImpl.java:449) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeSQLUpdate (DatabaseHelper.java:183) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeUpdate(Da tabaseHelper.java:142) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:122) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: No more data to read from socket at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1157) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:345) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:223) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement. java:207) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedSta tement.java:1044) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme

nt.java:1327) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePrep aredStatement.java:3584) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePrepar edStatement.java:3665) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(Oracl ePreparedStatementWrapper.java:1352) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPrep aredStatement.java:108) at com.sap.sql.jdbc.oracle.Oracle11gPreparedStatement.executeUpdate(Orac le11gPreparedStatement.java:167) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectP reparedStatement.java:372) ... 9 more # #2.0 #2013 06 08 20:00:13:156#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065520000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnecti onImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15e e#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@75f73bef has already been closed becau se of a fatal connection error..# #2.0 #2013 06 08 20:00:13:156#0-700#Error#com.sap.sql.jdbc.common.CommonConnection Impl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065530000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.jdbc.common.CommonConnectionImpl#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## Exception of type com.sap.sql.log.OpenSQLException caught: Connection object com .sap.sql.jdbc.common.CommonConnectionImpl@75f73bef has already been closed becau se of a fatal connection error.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.common.Comm onConnectionImpl@75f73bef has already been closed because of a fatal connection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78)

at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) # #2.0 #2013 06 08 20:00:13:157#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065540000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@75f73bef has already been closed because of a fatal connection error.# #2.0 #2013 06 08 20:00:13:157#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@75f73bef has already been closed because of a fatal connection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C 0000ADCD98C0034000065560000309A#8263150000000492#redwood.com/scheduler-ear#com.r edwood.scheduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000 007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thr ead[Redwood Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection objec t com.sap.sql.jdbc.common.CommonConnectionImpl@75f73bef has already been closed because of a fatal connection error.# #2.0 #2013 06 08 20:00:13:157#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@75f73bef has already been closed because of a fatal con nection error.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000655

80000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.clust er.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d0511 1e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Pol l Thread,5,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.com mon.CommonConnectionImpl@75f73bef has already been closed because of a fatal con nection error.# #2.0 #2013 06 08 20:00:13:157#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065590000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=1000026, STATE=SAP06): Connection object com.sap.sql.jdbc.common.Common ConnectionImpl@75f73bef has already been closed because of a fatal connection er ror. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:102) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:146) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=1000026, STATE=SAP06): Connection object com.sap.s ql.jdbc.common.CommonConnectionImpl@75f73bef has already been closed because of a fatal connection error. at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:111) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr eshInternal(GlobalPersistenceLockImpl.java:256) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.refr esh(GlobalPersistenceLockImpl.java:98) ... 4 more Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc. common.CommonConnectionImpl@75f73bef has already been closed because of a fatal connection error. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122) at com.sap.sql.jdbc.common.CommonConnectionImpl.validate(CommonConnectio nImpl.java:1457)

at com.sap.sql.jdbc.common.CommonConnectionImpl.prepare(CommonConnection Impl.java:1548) at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonC onnectionImpl.java:270) at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement( ConnectionHandle.java:114) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:340) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) ... 11 more # #2.0 #2013 06 08 20:00:13:270#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000655B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:270#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000655C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto

ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:271#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C00340000655D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.#

#2.0 #2013 06 08 20:00:13:271#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000655E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:271#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065600000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:272#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i

s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000065620000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:272#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065630000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more

# #2.0 #2013 06 08 20:00:13:272#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065640000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:272#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000065660000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:272#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065680000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain##

com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 20:00:13:272#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065690000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU

serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool

.java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:385#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000656B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:385#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000656C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils.

java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:385#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C00340000656D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.# #2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000656E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist

ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065700000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000065720000309A#8263150000000492#redwood.com/schedul

er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065730000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54)

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more #

#2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065740000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000065760000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:386#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065780000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu

m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 20:00:13:387#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065790000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more

Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261)

... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000657B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000657C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL

ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C00340000657D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.# #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000657E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc

eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065800000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000065820000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java

x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:498#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065830000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE

xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:499#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065840000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast

erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:499#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000065860000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:499#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065880000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#

#2.0 #2013 06 08 20:00:13:499#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065890000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora

ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296)

at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:611#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000658B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:611#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000658C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster

Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:611#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C00340000658D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.# #2.0 #2013 06 08 20:00:13:611#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000658E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2)

Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:611#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065900000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:611#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000065920000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable.

3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:612#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065930000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat

eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:612#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065940000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock

PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:612#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000065960000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:612#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065980000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 20:00:13:612#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065990000309A#8263

150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC

onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more

# #2.0 #2013 06 08 20:00:13:725#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000659B0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:725#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C00340000659C0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:725#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C00340000659D0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.# #2.0 #2013 06 08 20:00:13:725#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C00340000659E0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC

-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:725#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065A00000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:726#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000065A20000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:726#0-700#Error#com.redwood.scheduler.persistence.persis tence#

#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065A30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more

Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:726#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065A40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss

ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:726#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000065A60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:726#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065A80000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 20:00:13:726#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065A90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain##

Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio

n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:840#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl#

com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065AB0000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clus ter Component]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:840#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0034000065AC0000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#P lain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:840#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0034000065AD0000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Compone nt]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.# #2.0 #2013 06 08 20:00:13:840#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065AE0000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#

#2.0 #2013 06 08 20:00:13:840#0-700#Error#com.redwood.scheduler.persistence.persis tence# SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWO OD#redwood.com/scheduler-ear#C0000ADCD98C0034000065B00000309A#8263150000000492#r edwood.com/scheduler-ear#com.redwood.scheduler.persistence.persistence#Guest#0## ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111 e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plai n## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:840#0-700#Error#com.redwood.scheduler.persistence.persis tence# ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.#XX-PART-REDWOOD#redwood.com/sch eduler-ear#C0000ADCD98C0034000065B20000309A#8263150000000492#redwood.com/schedul er-ear#com.redwood.scheduler.persistence.persistence#Guest#0##ABAD0E84D05111E2CB E10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee #0#Thread[Redwood Master Poll Thread,5,Cluster Component]#Plain## ResourceException occurred in method ConnectionFactoryImpl.getConnection(): java x.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot c reate connection. Possible reasons: 1)Maximum allowed connections to DB or EIS i s reached. You can apply CSN Note 719778 in order to check and resolve connectio n leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.# #2.0 #2013 06 08 20:00:13:841#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065B30000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Cluster C

omponent]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. [EXCEPTION] com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException oc curred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceE xception: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Po ssible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can a pply CSN Note 719778 in order to check and resolve connection leaks. 2) Configur ation to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)

at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:841#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065B40000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#

#2.0 #2013 06 08 20:00:13:841#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98 C0034000065B60000309A#8263150000000492#redwood.com/scheduler-ear#com.redwood.sch eduler.cluster.ClusterMasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#a bad0e84d05111e2cbe10000007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwoo d Master Poll Thread,5,Cluster Component]#Plain## Exception in master lock thread com.redwood.scheduler.persistence.api.GlobalLock PersistenceException: com.redwood.scheduler.persistence.api.PersistenceException $SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occu rred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceExc eption: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Poss ible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can app ly CSN Note 719778 in order to check and resolve connection leaks. 2) Configurat ion to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are no t enough for current load.# #2.0 #2013 06 08 20:00:13:841#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.#XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065B80000309A# 8263150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.Cluster MasterRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe1000 0007e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5 ,Cluster Component]#Plain## com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in method Connect ionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in com ponent: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximu m allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current l oad.# #2.0 #2013 06 08 20:00:13:841#0-700#Error#com.redwood.scheduler.cluster.ClusterMas terRunnable# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0034000065B90000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.cluster.ClusterMast erRunnable#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007 e15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood Master Poll Thread,5,Clu ster Component]#Plain## Exception in master lock thread [EXCEPTION] com.redwood.scheduler.persistence.api.GlobalLockPersistenceException: com.redwoo d.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLExcepti

on (CODE=0, STATE=08003): ResourceException occurred in method ConnectionFactory Impl.getConnection(): javax.resource.ResourceException: (Failed in component: db pool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to c heck and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load. at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:152) at com.redwood.scheduler.cluster.ClusterComponent.masterThreadIteration( ClusterComponent.java:678) at com.redwood.scheduler.cluster.ClusterMasterRunnable.run(ClusterMaster Runnable.java:49) at java.lang.Thread.run(Thread.java:736) Caused by: com.redwood.scheduler.persistence.api.PersistenceException$SQLError: JCS-XXXXX: SQLException (CODE=0, STATE=08003): ResourceException occurred in met hod ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Fa iled in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reason s: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/E IS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough fo r current load. at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:162) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceFactoryImpl .getLockingReadWriteConnection(LowLevelPersistenceFactoryImpl.java:129) at com.redwood.scheduler.persistence.impl.GlobalPersistenceLockImpl.tryL ock(GlobalPersistenceLockImpl.java:116) ... 3 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceE xception occurred in method ConnectionFactoryImpl.getConnection(): javax.resourc e.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create con nection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached . You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Conne ctions are not enough for current load. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:60) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) ... 5 more Caused by: javax.resource.ResourceException: (Failed in component: dbpool, BC-JA S-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and re solve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is tempora ry unreachable. 3) Connections are not enough for current load. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:230) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) ... 8 more Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLE xception is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: E

xception of type java.sql.SQLRecoverableException caught: IO Error: Got minus on e from a read call. at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:192) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) ... 11 more Caused by: com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecov erableException caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) ... 12 more Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 15 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 27 more # #2.0 #2013 06 08 20:00:13:847#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# com.sap.sql_0019#BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0205000000010000309A#8 263150000000492#redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataS ourceImpl#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e 15ee#abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService P01_ProcessSer

ver: EventSynchronizerComponent for P01 \#42,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. # #2.0 #2013 06 08 20:00:13:848#0-700#Error#com.sap.sql.connect.datasource.DBDataSou rceImpl# #BC-JAS-PER-SQL#opensqlkernel#C0000ADCD98C0205000000020000309A#8263150000000492# redwood.com/scheduler-ear#com.sap.sql.connect.datasource.DBDataSourceImpl#Guest# 0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e84d05 111e2cbe10000007e15ee#0#Thread[Redwood SapService P01_ProcessServer: EventSynchr onizerComponent for P01 \#42,5,Workers]#Plain## Exception of type com.sap.sql.log.OpenSQLException caught: Exception of type jav a.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.. [EXCEPTION] com.sap.sql.log.OpenSQLException: Exception of type java.sql.SQLRecoverableExcep tion caught: IO Error: Got minus one from a read call. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104) at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:284) at com.sap.sql.connect.datasource.DBDataSourceImpl.getConnection(DBDataS ourceImpl.java:139) at com.sap.engine.core.database.impl.DatabaseDataSourceImpl.getConnectio n(DatabaseDataSourceImpl.java:36) at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.creat eManagedConnection(ManagedConnectionFactoryImpl.java:152) at com.sap.engine.services.connector.jca.ConnectionHashSet.match(Connect ionHashSet.java:221) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateC onnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allo cateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnectio n(ConnectionFactoryImpl.java:52) at com.redwood.scheduler.persistence.impl.db.DataSourceDBConnectionFacto ry.getUserConnection(DataSourceDBConnectionFactory.java:97) at com.redwood.scheduler.model.LowLevelPersistenceConfigurationImpl.getU serConnection(LowLevelPersistenceConfigurationImpl.java:460) at com.redwood.scheduler.persistence.impl.Utils.getUserConnection(Utils. java:153) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.connect (OnDemandConnectionImpl.java:69) at com.redwood.scheduler.persistence.impl.OnDemandConnectionImpl.prepare Statement(OnDemandConnectionImpl.java:339) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.prepareR ealPreparedStatement(PreparedStatementImpl.java:366) at com.redwood.scheduler.persistence.impl.PreparedStatementImpl.executeQ uery(PreparedStatementImpl.java:521) at com.redwood.scheduler.persistence.spi.DatabaseHelper.executeQuery(Dat abaseHelper.java:78) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut eQueryRetry(LowLevelPersistenceImpl.java:491) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access $1(LowLevelPersistenceImpl.java:481) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$1.exec ute(LowLevelPersistenceImpl.java:466) at com.redwood.scheduler.persistence.impl.InnerPersistenceUnitOfWorkMana ger.execute(InnerPersistenceUnitOfWorkManager.java:35) at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.execut

eQuery(LowLevelPersistenceImpl.java:460) at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistenc e.executeQuery(ClusteredLowLevelPersistence.java:155) at com.redwood.scheduler.model.BaseSchedulerSessionImpl.getSAPSystemIntB yName(BaseSchedulerSessionImpl.java:30862) at com.redwood.scheduler.connector.sap.rfc.service.SapService.getSapSyst em(SapService.java:2020) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.rehash(EventSynchronizerComponent.java:88) at com.redwood.scheduler.connector.sap.rfc.service.components.EventSynch ronizerComponent.execute(EventSynchronizerComponent.java:128) at com.redwood.scheduler.connector.sap.rfc.components.AbstractSapCompone nt.onMessage(AbstractSapComponent.java:115) at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(Mess ageEnabledWork.java:107) at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.j ava:140) at java.lang.Thread.run(Thread.java:736) Caused by: java.sql.SQLRecoverableException: IO Error: Got minus one from a read call at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:475) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java: 552) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:253) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtensio n.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendo rConnection(DriverPooledConnectionFactory.java:50) at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledCo nnection(DriverPooledConnectionFactory.java:37) at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnectio n(DBDataSourceImpl.java:651) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:995) at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceIm pl.java:43) at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool .java:95) at com.sap.sql.connect.pool.Pool.get(Pool.java:707) at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl. java:261) ... 29 more Caused by: oracle.net.ns.NetException: Got minus one from a read call at oracle.net.ns.Packet.receive(Packet.java:303) at oracle.net.ns.NSProtocol.connect(NSProtocol.java:296) at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1126) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337) ... 41 more # #2.0 #2013 06 08 20:00:13:848#0-700#Error#com.sap.engine.services.dbpool.spi.Manag edConnectionFactoryImpl# #BC-JAS-TRH#dbpool#C0000ADCD98C0205000000030000309A#8263150000000492#redwood.com /scheduler-ear#com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl#G uest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee#abad0e 84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService P01_ProcessServer: EventS ynchronizerComponent for P01 \#42,5,Workers]#Plain## ManagedConnectionFactoryImpl.createManagedConnection(): SQLException occured whi

le creating ManagedConnection: com.sap.sql.log.OpenSQLException: Exception of ty pe java.sql.SQLRecoverableException caught: IO Error: Got minus one from a read call.# #2.0 #2013 06 08 20:00:13:848#0-700#Error#com.redwood.scheduler.persistence.persis tence# #XX-PART-REDWOOD#redwood.com/scheduler-ear#C0000ADCD98C0205000000040000309A#8263 150000000492#redwood.com/scheduler-ear#com.redwood.scheduler.persistence.persist ence#Guest#0##ABAD0E84D05111E2CBE10000007E15EE#abad0e84d05111e2cbe10000007e15ee# abad0e84d05111e2cbe10000007e15ee#0#Thread[Redwood SapService P01_ProcessServer: EventSynchronizerComponent for P01 \#42,5,Workers]#Plain## SQLException opening connection: SQLException (CODE=0, STATE=08003): ResourceExc eption occurred in method ConnectionFactoryImpl.getConnection(): javax.resource. ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create conne ction. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connect ions are not enough for current load. com.sap.engine.services.dbpool.exceptions. BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.get Connection(): javax.resource.ResourceException: (Failed in component: dbpool, BC -JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connecti ons to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temp orary unreachable. 3) Connections are not enough for current load.#