Oracle® Fusion Middleware Messages for Oracle Service Bus
11g Release 1 (11.1.1.3)

E15034-01

Back to Index Page


OSB-Reporting Subsystem Messages

The OSB-Reporting catalog contains messages in the range BEA473500 - BEA473599. Messages in this catalog are part of the com.bea.wli.reporting.jmsprovider Internationalization package and the com.bea.wli.reporting.jmsprovider Localization package.

BEA-473500

Error: JMS Reporting Data Manager failed to deploy during server start up ex

Description

The JMS Reporting Data Manager failed to deploy during server start up. This could be caused by insufficient Security privileges, missing Reporting Tables, or a lost Database Connection.

Cause

JMS Reporting Data Manager failed to deploy successfully.

Action

Please verify the users Security privileges and the existence of Reporting Tables and/or a Database Connection If there are no Reporting Tables, please run the JMS Reporting Provider Database Script.

BEA-473501

Error: The JMS Reporting Data Manager failed to undeploy ex

Description

There was a problem with undeployment: all of the messages were already processed.

Cause

The JMS Reporting Data Manager failed to undeploy.

Action

Please contact Oracle Support with your log details.

BEA-473502

Error: Message reports are not persisted in the Reporting Table for MSG_GUID = messageId ex

Description

Message Reports are not persisting in the Reporting Table.

Cause

An unexpected error occurred when creating insert statement for message reports. There should be an error message that points to cause of the problem.

Action

Please contact Oracle Support with your log details.

BEA-473503

Error: A SQL Exception occurred during Message Reporting. Persistence with the SQL State is sqlState and the Error Code is ErrorCode ex

Description

A SQL Exception occurred while Message Reports were being inserted into the Message table.

Cause

The Exception was caused by a Database failure.

Action

Please refer to the log for the source of the failure or contact Oracle Support.

BEA-473504

Error: The JMS Report Data Handler failed to send the message to the JMS Queue : message ex

Description

The JMS Report Data Handler failed to send a message to the JMS Queue.

Cause

There may be no JMS Connection Factory or the data may be invalid.

Action

Please refer to the log for the source of the failure or contact Oracle Support.

BEA-473505

Error: JMS Reporting does not support this type of Database : driverName

Description

JMS Reporting does not support this type of Database.

Cause

The Database type is not supported.

Action

Please use a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.

BEA-473506

Error: An Error occurred while determining the Database type ex

Description

An Error occurred when determing the Database type.

Cause

The type of Database may not be supported or the Database may be disconnected.

Action

Please check your Database connection and that you are using a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.

BEA-473507

Error: JMS Reporting does not support this type of Database.

Description

JMS Reporting does not support this type of Database.

Cause

The Database type is not supported.

Action

Please use a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.

BEA-473508

Error: The Database connection is disconnected ex

Description

The Database is connection disconnected.

Cause

Database connection has been lost.

Action

Please check the Database connection.

BEA-473509

Error: The ReportingMDB received an invalid Object type and the message will not be processed ex

Description

The ReportingMDB received an invalid Object for processing. It requires a ReportMessage type object.

Action

Please contact Oracle Support.

BEA-473510

Error: An unexpected error occurred while processing the message in ReportingMDB ex

Description

An unexpected error occurred while processing the message in ReportingMDB.

Action

Please refer to the log for the source of the error or contact Oracle Support

BEA-473511

Error: Failed to lookup the JNDI Provider for the JMS Reporting datasource ex

Description

Failed to look up the configured JNDI Provider for the JMS Reporting datasource

Action

Please verify that the JNDI Provider referred to by JMS Reporting is up and running.

BEA-473512

Error: An error occured while retrieving the report data from the Reporting table.

Description

An error occured while retrieving the report data from the Reporting table.

Action

Please contact Oracle Support.

BEA-473513

Error: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Description

The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Action

Please verify the Payload or contact Oracle support.

BEA-473514

Error: An unexpected error occurred while receiving the message in ReportingMDB ex

Description

An unexpected error occurred while receiving the message in ReportingMDB. The message will not be processed.

Action

Please refer to the log for the source of the failure or contact Oracle Support.

BEA-473516

Error: An invalid message format was received in ReportMDB metadata. The message will not be processed. ex

Description

An Invalid message format was received. The message will not be processed.

Action

Please verify the Payload or the Report action configuration.

BEA-473517

Error: The JMS Reporting Provider Database tables weren't created and the JMS Reporting Data Manager didn't deploy.

Description

The JMS Reporting Provider Database tables weren't created and the JMS Reporting Data Manager didn't deploy.

Action

Please run the JMS Reporting Provider Database Script and restart the server.

BEA-473518

Error: An error occurred while inserting data into the Reporting Table with a batch update ex

Description

The Batch update failed.

Action

Please make sure batch update supports your database JDBC driver.

BEA-473519

Error: An error occurred when initializing the PurgingMDB ex

Description

Report messages will not be deleted due to an error in resource initialization.

Action

Please verify that the PurgingMDB is deployed and your database connection.

BEA-473520

Error: An error occurred while initializing the ReportingMDB and Database details.

Description

The ReportingMDB and Database details were not initialized.

Action

Please verify your Database connection.

BEA-473521

Error: No transaction is available to process the Report Message.

Description

No transaction is available to process the Report Message.

Action

Please refer to the log to determine why the transaction is unavailable and/or retry sending the request. If the problem persists, please contact Oracle support

BEA-473522

Error: An error occurred while inserting data into the Reporting Table with Batch Update {0}

Description

The Batch Update failed.

Action

Please make sure the Batch Update supports the database JDBC Driver.

BEA-473523

Error: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Description

The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Cause

Invalid payload

Action

Please verify the Payload.

BEA-473524

Error: Could not initialize PurgingMDB and Database details.

Description

Could not initialize PurgingMDB and Database details.

Action

Please verify the Database Connection.

BEA-473525

Error: Failed to lookup the JNDI Provider for the JMS Reporting datasource {0}

Description

Failed to look up the configured JNDI Provider for the JMS Reporting datasource

Action

Make sure that the JNDI provider referred to by JMS Reporting is up and running.

BEA-473526

Error: There is no Database connection.

Description

There is no Database connection.

Action

Please verify the Network connection.

BEA-473527

Error: There is No Report Index.

Description

There is No Report Index.

Cause

There is a Missing Key-Value pair in the Report Action.

Action

Please add a Key-Value pair to the Report Action.

 

Back to Index Page

Copyright © 2008, 2010, Oracle. All rights reserved.