Date Created: Thu Feb 20 11:08:26 EST 2003
BIB-1000Cause: The name that was specified in the createComponentObject
method is already bound to another ComponentObject
.
Action: Specify a different name for the ComponentObject
, or specify null so that the name will be generated automatically.
Cause: In remote mode (such as CORBA), exceptions that occur in the middle tier are transported back to the client through Piggyback streams. This exception merely wraps the exception for transporting purposes.
Action: No action is necessary.
ApplicationModule
.Cause: An exception occurred while creating the ApplicationModule
object.
Action: Check the reason that is provided in the message and take the appropriate action. Check the underlying error stack to find the root cause of the problem.
ApplicationModuleHome
cannot be found or created.Cause: The ApplicationModuleHome
cannot be found or created.
Action: Ensure that the middle tier is running and deployed correctly.
Cause: The BI Beans configuration file that is specified by the application for the BISession
cannot be found. This error can occur during the preview of a UIX page, if the project has not been built.
Action: Ensure that the file that is specified exists and can be located through the CLASSPATH setting if the file that you specified uses a relative path. If this error occurs during the preview of a UIX page, then build the project and try again.
Cause: The format of the BI Beans configuration file is not correct.
Action: Ensure that the BI Beans configuration file is a valid XML file. Check the underlying error stack to find the root cause of the problem.
ManagerFactory
.Cause: An exception has occurred while instantiating the ManagerFactory
.
Action: Check the underlying error stack to find the root cause of the problem.
ErrorHandler
.Cause: An exception has occurred while creating the ErrorHandler
that is specified in the BI Beans configuration file.
Action: Check the underlying error stack to find the root cause of the problem. Ensure that the class name that is specified for the ErrorHandler
inside the configuration file is correct.
DSSApplicationModule
client proxy.Cause: An exception occurred while creating the DSSApplicationModule
client proxy (in remote mode)
Action: Ensure that the JAR file that contains the remote proxy classes are in the client-tier CLASSPATH setting.
Cause: An exception occurred while disconnecting the current session.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An exception occurred while connecting the session.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The specified column number was greater than the total number of columns.
Action: Get the total number of columns from the DataAccess
, by calling the getColumnCount
method of the graph or of the column header in the table or crosstab. Then you can specify a column that does not exceed the total number of columns.
Cause: The specified row number was greater than the total number of rows.
Action: Get the total number of rows from the DataAccess
, by calling the getRowCount
method of the graph or of the column header in the table or crosstab. Then you can specify a row that does not exceed the total number of rows.
Cause: The specified slice number was greater than the total number of slices.
Action: Specify a slice that does not exceed the total number of slices.
Cause: The specified layer was greater than the total number of layers that are available on the given edge.
Action: Specify a layer that does not exceed the total number of layers.
Cause: The specified series was greater than the total series that is available in the graph.
Action: Specify a series that does not exceed the total series. The Graph.getDisplaySeries
method should provide the number of series that are displayed in the graph. Or, if Graph.isDataRowShownAsASeries
returns true
, then Graph.getRowCount
returns the number of series that can be displayed. If Graph.isDataRowShownAsASeries
returns false
, then Graph.getColumnCount
returns the total number of series that can be displayed.
Cause: The specified edge was greater than the total number of edges that are available on the given edge. Valid edges for methods that require an edge are: DataDirector.COLUMN_EDGE
, DataDirector.ROW_EDGE
, and DataDirector.PAGE_EDGE
. Application developers should not pass any other values as an edge
parameter.
Action: Specify a valid edge constant.
Cause: The DataSource
does not support the required type of data in its DataMap
. For example, the view requested DataMap.DATA_GROUPSORT
information, and the DataSource
that the view uses does not supply group sort information.
Action: Request support for the required data types in the DataSource
, or use a different DataSource
.
Cause: The specified DTD cannot be found. The XML parser needs a DTD in order to validate XML files.
Action: Ensure that the specified DTD file exists, or disable XML validation. DTDs for views are in their BI Beans packages. The graph.dtd
file is in oracle.dss.graph
. The table.dtd
file is in oracle.dss.table
. The crosstab.dtd
file is in oracle.dss.crosstab
. To turn off validation, call Dataview.setXMLValidated(false);
.
Cause: No default Mergeable
object was provided to resolve rules.
Action: Provide at least one default Mergeable
object, so that rules can be resolved. For more information about Mergeable
objects, see the javadoc for the oracle.dss.rules.Mergeable
interface, or look in BI Beans Help for topics on rules.
merge(Mergeable)
on an incompatible Mergeable
class.Cause: An attempt was made to merge incompatible Mergeable
classes. You can only merge two Mergeable
objects of the same class. For example, ViewStyle
objects can be merged together, but a ViewStyle
cannot be merged with a ViewFormat
.
Action: Merge two classes that are compatible. For more information, see the javadoc for the oracle.dss.rules.RuleBundle
class, or look in the BI Beans Help for topics on rules.
Cause: An X Server connection was not established. Graph cannot generate dynamic images.
Action: Ensure that the DISPLAY environment variable is set and is pointing to a valid X Server or XVFB instance.
Cause: An invalid edge identifier was passed when trying to set the Suppression
property.
Action: Ensure that the parameter to setSuppression
is within the range.
Cause: A development environment tried to activate the QueryManager's customizer, but the QueryBuilder classes could not be found.
Action: Ensure that the querybuilder.jar
file is available and in the development environment's CLASSPATH setting.
QueryManagerObject
type.Cause: A call to the clone
method passed in a subclass that does not override the QueryManager
constructor that requires a QueryManagerObject
argument.
Action: Override all of the QueryManager
constructors in any subclass.
createComponentObject
on BISession
object.Cause: An error has occurred in the BI Beans setup.
Action: Invoke the printStackTrace method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
Cause: An error has occurred while trying to copy the specified event.
Action: Invoke the printStackTrace method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
initCubeQuery
.Cause: A null measure list was passed to the initCubeQuery
method.
Action: Pass in a valid list of measures to the initCubeQuery
method.
initQuery
.Cause: Arguments for dimensions and a measure list were both null when passed to the initQuery
method.
Action: Pass in a valid value for either one or both of these arguments when calling the initQuery
method.
Cause: The client QueryManager
could not obtain the cursor that was established on the middle tier.
Action: Investigate whether Oracle OLAP and the middle tier are running properly.
Cause: The specified index was out of range in the method that was called for the specified edge and dimension arguments.
Action: Ensure that the index is valid when calling the method.
Cause: The specified dimension was out of range in the method that was called for the specified edge and dimension arguments.
Action: Ensure that the dimension is valid when calling the method.
Selection
argument must not be null.Cause: A null Selection
was passed to a method call.
Action: Call the method with a valid Selection
argument.
QueryManager
or subclass when cloning.Cause: Could not call the constructor that takes a QueryManagerObject
parameter when trying to clone a QueryManager
or a subclass of QueryManager
.
Action: If the actual object is a subclass of QueryManager
, then examine the subclass constructors for failure in the code that you have written that extends QueryManager
.
setUniverse
.Cause: A null dimension name was passed to the setUniverse
method.
Action: Call the setUniverse
method with a valid dimension name.
getUniverseSelection
.Cause: A null dimension name was passed to the getUniverseSelection
method.
Action: Call the getUniverseSelection
method with a valid dimension name.
Cause: The persistent XML file is not compatible with this object.
Action: Re-create the object.
Cause: There are no more operations on the stack to redo.
Action: No action is necessary.
QueryManager
property has not been set.Cause: The current query was not generated by the QueryManager
and has not had its QueryManager
property set.
Action: Set the QueryManager
property on the current query.
BISession
object has been set.Cause: The setSession
method must be called before performing operations using the QueryManager
.
Action: Call the setSession
method after creating the QueryManager
.
setSession
before using QueryManager
.Cause: The middle-tier proxy was not set.
Action: Call the setSession
method before performing operations using the QueryManager
.
BISession
object.Cause: The third-party JAR files that support BC4J might be missing or not in the CLASSPATH setting.
Action: Check the CLASSPATH setting for the directories of all third-party JAR files.
setDeploymentOption
on new BISession
object.Cause: The third-party JAR files that support BC4J might be missing or not in the CLASSPATH setting.
Action: Check the CLASSPATH setting for the directories of all third-party JAR files.
connect
on new BISession
object.Cause: The third-party JAR files that support BC4J might be missing or not in the CLASSPATH setting.
Action: Check the CLASSPATH setting for the directories of all third-party JAR files.
createComponentObject
on BISession
object.Cause: The third-party JAR files that support BC4J or the server-side BI Beans JAR files might be missing or not in the CLASSPATH setting.
Action: Check the server-side CLASSPATH setting for the directories of all third-party and BI Beans JAR files.
getApplicationModule
in BISession
class.Cause: An error has occurred in the BI Beans setup.
Action: Invoke the printStackTrace method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
createComponentObject
on BISession
object failed.Cause: The third-party JAR files that support BC4J or the server-side BI Beans JAR files might be missing or not in the CLASSPATH setting.
Action: Check the server-side CLASSPATH setting for the directories of all third-party and BI Beans JAR files.
Cause: The clone
method was called during design in a development environment.
Action: Do not call the clone
method during design.
Cause: The third-party JAR files that support BC4J might be missing or not in the CLASSPATH setting.
Action: Check the CLASSPATH setting for the directories of all third-party JAR files.
Cause: A measure name was specified that cannot be found in the database.
Action: Ensure that all named measures exist in the database.
Cause: A hierarchy name was specified that cannot be found in the database.
Action: Ensure that all named hierarchies exist in the database.
Cause: An invalid piece of metadata was specified that cannot be processed.
Action: Ensure that the metadata is valid.
Cause: There are no more operations on the stack to undo.
Action: No action is necessary.
Cause: During the evaluation of a selection step, the given evaluator class was not found.
Action: If this is an application or user-defined step, then ensure that the referenced evaluator class is available.
MetadataManager
not set.Cause: The MetadataManager
property of the QueryManager
object was not set.
Action: Set the MetadataManager
property to a valid MetadataManager
before using any other methods.
Cause: The MetadataManager
object returned an error while trying to get the source for the specified dimension.
Action: Ensure that the database still contains the referenced dimension.
Cause: Oracle OLAP failed while trying to get a cursor for use on the middle tier.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An error occurred in Oracle OLAP during the creation of the cursor for use on the client.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An invalid OLAP source was specified while trying to get a cursor for use on the middle tier.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The given dimensions or locations would not result in a legal pivot.
Action: Check the given arguments and reconcile them with the current query's layout.
Cause: The given dimensions or locations would not result in a legal swap.
Action: Check the given arguments and reconcile them with the current query's layout.
Cause: The given edges would not result in a legal swap.
Action: Check the given edges and reconcile them with the current query's layout.
findSelection
.Cause: The specified dimension's selection in the findSelection
method was not found.
Action: Check the specified dimension and ensure that it has a defined selection in the DataSource
.
Cause: A method was called that requires an existing query.
Action: Create a query before calling the method.
Cause: A measure name was specified that cannot be found.
Action: Ensure that all named measures exist in the database.
Cause: An attempt was made to undo to a state that does not have a defined query.
Action: No action is necessary.
Cause: An attempt was made to set a saved state that does not have a defined query.
Action: No action is necessary.
Cause: An attempt was made to redo to a state that does not have a defined query.
Action: No action is necessary.
DataSource
state.Cause: There is no matching saved state in the DataSource
object. Possibly the stack was undone to an earlier point than this save point was created.
Action: No action is necessary.
Cause: There was a problem with Oracle OLAP.
Action: Check Oracle OLAP and retry the operation.
Cause: The persistent XML file is not compatible with this object.
Action: Re-create the object.
Cause: The MetadataManager
did not load any measures from the database. This is a problem with metadata.
Action: Check the schema to ensure that the measures are properly defined.
Cause: A syntax error in a method of the OLAP API of the submit caused an error in Oracle OLAP.
Action: Check the database and the message that was displayed with the exception to take appropriate action, such as resolving non-existent server objects.
Cause: A syntax error in a method of the OLAP API of the commit caused an error in Oracle OLAP.
Action: Check the database and the message that was displayed with the exception to take appropriate action, such as resolving non-existent server objects.
Cause: The OLAP transaction could not be prepared.
Action: Check Oracle OLAP and retry the operation.
Cause: The OLAP transaction could not be committed.
Action: Check Oracle OLAP and retry the operation.
Cause: The OLAP transaction is inactive. There is a possible mismatch between the transaction with which this query started and the transaction with which this prepare or commit was attempted.
Action: Check Oracle OLAP and retry the operation.
Cause: The OLAP transaction was not prepared. The prepare might not have been called on the OLAP transaction prior to the commit.
Action: Check Oracle OLAP and retry the operation.
Cause: A hierarchy name was specified that cannot be found in the current database.
Action: Ensure that all named hierarchies are in the current database.
Cause: A dimension name was specified that cannot be found in the current database.
Action: Ensure that all named dimensions are in the current database.
Cause: A level name was specified that cannot be found in the current database.
Action: Ensure that all named levels are in the current database.
Cause: An invalid member name or method of specifying that member was given that cannot be processed.
Action: Ensure that the member is valid or, in the case of a custom measure, that the custom measure was properly constructed.
Cause: An invalid piece of metadata was specified that cannot be processed.
Action: Ensure that the metadata is valid.
Cause: The specified layout was not valid, possibly due to the selections that were previously set on the query. The layout may be illegal given previously set asymmetric selections. For example, two dimensions whose selections depend on each other cannot be placed orthogonally, one on the column edge and one on the row edge.
Action: Rotate the dimensions so that selections that depend on each other are on the same edge.
Cause: The MetadataManager could not load a persistable object.
Action: Verify that the persistable object exists and contains valid XML.
Cause: The application might have called the cancel
method on the connection.
Action: The call to the cancel
method is likely deliberate. No action is required.
Cause: An asymmetric selection was applied to a page edge that is dependent on a dimension on the row or column edge. Or, an asymmetric selection was applied on a column or row edge that is dependent on a dimension on a row or column (opposite orthogonally) edge.
Action: Ensure that the asymmetric selection is compatible with the current layout. Adjust the selection or the layout prior to applying the selection.
Cause: An attempt was made to consume an event that is not consumable.
Action: No action is necessary.
Cause: There are a variety of possible reasons why the connection was not made.
Action: Check the cause and action text for the BIB error message that is specified after "Reason:".
UserObject
.Cause: An attempt was made to bind or lookup an object whose state could not be set or retrieved by StateAgent
.
Action: Check the underlying error stack to find the root cause of the problem.
Persistence
handler could not be instantiated.Cause: A failure occurred while creating an instance of the PersistenceMetadataHandler
. The failure can happen only if the PersistenceMetadataHandler
is an interface or an abstract class.
Action: Check the underlying error stack to find the root cause of the problem.
Persistence
handler.Cause: A failure occurred while creating an instance of the PersistenceMetadataHandler
. The failure can happen only if the PersistenceMetadataHandler
is not public or is not in the MetadataManager
package.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: A failure occurred while creating an instance of the PersistenceMetadataHandler
. The failure can happen only if the MetadataHandlers
or Persistence
JAR files are not in the CLASSPATH setting.
Action: Ensure that all the MetadataManager
and Persistence
classes are included in the CLASSPATH setting.
BISession
was not specified.Cause: An instance of BISession
was not set on the MetadataManager
object.
Action: Set a BISession
on the MetadataManager
object, using the setSession
method.
Cause: An unsuccessful attempt was made to initialize the application module or middle tier or to create a proxy for the MetadataManager
object.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to set a property other than Label
on an MDObject
.
Action: Ensure that only the Label
property is set on the MDObject
.
Cause: MetadataManager could not disconnect the connection.
Action: Check the underlying error stack to find the root cause of the problem.
MetadataManager
could not free the connection.Cause: The MetadataManager
could not release the connection.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to save a folder using the bind
method.
Action: To create a new folder, use the createSubcontext
method. To copy a folder to another folder, use the copy
method. To move a folder to another folder, use the move
method.
Cause: The key or the value of the specified attribute(s) in the method was not valid. If the object is of driver type MDV.PERSISTENCE
, then check the PSRConstants
file for the correct value.
Action: Specify a valid attribute key and value.
Cause: The specified name was not valid. For any methods of BIContext
that require a name argument, you cannot specify a null value. The following methods also require that the name argument not be an empty string: bind
, rebind
, createSubcontext
, destroySubcontext
, rename
and unbind
.
Action: Specify a name whose value is not an empty string.
Cause: An attempt was made to save a UserObject
that contains an object that is not accepted by the specific driver. For example, for the Persistence
driver, the object must be of type Persistable
.
Action: Set the appropriate object in UserObject
for the specified driver type.
Cause: The specified search control is not valid for one of the following reasons:
OBJECT_SCOPE
, ONELEVEL_SCOPE
, SUBTREE_SCOPE
, ONELEVEL_SCOPE_WITH_FOLDERS
(from Persistence), or SELECTIVE_ONELEVEL_SCOPE
(from Persistence).Action: Review the possible reasons and take the appropriate action.
Cause: An attempt was made to save an object with a name that was already bound to an object in the storage system, or the destination folder already contained an object that was bound to that particular name when the copy or move operation was performed.
Action: If this is a save operation, then use the rebind
method to overwrite the existing object that is bound with that name. If this is a copy operation, then specify a different target name.
Cause: An attempt was made to retrieve, copy, or move an object that does not exists.
Action: No action is necessary.
Cause: An attempt was made to perform an operation that requires specific privileges. For example, saving an object to a folder in which the user does not have write access.
Action: Request that the owner or user of the folder with full-control privileges assigns sufficient privileges to the appropriate user to perform the operation.
Cause: Depending on the operation, this error can occur because:
copy
or move
operations is not a valid folder.name
argument in list
, listBindings
, or search
operations does not resolve to a folder.Action: Specify a valid folder name.
Cause: The operation is not supported by the driver in which the operation is invoked. For example, the MDV.MDM
driver does not allow any write operations.
Action: No action is necessary.
Cause: An unknown error has occurred.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An error has occurred while performing the modifyAttributes
operation.
Action: Check the underlying error stack to find the root cause of the problem.
MetadataManager
driver could not be instantiated.Cause: A failure occurred while creating an instance of the MetadataManager
driver. The failure can happen only if the MetadataManager
drivers are interfaces or are abstract classes.
Action: Check the underlying error stack to find the root cause of the problem.
MetadataManager
driver.Cause: A failure occurred while creating an instance of the MetadataManager
driver. The failure can happen only if the MetadataManager
drivers are not public or are not in the MetadataManager
package.
Action: Check the underlying error stack to find the root cause of the problem.
MetadataManager
driver was not found.Cause: A failure occurred while creating an instance of the MetadataManager
driver. The failure can happen only if the MetadataManager
or Persistence
JAR files are not in the CLASSPATH setting.
Action: Ensure that all the MetadataManager
and Persistence
classes are included in the CLASSPATH setting.
Cause: An attempt was made to set a property other than Label
on the MeasureDimension MDObject
.
Action: Ensure that only the Label
property is set on the MeasureDimension MDObject
.
Cause: The OLAP API calls cannot connect to Oracle OLAP, or the analytic workspace cannot be opened. The calls might contain missing or inaccurate information.
Action: Check the completeness and accuracy of the information in the calls for connecting and for opening the workspace.
Cause: An error occurred in the driver that connects to Oracle OLAP, which can indicate a problem with authentication or with security.
Action: Check the underlying error stack to find the root cause of the problem, and if the caller has sufficient privileges, then try again.
Cause: An attempt to open an analytic workspace failed, because the workspace is already open.
Action: Close the previously opened workspace and try again.
Cause: An attempt was made to create an MdmMetadataProvider
, but the database cannot provide the kind of metadata that the MdmMetadataProvider
requires.
Action: Gain access to a database that contains OLAP metadata.
Cause: The requested MdmObject
was not available from the MetadataProvider
, or an attempt was made to retrieve a property from MdmObject
that is not set in the MdmObject
.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An OLAP API call requested information from Oracle OLAP, but communication is not possible. The analytic workspace has been closed, or the connection has been disconnected.
Action: Connect to the workspace before making the OLAP API call. Ensure that the detach
method is not called before metadata is retrieved.
Cause: An attempt was made to attach with an invalid serverType
.
Action: Ensure that the serverType
is OLAPServer
.
UserObject
found or UserObject
was empty.Cause: An attempt was made to save an MDObject
that contains no UserObject
or an empty UserObject
.
Action: Ensure that the MDObject
that is being saved meets the following criteria:
MDObject
contains a UserObject
.UserObject
has a Persistable
object set on it.MDObject
.Cause: An attempt to save an MDObject
to the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
MDObject
.Cause: An attempt to remove an MDObject
from the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
MDObject
.Cause: An attempt to read an MDObject
from the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to perform one of the following invalid operations on a object that is not a folder:
AclEntry
objects.Action: Re-try the operation, being sure to specify a valid folder.
MDObject
to another folder.Cause: An attempt to copy an MDObject
to a folder in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
MDObject
to another folder.Cause: An attempt to move an MDObject
to a folder in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to add ACL entries to a folder in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to remove ACL entries from a folder in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to retrieve ACL entries from a folder in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to retrieve users for a folder in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to retrieve the folder in the BI Beans Catalog has failed.
Action: Ensure that the folder does exist in the BI Beans Catalog and that the user has sufficient privileges to access it.
Cause: The object with the specified name is not a folder.
Action: If you have specified a root folder while creating a connection to the BI Beans Catalog, then ensure that the name is bound to a folder object.
Cause: An attempt to retrieve the privilege of a user in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to retrieve the attributes of an object in the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The value of an argument that is specified in the method is not valid. Check the javadoc for the valid values for the argument.
Action: Change the method call to specify a valid argument.
Cause: The value of the argument that is specified in the method is not valid. Check the javadoc for the method for the valid values for the argument.
Action: Change the method call to specify a valid argument.
Cause: An unexpected XML version was found. An attempt was likely made to open an object that was created in a version of BI Beans that is newer than the version that was running.
Action: Ensure that the version of the object is less than or equal to the version of BI Beans that is used to open the object.
Cause: An XML parsing problem was caused by a syntax error or by a BI Beans version mismatch.
Action: Ensure that the XML code is valid and that the version of the object is less than or equal to the version of BI Beans that is used to open the object.
Cause: An unknown exception occurred in a call to a different class.
Action: Check the underlying error stack to find the root cause of the problem.
BISession
is not specified in the environment.Cause: A BISession
instance is required to create the InitialPersistenceManager
. The instance must be set in the environment using the PSRConstants.BISESSION
key when creating the InitialPersistenceManager
.
Action: Specify the BISession
instance in the environment properties when creating the InitialPersistenceManager
.
Cause: The specified name is not valid. For any methods of PersistenceManager
that require a name
argument, you cannot specify a null value. The following methods also require that the name
argument not be an empty string: bind
, rebind
, createSubcontext
, destroySubcontext
, rename
and unbind
.
Action: Specify a name whose value is not an empty string.
Cause: An attempt was made to perform an action on a context that is already closed explicitly.
Action: Retrieve the context again by performing a lookup operation.
Cause: The connection to the PersistenceManager
failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An unknown error has occurred while trying to save an object.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to save a folder using the bind
method.
Action: To create a new folder, use the createSubcontext
method. To copy a folder to another folder, use the copy
method. To move a folder to another folder, use the move
method.
Persistable
object.Cause: An attempt was made to save a non-persistable object.
Action: Before calling the bind
or rebind
methods to save an object, ensure that the object implements the Persistable
interface. Any other types of object cannot be saved.
Cause: An unknown error has occurred while trying to look up an object.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The persistable component threw an exception during a call to the bind
method.
Action: Check the name of the component and the reason. Given the name of the method that caused the problem, consult the documentation for the component to determine why the exception was thrown.
Cause: The persistable component threw an exception during a call to the lookup
method.
Action: Check the name of the component and the reason. Given the name of the method that caused the problem, consult the documentation for the component to determine why the exception was thrown.
Cause: An unknown error has occurred while copying an object to another folder.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The value of the copy mode in the copy
method is invalid. The value must be one of the following: PSRConstants.DEEP_COPY
or PSRConstants.NORMAL_COPY
.
Action: Use a valid value when performing the copy operation.
Cause: An unknown error has occurred while moving an object to another folder.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: Depending on the operation, this error can occur because:
copy
or move
operations is not a valid folder.name
argument in list
, listBindings
, or search
operations does not resolve to a folder.Action: Specify a valid folder name.
Cause: The specified target objects must not be null.
Action: Specify valid target objects.
Cause: The specified identifiers must not be null.
Action: Specify valid identifiers.
Cause: The specified number of identifiers does not match the specified number of target objects.
Action: Specify the correct number of identifiers and target objects. Each target object should be matched with a corresponding unique identifier.
Cause: Not all the search results were returned during a search call.
Action: Increase the time limit on the search scope.
Cause: The search operation generated more search results than the specified maximum limit.
Action: Increase the limit to see more search results.
Cause: There are no more elements in the returned NamingEnumeration
from a list
, listBindings
, or search
operation.
Action: Call the nextElement
method instead of next
.
Cause: An error has occurred while performing the modifyAttributes
operation.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The operation is not supported.
Action: No action is necessary.
Cause: An unknown error has occurred.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The key or the value of the attribute that is specified in the method was not valid. The key of the attributes must be one of the constants that are defined in PSRConstants.Attributes
. The value of the attribute must be the proper type to correspond with the key. For example, for PSRConstants.Attributes.OBJECT_NAME
, the value must be of type String
.
Action: Specify a valid attribute key and value.
Cause: An attempt was made to perform an operation that requires specific privileges. For example, saving an object to a folder in which the user does not have write access.
Action: Request that the owner or user of the folder with full-control privileges assigns sufficient privileges to the appropriate user to perform the operation.
Cause: An attempt was made to save an object with a name that was already bound to an object in the storage system, or the destination folder already contained an object that was bound to that particular name when the copy or move operation was performed.
Action: If this is a save operation, then use the rebind
method to overwrite the existing object that is bound with that name. If this is a copy operation, then specify a different target name.
Cause: An attempt was made to retrieve, copy, or move an object that does not exists.
Action: No action is necessary.
Cause: The filter that was specified was not valid.
Action: Check the syntax of the filter to ensure the specification of a valid filter.
Cause: The specified search control is not valid for one of the following reasons:
OBJECT_SCOPE
, ONELEVEL_SCOPE
, SUBTREE_SCOPE
, ONELEVEL_SCOPE_WITH_FOLDERS
(from Persistence), or SELECTIVE_ONELEVEL_SCOPE
(from Persistence).Action: Review the possible reasons and take the appropriate action.
StorageManager
could not be created.Cause: The StorageManager
cannot be created or an error has occurred during initialization.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The specified folder is not found. The folder might not exist, or the user might lack sufficient privileges to see the folder.
Action: Ensure that the folder name is correct and that the user has at least read access to the folder.
Cause: An attempt to remove the folder failed. The user might lack sufficient privileges to remove a folder.
Action: Ensure that the user has at least write access to the folder.
Cause: The command line option is not valid.
Action: Use valid command line options.
Cause: The specified option requires an argument.
Action: Provide an argument for the option. Follow the option name with a blank space and the name of the argument.
Cause: A required option parameter is missing.
Action: Specify the option using the appropriate parameters.
Cause: The incorrect number of arguments was specified.
Action: Ensure that the correct number of arguments is specified.
Cause: The file cannot be opened. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: The required encoding is not supported by the current JDK setup.
Action: Modify the JDK environment to support the desired encoding.
Cause: The specified folder is not found. The folder might not exist, or the user might lack sufficient privileges to see the folder.
Action: Ensure that the folder name is correct and that the user has at least read access to the folder.
Cause: The object was not accessible. The user might lack sufficient privileges to read the object or the object might contain a circular reference to other objects.
Action: Ensure that no circular references exist and that the user has at least read access to the object.
Cause: An attempt to export to the folder failed. The user might lack sufficient privileges to write to the folder.
Action: Ensure that the user has at least write access to the folder.
Cause: The internal state of the objects is incorrect.
Action: Ensure that the application saved the object correctly.
Cause: The internal state of the objects is incorrect.
Action: Ensure that the application saved the object correctly.
Cause: The internal state of the objects is incorrect.
Action: Ensure that the application saved the object correctly.
Cause: An error occurred while exporting the access controls.
Action: Ensure that the ACLs are correct.
Cause: The folder is no longer available. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: The file cannot be opened. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: The specified folder is not found. The user might lack sufficient privileges to see the folder or the object might contain a circular reference to other objects.
Action: Ensure that no circular references exist and that the user has at least read access to the folder.
Cause: The XML parser could not be initialized.
Action: Verify that the correct XML parser is being used.
Cause: The user lacks sufficient priviliges to remove the temporary folder.
Action: Ensure that the user has at least write access to the temporary folder.
Cause: The temporary folder is no longer available. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: Permissions could not be added. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: The folder is no longer available. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: An "ID reference" references an identifier that has not been found in the retrieved object.
Action: Ensure that the import file has not been modified.
Cause: The format of a date field is not correct.
Action: Ensure that the import file has not been modified.
Cause: The security driver manager could not be created.
Action: Ensure that a BIUser
is specified and that the BISecurityDriver
settings in the BI Beans configuration file are correct.
Cause: The operation to create a temporary folder has failed.
Action: Ensure that the user has the appropriate privileges for the import folder.
Cause: An error occurred while importing the folder.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The name of the folder is already bound to an object that is not a folder.
Action: Remove the object with the conflicting name.
Cause: An operation failed during the export.
Action: Use the -v (verbose) argument for the export command or check the underlying error stack to find more detailed information.
Cause: Cannot establish a connection to the BI Beans Catalog.
Action: Ensure that all the necessary parameters, such as user name, password, service name, host, port, and SID are specified correctly. Ensure that if you specify the "-j thin" driver parameter, then you also provide the -h -po -sid parameters. If you specify the "-j oci8" driver parameter, then you should provide the -s parameter. In addition, consult the reason that is provided in the message.
Cause: Cannot establish a connection to the database. The JDBC JAR or ZIP files are incompatible with the OCI client installation of the current ORACLE_HOME or the nls_charset12.zip
file is missing.
Action: Ensure that all the necessary settings, such as CLASSPATH, are specified correctly, and that there are correct JAR or ZIP files in the CLASSPATH specification (such as classes12.zip
for JDBC). Ensure that you include the $ORACLE_HOME/jdbc/lib/nls_charset12.zip
setting in the CLASSPATH specification.
Cause: Cannot establish a connection to the database. The JDBC JAR or ZIP files are incompatible with the OCI client installation of the current ORACLE_HOME or the nls_charset12.zip
file is missing. Another possible cause is that settings such as the user name or password are incorrect.
Action: Ensure that all the necessary settings, such as CLASSPATH, user name and password are specified correctly, and that there are correct JAR or ZIP files in the CLASSPATH specification (such as classes12.zip
for JDBC). Ensure that you include the $ORACLE_HOME/jdbc/lib/nls_charset12.zip
setting in the CLASSPATH specification. In addition, consult the reason that is provided in the message.
Cause: A null or empty name was provided as the name argument.
Action: Ensure that a valid name is provided as the argument.
Cause: The specified parent folder does not exist.
Action: Ensure that the specified parent folder exists.
BIStoragemanagerImpl
does not have an active adapter.Cause: An attempt was made to perform an operation on a folder that was already closed or was not initialized; therefore, no adapter is active. An adapter is active only when a folder is open.
Action: Ensure that the folder was not closed and was properly initialized.
BIStoragemanagerImpl
does not have a folder identifier.Cause: An attempt was made to perform an operation on a folder that was already closed or was not initialized.
Action: Ensure that the folder was not closed and was properly initialized.
Cause: An error occurred while attempting to create a folder.
Action: Ensure that sufficient privileges are available to create the folder.
Cause: The folder was not found.
Action: Ensure that the name of an existing folder is specified.
Cause: The name was bound to an object and not to a folder.
Action: Ensure that the name of an existing folder is specified.
StateAgent
.Cause: The name was bound to a folder and not to an object.
Action: Ensure that the name of an existing object is specified.
StateAgent
objects was a named object but does not have an object identifier.Cause: The internal object state is incorrect.
Action: Verify the state of the named object.
StateAgent
or one of its aggregate StateAgent
objects does not have the OBJECT_TYPE specified.Cause: The internal object state is incorrect.
Action: Verify the state of the named object.
StorageManager
attributes updated.Cause: A BI Beans error has occurred.
Action: Attempt to re-establish the connection and retry the operation. If you are still unsuccessful, then check the configuration for any incompatibility in the versions of the JAR files. If you are still unsuccessful, then contact Oracle Support Services via Metalink for assistance.
Cause: A full path name could not be constructed, possibly because the path name is not syntactically correct.
Action: Ensure that the specified path name is correct.
StateAgent
was null.Cause: A BI Beans error has occurred.
Action: Attempt to re-establish the connection and retry the operation. If you are still unsuccessful, then check the configuration for any incompatibility in the versions of the JAR files. If you are still unsuccessful, then contact Oracle Support Services via Metalink for assistance.
Cause: An invalid attribute key was specified.
Action: Ensure that the specified attribute keys are valid.
Cause: The name of the object contains too many characters.
Action: Ensure that the attribute value does not exceed the maximum object name length.
Cause: The attribute does not contain a value.
Action: Ensure that the attribute contains a key and a value.
Cause: The attribute contains a value of the wrong data type.
Action: Ensure that the attribute values are of the correct data type.
Cause: A null value was provided as the name argument.
Action: Ensure that a valid name is provided as the argument.
Cause: The specified object identifier was null.
Action: Ensure that a valid object identifier is specified.
Cause: The object that is specified by the object identifier is not found.
Action: Ensure that the object exists and that the proper access is available.
Cause: The path names for the previous and new names are not the same.
Action: Ensure that the path names are the same.
Cause: The new name is identical to the previous name.
Action: Ensure that the new name is different from the previous name.
Cause: The attribute modification operation was not supported.
Action: Only the replace operation is supported. Ensure that only this operation is specified.
Cause: An attempt was made to change the value of a read-only attribute.
Action: Ensure that only read-write attributes are specified for change.
Cause: The operation is not allowed on the root folder.
Action: Ensure that the operation is not specified for the root folder.
Cause: The specified folder for which a search was attempted does not exist.
Action: Ensure that the specified folder exists before attempting the search.
Cause: The entries argument is null.
Action: Ensure that non-null ACL entries are provided.
AclEntry
or no user or privilege was specified.Cause: One or more of the specified entries is not valid, for one of the following possible reasons:
AclEntry
.Action: Request that the owner or user of the folder who has full-control privileges assign sufficient privilege to this user to perform the operation.
Cause: The specified AclEntry
contains the current user, and users cannot change their own privileges.
Action: Ensure that the current user does not specify himself or herself in the entries.
Cause: The argument for the user is null.
Action: Ensure that the user argument is not null.
Cause: The argument for the privilege is null.
Action: Ensure that the privilege argument is not null.
BIStorageManagerImpl
.Cause: The target argument is null or contains an object that does not represent a BIStorageManagerImpl
.
Action: Ensure that the target argument contains a BIStorageManagerImpl
.
Cause: An unsupported copy mode argument was provided.
Action: Ensure that a valid copy mode argument is specified.
StateAgent
was specified; aggregate number ignored.Cause: An aggregate did not contain a child StateAgent
.
Action: Ensure that all aggregates contain child StateAgent
objects.
StateAgent
aggregate tree.Cause: A set of StateAgent
objects are specified that contain a circular reference.
Action: Ensure that no circular references are specified.
Cause: The specified associate identifier attribute is null or the value of the attribute is null.
Action: Ensure that the identifier attribute is not null and that a non-null value is specified.
Cause: The identifier of the root folder could not be obtained.
Action: Ensure that the BI Beans Catalog schema is correct and current.
Cause: The name of the object is invalid. The name cannot contain the characters that are specified in the exception.
Action: Ensure that the name of the object does not contain any invalid characters.
Cause: The environment argument to the init
method is null.
Action: Provide the environment argument to the init
method.
Cause: The security driver manager is not specified.
Action: Ensure that the BISession is created and is set as part of the environment that is passed to Persistence.
Cause: The pluggable authentication driver threw an exception.
Action: Review the cause and action that is suggested in the exception that the pluggable authentication driver threw.
Cause: The pluggable connection driver threw an exception.
Action: Review the cause and action that is suggested in the exception that the pluggable connection driver threw.
Cause: The pluggable user community driver threw an exception.
Action: Review the cause and action that is suggested in the exception that the pluggable user community driver threw.
Cause: An error occurred during the initialization of the RDBMS-based storage manager.
Action: Examine the reason and check the underlying error stack to find the root cause of the problem.
Cause: The BI Beans Catalog schema was not found or is incomplete.
Action: Ensure that the BI Beans Catalog is installed in the schema for the specified database user.
Cause: The BI Beans version is not compatible with the BI Beans Catalog schema.
Action: Upgrade the BI Beans Catalog schema to work with the current version of BI Beans.
Cause: The attribute that is provided in the message was not specified.
Action: Set the attribute to an appropriate value.
Cause: The ModificationItem
argument is null in the modifyAttributes
method.
Action: Provide a value that is not null for the ModificationItem
argument.
Cause: The modification value was not supplied for the attribute that is specified in the message.
Action: Provide a valid modification value for the attribute.
Cause: The specified attribute was provided with more than one value.
Action: Provide only one value for this attribute.
Cause: The specified attribute is inserted more than once in the ModificationItem
argument.
Action: Provide the attribute only once.
Cause: The specified object name already exists.
Action: Specify a different name for the object.
Cause: The specified attribute cannot be modified, because it is a system attribute.
Action: No action is necessary.
Cause: The value that was supplied for the specified attribute is invalid.
Action: Provide a valid and non-null value for the attribute.
Cause: The time limit was exceeded for the query.
Action: Extend the limit of the timeout setting for the query.
Cause: The object from the BI Beans Catalog is a folder, and the rebind
method was called with an object name.
Action: Do not rebind a folder with an object. Rebind an object with another object.
Cause: The number of relationship identifiers does not match the number of associations.
Action: Every association requires an identifier. Ensure that the number of associations matches the number of identifiers that are passed.
Cause: An association does not exist.
Action: Ensure that the association exists before calling the method.
Cause: A circular reference was detected in the object hierarchy.
Action: Remove any circular references in the object hierarchy.
Cause: An invalid folder was specified in the path.
Action: Specify a valid folder path.
Cause: The folder identifier was not specified in the bind operation.
Action: Provide a folder identifier as an argument to the bind operation.
Cause: An object contains the same aggregate more than once.
Action: When adding aggregates to an object, add any given aggregate only once.
Cause: The user community driver specification is null.
Action: To use the getAllUsers
method, specify a valid (non-null) user community driver in the environment argument that is passed to the init
method.
Cause: The value for the association identifier is not supplied.
Action: The association identifier (both the name and the value) must be supplied to the calling method.
Cause: The association value that was supplied is not of type String.
Action: Ensure that the value that is supplied for the association value is of type String.
Cause: Invalid or insufficient arguments were passed to the method for the operation.
Action: Check the method call and specify sufficient and valid arguments. Ensure that non-null arguments are passed.
Cause: Copying the root folder is not allowed.
Action: Do not attempt to copy the root folder.
Cause: The unbind
method was called on a folder. The unbind
method should be called only for objects.
Action: Use the destroySubcontext
method to remove a folder.
Cause: A folder can never be moved to its subfolder.
Action: Move the folder to another folder that is not a subfolder of the source folder.
Cause: A root folder can never be moved.
Action: Do not attempt to move a root folder.
Cause: A folder can never be copied to its subfolder.
Action: Copy the folder to another folder that is not a subfolder of the source folder.
Cause: The operation that is specified in the message is not supported.
Action: Do not perform this operation.
Cause: The user lacks sufficient privileges for the folder.
Action: Assign appropriate privileges to the user.
Cause: The user lacks sufficient privileges for the source folder.
Action: Assign appropriate privileges to the user for the source folder.
Cause: The user lacks sufficient privileges for the target folder.
Action: Assign appropriate privileges to the user for the target folder.
Cause: The user lacks sufficient privileges for one or more folders in the hierarchy.
Action: Assign appropriate privileges to the user for the entire folder hierarchy.
Cause: The user has no privileges for the folder.
Action: Assign appropriate privileges to the user for the folder.
Cause: The user has no privileges for the source folder.
Action: Assign appropriate privileges to the user for the source folder.
Cause: The user has no privileges for the target folder.
Action: Assign appropriate privileges to the user for the target folder.
Cause: The user has no privileges for one or more folders in the hierarchy.
Action: Assign appropriate privileges to the user for the folders in the entire hierarchy.
Cause: An attempt was made to assign an invalid privilege to a user.
Action: Assign only valid privileges to users.
Cause: The root folder was not found.
Action: Ensure that the schema has been properly installed.
Cause: The folder was not found.
Action: Specify a valid folder and repeat the operation.
Cause: The source folder was not found.
Action: Specify a valid source folder and repeat the operation.
Cause: The target folder was not found.
Action: Specify a valid target folder and repeat the operation.
Cause: The source or parent folder was not found.
Action: Specify a valid source or parent folder and repeat the operation.
Cause: The target was not a folder.
Action: Specify a folder for the target.
Cause: A folder with the specified name already exists.
Action: Specify a different name for the folder.
Cause: The folder has dependents; therefore, the operation cannot be performed.
Action: No action is necessary.
Cause: An attempt was made to delete a folder that cannot be deleted.
Action: Do not delete the folder.
Cause: The path that was specified could not be found.
Action: Specify a valid path.
Cause: The object that was specified could not be found.
Action: Provide the name of an object that exists in the BI Beans Catalog.
Cause: The object already exists in the folder.
Action: Specify a different name for the object.
Cause: The object has dependents; therefore, the operation cannot be performed.
Action: No action is necessary.
Cause: The source object that was specified could not be found.
Action: Specify a valid source object.
Cause: The target object that was specified could not be found.
Action: Specify a valid target object.
Cause: The object hierarchy refers to one or more named objects that do not exist.
Action: Check the named objects in the hierarchy and ensure that the objects exist in the BI Beans Catalog.
Cause: The named objects that are not at the top level of the hierarchy require the OBJECT_ID attribute and value.
Action: Specify the OBJECT_ID attribute and value for the appropriate objects.
Cause: An attempt was made to bind an object that contains an anonymous object, which is shared by a named object and an anonymous object. This sharing is not allowed.
Action: Bind the anonymous object by giving it an explicit name.
Cause: The length of the folder path name has exceeded 2000 characters.
Action: Use a folder path name that contains less than 2000 characters.
Cause: The specified user name is either null or contains an empty string.
Action: Specify a valid user name.
Cause: The specified user name was not found in the BI Beans Catalog table (bism_subjects).
Action: Specify a user that exists in the BI Beans Catalog or add this user name to the bism_subjects table.
Cause: The specified user name exists more than once in the BI Beans Catalog table (bism_subjects).
Action: Remove the duplicate entries for the user name.
Cause: The BIUser is not specified in the environment argument to the init
method.
Action: Create a BIUser and set it in the environment argument that is passed to the init
method.
Cause: The listed user or users cannot be found in the BI Beans Catalog.
Action: Ensure that these users exist in the BI Beans Catalog.
Cause: An error occurred during the transaction.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An error occurred during the commit operation.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An error occurred during the rollback operation.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The BI Beans runtime environment received an unrecognized or unexpected return value.
Action: Ensure that the schema is installed correctly and that arguments for methods are passed correctly. Contact Oracle Support Services via Metalink for assistance.
Cause: The BI Beans runtime environment received an unexpected SQLException
.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
Cause: The BI Beans runtime environment received an unexpected NamingException.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
Cause: The BI Beans runtime environment received an unknown or unexpected Java runtime exception.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
Cause: The BI Beans runtime environment received an unknown or unexpected Java exception.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem. Contact Oracle Support Services via Metalink for assistance.
Cause: The associate operation encountered a problem.
Action: Check the suggested reason and take the appropriate action.
Cause: The associate operation encountered an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The dissociate operation encountered a problem.
Action: Check the suggested reason and take the appropriate action.
Cause: The dissociate operation encountered an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An invalid copy type was specified.
Action: Specify one of the two valid copy types: shallow copy or deep copy.
getAllUsers
was invoked.Cause: The getAllUsers
method that the user community driver implemented threw an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: This operation is not supported.
Action: No action is necessary.
bind
.Cause: An IOException
has occurred while writing the XML for the object to the file.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to save to a file with a name that is the same as an existing directory.
Action: Specify another name for the object.
lookup
.Cause: An IOException
has occurred while reading the XML from a file.
Action: Check the underlying error stack to find the root cause of the problem.
unbind
method.Cause: An attempt was made to delete a directory using the unbind
method.
Action: Use the destroySubcontext
method to delete a directory.
Cause: Deleting the specified file from the file system failed with no exception. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: Renaming the specified file from the file system failed with no exception. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: Creating the specified directory on the file system failed with no exception. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
Cause: Deleting the specified directory from the file system failed with no exception. The most likely common causes are listed here:
Action: Review the possible causes and take the appropriate action.
getObject
.Cause: An IOException
has occurred while reading the XML from a file.
Action: Check the reason that is provided in the message and take the appropriate action. Check the underlying error stack to find the root cause of the problem.
getAttribute
.Cause: An IOException
has occurred while reading the XML from a file to get the attributes.
Action: Check the reason that is provided in the message and take the appropriate action. Check the underlying error stack to find the root cause of the problem.
modifyAttribute
.Cause: An IOException
has occurred while reading the XML from a file to get the attributes to modify.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to copy or move a directory to one of its children. This will result in a endless loop if not stopped.
Action: Do not copy or move a directory to its children.
copy
or move
.Cause: An IOException
has occurred while reading or writing the XML from or to a file during a copy
or move
operation.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The file is most likely still open by another application.
Action: Check the underlying error stack to find the root cause of the problem. Check to see if any application is using the file; close the file as appropriate.
Cause: An attempt was made to bind an object in which the object contains an anonymous object that is shared by a named object and an anonymous object. This sharing is not allowed.
Action: Copy or bind the anonymous object explicitly with a name.
Cause: An attempt was made to bind an object where more than one of its aggregate objects (which was a named object) has been removed.
Action: The object is corrupted. Replace the named object that was removed with either another named object or with an anonymous object.
Cause: The name of the root path was not specified when attempting to connect to the file-based storage manager.
Action: Specify the name of the root path when connecting.
Cause: The name of the zip or jar file was not specified when attempting to connect to the zip-file storage manager.
Action: Specify the name of a zip or jar file when connecting.
Cause: An exception has occurred while reading the zip or jar file.
Action: Ensure that the zip or jar file is in the specified location and is not corrupted. Check the underlying error stack to find the root cause of the problem.
Cause: The specified root path cannot be found.
Action: Specify an existing root path.
Cause: The specified root path is not a directory.
Action: Specify a path that resolved to a directory.
MetadataManager
property not set.Cause: The MetadataManager
property of the CalcBuilder
was not set.
Action: Set the MetadataManager
property to the name of a valid MetadataManager
object before using any of the CalcBuilder
methods.
MetadataManager
.Cause: A persistence connection was not associated with the MetadataManager
object.
Action: Set a persistence connection on the MetadataManager
before using any of the CalcBuilder
methods.
MetadataManager
.Cause: The specified MetadataManager
object does not contain a valid calculation step.
Action: Set a persistence connection on the MetadataManager
before using any of the CalcBuilder
methods, and verify that the MetadataManager
does not contain a null or invalid CalcStep
.
Cause: The QueryContext
property of the CalcBuilder
was not set.
Action: Set the QueryContext
property to the name of a valid QueryContext
object before using any of the CalcBuilder
methods.
ObjectNode
associated with the calculation.Cause: System memory might be depleting or invalid ObjectNode
properties were set.
Action: Verify that system memory is not depleting and that the ObjectNode
properties are being set correctly.
ObjectNode
.Cause: The XML stream might be invalid, or system resources might be depleting.
Action: Verify that you have proper write access to the ObjectNode
and that system resources have not been depleted.
Cause: The XML string was invalid.
Action: Ensure that the XML string is not null and does not have a zero length.
ObjectNode
associated with the specified calculation XML.Cause: The XML string may be invalid.
Action: Verify that the XML for the specified calculation is valid.
Cause: The specified look and feel class could not be loaded.
Action: Verify that the CLASSPATH setting and the look and field class are valid.
Cause: The custom measure could not be saved in the specified folder.
Action: Verify that you have proper write access to the specified folder and that system resources have not been depleted. Review the underlying error stack trace to find the root cause of the problem.
Cause: A custom measure could not created for the specified calculation step.
Action: Verify that the calculation step represents a valid custom measure. Review the underlying error stack to find the root cause of the problem.
Cause: Each calculation step stores a reference to a folder. The folder name could not be retrieved from the specified calculation step.
Action: Verify that a valid folder name and path have been specified for the calculation step.
Cause: An attempt was made to edit or to save a null calculation (CalcStep) in the CalcBuilder.
Action: Ensure that the calculation to be edited is not null. Null calculations can occur in various instances, including the one in which the CalcBuilder is run in tabbed mode but is initialized with a null MDObject
or an MDObject
that contains a null CalcStep
.
Cause: An unknown exception occurred in a call to a different class.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: Could not update the contents of the panel, based on the selected measure.
Action: Verify that the selected measure is valid, including the proper dimensionality. Check the underlying error stack to find the root cause of the problem.
Cause: Time calculations require a measure that is dimensioned by time, and no time dimension could be located.
Action: Verify that the list of available measures contains a measure that is dimensioned by a time dimension.
Cause: A calculation panel that contains data for the calculation could not be initialized. The calculation step might contain invalid information.
Action: Check the underlying error stack to find the root cause of the problem. The calculation might have to be re-created.
Cause: The specified operand is invalid or could not be found for the chosen calculation.
Action: Verify that the operand is valid for the chosen calculation type. Invalid operands are often associated with invalid metadata IDs or with incorrectly formatted numbers.
Cause: An attempt was made to divide with an operand whose value is zero.
Action: Verify that you are not dividing a value by zero.
Cause: An attempt was made to overwrite a calculation that already exists.
Action: Verify that you want to replace the existing calculation with the same name.
Cause: An attempt was made to create a calculation that either directly or indirectly references itself.
Action: Verify that the name of the calculation that you are trying to create does not appear in the calculation itself. Either rename the calculation or ensure that {0} is not used in the calculation.
Cause: The name of the calculation is invalid. The name cannot contain the characters that are specified in the exception.
Action: Ensure that the name of the calculation does not contain any invalid characters.
Cause: An unsuccessful attempt was made to initialize the application module or middle tier or to create a proxy for the Connection
object.
Action: Check the underlying error stack to find the root cause of the problem.
BISession
was not specified.Cause: An instance of BISession
was not set on the Connection
object.
Action: Set a BISession
on the Connection
object using the setSession
method.
Cause: The connection was not initialized.
Action: Invoke the connect
method before performing this operation.
Connection
driver could not be instantiated.Cause: A failure occurred while creating an instance of the Connection
driver. The failure can happen only if the Connection
drivers are interfaces or abstract classes.
Action: Check the underlying error stack to find the root cause of the problem.
Connection
driver.Cause: A failure occurred while creating an instance of the Connection
driver. The failure can happen only if the Connection
drivers are not public or are not in the Connection
package.
Action: Check the underlying error stack to find the root cause of the problem.
Connection
driver was not found.Cause: A failure occurred while creating an instance of the Connection
driver. The failure can happen if the Connection
or Persistence
JAR files are not in the CLASSPATH setting.
Action: Ensure that all the Connection
and Persistence
classes are included in the CLASSPATH setting.
Cause: There are a variety of possible reasons why the connection was not made.
Action: Check the cause and action text for the BIB error message that is specified after "Reason:".
Cause: An attempt to connect to the OLAP service failed, because the user could not be authenticated or because a CORBA error occurred.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to connect to the database failed.
Action: Check the underlying error stack to find the root cause of the problem.
ServerUrl
contains invalid context; nothing bound.Cause: The context that is specified in ServerUrl
is invalid.
Action: Ensure that a valid context is specified and that the object name that is specified in the context is bound to ONS.
Cause: The DAD file that is specified by the application cannot be found.
Action: Ensure that the file that is specified exists and can be located through the CLASSPATH setting if the file that you specified uses a relative path.
Cause: The IOR entry for the specified OLAP instance is no longer valid in the OLAP instance table (ALL_OLAP_OS_CHILD_INSTANCES).
Action: Stop the OLAP service. Clean the OLAP instance table. Restart the OLAP service.
Cause: Either the user name or password in the Database Access Descriptor (DAD) file is empty or the application failed to pass the user name or password.
Action: Ensure that the user name and password are provided by the application or the DAD file.
Cause: Either the connection information in the biconfig.xml
file is incomplete or the application failed to pass adequate connection information.
Action: Ensure that the host, port, and SID are specified properly.
Cause: The user information that was provided was incomplete or incorrect.
Action: Verify that the user information that was provided is correct. This information was provided by the application or the DAD (Database Access Descriptor) file.
Cause: A database access error occurred.
Action: Check the underlying error stack to find the database error.
Cause: The JDBC connection could not be initialized.
Action: Check your JDBC configuration, such as the version of your JDBC libraries.
Cause: An error occurred while executing the OLAP DML command because either the command syntax is incorrect or the log returned is too long.
Action: Ensure that the OLAP DML command syntax is correct or check the underlying error stack to find the root cause of the problem.
Cause: A connection to the database was not established.
Action: Invoke the connect
method. Try to execute the commmand again.
Cause: The CLASSPATH setting does not contain the OLAP client
classes (olap_api_xx.jar
).
Action: Include the OLAP client classes in the CLASSPATH setting.
Cause: Cannot connect to the database because the initialization failed.
Action: Ensure that you have the correct JDBC library (classes12.jar
) or check the underlying error stack to find the root cause of the problem.
Cause: A database error occurred while initializing the OLAP DML command executor.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The connection failed because the OLAP option in the Oracle9i Release 2 database requires a JDBC driver for Oracle9i Release 2.
Action: If there is a JDBC driver mismatch, then reinstall BI Beans and choose the appropriate database version on the Choose Oracle Database page.
Cause: The connection failed because BI Beans is compatible only with Oracle 9i Release 2 (9.2.0.2) and higher database versions.
Action: Use only Oracle 9i Release 2 (9.2.0.2) or higher database versions with this version of BI Beans.
PersistenceManager
failed.Cause: An attempt to connect to the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt was made to execute one of the following unsupported operations: executeCommand
or evaluateExpression
.
Action: Ensure that the code does not call the executeCommand
or evaluateExpression
methods.
PersistenceManager
failed.Cause: An attempt to disconnect from the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to connect to the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem. Check that the environment passed to the init
method of the BIBeansPresentationDeployerImpl
is not null.
Cause: An XML parsing error occurred. The XML format is probably invalid.
Action: Check the XML format of the input data and ensure that the format conforms to the requirements.
Cause: The metadata is invalid or there is an error in the Oracle OLAP connection.
Action: Check the underlying error stack to find the root cause of the problem. Also check that the metadata that is specified in the XML code is valid.
Cause: An error occurred while applying selections or initializing the query during the deployment of a presentation.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An error occurred while saving the newly created presentation in the BI Beans Catalog.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: An attempt to disconnect from the BI Beans Catalog has failed.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The specified attribute cannot be found. The XML that is set on the BIBeansPresentationDeployerImpl
contains invalid values.
Action: Check that the XML for the metadata and presentation description is valid.
Cause: The configuration settings were not specified in the obsolete ASCII configuration file.
Action: Specify the configuration settings, if you are using the obsolete ASCII configuration file.
Cause: The obsolete ASCII configuration file was not found.
Action: Specify the path for the file, if you are using the obsolete ASCII configuration file.
BISession
object was not populated with required entries.Cause: The BISession
object was not populated with the required entries.
Action: Specify the required settings on the BISession
object or specify the settings in the obsolete ASCII configuration file.
Cause: An exception occurred while reading the obsolete ASCII configuration file.
Action: Ensure that the settings in the obsolete ASCII configuration file contain no errors.
Cause: The pluggable authentication driver class name was not specified.
Action: Provide the name of the pluggable authentication driver in the obsolete ASCII configuration file.
Cause: The pluggable connection driver class name was not specified.
Action: Provide the name of the pluggable connection driver in the obsolete ASCII configuration file.
Cause: Some of the required entries were missing in the obsolete ASCII configuration file.
Action: Ensure that the pluggable driver settings are specified in the obsolete ASCII configuration file.
Cause: The obsolete ASCII configuration file (config.cfg
) contains invalid configuration settings. It is likely that fewer than the expected number of fields was found.
Action: Ensure that the config.cfg
file has not been modified. This is an obsolete ASCII configuration file that contains settings for pluggable drivers. Restore this file and specify pluggable drivers in the XML version of the configuration file.
Cause: An invalid first field occurred at the specified line number in the obsolete ASCII configuration file.
Action: Fix the first field at the specified line number in the obsolete ASCII configuration file.
Cause: An invalid second field occurred at the specified line number in the obsolete ASCII configuration file.
Action: Fix the second field at the specified line number in the obsolete ASCII configuration file.
Cause: An invalid third field occurred at the specified line number in the obsolete ASCII configuration file.
Action: Fix the third field at the specified line number in the obsolete ASCII configuration file.
Cause: An invalid fourth field occurred at the specified line number in the obsolete ASCII configuration file.
Action: Fix the fourth field at the specified line number in the obsolete ASCII configuration file.
Cause: The obsolete ASCII configuration file could not be initialized.
Action: Ensure that the obsolete ASCII configuration file exists. The file should be accessible by the server in multitier mode.
Cause: The requested operation cannot proceed.
Action: Check the reason that is provided in the message and fix the problem.
Cause: The pluggable user community driver class name was not specified in the obsolete ASCII configuration file.
Action: Specify a valid user community driver in the obsolete ASCII configuration file.
Cause: The pluggable user community can be specified for the session only.
Action: In the obsolete ASCII configuration file, specify that the user community driver be at the session level.
Cause: The specified pluggable user community driver class was not found.
Action: Ensure that the specified class exists. The middle tier loads the pluggable driver in multitier mode.
Cause: The supplied input stream was invalid.
Action: Ensure that the obsolete ASCII configuration file exists. The file should be accessible by the middle tier in multitier mode.
SQLException
exception.Cause: The BI Beans runtime environment received an unexpected SQLException
.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem.
Cause: The BI Beans runtime environment received an unknown or unexpected Java exception.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem.
Cause: The specified name for the pluggable authentication driver class was not found.
Action: Ensure that the specified class exists. The middle tier loads the pluggable driver in multitier mode.
Cause: The specified class could not be instantiated.
Action: Ensure that the specified class exists. The middle tier instantiates the driver in multitier mode.
Cause: Authentication at the specified level failed.
Action: Refer to the authentication driver exception message and take the appropriate action. Ensure that the correct user name is specified.
BISession
does not contain BISecurityConstants.BIUSER
.Cause: The BIUser
is not specified for the BISession
; therefore, the application cannot proceed.
Action: Specify a valid BIUSer
.
Cause: The specified pluggable connection driver class was not found.
Action: Ensure that the specified class exists. The middle tier loads the pluggable driver in multitier mode.
Cause: The specified driver class could not be instantiated.
Action: Ensure that the specified class exists. The middle tier instantiates the pluggable driver in multitier mode.
Cause: The connection type failed.
Action: Refer to the exception message that was thrown by the connection driver and take the appropriate action. Check the connection string, ensure that the service is available, specify the correct user name and password, and so on.
Cause: The RDBMS user information was not specified.
Action: Specify the RDBMS user information.
Cause: The specified DAD file was not found.
Action: Specify a valid DAD file name. The middle tier loads the DAD file in multitier mode.
Cause: The specified DAD file could not be initialized.
Action: Ensure that the specified DAD file exists. The middle tier loads the DAD file in multitier mode.
Cause: The DAD file name was not specified.
Action: Specify a valid DAD file name and ensure that the middle tier can access the file in multitier mode.
Cause: The BI Beans runtime environment received an unknown or unexpected Java exception.
Action: Invoke the printStackTrace
method on the exception object to display the full error stack. Check the underlying error stack to find the root cause of the problem.
Cause: The DAD file contains more than two fields per entry.
Action: Fix the DAD file so that it contains only two fields per entry, with each field separated with a color (:) delimiter.
Cause: The DAD file contains invalid settings.
Action: Check the reason that is provided in the message and fix the problem.
Cause: The DAD file does not contain two fields per entry.
Action: Fix the DAD file so that it contains two fields per entry, with each field separated with a color (:) delimiter.
Cause: The DAD file contains invalid fields.
Action: Adjust the fields in the DAD file. Refer to the DAD file documentation for more information.
Cause: Unobfuscation of the DAD file failed.
Action: Check the reason that is provided in the message and take the appropriate action.
InitialPersistenceManager
is not registered with the ManagerFactory
.Cause: No InitialPersistenceManager
has been registered with the ManagerFactory
. The ManagerFactory
cannot proceed without the persistence services.
Action: Register an InitialPersistenceManager
with the ManagerFactory
by calling the getInstance
method with the name of the InitialPersistenceManager
as the argument.
Cause: The specified path does not resolve to a folder.
Action: Ensure that the path specifies a valid folder.
MetadataManager
object.Cause: The name that is specified in the lookupQueryManager
and lookupMetadataManager
methods does not resolve to a stored MetadataManager
object.
Action: Verify that the name that is specified actually binds to a MetadataManager
object.
Cause: A NamingException
has occurred while looking up of one of the following:
MetadataManager
is stored.MetadataManager
.Action: Ensure that the path name and object name are correct. Check the underlying error stack to find the root cause of the problem.
Cause: A ConnectionException
has occurred while creating a persistence connection that is based on an existing connection from the PersistenceManager
.
Action: Check the reason that is provided in the message and take the appropriate action. Check the underlying error stack to find the root cause of the problem.
Cause: A MetadataManagerException
has occurred while attaching an analytic workspace.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: A ParseException
, SAXException
, or IOException
has occurred while parsing the BI Beans configuration file.
Action: Check the underlying error stack to find the root cause of the problem.
MetadataManager
exception has occurred.Cause: A MetadataManagerException
was thrown while performing an operation on the MetadataManager
instance.
Action: Check the underlying error stack to find the root cause of the problem.
QueryContext
defined.Cause: A method was called that requires an existing QueryContext
object.
Action: Create a QueryContext
object before calling the method.
Selection
defined.Cause: A method was called that requires an existing Selection
object.
Action: Create a Selection
object before calling the method.
QueryAccess
could not be created.Cause: A QueryAccess
object could not be created.
Action: Verify that a valid QueryContext
object exists. You create a QueryAccess
using syntax such as queryContext.createQueryAccess
.
DataAccess
could not be created.Cause: A DataAccess
object could not be created.
Action: Verify that a valid QueryAccess
object exists and that the dimension that is specified for the Selection
is valid.
Cause: An unknown exception occurred in a call to a different class.
Action: Check the underlying error stack to find the root cause of the problem.
PersistenceManager
exception has occurred.Cause: A NamingException
was thrown during the creation of the PersistenceManager
instance.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The view's data source generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The view's data source generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The persistence service generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: Invalid export parameters were passed into the export event.
Action: Check the server error log for more information.
Cause: The export engine generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The view's data source generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The view's data source generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
BIContext
was null.Cause: The BIContext
on the HttpSession
was null.
Action: Check to ensure that the application has passed the BIContext
on the HttpSession
.
Cause: The view's data source generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The view's data source generated an exception.
Action: Check the underlying error stack to find the root cause of the problem.
Cause: The servlet response stream was null.
Action: Do not write to the servlet response stream before the view handles the export event.
Cause: The ThinCrosstab was not set on the CrosstabBean.
Action: The ThinCrosstab must be set on the CrosstabBean before the CrosstabBean is rendered.
Cause: The ThinGraph was not set on the GraphBean.
Action: The ThinGraph must be set on the GraphBean before the GraphBean is rendered.
Cause: The ThinTable was not set on the TableBean.
Action: The ThinTable must be set on the TableBean before the TableBean is rendered.
Cause: The ExplorerTree was not set on the ExplorerTreeBean.
Action: The ExplorerTree must be set on the ExplorerTreeBean before the ExplorerTreeBean is rendered.
Cause: The ExplorerDetail was not set on the ExplorerDetailBean.
Action: The ExplorerDetail must be set on the ExplorerDetailBean before the ExplorerDetailBean is rendered.
Cause: The ExplorerSearch was not set on the ExplorerSearchBean.
Action: The ExplorerSearch must be set on the ExplorerSearchBean before the ExplorerSearchBean is rendered.
Cause: The ViewToolbar was not set on the ViewToolbarBean.
Action: The ViewToolbar must be set on the ViewToolbarBean before the ViewToolbarBean is rendered.
Cause: The RotateTool was not set on the RotateToolBean.
Action: The RotateTool must be set on the RotateToolBean before the RotateToolBean is rendered.
Cause: The ViewTypeTool was not set on the ViewTypeToolBean.
Action: The ViewTypeTool must be set on the ViewTypeToolBean before the ViewTypeToolBean is rendered.
Cause: The SortTool was not set on the SortToolBean.
Action: The SortTool must be set on the SortToolBean before the SortToolBean is rendered.
Cause: The FavoriteTool was not set on the FavoriteToolBean.
Action: The FavoriteTool must be set on the FavoriteToolBean before the FavoriteToolBean is rendered.
Cause: The FindMember was not set on the FindMemberBean.
Action: The FindMember must be set on the FindMemberBean before the FindMemberBean is rendered.
Cause: The PrinterFriendlyView was not set on the PrinterFriendlyViewBean.
Action: The PrinterFriendlyView must be set on the PrinterFriendlyViewBean before the PrinterFriendlyViewBean is rendered.
Cause: The PrintOptions was not set on the PrintOptionsBean.
Action: The PrintOptions must be set on the PrintOptionsBean before the PrintOptionsBean is rendered.
Cause: The ExportOptions was not set on the ExportOptionsBean.
Action: The ExportOptions must be set on the ExportOptionsBean before the ExportOptionsBean is rendered.
Cause: The SaveConfirmation was not set on the SaveConfirmationBean.
Action: The SaveConfirmation must be set on the SaveConfirmationBean before the SaveConfirmationBean is rendered.
Cause: The SaveAs was not set on the SaveAsBean.
Action: The SaveAs must be set on the SaveAsBean before the SaveAsBean is rendered.
Cause: The Exception was not set on the ErrorDialog.
Action: The Exception must be set on the ErrorDialog before the ErrorDialog is rendered.
Cause: The thin bean is not contained by a form.
Action: The thin bean should be contained by a form
Cause: An input/output error occurred while saving the graph image on disk.
Action: Ensure that the user has write access to the folder in which dynamic UIX component images are saved.
Cause: The RotateTool
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the RotateTool
.
Cause: The handling of the BIConstants.SELECT_OBJECT_EVENT
failed.
Action: Check if the object path is valid. Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer bean.
Cause: The Explorer bean could not select the path.
Action: Check if the path name is valid. Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer bean.
Cause: The handling of the BIConstants.FILTER_EVENT
failed. The Explorer bean could not change the object type.
Action: Check if the object type is a valid constant as defined in PersistableConstants
. Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer bean.
Cause: The handling of the BIConstants.DELETE_EVENT
failed. The Explorer Detail bean could not refresh the model.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer Detail bean.
Cause: The handling of the BIConstants.EXPAND_FOLDER_EVENT
failed. The Explorer Tree bean could not expand the folder.
Action: Check the folder path name. Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer Tree bean.
Cause: The handling of the BIConstants.SEARCH_EVENT
failed. The Explorer Search bean could not perform the search.
Action: Check the search parameters. Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer Search bean.
ExplorerTree
rendering failed.Cause: The ExplorerTree
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer Tree bean.
ExplorerDetail
rendering failed.Cause: The ExplorerDetail
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer Detail bean.
ExplorerSearch
rendering failed.Cause: The ExplorerSearch
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the BIContext
that is set on the Explorer Search bean.
Cause: The favorite could not be retrieved.
Action: Check the name of the favorite. Check the underlying error stack to find the root cause of the problem. The problem is often related to the BIContext
that is set on the FavoriteTool
or to the data source of the view that is set on the FavoriteTool
.
Cause: The favorite could not be applied to the data source of the view.
Action: Check the name of the favorite. Check the underlying error stack to find the root cause of the problem. The problem is often related to the data source of the view that is set on the FavoriteTool
.
Cause: The specified sort operation could not be performed on the view.
Action: Check the underlying error stack to find the root cause of the problem. The problem is often related to the data source of the view that is set on the SortTool
.
FavoriteTool
rendering failed.Cause: The FavoriteTool
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the FavoriteTool
.
SortTool
rendering failed.Cause: The SortTool
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the SortTool
.
Cause: The Find Member bean could not be initialized. The handling of the BIConstants.INIT_FIND_MEMBER_EVENT
failed.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the FindMember
.
Cause: The Find Member bean could not handle the BIConstants.SEARCH_EVENT
.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the FindMember
.
Cause: The PrinterFriendlyView bean could not be initialized. The handling of BIConstants.INIT_PRINTER_FRIENDLY_VIEW_EVENT
failed.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the PrinterFriendlyView
.
FindMember
rendering failed.Cause: The FindMember
object could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the FindMember
.
PrintOptions
rendering failed.Cause: The PrintOptions
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the PrintOptions
.
PrinterFriendlyView
rendering failed.Cause: The PrinterFriendlyView
could not be rendered.
Action: Check the underlying error stack to find the root cause of the problem. The problem is related to the data source of the view that is set on the PrinterFriendlyView
.
Cause: The specified target object did not exist.
Action: Check the targetId attribute of the Render tag. Check the attributes of the definition tag for the target object.
Cause: One or both the following attributes are not specified: saveConfirmationPage and saveConfirmationId.
Action: Specify the saveConfirmationPage and the saveConfirmationId attributes.