Cause: MapViewer could not obtain the necessary resource to process an incoming request.

Action: Try increasing the value of the "number_of_mappers" attribute in the definition of the involved data source.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00003: SQL error occurred while generating map.

Cause: MapViewer encountered an error while executing a SQL query.

Action: Check the MapViewer server logs for details about the SQL exception and take appropriate actions.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00004: Unable to add a predefined theme.

Cause: MapViewer could not add or load a predefined theme while processing the current map request.

Action: Ensure the predefined theme exists in the database or is accessible via the given data source.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00005: Error while compressing raw image data.

Cause: MapViewer could not successfully compress a generated map image into the requested file format.

Action: Check the MapViewer server logs for the actual stack trace and take appropriate actions.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00006: Location for saving map image files not specified.

Cause: MapViewer could not obtain the path information for saving generated map files.

Action: Check the MapViewer configuration file and make sure a path for saving image files is specified or the default path is a valid one.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00007: No map image generated.

Cause: MapViewer did not generate a map image.

Action: Check the MapViewer server logs for details/exceptions and take appropriate actions.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00008: Unable to add local theme(s).

Cause: MapViewer could not create a new local theme for the current map request.

Action: Check the MapViewer server logs for details/exceptions and take appropriate actions. Make sure the individual Geo-Features are in proper format.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00009: Unable to add JDBC theme(s).

Cause: MapViewer could not create a new JDBC (dynamic) theme for the current map request.

Action: Check the MapViewer server logs for details/exceptions and take appropriate actions. Make sure the data source information is correct, and characters in the user-supplied SQL query are properly escaped for XML.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00010: Error loading MapViewer configuration file.

Cause: MapViewer could not properly load its configuration file.

Action: Make sure the XML configuration file is in valid and well-formed format.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00011: Error creating a map data source.

Cause: MapViewer could not create a new data source.

Action: Make sure correct database connection information is supplied, including host name, database instance name/sid, listener port, and login user/password. Also make sure the host name or IP address is reachable by the host running the MapViewer server.

Cause: MapViewer could not obfuscate the login password for a data source defined in its configuration file.

Action: Make sure the password is prefixed with an exclamation point (!).

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00013: Clear-text passwords in the config file must be prefixed with a '!' (exclamation mark).

Cause: Clear text password in the MapViewer configuration file was not prefixed with '!'.

Action: Make sure the database login password for any data source defined in the configuration file is prefixed with an exclamation point (!).

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00014: Error adding a MARKER style from an image URL.

Cause: MapViewer could not create a dynamic MARKER style that is based on a URL.

Action: Make sure the URL of the image is reachable from the host running the MapViewer server. If MapViewer is running behind a firewall, you may need to set up HTTP proxy information in MapViewer's configuration file, or via JVM run-time properties.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00015: Cannot fetch image from given URL

Cause: MapViewer could not fetch and load an image from a given URL.

Action: Make sure the URL of the image is reachable from the host running the MapViewer server. If MapViewer is running behind a firewall, you may need to set up HTTP proxy information in MapViewer's configuration file, or via JVM run-time properties.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00016: Error while attempting to clear a mapping metadata cache.

Cause: MapViewer could not clear the cached mapping metadata (style/theme/basemap definitions) for a given data source from memory.

Action: Make sure a correct data source name is specified. Also check MapViewer server logs for possible exceptions and stack traces.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00017: MapViewer is not ready. Please try again later.

Cause: MapViewer was still starting core services such as the mapping servlet. If this error still occurs 30 seconds after starting MapViewer, it may be stuck trying to connect to one or more database instances.

Action: Check and monitor MapViewer server logs to see which server has not been started yet. Check data source definitions in the configuration file and make sure all the database instances involved are up and running.

Action: Make sure proper value scale ranges are set for all themes in the map request.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00112: XML map request: invalid WMS theme specified.

Cause: The incoming map request contained an invalid WMS theme.

Action: Make sure all WMS themes are properly defined in the XML map request.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00113: Permission denied for this operation.

Cause: The requested operation was not permitted by the MapViewer server.

Action: Make sure your operation is permitted by MapViewer. For example, the server may disallow JDBC themes in the map request, or disable direct INFO requests. You will need either to avoid performing these operations or to modify MapViewer configuration to allow these operations.

