10 DVT-02012 to DVT-26021
- DVT-02012: Column {0} exceeds boundary {1}.
-
Cause: The specified column number was greater than the total number of columns.
-
Action: Get the total number of columns, by calling the getColumnCount method of the graph or of the column header in the pivot table. Then specify a column that does not exceed the total number of columns.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-02013: Row {0} exceeds boundary {1}.
-
Cause: The specified row number was greater than the total number of rows.
-
Action: Get the total number of rows, by calling the getRowCount method of the graph or of the column header in the pivot table. Then specify a row that does not exceed the total number of rows.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-02017: Series {0} exceeds boundary {1}.
-
Cause: The specified series was greater than the total series that is available in the graph.
-
Action: Specify a zero-based series index 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.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-02018: Edge {0} exceeds boundary {1}.
-
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.
-
Action: Specify a valid edge constant.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-02019: Current DataSource does not support required type: {0}.{1}.
-
Cause: The DataSource did 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 did not supply group sort information.
-
Action: Request support for the required data types in the DataSource, or use a different DataSource.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-02020: DTD file cannot be found.
-
Cause: The specified DTD could not be found. The XML parser needed the DTD in order to validate XML files.
-
Action: Ensure that the specified DTD file exists, or disable XML validation. DTDs for Data Visualization components are in their respective packages. To turn off validation, call Dataview.setXMLValidated(false);.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-03000: No Mergeable object is provided.
-
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.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-03001: attempt to call merge(Mergeable) on an incompatible Mergeable class
-
Cause: An attempt was made to merge incompatible Mergeable classes. Only Mergeable objects of the same class can be merged. For example, ViewStyle objects can be merged, 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.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-06001: no Converter for data type {0} during Pivot Table text formatting
-
Cause: The application could not create a Converter for a specific data type. The most likely reason was that a Converter was not registered for that data type.
-
Action: Log a bug against the application. Verify that the application can create a default Converter for all data types rendered by the Pivot Table.
Level: 1
Type: TRACE
Impact: Configuration
- DVT-07001: cannot create Graph image
-
Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.
-
Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-22004: cannot create Gauge image
-
Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.
-
Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-23001: The time unit in the major axis must be greater than the time unit in the minor axis.
-
Cause: The time unit specified in the major axis was not greater than the time unit specified in the minor axis. For example, if "days" was specified as the time unit for the minor axis, then the time unit specified in the major time axis must be greater than "days", such as "months", and not anything less, such as "hours".
-
Action: Ensure that the time unit in the major axis is greater than the time unit in the minor axis.
Level: 1
Type: ERROR
Impact: Programmatic
- DVT-23006: The number of tooltip keys does not match the number of tooltip labels.
-
Cause: The number of tooltip keys did not match the number of tooltip labels specified in the Gantt tag.
-
Action: Ensure that the number of tooltip keys specified in the Gantt tag (tooltipKeys attribute) matches the tooltip labels specified in the Gantt tag (tooltipLabels attribute).
Level: 1
Type: WARNING
Impact: Programmatic
- DVT-23007: The number of legend keys does not match the number of legend labels.
-
Cause: The number of legend keys did not match the number of legend labels specified in the Gantt tag.
-
Action: Ensure that the number of legend keys specified in the Gantt tag (legendKeys attribute) matches the legend labels specified in the Gantt tag (legendKeyLabels attribute).
Level: 1
Type: WARNING
Impact: Programmatic
- DVT-23008: The start date of the task is out of range. Value: {0}
-
Cause: The start and end date of a task was outside of the time range specified for the Gantt chart.
-
Action: No action necessary, if it is okay not to show the task. Otherwise, verify data is correct or specify a wider time range for the Gantt chart (using the startTime and endTime attributes)
Level: 1
Type: WARNING
Impact: Data
- DVT-23010: The specified day of the week is invalid. Value: {0}
-
Cause: The day of the week specified was not recognized.
-
Action: Specify a value for the day of the week that is one of these seven constants from the java.util.Calendar class: Calendar.SUNDAY, Calendar.MONDAY, Calendar.TUESDAY, Calendar.WEDNESDAY, Calendar.THURSDAY, Calendar.FRIDAY, Calendar.SATURDAY.
Level: 1
Type: WARNING
Impact: Programmatic
- DVT-23011: The value specified for alignment is invalid. Task ID: {0}
-
Cause: The alignment value specified for the label or icon was invalid.
-
Action: Specify a value for alignment that is one of these three constants from the oracle.adf.view.faces.bi.component.gantt.GanttConstants class: GanttConstants.LEFT, GanttConstants.RIGHT, GanttConstants.INSIDE.
Level: 1
Type: WARNING
Impact: Programmatic
- DVT-23012: GanttDropTarget can only be attached to a Gantt component.
-
Cause: The GanttDropTarget tag was added as a child of a non-Gantt component.
-
Action: Ensure that the GanttDropTarget tag is a child tag of either a Project Gantt or Scheduling Gantt component.
Level: 1
Type: WARNING
Impact: Programmatic
- DVT-26010: The mouse click behavior of {0} is to render a popup, but there is no popup facet in the map.
-
Cause: The map had no popup facet, but the leftClickBehavior property was specified to render a popup.
-
Action: Check whether the mouse click behavior is correct.
Level: 1
Type: WARNING
Impact: Data
- DVT-26011: The right-click behavior of {0} is to render a popup, but there is no popup facet in the map.
-
Cause: The map had no popup facet, but the rightClickBehavior property was specified to render a popup.
-
Action: Check whether the right-click behavior is correct.
Level: 1
Type: WARNING
Impact: Data