BPEL Adapter Exceptions ORABPEL 03000 - 03015
BPEL Adapter Exceptions ORABPEL 03000 - 03015
Adapter Exceptions 03000 - 03015
ORABPEL-03000
severity: 10
type: error
name: Cannot bind adaptors
description: The process domain was unable to bind the connection/database adaptors for \"{0} \", datasource \"{1}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
ORABPEL-03001
severity: 10
type: error
name: Cannot lookup datasource type
description: The process domain was unable to determine the database type. The version table contains the vendor type for the current datasource. The exception reported is: {0}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for OraBPEL has been installed in the datasource.
ORABPEL-03002
severity: 10
type: error
name: Cannot lookup db schema version
description: The server was unable to lookup the database schema version. The version table is used to verify that the proper database schema has been installed for use with the server. The exception reported is: {0}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for OraBPEL has been installed in the datasource.
ORABPEL-03003
severity: 10
type: error
name: Incorrect db schema version
description: The database schema version \"{0}\" from the database does not match the version \"{1}\" expected by the server.
fix: The database schema currently in place has probably been configured for a previous release; please re-install the database schema and try to start the server again.
ORABPEL-03004
severity: 10
type: error
name: Missing datasource type
description: The database table \"version\" does not contain a datasource vendor type. This value is used by the process domain to initialize resources used to connect to the JDBC datasource.
fix: The database schema may have been modified by hand. Please re-install the database schema and try to start the process domain again.
ORABPEL-03005
severity: 10
type: error
name: Missing db schema version
description: The database table \"version\" does not contain a version guid. This guid is used by the server to verify that the correct database schema is currently installed.
fix: The database schema may have been modified by hand. Please re-install the database schema and try to start the server again.
ORABPEL-03010
severity: 10
type: error
name: Error while creating adaptor manifest
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor manifest for \"{1}\", datasource \"{2}\". The exception reported is: {3}
ORABPEL-03011
severity: 10
type: error
name: Wrong adaptor manifest interface
description: The class \"{0}\" (for the adaptor manifest for \"{1}\", datasource \"{2}\") does not implement the IAdaptorManifest interface. All adaptor manifests used by the OraBPEL server must implement this interface.
ORABPEL-03012
severity: 10
type: error
name: Unknown adaptor manifest classname
description: The adaptor manifest classname for \"{0}\", datasource \"{1}\" has not been specified.
ORABPEL-03013
severity: 10
type: error
name: Cannot instantiate class
description: Cannot instantiate an instance for the class \"{0}\". Java classes that need to be dehydrated/rehydrated within the OraBPEL server must implement the java.io.Serializable interface. These classes must implement a default constructor.
ORABPEL-03014
severity: 10
type: error
name: Cannot install PointBase schema
description: The process domain was unable to create the schema for PointBase. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
ORABPEL-03015
severity: 10
type: error
name: Cannot install Oracle Lite schema
description: The process domain was unable to create the schema for Oracle Lite. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
Adapter Exceptions 03000 - 03015
ORABPEL-03000
severity: 10
type: error
name: Cannot bind adaptors
description: The process domain was unable to bind the connection/database adaptors for \"{0} \", datasource \"{1}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
ORABPEL-03001
severity: 10
type: error
name: Cannot lookup datasource type
description: The process domain was unable to determine the database type. The version table contains the vendor type for the current datasource. The exception reported is: {0}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for OraBPEL has been installed in the datasource.
ORABPEL-03002
severity: 10
type: error
name: Cannot lookup db schema version
description: The server was unable to lookup the database schema version. The version table is used to verify that the proper database schema has been installed for use with the server. The exception reported is: {0}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for OraBPEL has been installed in the datasource.
ORABPEL-03003
severity: 10
type: error
name: Incorrect db schema version
description: The database schema version \"{0}\" from the database does not match the version \"{1}\" expected by the server.
fix: The database schema currently in place has probably been configured for a previous release; please re-install the database schema and try to start the server again.
ORABPEL-03004
severity: 10
type: error
name: Missing datasource type
description: The database table \"version\" does not contain a datasource vendor type. This value is used by the process domain to initialize resources used to connect to the JDBC datasource.
fix: The database schema may have been modified by hand. Please re-install the database schema and try to start the process domain again.
ORABPEL-03005
severity: 10
type: error
name: Missing db schema version
description: The database table \"version\" does not contain a version guid. This guid is used by the server to verify that the correct database schema is currently installed.
fix: The database schema may have been modified by hand. Please re-install the database schema and try to start the server again.
ORABPEL-03010
severity: 10
type: error
name: Error while creating adaptor manifest
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor manifest for \"{1}\", datasource \"{2}\". The exception reported is: {3}
ORABPEL-03011
severity: 10
type: error
name: Wrong adaptor manifest interface
description: The class \"{0}\" (for the adaptor manifest for \"{1}\", datasource \"{2}\") does not implement the IAdaptorManifest interface. All adaptor manifests used by the OraBPEL server must implement this interface.
ORABPEL-03012
severity: 10
type: error
name: Unknown adaptor manifest classname
description: The adaptor manifest classname for \"{0}\", datasource \"{1}\" has not been specified.
ORABPEL-03013
severity: 10
type: error
name: Cannot instantiate class
description: Cannot instantiate an instance for the class \"{0}\". Java classes that need to be dehydrated/rehydrated within the OraBPEL server must implement the java.io.Serializable interface. These classes must implement a default constructor.
ORABPEL-03014
severity: 10
type: error
name: Cannot install PointBase schema
description: The process domain was unable to create the schema for PointBase. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
ORABPEL-03015
severity: 10
type: error
name: Cannot install Oracle Lite schema
description: The process domain was unable to create the schema for Oracle Lite. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.
Comments