Skip Headers
Oracle® Communications Network Integrity Developer's Guide
Release 7.1

E23701-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

29 Network Integrity Plug-in Validation Error Messages

This chapter provides information about the Oracle Communications Network Integrity plug-in validation error messages.

Error Message Classifications and Conditions

Table 29-1 lists the error messages, error classifications, and error conditions for the Network Integrity plug-in.

Note:

Text inside {} represents a variable that is replaced based on the current error condition.

Table 29-1 Network Integrity Error Message, Classification, and Error Condition

Error Message Classification Error Condition

Action names must start with a letter.

Error

Occurs when creating an Action without a letter as the first character in the Name.

The character {character} is not valid in an implementation prefix.

Error

Occurs when the implementation prefix of an Action or Processor contains characters that cannot be part of a Java identifier.

Processor {processor name} already has more than one parent Action assigned.

Error

Occurs if an attempt is made to associate a Processor to a second Action. A Processor can have only one parent.

Processor Parameter: {parameter name} not found in Parameter list for Processor {processor name}.

Informational

Occurs if an attempt is made to rename a Processor's Input or Output Parameter, which no longer exists in the Parameter list.

Processor Property Group: {property group name} not found in Property Group list for Processor {processor name}.

Informational

Occurs if an attempt is made to rename a Processor's Property Group, which no longer exists in the Property Group list.

Action Condition {condition name} not found in Condition list for Action {action name}.

Informational

Occurs if an attempt is made to rename an Action's Condition, which no longer exists in the Condition list.

The generated implementation prefix for this entity conflicts with the implementation prefix of entity \"{entity name}\". Choose a different name.

Error

Occurs when an Action's or Processor's Implementation Prefix conflicts with an existing prefix.

Cannot get cartridge from Action: {action name}.

Error

Occurs when Studio is unable to determine the Cartridge to which the current Action belongs as part of dependency checks before building.

SNMP Parameters cannot be added to the Discovery Action because the project does not have a data dictionary.

Warning

Occurs when a SNMP Processor is created and no Data Dictionary exists with the Integrity Project. To correct, first create a Data Dictionary, then create the SNMP Processor.

SNMP Parameters cannot be added to the Discovery Action because a DataDictionary Element matching the name SnmpParameters was found but it is not assigned the UI Parameter Specification type.

Warning

Occurs when a SNMP Processor is created and the Integrity Project's Data Dictionary exists with an SnmpParameters structure that is not of Entity Type UI Parameter Specification. To correct, delete the conflicting SnmpParameters or change its Entity Type to UI Parameters Specification.

SNMP Processor has not specified any OIDs

Error

Occurs if an SNMP Processor has not specified any OIDs.

Processor implementation has not been specified

Error

Occurs if the Processor's Implementation Class is not specified on the Processor's Details tab.

Processor implementation is missing

Error

Occurs if the Processors implementation class, which is specified on the Processor's Details tab, is missing in Studio.

Processor implementation package does not match Processor interface package

Error

Occurs if the package defined in the Processor's Implementation Class does not match the package of the Processor's generated interface.

MIB Directory has not been specified. See Oracle Design Studio Network Integrity preferences.

Error

Occurs if the MIB Directory is not specified in the Oracle Design Studio Network Integrity Preferences (Window -> Preferences -> Oracle Design Studio -> Network Integrity).

MIB directory \"{mib directory}\" does not exist. See Oracle Design Studio Network Integrity preferences

Error

Occurs if the MIB Directory as specified in the Oracle Design Studio Network Integrity Preferences (Window -> Preferences -> Oracle Design Studio -> Network Integrity) does not exist.

MIB module \"{mib module name}\" does not exist

Error

Occurs if the MIBs specified as part of the SNMP Processor are not available in the MIB Directory.

Processor is not used in an Action

Warning

Occurs if the Processor is not used by an Action.

Action has not specified a result category. At least one result category must be specified

Error

Occurs if the Action has not defined at least one Result Category.

Action has not specified a result source. At least one result source must be specified

Error

Occurs if the Discrepancy Detection Action does not contain at least one Result Source.

Result source Action \"{action name}\" cannot be found

Error

Occurs if the Discrepancy Detection Action's Result Source Action cannot be found. For example, the Action has been deleted.