Action: Make sure values for your theme's binding parameters are all of correct type.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00115: list_predefined_themes: No base map found for map tile layer.

Cause: The 'list_predefined_themes' request specified a map tile layer that is based on a nonexistent base map.

Action: Make sure the base map for the specified map tile layer exists in the database view.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-00116: list_predefined_themes: Map tile layer not found.

Cause: The 'list_predefined_themes' request specified a map tile layer that is not found.

Action: Make sure the specified map tile layer exists in the database view.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01000: No themes to render.

Cause: The Map request had no base map or themes defined.

Action: Add a base map that contains a list of themes or define individual themes on your request.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01001: Cannot load base map.

Cause: A database error may have happened while reading the base map definition from the USER_SDO_MAPS view, or the requested base map was not defined.

Action: Make sure the base map exists in the database; also check the MapViewer log for database errors and additional details.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01002: Cannot load theme.

Cause: A database error may have happened while reading the theme definition from the USER_SDO_THEMES view, or the requested theme was not defined.

Action: Make sure the theme exists in the database; also check the MapViewer log for database errors and additional details.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01003: Cannot load style.

Cause: A database error may have happened while reading the style definition from the USER_SDO_STYLES view. Or the requested style was not defined.

Action: Make sure the style exists in the database; also check the MapViewer log for database errors and additional details.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01004: Bounding Themes returned null MBR. Themes were not rendered.

Cause: Bounding themes may have been used to define the query window for the map request, but it produced no spatial feature. The map request was aborted due to this condition.

Action: Change the bounding theme or themes definition, so the definition defines a select statement that returns one or more features. In Map Builder, this message can happen when previewing base maps with full extent (no center and size defined). Map Builder uses the first theme of the base map as the bounding theme when a full extent is applied. If this first theme returns no features for a full extent request, then you should remove it from the base map list of themes.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01005: No spatial data to render.

Cause: A full extent request (no center and size defined) returned no features.

Action: Change the theme or themes definition to select one or more features.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01006: Invalid style type for Point features.

Cause: The style type used could not be applied to render point features.

Cause: The WFS theme definition did not contain the service URL attribute.

Action: Define the attribute 'service_url' in the WFS theme definition.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01023: Unable to find entry in ALL_SDO_GEOM_METADATA table for theme:

Cause: Theme base table and spatial column have not been registered in the user metadata view (USER_SDO_GEOM_METADATA).

Action: Register the theme base table and spatial column in the user metadata view, by inserting a row in the USER_SDO_GEOM_METATADA view.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01024: Unable to convert query window SRID to theme SRID.

Cause: Conversion of map request query window projection to theme projection has failed. The database procedure sdo_cs.transform was used to convert coordinates from one SRID to another SRID.

Action: Check the log for database errors.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01025: Cannot use ratio scale mode with theme that has unknown SRID.

Cause: A request with a ratio scale was attempted, but the data did not contain a valid Oracle SRID.

Action: Assign a valid SRID to the spatial data.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01026: Unable to get an instance of spatial provider.

Cause: A custom spatial provider was not be defined in MapViewer's configuration file, or the provider class path was not accessible.

Action: Check the spatial provider section in the MapViewer configuration file for the definition of the provider. If it is defined there, check the libary jar file path, and make sure it is part of the classpath definition for the application.

Cause: The custom geometry theme definition did not contain the spatial provider attribute.

Action: Define the attribute 'provider_id' in the custom theme definition.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01028: Custom spatial data provider is null.

Cause: The custom spatial data provider was not initialized and is null.

Action: Check if the provider name is defined in the theme definition, and also check if the provider class library is defined in the MapViewer configuration file and is part of the application classpath.

MAPVIEWER-01030: A set of four question marks separated by commas is required to define a geometry theme with a dynamic SDO_FILTER.

Cause: A set of questions marks was not used in the SDO_ORDINATE_ARRAY for a dynamic geometry theme with a SQL expression that also includes the spatial filter operator (SDO_FILTER). These question marks will be replaced with values based on the map request center and size.

Action: Use the following pattern for the ordinate array on the SOD_FILTER expression: SDO_ORDINATE_ARRAY(?,?,?,?).

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01031: Not enough binding parameters defined.

