|
BEA-001000(retired)
|
Emergency: Error ! Blob: Exception attempting to close OciOutputStream exText
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001001(retired)
|
Emergency: The driver class aDriver throws an exception when Class.forName(aDriver).newInstance is executed: aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001002(retired)
|
Info: Returning cached connection: aCachename
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001003(retired)
|
Info: Loading driver class: sDriverName
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001004(retired)
|
Info: JDBC log stream started at aStartDate
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001005(retired)
|
Error: Could not create ParamSet for SQL logging event: anException
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001006(retired)
|
Emergency: Could not submit SQL logging event: anException
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001007(retired)
|
Info: aMessage issued.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001008(retired)
|
Error: Problem loading Driver: aDriverName - aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001009(retired)
|
Info: Checking License file for jdbcKona/MSSQLServer
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001010(retired)
|
Error: Driver: Error trying to determine DBType !
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001011(retired)
|
Emergency: Driver: autocommit setting unreliable !
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001012(retired)
|
Emergency: Error ! Blob: Exception attempting to close OciOutputStream aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001013(retired)
|
Error: Error ! Blob: Exception attempting to close InputStream aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001014(retired)
|
Error: Error ! Blob: unexpected stream type in streams Vector
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001015(retired)
|
Emergency: Error ! Clob: Exception attempting to close OciOutputStream aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001016(retired)
|
Error: Error ! Clob: Exception attempting to close Reader aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001017(retired)
|
Error: Error ! Clob: Exception attempting to close OutputStream aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001018(retired)
|
Error: Error ! Clob: Exception attempting to close Writer aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001019(retired)
|
Error: Error ! Clob: unexpected stream type in streams Vector
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001020(retired)
|
Error: DataTruncation: index(anIndex) parameter(aParameter) read(aRead) data size(aDataSize) transfer size(aTransferSize);
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001021(retired)
|
Error: Connection.setQueryTimeout is only supported in JDK 1.1 (or newer), exception: anException
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001022(retired)
|
Warning: aClassName.connect - cannot handle url anUrl
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001023(retired)
|
Error: Driver: error getting ConnectionInfo: aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001024(retired)
|
Warning: BaseHandler.appendWarning - aWarning
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001025(retired)
|
Error: SQLException attempting to close Stmt aErrorCode aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001026(retired)
|
Error: findDBType: createStatement Exception ! aErrorCode aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001027(retired)
|
Error: findDBType: SQLException while attempting to rollback ! aErrorCode aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001028(retired)
|
Error: findDBType: Connection Error while trying to determine DBType during SET LOCK MODE Trial. aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001029(retired)
|
Emergency: findDBType: ERROR attempting to close statement ! aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001030(retired)
|
Error: findDBType: SET LOCK Exception ! aErrorCode aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001031(retired)
|
Error: findDBtype: SQLException while attempting to determine logging status ! aErrorCode aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001032(retired)
|
Error: Error closing Informix connection. aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001033(retired)
|
Error: ConnectionInfo - error - this is not a valid jdbc connection url
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001034(retired)
|
Warning: aError creating BigDecimal decimal.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001035
|
Error: The following error has occured: aMessage.
|
Description
| The indicated error has occured. |
|
Cause
| This message should contain an explanation of the failure. |
|
Action
| Take appropriate action. |
|
|
BEA-001036
|
Debug: aMessage
|
Description
| Debug only, called from trace method. |
|
|
BEA-001037(retired)
|
Warning: Bytes read (aReadBytes) do not match row bytes (aRowBytes)
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001038(retired)
|
Warning: ResultSetMetaData: getFromServerRowSize: is zero ! returning default (short) 10,00
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001039(retired)
|
Emergency: Timeout on connection's socket cannot be set because aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001040(retired)
|
Warning: Statement.close: deregisterStmt did not remove Statement !
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001041(retired)
|
Warning: Packet type unknown = aTypeID. Processing as an update.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001042(retired)
|
Error: Version response packet ID 0x35 expected but got aPacketID
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001043(retired)
|
Warning: SocketExtras - couldn't understand the anOption option.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001044(retired)
|
Error: TdsDatabaseMetaData - an exception was raised while processing sp_server_info (will use default values), aSql
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001045(retired)
|
Error: TdsInputStream.read - got an exception while sleeping, anException
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001046(retired)
|
Error: Statement.close - closing the stream raised this exception anException
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001047(retired)
|
Error: TdsStatement.parseWarning - exception while reading warning anException
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001048(retired)
|
Error: TdsCallableStatement.setProcedureOutResult - error - all parameters have already been filled
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001049(retired)
|
Info: Connecting to database using: aLoginStr at aTime
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001050(retired)
|
Info: Connected to database at: aTime
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001051(retired)
|
Info: Done logging in at: aTime
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001052(retired)
|
Info: Loading library: aLibname
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001053(retired)
|
Info: Finished loading library at: aTime
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001054(retired)
|
Info: Parsing: aSql
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001055(retired)
|
Info: Executing: aSql
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001056(retired)
|
Warning: aMessage issued.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001057(retired)
|
Error: Could not initialize JDBC log file: aFile
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001058
|
Error: Could not get JNDI context: aError
|
Description
| A call to get a new InitialContext "weblogic.jndi.WLInitialContextFactory". |
|
Cause
| Look at the printed exception to see why the call failed. |
|
Action
| Correct the problem and re-run the operation. |
|
|
BEA-001059(retired)
|
Error: Error during Data Source creation: aError
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001060(retired)
|
Error: Cannot startup connection pool "aPool" aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001061(retired)
|
Error: Failed to init pools: aList
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001062(retired)
|
Error: Realm aName is unknown here
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001063(retired)
|
Error: User aUserName is unknown in realm aRealmName : Realm aRealmName does not accept the submitted credential for user aUserName
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001064
|
Warning: Ignoring property 'enableTwoPhaseCommit' for JDBCTxDataSource "aName". This property is used only for those drivers that do not natively support XA.
|
Description
| The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored. |
|
Cause
| The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored. |
|
Action
| No action required. |
|
|
BEA-001065(retired)
|
Info: Sleeping in createResource()
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001066
|
Info: Delaying delaySecs seconds before making a aPoolname pool connection.
|
Description
| The thread is sleeping for the specified number of seconds before creating a connection. |
|
Cause
| Some databases cannot handle a tight loop of making multiple connections from one application. If this is the case and the delay is more than 2 seconds, this message will be printed. |
|
Action
| No action required. |
|
|
BEA-001067
|
Info: Connection for pool "aPoolname" refreshed.
|
Description
| A connection for the specified pool has been refreshed. |
|
Cause
| A connection for the specified pool has been refreshed. |
|
Action
| No action required. |
|
|
BEA-001068
|
Info: Connection for pool "aPoolname" created.
|
Description
| A connection for the specified pool has been created. |
|
Cause
| A connection for the specified pool has been created. |
|
Action
| No action required. |
|
|
BEA-001069(retired)
|
Info: Attempting to create connection pool aPoolName requested by user aCaller
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001070(retired)
|
Info: Checking existence of connection pool aPoolName requested by user aCaller
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001071(retired)
|
Info: Creating TX Data Source named anJndiName for pool aPoolName
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001072
|
Info: Connection for XA pool "aPoolname" created.
|
Description
| A connection for the specified XA pool has been created. |
|
Cause
| A connection for the specified XA pool has been created. |
|
Action
| No action required. |
|
|
BEA-001073
|
Info: Connection for XA pool "aPoolName" refreshed.
|
Description
| A connection for the specified XA pool has been refreshed. |
|
Cause
| A connection for the specified XA pool has been refreshed. |
|
Action
| No action required. |
|
|
BEA-001074
|
Warning: A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the connection pool. The following stack trace at create shows where the leaked connection was created. stackTrace
|
Description
| A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the connection pool. A stack trace is printed indicating where the leaked connection was created. |
|
Cause
| A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the connection pool. A stack trace is printed indicating where the leaked connection was created. |
|
Action
| Close the connection appropriately. |
|
|
BEA-001075(retired)
|
Warning: Test table "aTable" for pool "aPool" does not exist or is not available. Provide proper name for test table.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001076
|
Warning: An attempt was made to release a connection that belongs to a non-existing pool. Make sure the pool "aPool" has been destroyed by intent.
|
Description
| An attempt was made to release a connection that belongs to a non-existing pool. |
|
Cause
| An attempt was made to release a connection that belongs to a non-existing pool. |
|
Action
| Correct the destroy operation to specify a valid pool name. |
|
|
BEA-001077(retired)
|
Error: The pool "aPool" was created successfully. But it must be killed because of: aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001078(retired)
|
Error: Failed to init JDBC Services: aMessage
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001079(retired)
|
Info: Connection pool "poolName" will be shutdown.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001080(retired)
|
Info: Connection pool "poolName" has been successfully shutdown
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001081(retired)
|
Error: Error during shutdown of connection pool "poolName" : error
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001082(retired)
|
Info: Creating Data Source named anJndiName for pool aPoolName
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001083
|
Info: MultiPool "aName" was created with aNumOfPools connection pools for anAlgorithm.
|
Description
| A multiple was created with the specified number of connection pools. |
|
Cause
| A multiple was created with the specified number of connection pools. |
|
Action
| No action required. |
|
|
BEA-001084
|
Info: MultiPool "aName" will be shutdown
|
Description
| The specified MultiPool is being shut down. |
|
Cause
| The specified MultiPool is being shut down. |
|
Action
| No action required. |
|
|
BEA-001085(retired)
|
Info: MultiPool "aName" has been shutdown
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001086
|
Info: DataSource "aName" with JNDI name "aJNDIName" will be shutdown
|
Description
| The specified DataSource is being shut down. |
|
Cause
| The specified DataSource is being shut down. |
|
Action
| No action required. |
|
|
BEA-001087(retired)
|
Info: DataSource "aName" with JNDI name "aJNDIName" has been shutdown
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001089
|
Info: Connection Pool poolName has been started for application appName, module modName.
|
Description
| The specified connection pool is being started. |
|
Cause
| The specified connection pool is being started. |
|
Action
| No action required. |
|
|
BEA-001090(retired)
|
Info: Pool "poolname" will not be periodically tested once connected.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001091(retired)
|
Info: Pool "poolName" will be tested at "minutes" minute intervals.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001092(retired)
|
Warning: Cannot set pool "poolName" refreshTestMinutes with "minutes". Will use 5 minutes.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001093(retired)
|
Warning: Pool "poolName" set for testOnReserve but no test table defined.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001094(retired)
|
Warning: A connection from pool "poolName" was tested during reserve with the SQL "sql" and failed:\nstack\nThis connection will now be refreshed.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001095(retired)
|
Warning: A connection from pool "poolName" was tested during reserve with a select count(*) from "sql" and failed:\n"stack\nThis connection will now be refreshed.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001096(retired)
|
Warning: Refreshing this bad pool connection failed\ne
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001097(retired)
|
Warning: Refreshing this bad pool connection failed\ne\n Further refreshing postponed.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001098(retired)
|
Warning: Pool "poolName" set for testOnRelease but no test table defined.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001099
|
Info: Connection pool "poolName" reset by "subject"
|
Description
| The specified connection pool has been reset. |
|
Cause
| The specified connection pool has been reset. |
|
Action
| No action required. |
|
|
BEA-001100
|
Info: Connection pool "poolName" shutdown by "subject"
|
Description
| The specified connection pool has been shutdown by the specified user. |
|
Cause
| The specified connection pool has been shutdown, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001101
|
Info: Connection pool "poolName" disabled by "subject"
|
Description
| The specified connection pool has been disabled. |
|
Cause
| The specified connection pool has been disabled. |
|
Action
| No action required. |
|
|
BEA-001102
|
Info: Connection pool "poolName" enabled by "subject"
|
Description
| The specified connection pool has been enabled. |
|
Cause
| The specified connection pool has been enabled. |
|
Action
| No action required. |
|
|
BEA-001103(retired)
|
Warning: Pool "poolName" failed to replenish "killCount" connections during hard disable.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001104
|
Warning: A globally scoped connection pool named (poolName) already exists.
|
Description
| When adding/referencing a JDBC connection pool that is an application scoped pool, a globally scoped connection pool with the same name already exists. The locally scoped pool has precedence over the global pool. |
|
Cause
| When adding/referencing a JDBC connection pool that is an application scoped pool, a globally scoped connection pool with the same name already exists. The locally scoped pool has precedence over the global pool. |
|
Action
| If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique. |
|
|
BEA-001105
|
Warning: Referenced global pool (global) has the same name as a locally defined connection pool or data source (local)
|
Description
| When deploying a JDBC connection pool (not application scoped) an application (locally) scoped connection pool with the same name already exists. The locally scoped pool has precedence over the global pool. |
|
Cause
| When deploying a JDBC connection pool (not application scoped) an application (locally) scoped connection pool with the same name already exists. The locally scoped pool has precedence over the global pool. |
|
Action
| If you want to reference the global pool in your application, the name of the global pool or the application scoped pool must be changed to be unique. |
|
|
BEA-001106(retired)
|
Warning: Referenced global data source (global) has the same JNDI name (JNDIName) as a locally defined data source
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
BEA-001107
|
Warning: There is a globally defined data source (global) with the same JNDI name (JNDIName) as a locally defined data source.
|
Description
| It is possible to use resource-descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is a pool that the application meant to use and it is bound into comp/env. However, a check in the global namespace indicates that there is also a global pool with the same JNDI name. |
|
Cause
| It is possible to use resource-descriptor with application scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is a pool that the application meant to use and it is bound into comp/env. However, a check in the global namespace indicates that there is also a global pool with the same JNDI name. |
|
Action
| If you want to reference the global pool in your application, the JNDI name of the global pool or the application scoped pool must be changed to be unique. |
|
|
BEA-001108
|
Info: A locally scoped pool (local) was bound into comp/env with the JNDI name (JNDIName).
|
Description
| It is possible to use resource-descriptor with application scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is the pool that the application meant to use and it is bound into comp/env. |
|
Cause
| It is possible to use resource-descriptor with application scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is the pool that the application meant to use and it is bound into comp/env. |
|
Action
| No action required. If this association is not desired, specify a unique JNDI name in the resource-descriptor. |
|
|
BEA-001109
|
Info: A globally scoped pool (global) was bound into comp/env with the JNDI name (JNDIName).
|
Description
| It is possible to use a resource-descriptor with global connection pools. If the JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is pool that the application meant to use and it is bound into comp/env. |
|
Cause
| It is possible to use a resource-descriptor with global connection pools. If the JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is pool that the application meant to use and it is bound into comp/env. |
|
Action
| No action required. If this association is not desired, specify a unique JNDI name in the resource-descriptor. |
|
|
BEA-001110
|
Warning: No test table set up for pool "poolName". Connections will not be tested.
|
Description
| TestConnectionsOnReserve,TestConnectionsOnRelease, TestConnectionsOnCreate, or TestFrequencySeconds were configured. However, TestTableName was not configured. Connections for this pool will not be tested (the configured Test attributes will be ignored). |
|
Cause
| TestConnectionsOnReserve, TestConnectionsOnRelease, TestConnectionsOnCreate, TestFrequencySeconds were configured but TestTableName was not configured. |
|
Action
| Configure a valid TestTableName for the connection pool. |
|
|
BEA-001111
|
Error: Unable to verify the test "test" set up for pool "poolName". Connections will not be tested. The test will not be used by isValid neither.
|
Description
| While creating a connection pool with attributes specified to test the pool connections, a test is run during the pool initialization. This test failed with the printed error. |
|
Cause
| While creating a connection pool with attributes specified to test the pool connections, a test is run during the pool initialization. This test failed with the printed error. |
|
Action
| Check the SQL error that occurred and correct the problem. The specified TestTableName might not exist. |
|
|
BEA-001112
|
Error: Test "test" set up for pool "poolName" failed with exception: "err".
|
Description
| The specified connection pool has been configured with one or more attributes to test the pool connections. One of those test attempts failed. The associated error is printed. |
|
Cause
| The specified connection pool has been configured with one or more attributes to test the pool connections. One of those test attempts failed. The associated error is printed. |
|
Action
| Check the associated error to see what the problem is and correct it. Normally, this indicates that a connection was lost to the database (the database is down) and needs to be corrected by the database administrator. |
|
|
BEA-001113
|
Info: Connection pool "poolName" shrunk by "subject"
|
Description
| The connection pool has been shrunk by the specified amount as requested by the application. |
|
Cause
| The connection pool has been shrunk by the specified amount as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001114
|
Info: Soft shutdown called on connection pool "poolName" by "subject".
|
Description
| A soft shutdown operation on the specified connection pool has been started, as requested by the application. |
|
Cause
| A soft shutdown operation on the specified connection pool has been started, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001115
|
Info: Hard shutdown called on connection pool "poolName" by "subject"
|
Description
| A hard shutdown operation on the specified connection pool has been started, as requested by the application. |
|
Cause
| A soft shutdown operation on the specified connection pool has been started, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001116
|
Info: Disable and freeze users called on connection pool "poolName" by "subject".
|
Description
| An operation to disable and freeze users on the specified connection pool has been started, as requested by the application. |
|
Cause
| An operation to disable and freeze users on the specified connection pool has been started, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001117
|
Info: Disable and drop users called on connection pool "poolName" by "subject".
|
Description
| An operation to disable and drop users on the specified connection pool has been started, as requested by the application. |
|
Cause
| An operation to disable and drop users on the specified connection pool has been started, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001118
|
Warning: Unable to register for receiving MBean notifications of dynamic configurations changes for pool "poolName": "err". Pool will not be dynamically reconfigured.
|
Description
| The server was unable to register for receiving MBean notifications of dynamic configurations changes for the specified connection pool. The pool will not be dynamically reconfigured. |
|
Cause
| The server was unable to register for receiving MBean notifications of dynamic configurations changes for the specified connection pool. The pool will not be dynamically reconfigured. |
|
Action
| Check the exception that is printed along with this message to see what the cause of the failure was. |
|
|
BEA-001119
|
Error: Unable to delete configuration MBean for pool "poolName": "err"
|
Description
| While doing a hard shutdown, the connection pool was removed but the associated MBean for the connection pool was not removed. |
|
Cause
| While doing a hard shutdown, the connection pool was removed but the associated MBean for the connection pool was not removed. |
|
Action
| Check the exception that is printed along with this message to see what the cause of the failure was. |
|
|
BEA-001120
|
Info: Created Data Source named dsName for Pool poolName.
|
Description
| The named Data Source has been created. |
|
Cause
| The user requested that the Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001121
|
Info: Created TX Data Source named dsName for Pool poolName.
|
Description
| The named TX Data Source has been created. |
|
Cause
| The user requested that the TX Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001122
|
Info: Destroyed TX Data Source named dsName for Pool poolName.
|
Description
| The named TX Data Source has been destroyed. |
|
Cause
| The user requested that the TX Data Source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001123
|
Info: Destroyed Data Source named dsName for Pool poolName.
|
Description
| The named Data Source has been destroyed. |
|
Cause
| The user requested that the Data Source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001124
|
Info: Created Connection Pool named poolName.
|
Description
| The named connection pool has been created. |
|
Cause
| The user requested that the connection pool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001125
|
Info: Created Multi Pool named poolName.
|
Description
| The named multipool has been created. |
|
Cause
| The user requested that the multipool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001126
|
Info: Destroyed Connection Pool named poolName.
|
Description
| The named connection pool has been destroyed. |
|
Cause
| The user requested that the connection pool be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001127
|
Info: Destroyed Multi Pool named poolName.
|
Description
| The named multipool has been destroyed. |
|
Cause
| The user requested that the multipool be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001128
|
Info: Connection for pool "aPoolname" closed.
|
Description
| A connection for the specified pool has been closed. |
|
Cause
| A connection for the specified pool has been closed. |
|
Action
| No action required. |
|
|
BEA-001129
|
Warning: Received exception while creating connection for pool "pool": err
|
Description
| An error occurred while creating a connection for the specified pool. |
|
Cause
| The exception message should indicate the probable cause of the error. |
|
Action
| Check the error to see why the connection creation failed and correct the problem. |
|
|
BEA-001130
|
Info: Disabled statement caching for connection in pool "pool" as it using the WebLogic Type-2 XA driver.
|
Description
| Statement caching has been disabled for the specified connection pool because it is using the WebLogic Type-2 XA driver. |
|
Cause
| Statement caching has been disabled for the specified connection pool because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when the XAResource.end is called, causing all prepared statements to be no longer valid. |
|
Action
| No action required. Use a different driver if you want to use the prepared statement cache with the driver. |
|
|
BEA-001131
|
Error: Received an exception when closing a cached statement for the pool "pool": err.
|
Description
| When closing a prepared statement in the prepared statement cache for the specified pool, an error occurred. |
|
Cause
| When closing a prepared statement in the prepared statement cache for the specified pool, an error occurred. |
|
Action
| Check the associated error that is printed and correct the problem if possible. |
|
|
BEA-001132
|
Info: Initialized statement cache of size "size" for connection in pool "pool".
|
Description
| A prepared statement cache has been enabled for a connection in the specified pool. |
|
Cause
| A prepared statement cache has been enabled for a connection in the specified pool. |
|
Action
| No action required. If you do not want statement caching turned on for the pool, do not configure or disable it. |
|
|
BEA-001133
|
Info: Statement caching not enabled for connection in specified pool "pool".
|
Description
| Statement caching has not been enabled for connections in the specified pool. |
|
Cause
| A configured connection pool has been started without statement caching being enabled. |
|
Action
| No action required. If you want statement caching turned on for the pool, configure and enable it. |
|
|
BEA-001134
|
Info: Statement caches of connections in the pool "pool" have been cleared by "subject".
|
Description
| The statement caches for connections in the specified pool have been cleared, as requested by the application. |
|
Cause
| The statement caches for connections in the specified pool have been cleared, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001135
|
Info: Initializing the JDBC service.
|
Description
| Initializing the JDBC service. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001136
|
Info: Initialization failed.
|
Description
| Initialization of the JDBC Service failed. Check earlier log messages. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001137
|
Info: Initialization complete.
|
Description
| Initialization of the JDBC Service completed. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001138
|
Info: Resuming the JDBC service.
|
Description
| Resuming the JDBC service. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001139
|
Info: Resume failed.
|
Description
| Resuming of the JDBC Service failed. |
|
Cause
| Check earlier messages that are printed in the log. |
|
Action
| No action required. |
|
|
BEA-001140
|
Info: Resume complete.
|
Description
| Resuming the JDBC service completed. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001141
|
Info: Suspending the JDBC service.
|
Description
| Suspending the JDBC service. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001142
|
Info: Suspend of JDBC service failed.
|
Description
| Suspend of JDBC service failed. |
|
Cause
| Check earlier messages that are printed in the log. |
|
Action
| No action required. |
|
|
BEA-001143
|
Info: Suspend completed.
|
Description
| Suspend of the JDBC service completed. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001144
|
Info: Force Suspending the JDBC service.
|
Description
| Force Suspending the JDBC service. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001145
|
Info: Force suspend of the JDBC Service failed.
|
Description
| Force suspend of the JDBC Service failed. |
|
Cause
| Check earlier messages that are printed in the log. |
|
Action
| No action required. |
|
|
BEA-001146
|
Info: Force suspend of the JDBC service completed.
|
Description
| Force suspend of the JDBC service completed. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001147
|
Info: Shutting down the JDBC service.
|
Description
| Shutting down the JDBC service. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001148
|
Info: Shutdown of the JDBC service failed.
|
Description
| Shutdown of the JDBC service failed. |
|
Cause
| Check earlier messages that are printed in the log. |
|
Action
| No action required. |
|
|
BEA-001149
|
Info: Shutdown of the JDBC service completed.
|
Description
| Shutdown of the JDBC service completed. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001150
|
Error: Connection Pool "poolName" deployment failed with the following error: err.
|
Description
| Unable to deploy the connection pool due to the reason indicated. |
|
Cause
| Cause should be indicated in the exception message. |
|
Action
| Correct the problem described in the exception message. |
|
|
BEA-001151
|
Error: Data Source "poolName" deployment failed with the following error: err.
|
Description
| Unable to deploy the data source due to the reason indicated. |
|
Cause
| Should be indicated in the exception message. |
|
Action
| Correct the problem described in the exception message. |
|
|
BEA-001152
|
Info: Cannot enable statement caching for connection in pool "pool", because it is using the WebLogic Type-2 XA driver.
|
Description
| Statement caching has been disabled for the specified connection pool, because it is using the WebLogic Type-2 XA driver. |
|
Cause
| Statement caching has been disabled for the specified connection pool, because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to no longer be valid. |
|
Action
| No action required. Use a different driver if you want to use the prepared statement cache with the driver. |
|
|
BEA-001153
|
Warning: Forcibly releasing inactive connection "conn" back into the connection pool "pool", currently reserved by: user.
|
Description
| The indicated connection is being forcibly released back into the indicated connection pool. |
|
Cause
| The connection was found to be unused by the application for the specified duration (configured using InactiveConnectionTimeoutSeconds attribute of the pool MBean), and hence is being forcibly released back into pool. |
|
Action
| Check the application code for leakages of connection objects, or tune the configured value of the specifed pool attribute. |
|
|
BEA-001154
|
Info: Disabling statement caching for connection in pool "pool", because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.
|
Description
| Statement caching has been disabled for the specified connection pool, because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS. |
|
Cause
| Statement caching has been disabled for the specified connection pool, because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to be no longer valid. Pointbase DBMS does not allow the reuse of cached Statements across table drops and creates. Therefore statement caching has been disabled. |
|
Action
| Use a different driver if you want to use the prepared statement cache with the driver. If you are using Pointbase DBMS and are NOT dropping and creating tables in your application, you can enable Statement caching at runtime by setting the attribute StatementCacheSize of the pool JDBCConnectionPoolMBean. |
|
|
BEA-001155
|
Info: The following exception has occurred: \n
|
Description
| A stack trace is being printed for an exception that occurred. |
|
Cause
| An error condition has occurred. |
|
Action
| Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem. |
|
|
BEA-001156
|
Info: Stack trace associated with message id follows: \n
|
Description
| A stack trace for a previously logged message is being printed. |
|
Cause
| An error condition was reported. |
|
Action
| No action required. |
|
|
BEA-001157
|
Info: Connection pool "poolName" being suspended by user "subject".
|
Description
| The specified connection pool is being suspended by the specified user. All access to the pool and its connections will be frozen, until the pool is resumed. |
|
Cause
| The specified connection pool is being suspended, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001158
|
Info: Connection pool "poolName" being forcibly suspended by user "subject".
|
Description
| The specified connection pool is being forcibly suspended by the specified user. All current users of connections in the pool will be forcibly logged off. All access to the pool and its connections will be frozen, until the pool is resumed. |
|
Cause
| The specified connection pool is being forcibly suspended, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001159
|
Info: Connection pool "poolName" is being resumed by user "subject".
|
Description
| The specified connection pool is being resumed by the specified user. All access to the pool and its connections will be restored. |
|
Cause
| The specified connection pool is being resumed, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001160
|
Info: Connection pool "poolName" being forcibly destroyed by user "subject"
|
Description
| The specified connection pool is being forcibly destroyed by the specified user. All current users of connections in the pool will be forcibly logged off. All information about the pool will be deleted from the configuration. |
|
Cause
| The specified connection pool is being forcibly destroyed, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001161
|
Info: Connection pool "poolName" being destroyed by user "subject".
|
Description
| The specified connection pool is being destroyed by the specified user. All information about the pool will be deleted from the configuration. |
|
Cause
| The specified connection pool is being destroyed, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001162
|
Info: Connection pool "poolName" being forcibly shutdown by user "subject".
|
Description
| The specified connection pool is being forcibly shutdown by the specified user. All current users of connections in the pool will be forcibly logged off. |
|
Cause
| The specified connection pool is being forcibly shutdown, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001163
|
Info: Connection pool "poolName" being shutdown by user "subject".
|
Description
| The specified connection pool is being shutdown by the specified user. |
|
Cause
| The specified connection pool is being shutdown, as requested by the application. |
|
Action
| No action required. |
|
|
BEA-001164
|
Warning: Unable to initialize connection in pool "poolName". Initialization SQL = "query". Received exception: "ex".
|
Description
| Unable to initialize a connection of the specified pool due to failure. |
|
Cause
| Exception message should contain a reason for the failure. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001165
|
Warning: Invalid statment cache size "size" specified for connection in pool "poolName".
|
Description
| An invalid value has been specified for statement cache size for connections in the indicated pool. |
|
Cause
| An invalid value has been specified for statement cache size for connections in the indicated pool. |
|
Action
| Check the allowed limits for statement cache size for this pool and fix the specified value. |
|
|
BEA-001166
|
Error: Activation of application-scoped pool "appName":"moduleName":"poolName" failed. Received exception: "ex".
|
Description
| An attempt to activate the indicated application-scoped connection pool has failed for the indicated reason. |
|
Cause
| The error message should contain the reason for the failure. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001167
|
Error: Deactivation of application-scoped pool "appName":"moduleName":"poolName" failed. Received exception: "ex".
|
Description
| An attempt to deactivate the indicated application-scoped connection pool has failed for the indicated reason. |
|
Cause
| The error message should contain the reason for the failure. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001168
|
Warning: Attempt to resume JDBCService when it is already running...Ignoring.
|
Description
| JDBCService is ignoring the call to resume it, as it is already running. |
|
Cause
| Application attempted to resume JDBCService, although the service is already running. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001169
|
Error: Error occured during shutdown of pool "name". Received exception: "err".
|
Description
| Shutdown of indicated pool failed due to the indicated error. |
|
Cause
| Message should contain the reason for the failure. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001170
|
Error: Unable to initialize JDBC Log. Received exception: "err".
|
Description
| Initialization of JDBC Log failed due to the indicated error. |
|
Cause
| Message should contain reason for failure. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001171
|
Error: Unable to close connection "conn". Received exception: "err".
|
Description
| Close operation on a connection failed due to the indicated reason. |
|
Cause
| Message should contain reason for failure. |
|
Action
| Take suitable action if possible. Otherwise, contact Oracle Support. |
|
|
BEA-001172
|
Error: Error occured during shutdown of data source "name". Received exception: "err".
|
Description
| Shutdown of indicated data source failed due to the indicated error. |
|
Cause
| Message should contain the reason for the failure. |
|
Action
| Take appropriate corrective action. |
|
|
BEA-001173
|
Info: "TestTableName" attribute for pool "poolName" being dynamically changed to "newName".
|
Description
| The attribute that controls the testing of connections at run time and creation time is being dynamically modified. |
|
Cause
| This is an informational message. |
|
Action
| No action required. |
|
|
BEA-001174
|
Info: Creating Data Source named dsName, JNDI Name = poolName.
|
Description
| The named Data Source is being created. |
|
Cause
| The user requested that the Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001175
|
Info: Creating TX Data Source named dsName for Pool poolName.
|
Description
| The named Transactional Data Source is being created. |
|
Cause
| The user requested that the Transactional Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001176
|
Info: Creating Multi Pool named poolName.
|
Description
| The named multipool is being created. |
|
Cause
| The user requested that the multipool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001177
|
Info: Creating Connection Pool named poolName, URL = url, Properties = props.
|
Description
| The named connection pool is being created. |
|
Cause
| The user requested that the connection pool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001178
|
Info: Attempt to set query timeout on a statement failed : error
|
Description
| JDBC Driver threw the indicated error when WebLogic Server attempted to configure a query timeout for the statement. |
|
Cause
| Message should contain a description of the failure. |
|
Action
| Contact Oracle Technical Support. |
|
|
BEA-001250
|
Error: Unable to load application configured callback cbClassName for MultiPool name, got error: error. Application control of MultiPool failover behaviour will not work.
|
Description
| WebLogic Server is unable to load the indicated application-defined class. Due to this, the indicated feature will not work. |
|
Cause
| This is most likely because the application-defined class location has not been added to the CLASSPATH environment varible. |
|
Action
| Please check your CLASSPATH setting and retry. If problem persists, contact Oracle Technical Support. |
|
|
BEA-001251
|
Error: Application configured callback cbClassName for MultiPool name does not implement required interface ifName. Application control of MultiPool failover behaviour will not work.
|
Description
| Configured application callback does not implement the required interface. As a result, indicated WebLogic Server feature will not function correctly. |
|
Cause
| Configured callback cbClassName does not implement required interface ifName. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001252
|
Error: Unable to add notification listener for Config MBean for MultPool name failed, got exception: err.
|
Description
| Call to internal WebLogic Server APIs failed with the indicated exception. |
|
Cause
| Received exception should indicate cause of failure. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001254
|
Error: MultiPool mp unable to disable connection pool cp, got exception: err.
|
Description
| Named MultiPool received the indicated exception when trying to disable the specified connection pool. |
|
Cause
| Received exception should indicate cause of failure. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001255
|
Error: MultiPool mp unable to disable connection pool cp, got exception: err.
|
Description
| Named MultiPool received the indicated exception when trying to disable the specified connection pool. |
|
Cause
| Received exception should indicate cause of failure. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001256
|
Info: Dynamically changing value of attribute FailoverRequestIfBusy for MultiPool name from curr to new.
|
Action
| Informational message, no action required. |
|
|
BEA-001257
|
Info: Dynamically changing value of attribute HealthCheckFrequencySeconds for MultiPool name from curr to new.
|
Action
| Informational message, no action required. |
|
|
BEA-001258
|
Error: Unable to setup timer for MultiPool mp, got exception: err.
|
Description
| Call to internal WebLogic Server APIs failed with the indicated exception. |
|
Cause
| Received exception should indicate cause of failure. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001259
|
Info: Application has disallowed MultiPool mp from re-enabling connection pool cp, which had previously been found dead and was disabled.
|
Action
| Informational message, no action required. |
|
|
BEA-001260
|
Error: MultiPool mp unable to enable connection pool cp, got exception: err.
|
Description
| Named MultiPool received the indicated exception when trying to enable the specified connection pool. |
|
Cause
| Received exception should indicate cause of failure. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001261
|
Error: MultiPool mp unable to enable connection pool cp, got exception: err.
|
Description
| Named MultiPool received the indicated exception when trying to enable the specified connection pool. |
|
Cause
| Received exception should indicate cause of failure. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001262
|
Info: Registered application callback cbClass for MultiPool mp to control MultiPool failover behavior.
|
Action
| Informational message only, no action required. |
|
|
BEA-001500
|
Info: Creating Application Scoped Multi Pool name, algorithm type alg for Application appName, Module moduleName.
|
Description
| The named Application Scoped Multi Pool is being created. |
|
Cause
| The user requested that the Multi Pool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001501
|
Info: Creating Multi Pool name, algorithm type alg.
|
Description
| The named Multi Pool is being created. |
|
Cause
| The user requested that the Multi Pool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001503
|
Info: Creating Application Scoped Connection Pool name for Application appName, Module moduleName, URL = url, Properties = props.
|
Description
| The named Application Scoped connection pool is being created. |
|
Cause
| The user requested that the connection pool be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001504
|
Info: Destroying Multi Pool name, created for Application appName, Module moduleName.
|
Description
| The named Application Scoped Multi Pool is being destroyed. |
|
Cause
| The user requested that the Multi Pool be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001505
|
Info: Destroying Multi Pool name.
|
Description
| The named Multi Pool is being destroyed. |
|
Cause
| The user requested that the Multi Pool be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001507
|
Info: Destroying Connection Pool name, created for Application appName, Module moduleName.
|
Description
| The named Application Scoped Connection Pool is being destroyed. |
|
Cause
| The user requested that the Connection Pool be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001508
|
Info: Destroying Connection Pool name.
|
Description
| The named Connection Pool is being destroyed. |
|
Cause
| The user requested that the Connection Pool be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001510
|
Info: Creating Application Scoped Data Source name for Application appName, Module modName, Application Context Name = ctxName.
|
Description
| The named Application Scoped data source is being created. |
|
Cause
| The user requested that the data source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001512
|
Info: Data Source name has been successfully created.
|
Description
| The named data source has been successfully created. |
|
Cause
| The user requested that the data source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001513
|
Info: Destroying Application Scoped Data Source name, created for Application appName, Module modName.
|
Description
| The named Application Scoped data source is being destroyed. |
|
Cause
| The user requested that the data source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001514
|
Info: Destroying Data Source name.
|
Description
| The named data source is being destroyed. |
|
Cause
| The user requested that the data source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001515
|
Info: Data Source name has been successfully destroyed.
|
Description
| The named data source has been successfully destroyed. |
|
Cause
| The user requested that the data source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001516
|
Info: Connection Pool "poolName" connected to Database: "DBName", Version: "DBVer".
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001517
|
Info: Connection Pool "poolName" using Driver: "DriverName", Version: "DriverVer".
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001518
|
Info: Connection Pool "poolName" Connection Usage Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001519
|
Info: Id : "id"
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001520
|
Info: Timestamp : "timestamp"
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001521
|
Info: User : "user"
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001522
|
Info: Connection Pool "poolName" Connection Wait Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001523
|
Info: Connection Pool "poolName" Connection Leak Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001524
|
Info: Connection Pool "poolName" Connection Reserve Fail Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001525
|
Info: Connection Pool "poolName" Statement Cache Entry Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001526
|
Error: Unable to load class "className", got exception : error. Driver Interception feature disabled.
|
Description
| WebLogic Server is unable to load the indicated application-defined class. Due to this, the indicated feature will not work. |
|
Cause
| This is most likely because the application-defined class location has not been added to the CLASSPATH environment varible. |
|
Action
| Please check your CLASSPATH setting and retry. If problem persists, contact Oracle Technical Support. |
|
|
BEA-001527
|
Error: Application configured class className does not implement required interface typeName. Driver Interception feature disabled.
|
Description
| Configured application class does not implement the required interface. As a result, indicated WebLogic Server feature will not function correctly. |
|
Cause
| Configured class className does not implement required interface typeName. |
|
Action
| Please consult WebLogic Server documentation, or contact Oracle Technical Support. |
|
|
BEA-001528
|
Info: Driver Interceptor class className loaded.
|
Description
| Configured application class successfully loaded to enable Driver Interception feature. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001529
|
Info: JDBC LLR (logging last resource) connection pool poolName did not find its table and is creating a new one using the following SQL:\n sql
|
Description
| JDBC LLR connection pools create a table per server for use by the transaction manager to store transaction records. Multiple LLR connection pools within a server may share a table. For instructions on customizing the LLR connection pool table name and location, see the documentation. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001530
|
Info: JDBC LLR (logging last resource) connection pool poolName retrieved recordCount record(s) from the database table dmlName.
|
Description
| JDBC LLR connection pools create a table per server for use by the transaction manager to store transaction records. Multiple LLR connection pools within a server may share a table. For instructions on customizing the LLR connection pool table name and location, see the documentation. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001531
|
Warning: Received updated event for unexpected type of bean: bean.
|
Description
| Received unexpected bean update event. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001532
|
Info: Connection Pool "poolName" Statement Usage Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001533
|
Info: Pool Name : "id"
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001534
|
Info: Connection Pool "poolName" Connection Last Usage Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001535
|
Info: Connection Pool "poolName" Connection Multi-threaded Usage Data:
|
Description
| Informational Message. |
|
Cause
| Informational Message. |
|
Action
| No action required. |
|
|
BEA-001536
|
Info: Creating Multi Data Source named dsName, JNDI Name = poolName.
|
Description
| The named Multi Data Source is being created. |
|
Cause
| The user requested that the Multi Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001537
|
Info: Creating Application Scoped Multi Data Source name for Application appName, Module modName, Application Context Name = ctxName.
|
Description
| The named Application Scoped Multi Data Source is being created. |
|
Cause
| The user requested that the Multi Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001538
|
Info: Created Multi Data Source named dsName.
|
Description
| The named Multi Data Source has been created. |
|
Cause
| The user requested that the Multi Data Source be created, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001539
|
Info: Destroying Multi Data Source name.
|
Description
| The named Multi Data Source is being destroyed. |
|
Cause
| The user requested that the Multi Data Source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001540
|
Info: Destroying Application Scoped Multi Data Source name, created for Application appName, Module modName.
|
Description
| The named Application Scoped Multi Data Source is being destroyed. |
|
Cause
| The user requested that the multi data source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001541
|
Info: Destroyed Multi Data Source named dsName.
|
Description
| The named Multi Data Source has been destroyed. |
|
Cause
| The user requested that the Multi Data Source be destroyed, either implicitly or explicitly. |
|
Action
| No action required. |
|
|
BEA-001542
|
Info: JVM DriverManager Login Timeout value set to timeout.
|
Description
| This WLS JVMs JDBC Driver Managers login timeout value has been set to the value specified. Any JDBC driver loaded into this JVM that tries to create JDBC connections can access and make use of this setting. |
|
Cause
| Application has specified this behavior to be enabled, via the corresponding configuration setting. |
|
Action
| No action required. |
|
|
BEA-001543
|
Warning: Received change event: event for unexpected type of bean: bean.
|
Description
| Received unexpected bean update event. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001544
|
Warning: Received add event: event for unexpected type of bean: bean.
|
Description
| Received unexpected bean update event. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001545
|
Warning: Received unexpected event: event for unexpected type of bean: bean.
|
Description
| Received unexpected bean update event. |
|
Cause
| Information message. |
|
Action
| No action required. |
|
|
BEA-001546
|
Info: Connection pool "poolName" is being started by user "subject".
|
Description
| The specified connection pool is being started by the specified user. All access to the pool and its connections will be restored. |
|
Cause
| The specified connection pool is being started, as requested by the administrator. |
|
Action
| No action required. |
|
|
BEA-001547
|
Error: The "type" field value "val" in table reference "tableRef" (format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "maxLength" for this field.
|
Description
| Databases have limits on the length of identifiers. |
|
Cause
| Configuration error. |
|
Action
| When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name. |
|
|
BEA-001548
|
Error: Empty field value in table reference "tableRef" (format [[[catalog.]schema.]table).
|
Description
| The location of the JDBC table has been configured incorrectly. |
|
Cause
| Configuration error. |
|
Action
| Make sure the entire table reference is blank, or that the table field is not blank. If there is no schema, make sure there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references. |
|
|
BEA-001549
|
Info: An old style WebLogic driver URL oldURL is used. Because the WebLogic driver URL auto-convert switch is turned on, it is converted to newURL
|
Description
| An old style WebLogic driver URL is used. Because the WebLogic driver URL auto-convert switch is turned on, the old style URL is converted to new style. |
|
Cause
| An old style WebLogic driver URL is used and the WebLogic driver URL auto-convert switch is turned on. |
|
Action
| No action required. |
|
|
BEA-001550
|
Warning: WebLogic Oracle driver is used. The driver URL is anURL. WebLogic Server does not support WebLogic Oracle driver any more.
|
Description
| WebLogic Oracle driver is used. WebLogic Server does not support WebLogic Oracle driver any more. |
|
Cause
| WebLogic Oracle driver is deprecated and removed. |
|
Action
| Stop using WebLogic Oracle driver, using Oracle Thin driver instead. |
|
|
BEA-001551
|
Error: Application context for member data source memberDS not found for standalone multi-data source module multiDS. Ensure that multi-data source standalone modules have a higher deployment order than member data source standalone modules.
|
Description
| Application context for member data source memberDS not found for standalone multi-data source module multiDS. Ensure that multi-data source standalone modules have a higher deployment order than member data source standalone modules. |
|
Cause
| The deployment order of the multi-data source is the same or lower than one of its member datasources. |
|
Action
| Change the deployment order of the standalone multi-data source to be greater than each member data sources deployment order. |
|
|
BEA-001552
|
Warning: The Logging Last Resource (LLR) data source dsName will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.
|
Description
| LLR requires remote JDBC access when the data source participates in a global transaction that spans two or more WebLogic Server instances. |
|
Cause
| Remote JDBC access over RMI is disabled. |
|
Action
| Either configure the data source to use a XA-capable driver, or enable remote JDBC on all servers. |
|
|
BEA-001553
|
Error: Unable to deploy JDBC data source dsName. No credential mapper entry found for password indirection user user
|
Description
| The JDBC data source dsName is configured to use password indirection which requires a credential mapper entry to be pre-configured in order to obtain the password to use in authenticating database connections. However, no credential mapper entry was found for the specified user user. |
|
Cause
| No credential mapper entry was found for user user on data source dsName |
|
Action
| Ensure that a credential mapper entry is defined for the data source dsName that maps the specified user name user to a password. The WebLogic Server administration console provides support for managing data source credential mapper entries. |
|