Result source \"{action name} {result source name}\" cannot be found

Error

Occurs if the Discrepancy Detection Action's Result Source cannot be found. For example, it has been deleted from the Action.

UI parameter \"{parameter name}\" does not exist

Error

Occurs if the Data Dictionary Structure referenced by an Action's UI Parameters has been deleted.

Data dictionary element for UI parameter \"{parameter name}\" is invalid

Error

Occurs if the Data Dictionary Structure or its Elements are invalid. For example, the Entity Type is not UI Parameter Specification.

SNMP Processor requires "SnmpParameters" UI parameter

Error

Occurs if the SnmpParameters UI Parameters are not available in the workspace. To correct, ensure the MIB_II_SNMP_Cartridge is imported in the workspace. Next, remove and re-add the SNMP Processor to the Discovery Action.

Address handler implementation has not been specified

Error

Occurs if the Implementation Class for an AddressHandler is not specified.

Address handler implementation is missing

Error

Occurs if the Implementation class itself is not in Studio.

Address handler implementation package does not match interface package

Error

Occurs if the package defined in the AddressHandler's Implementation Class does not match the package of the AddressHandler's generated interface.

Specification \"{specification name}\" does not exist

Error

Occurs if the Specification referenced by a Processor's Model Collection does not exist. For example, it has been deleted.

Data dictionary element for specification \"{specification name}\" is invalid

Error

Occurs if the Data Dictionary Element is invalid. For example, POMS does not support it.

Stale imported Action \"{action name}\". The imported Action's Processors have changed since they were imported.

Error

Occurs when imported Action's Processors have changed. For example, the ordering of the Processors in the owning Action has changed.

Action contains no Processors

Warning

Occurs when an Action exists without any Processors.

Cartridge contains neither Actions nor address handlers

Error

Occurs when a new Integrity Project contains no Actions or AddressHandlers.

Provider has not been specified

Warning

Occurs when the Cartridge Provider has not be specified on the Network Integrity Cartridge Properties tab.

Cartridge cannot contain both Actions and Address Handlers

Error

Occurs when an Integrity Project contains both Address Handlers and Actions, which is invalid.

Condition implementation has not been specified for Condition \"{condition name}\"

Error

Occurs when the Implementation Class has not been provided for a Condition within an Action.

Condition implementation is missing for Condition \"{condition name}\"

Error

Occurs if the Implementation class itself is not in Studio.

Model Collection is not associated with any Actions. A model collection must be associated with at least one Action.

Error

Occurs when the Model Collection is not associated to at least one Action.

Resolution Action has not specified a Resolution Action Label.

Error

Occurs when the Resolution Action does not have a Resolution Action Label, which is used as the resolution string in the UI for resolving discrepancies.

Error Retrieving Cartridge Model

Error

Occurs when a given Action's Processors do not have a Provider.

Action "{action name}" is not a valid Action and cannot be added.

Error

Occurs when selecting an invalid Action when adding Processors to an Action.

Action "{action name}" does not contain any Processors. Actions must contain at least one processor to be eligible for inclusion in another Action.

Error

Occurs when importing an Action, which contains no Processors.

The are no output parameters on any of the Processors that are of a type that can be iterated over.

Error

Occurs when adding a For Each to an Action, which has Processors that do not have an output parameter that allows iteration.

The order of Processors from Imported Actions can not be changed.

Error

Occurs when the order of Processors from Imported Actions is changed.

Processor "{processor name}" uses parameter "{parameter name}" and Processor "{processor name}" outputs this parameter, continuing may make the Action invalid. Do you want to continue?

Confirmation

Occurs when changing the order (Moving Down) of Processors within an Action resulting in invalidating the flow of parameters thus making the Action as a whole invalid.

Processor "{processor name}" has a condition that uses parameter "{parameter name}" and Processor "{processor name}" outputs this parameter, continuing may make the Action invalid. Do you want to continue?

Confirmation

Occurs when changing the order of Processors (Moving Down) within an Action resulting in invalidating one or more conditions.

Processor "{processor name}" outputs parameter "{parameter name}" and Processor "{processor name}" uses this parameter, continuing may make the Action invalid. Do you want to continue?

Confirmation