Cause: The theme definition contained binding parameters on its query expression, but the parameters were not provided inn the map request.

Action: Pass the theme binding parameters to your theme definition, using the methods provided by the JavaScript API (Oracle Maps), or by the Java API; or if issuing a direct XML request, define the binding parameters in the theme section.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01032: GeoRaster spatial extent is null.

Cause: The GeoRaster object contained a null geometry as its spatial extent.

Cause: The image stretch low value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range.

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01034: Invalid image stretch high value.

Cause: The image stretch high value was not numeric and ranging from 0 to 256. The default value 100 is used if the number is out of this range.

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01035: Invalid brightness value.

Cause: The image brightness value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01036: Undefined brightness value for image processing.

Cause: The image brightness value was not defined, as required when a brightness operation is to be applied on a GeoRaster object.

Action: Define the parameter 'value' for brightness in the theme definition.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01037: Invalid contrast value.

Cause: The image contrast value was not numeric and ranging from 0 to 256. The default value 256 is used if the number is out of this range

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01038: Undefined contrast value for image processing.

Cause: The image contrast value was not defined, as required when a contrast operation is to be applied on a GeoRaster object.

Action: Define the parameter 'value' for contrast in the theme definition.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01039: Invalid threshold value.

Cause: The image threshold value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01040: Invalid low threshold value.

Cause: The image threshold low value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01041: Invalid high threshold value.

Cause: The image threshold high value was not numeric and ranging from 0 to 256. The default value 0 is used if the number is out of this range

Action: Define a numeric value within the specified range.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01042: Invalid image column type for image theme.

Cause: The image theme data was not stored in a column of type BLOB or ORDIMAGE.

Action: Assign a valid image column in the image theme definition.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01043: Network category is null.

Cause: The network model category information was null in the metadata view.

Action: Check the contents of column 'network_category' in the network metadata view USER_SDO_NETWORK_METADATA.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01044: Network geometry type is null.

Cause: The network model geometry type information was null in the metadata view.

Action: Check the contents of column 'geometry_type' in the network metadata view USER_SDO_NETWORK_METADATA.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01045: Undefined topology column for topology theme.

Cause: The topology theme definition did not contain the spatial column attribute.

Action: Define the attribute 'spatial_column' in the topology theme definition.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01046: WFS theme server URL is null.

Cause: The WFS server URL was not defined.

Action: Check if the WFS theme definition has a value for the attribute 'service_url'.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01047: WMS theme server URL is null.

Cause: The WMS server URL was not been defined.

Action: Check if the WMS theme definition has a value for attribute 'service_url'.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01048: Cannot load WMS map image.

Cause: The image could not be retrieved from the WMS server.

Action: Check if the WMS server URL defined in the theme definition is accessible. Change the timeout value in the theme definition if a timeout has happened.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-01049: X or Y column not found in SQL query.

Cause: The SQL query string in a dynamic JDBC theme did not contain either x or y column.

Action: If your dynamic JDBC theme is using x and y columns to specify the location of a point theme (instead of an SDO_GEOMETRY column), make sure that both the x and y columns are present in the SQL query. Otherwise, check the query itself and make sure a proper SDO_GEOMETRY type column is selected.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02000: There is no database connection loaded.

Cause: Operation could not be performed unless a database connection has been added or loaded.

Action: Use Map Builder interface options to create or to add (load) a connection.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02001: Connection test failed.

Cause: The connection parameters were wrong, the database was down, or the listener was not running.

Action: Check the MapViewer log or console for database errors, and change connection parameters if necessary.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02002: Unable to register data source connection.

Cause: The connection parameters were wrong, the database was down, or the listener was not running.

Action: Check the MapViewer log or console for database errors. If the connection has been already added to Map Builder, check the connections parameters in the Map Builder preferences file (default file is oasmapbuilder.xml), and modify them if needed. Restart Map Builder to load the current preferences file. If it is a new connection being added, change the connection parameters and test the connection before trying to add it.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02050: Unable to save base map definition.

Cause: A database error may have happened while saving the base map in the USER_SDO_MAPS view.

Action: Check the MapViewer log for database errord.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02051: Unable to save style definition.

Cause: A database error may have happened while saving the style in the USER_SDO_STYLES view.

Action: Check the MapViewer log for database errors.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02052: Unable to save theme definition.