Occurs when changing the order (Moving Up) of Processors within an Action resulting in invalidating the flow of parameters thus making the Action as a whole invalid.

Processor "{processor name}" outputs parameter "{parameter name}" and Processor "{processor name}" has a condition that uses this parameter, continuing may make the Action invalid. Do you want to continue?

Confirmation

Occurs when changing the order of Processors (Moving Up) within an Action resulting in invalidating one or more conditions.

Action should not be null

Error

Occurs when adding or removing elements (Processors, For Each blocks, and so on) from an Action, which is null.

The condition could not be added because the following {action name} are read only

Error

Occurs when attempting to add a Condition to an Action, which is read only.

The condition could not be removed because the following {action name} are read only

Error

Occurs when attempting to remove a Condition from an Action, which is read only.

The condition interface {condition interface name} has not been generated. It is recommended to save and build the Action before creating the implementation so that the interface is generated. Continue creating the implementation class anyway?

Confirmation

Occurs if the Condition's interface has not been generated before the implementation class being generated.

Condition ''{condition name}'' has relations. Are you sure you want to delete it?

Warning

Occurs when the Condition to be deleted has relationship to a Processor.

A Condition called {condition name} already exists on this plug-in, specify a different name.

Error

Occurs when attempting to create a Condition with a name that already exists within the Action.

The Condition Name must have a length greater than 0 but not exceeding 50 characters

Error

Occurs when the length of the target Condition name is not within the valid range of 1 – 50 characters.

This Output Parameter type is used by a for each, therefore the parameter type must be an iterable type.

Error

Occurs when the Output Parameter type used as an input to a For Each is not iterable.

Processor "{processor name}" is not writable, so references to this output parameter is not updated.

Error

Occurs when trying to modify a Processor, which is read only.

Input Parameters are referencing this Output Parameter. Changing the name or type may generate compile errors. Do you want to continue?

Warning

Occurs when changing the name of an Output Parameter, which has referencing Input Parameters on Processors whose java classes are already generated.

Input Parameters are referencing this Output Parameter. Removing it generates compile and validation errors. Do you want to continue?

Warning

Occurs when removing an Output Parameter, which has referencing Input Parameters on Processors whose java classes are already generated.

There are no output parameters available from preceding Processors to be selected

Informational

Occurs when selecting a Processor's Input Parameters and no preceding Processor has an Output Parameters.

No uses of output parameter "{parameter name}" were found.

Informational

Occurs when viewing the Usage of an Output Parameter, which is not used as an Input Parameter.

The provided name already exists. Enter a different name.

Error

Occurs when adding a Condition using a name that already exists.

The Name cannot exceed 50 characters

Error

Occurs when adding a Condition with a name that exceeds 50 characters.

The name must start with a letter.

Error

Occurs when creating an Element (for example, Processor, AddressHandler) with an invalid name (i.e. starts with a digit) using the Studio Model Entity Wizard.

Action names must start with a letter.

Error

Occurs when creating an Action with an invalid name.

A value for implementation prefix is required when the use default option is not selected.

Error

Occurs when creating an Action and no implementation prefix is specified when the default option is not selected.

The implementation prefix must begin with a letter.

Error

Occurs when specifying an Action's or Processor's Implementation Prefix starting with a character other than a letter.

Error trying to lookup interface in project.

Error

Occurs when Studio is attempting to create a class that implements an interface, which does not exist in the Project.

An error occurred attempting to create a Java class. Details: {error details}

Error

Occurs when Studio is unable to create a Java class likely due to a Java Model problem or permissions.

The generated interface {interface name} could not be found in your project. It is recommended to save and build before creating the implementation so that the interface is available. Continue creating the implementation class anyway?

Warning

Occurs when generating the implementation before the interface is available. For example, when creating a new Processor, it is recommended to Save and Build before creating the implementation class.

The required interface, {interface name}, could not be found. Please clean and build the project.

Error

Occurs when selecting the implementation before the interface is available. For example, when creating a new Processor, it is recommended to Save and Build before selecting the implementation class.

The package rename cannot be performed because the following entities are not writable:

Error

Occurs when modified the Default Package property on the Network Integrity Cartridge Properties tab and the underlying classes are read only.

Project name should not contain spaces.

Error

Occurs when attempting to create a Integrity Project with a name that contains spaces.

A Default Cartridge Package is required

Error

Occurs if there is no Default Cartridge Package specified under the Oracle Design Studio -> Network Integrity section in the Design Studio Preferences located under Window -> Preferences.

Spaces are not allowed in the package name

Error

Occurs if the Default Cartridge Package value contains spaces.

This removes all generated UI hints artifacts. Do you wish to continue?

Confirmation

Occurs when clicking the Clean UI Hints button located on the UI Hints tab of the Network Integrity Cartridge element.

The UI Hints could not be cleaned, please ensure the mds.mar file is not read only

Error

Occurs when attempting to clean the UI Hints while the mds.mar file is read only. The mds.mar is located in the cartridge lib directory.

Spaces are not allowed in the package name

Error

Occurs when attempting to rename the Default Package property on the Properties tab of the Network Integrity Cartridge element.

Please fix fields with errors.

Error

Occurs when creating an Output Parameter with an invalid Type.

The first character in a parameter name should be lowercase

Warning

Occurs when adding Output Parameters to a Processor and the Parameter Name begins with an invalid character (i.e. uppercase).

A {field name} value must be entered.

Error

Occurs when adding Output Parameters, Property Groups and Properties to a Processor and no Name value is specified.

Parameter {parameter name} could not be added because a parameter with the same name already exists. Remove the parameter with the same name and retry the operation.

Error

Occurs when adding an Output or Input Parameter using a name that already exists in the Parameter list. Names must be unique in the parameter list since the Name is used to generate the getter methods.

The name "{parameter name}" already exists as a parameter, enter a different name

Error

Occurs when adding an Output Parameter using a name that already exists.

The name cannot contain spaces

Error

Occurs when adding an Output Parameter or Property Group to a Processor and the name contains spaces.

The name cannot start with a number

Error

Occurs when adding an Output Parameter or Property Group to a Processor and the name starts with a number.

Parameter Type "{parameter type}" may produce warnings in generated code. Do you want to continue?

Confirmation

Occurs if the Parameter Type of an Output or Input Parameter may cause compile warnings.

The Parameter Type "{parameter type}" produces the following warning in generated code. Do you want to continue?

Confirmation

Occurs if the generated code contains warnings based on the Parameter Type of an Output or Input Parameter.

The name must be a valid java identifier that does not contain special characters

Error

Occurs when adding an Output Parameter or Property Group to a Processor and the name contains a special character (for example, %).

The name "{parameter name}" is a reserved word in Java, enter a different name

Error

Occurs when adding an Output Parameter or Property Group to a Processor and the name is equivalent to a reserved word in Java and therefore would cause compiling errors.

Type {parameter type} could not be found in the project

Error

Occurs if the Parameter Type of an Output or Input Parameter could not be found in the Integrity Project.

A property group with the name "{property group name}" already exists on this input

Error

Occurs when adding a Property Group using a name that already exists.

A Property with the name "{property name}" and value "{property value}" already exists, please choose a different name/value combination

Error

Occurs when adding or modifying a Property using a name and value that already exists.

One or more errors exist with the fields

Error

Occurs when creating a Property Group with an invalid Name.

A Property Group with the name "{property group name}" already exists, please choose a different name

Error

Occurs when modifying a Property Group changing its name to a name that already exists.

One or more errors exist with the fields

Error

Indicates a problem with Result Groups or Result Source.

A {field name} value must be entered.

Error

Occurs when creating a Result Category or Condition with no name.

The Result Category Name must have a length greater than 0 but not exceeding 255 characters

Error

Occurs when modifying a Result Category changing its name to have a length of 0 or greater than 255 characters.

Data Dictionary named "{data dictionary name}" could not be found.

Error

Occurs when the Data Dictionary elements of a Model Collection cannot be found.

The MIB File "{mib filename}" could not be loaded because of the following error:\n\n {error details}

Error

Occurs when a file other than a MIB File is selected when clicking the Load MIB button within an SNMP Processor.

A valid MIB Module called "{mib module name}" could not be found in MIB File: "{mib filename}"

Error

Occurs when the target MIB File attempting to be loaded by a SNMP Processor does not contain any MIB Modules.