Cause: A database error may have happened while saving the theme in the USER_SDO_THEMES view.

Action: Check the MapViewer log for database errors.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02053: Unable to save tile layer definition.

Cause: A database error may have happened while saving the tile layer in the USER_SDO_CACHED_MAPS view.

Action: Check the MapViewer log for database errors.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02054: Unable to duplicate metadata.

Cause: A database error may have happened while saving a duplicate metadata.

Action: Make sure the new metadata name does not exist on the target database. Check the MapViewer log for database errors.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02055: Unable to delete metadata.

Cause: A database error may have happened while removing metadata from a database view.

Action: Fix the style XML definition with an external tool, and refresh the connection in Map Builder.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02101: Unable to build theme definition.

Cause: A database error may have happened while reading theme parameters.

Action: Check the MapViewer log for database errors.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02102: Unable to parse hexadecimal value.

Cause: The string value was not recognized as a valid hexadecimal expression.

Action: Use the pattern #xxxxxx to represent the hexadecimal color value. Character # must be first followed by six digits or letters. Each x may be a digit between 0 and 9, or one of the letters "a,b,c,d,e,f".

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02103: Unable to parse style definition.

Cause: Database-related errors or SQL exceptions may have happened while reading style parameters.

Cause: The list of registered spatial data providers did not contain the provider name.

Action: Check the Map Builder preferences file (default file is oasmapbuilder.xml) to see if it defines the provider parameters. Spatial providers are registered at Map Builder startup if they are defined in the preferences file.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-02301: Unable to initialize spatial data provider.

Cause: Initialization parameters were missing or were not accepted by the spatial provider.

Cause: The map tile layer was not successfully added to the MVMapView instance.

Action: Make sure both of the following two conditions are met when adding a map tile layer to the MVMapView instance: 1. The MapViewer base URL is valid. 2. The map tile layer name and data source name are specified correctly.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05519: One or more parameter is missing or invalid.

Cause: One or more parametesr in the function call were missing or invalid.

Action: Make sure all required parameters are specified correctly.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05520: Geometry SRID is null.

Cause: The srid attribute of the MVSdoGeometry object was not specified.

Action: Make sure the srid is specified.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05521: Call back function cannot be null when browser's builtin XMLHttp/XMLHttpRequest is disabled.

Cause: The callback function was not specified when Oracle Maps' non-AJAX remoting mechanism was used.

Action: Specify a callback function.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05522: Client side coordinate system conversion not supported.

Cause: The client tried to invoke client-side coordinate system conversion that is not supported.

Action: Contact Oracle Support if the issue persists.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05523: Cannot process response from MapViewer server.

Cause: The client encountered an error when processing the response from the MapViewer server.

Action: Check the server response and server-side log file for the real cause.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-05524: Theme feature highlighting is disabled for this theme.

Cause: The application tried to highlight or de-highlight a theme-based FOI layer that had theme feature highlighting disabled.

Cause: The theme-based FOI layer had not been added to an MVMapView instance when the application invoked certain theme method.

Action: Make sure the theme method is invoked after the theme is added to an MVMapView instance.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06001: FOI width value is wrong.

Cause: MapViewer received an invalid width value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06002: FOI height value is wrong.

Cause: MapViewer received an invalid height value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06003: FOI ratX value is wrong.

Cause: MapViewer received an invalid ratX value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06004: FOI ratY value is wrong.

Cause: MapViewer received an invalid ratY value for a FOI request.

Action: This typically indicates an application coding error. The two most common coding errors that may cause this error are: 1. The JavaScript function MVMapView.display() may have been invoked before the map container DIV object is fully materialized by the browser. 2. The map center X and Y coordinates were not specified as valid numbers. For cause 1, delay the execution of MVMapView.display() until the map container DIV object is fully materialized by the browser. For cause 2, make sure the map center X and Y coordinates are valid numbers.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06005: FOI bounding box value is wrong.

Cause: MapViewer received an invalid bounding box for a FOI request.

Action: This error should never happen. Contact Oracle Support if the issue persists.

Level: 1

Type: ERROR

Impact: Process

MAPVIEWER-06007: Error rendering a FIG.

Cause: MapViewer encountered an error while rendering a feature of interest (FOI) object.