The MIB directory "{mib directory}" either does not exist or is not accessible. Either create this directory or change the configured MIB Directory in the Network Integrity Preferences Page (Preferences then Oracle Design Studio then Network Integrity)

Error

Occurs when the configured MIB Directory as specified in the Network Integrity Preferences Page is not accessible.

The following error occurred loading MIB "{mib filename}":\n\n {error details}

Error

Occurs when the target MIB File is corrupt.

Selected node: {oid}, is not readable, only readable nodes are supported.

Error

Occurs when attempting to load an OID, which is not readable.

Selected node: {oid}, is not supported (only scalar and table column are supported).

Error

Occurs when attempting to load an OID, which is not scalar or a table column.


Design Studio Logging

When developing cartridges within Design Studio for Network Integrity it is likely that the developer requires logging for traceability during normal cartridge operation and for debugging. This section outlines how to introduce logging into the developer's implementation. This section addresses logging that is visible inside the WebLogic log files. It does not discuss introducing Design Studio logging (for example, Design Studio Error Logs).

Network Integrity uses the java.util.logging package for logging messages. For an overview of the Java logging framework, visit Oracle's site on the subject at

http://download.oracle.com/javase/6/docs/api/index.html.

To create an instance of the appropriate logger add a static variable to an implementation class passing in the name of the current class. For example,

private static final Logger logger = Logger
                    .getLogger(DiscrepancyDetectorImpl.class.getName());

When the above is defined, invoke logging according to the API specification. For example,

logger.log(Level.SEVERE, "Error while detecting discrepancies.", e);

To redirect the Network Integrity logs produced by the above into a WebLogic log file use the following procedure:

  1. Insert the following 2 XML fragments into the file <DOMAIN_HOME> /config/fmwconfig/servers/<TargetServer>/logging.xml.<TargetServer>. <TargetServer> represents the name of the WebLogic Server where the Network Integrity application is running.

    1. The following fragment goes inside the <log_handlers> block and defines the log handler and log file location. If required, change the log handler; however, this value must match the value referenced in the fragment in step b. If necessary, change the location where the log file is generated.

           <log_handler name='ni-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
           <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/ni-weblogic.log'/>
           <property name='maxFileSize' value='10485760'/>
           <property name='maxLogSize' value='104857600'/>
         </log_handler>
      
    2. This fragment goes inside the <loggers> block (at the end) and defines the logger name. This name refers to the Java package of a customer's implementation code, the log level and the handler. The handler must match the value configured in step a (for example, ni-handler). If necessary, tailor the log level. Consult Table 29-2 that maps the Java log levels to the ODL log levels (for example, TRACE:32) used in the logging.xml file.

          <logger name="oracle.communications.integrity" level="TRACE:32">
            <handler name="ni-handler"/>
          </logger>
          <logger name="oracle.communications.activation" level="TRACE:32">
            <handler name="ni-handler"/>
          </logger>
          <logger name="oracle.communications.inventory" level="TRACE:32">
            <handler name="ni-handler"/>
          </logger>
      
  2. Save the changes to the logging.xml file.

When determining what level to set in the logging.xml (step 1) use Table 29-2 to map the Java Log Levels to ODL Log Levels.

Table 29-2 Java Log Level to ODL Log Level Mapping

Java Log Level ODL Message Type:Log Level ODL Description

SEVERE.intValue()+100

INTERNAL_ERROR:1

The program has experienced an error for some internal or unexpected non-recoverable exception.

SEVERE

ERROR:1

A problem requiring attention from the system administrator has occurred.

WARNING

WARNING:1

An action occurred or a condition was discovered that should be reviewed and may require action before an error occurs.

INFO

NOTIFICATION:1

A report of a normal action or event. This could be a user operation, such as ”login completed” or an automatic operation such as a log file rotation.

CONFIG

NOTIFICATION:16

A configuration-related message or problem.

FINE

TRACE:1

A trace or debug message used for debugging or performance monitoring. Typically contains detailed event data.

FINER

TRACE:16

A fairly detailed trace or debug message.

FINEST

TRACE:32

A highly detailed trace or debug message.


For more information on ODL visit

http://download.oracle.com/docs/cd/B31017_01/web.1013/b28952/logging.htm#JIDEV400