102 NNF-00001 to NNF-04009

NNF-00001: Not a TNS address: Cause: While asking to read an address the name service returned a record which was not an address.; Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-00002: Invalid value passed to function call: Cause: An invalid value was passed to an interface function.; Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-00003: Naming adapter string does not exist: Cause: The requested name service adapter was not found in the current adapter table.; Action: Check the spelling of the adapter reqested. Verify that the adapter runs on this platform, and the adapter is compiled into the adapter table linked into the executable.

NNF-00004: Operation not supported in string: Cause: The operation requested is not supported under this adapter.; Action: Verify that the operation being performed is not under restriction, such as writing to read-only name service. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-00005: Functionality not implemented: Cause: The operation requested is not supported in this implementation.; Action: If this is retrieved from a production release, contact Worldwide Customer Support. Otherwise, check the release notes as to the restrictions in this release.

NNF-00110: no values exist: Cause: Test program help text.; Action: None

NNF-00540: Failed to insert name: string: Cause: Failed to insert name into the native service.; Action: Verify that the name is not already in the native namespace and the appropriate access permissions are set for the namespace.

NNF-01001: ds_initialize: workspace initialization failed: Cause: The DCE workspace as setup by ds_initialize() failed to initialize.; Action: Verify that conditions necessary for a successful ds_initialize() call are present on this platform (e.g is there enough memory?). Check that there is not another workspace user in this program. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-01002: DCE could not open configuration file: Cause: A DCE call returned an error that it could not access its configuration file.; Action: Check that the DCE configuration file for this platform is present, and accessable. On Unix this file is dce_cf.db. Check if a simple call to dce_cf_get_cell_name() succeeds.

NNF-01003: DCE could not find cell name: Cause: A DCE call returned an error that it could not find the cell name in its configuration file.; Action: Check that this machine has been configured for a DCE cell. Chcek that the DCE configuration file is not corrupted. On Unix, this file is dce_cf.db. Check if a simple call to dce_cf_get_cell_name() succeeds.

NNF-01004: DCE returned unspecified error string: Cause: A DCE call returned an status that was not in this implementation's list of possible status values for this DCE call.; Action: Verify that this platform's DCE release is not beyond those supported by this Oracle application. If the error persists, contact Worldwide Customer Support.

NNF-01005: Internal XOM class violation: Cause: A DCE XOM call returned statuses inconsistent with the class definitions in the DCE documentation.; Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-01006: Attribute string not available: Cause: A insertion call attempted to use an attribute which did not have a translation to a DCE attribute.; Action: Use another attribute, or insert the translation into DCE.

NNF-01007: DCE long strings are not supported: Cause: A query returned a object which has a XOM OM_S_LONG_STRING. The current implementation does not support such objects.; Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-01008: XDS attribute syntax string incorrect for Oracle Names syntax string: Cause: The syntax as specified in the XDS object is different than that which is expected for the given Oracle names syntax.; Action: For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

NNF-02001: NIS client error string: string: Cause: A call to an NIS (YP) function failed. This message contains the text of the NIS error code returned.; Action: Should only be visible when returned as part of another error. If the error persists, contact Worldwide Customer Support.

NNF-02002: NIS value does not conform to adapter schema: string: Cause: The values in the maps used by the NIS adapter must conform to a specific set of internal formatting rules. This value returned did not conform to those rules.; Action: Should not be visible, unless you are attempting to create your own maps. If the error persists, contact Worldwide Customer Support.

NNF-02003: Unknown NIS error code: string: Cause: An error code returned by a NIS (YP) function was not in the list expected by this program.; Action: Verify that the error is generated by the YP functions on this platform. Notify Worldwide Customer Support of the error.

NNF-02004: NIS map string does not exist: Cause: The requested attribute does not exist.; Action: For an unused attribute, no action is required, as this is the expected error. Otherwise, add the attribute and reload the NIS (YP) maps.

NNF-02005: NIS key string does not exist in map string: Cause: The requested name was not found.; Action: For an unused name, no action is required, as this is the expected error. Otherwise, add the name to the map and reload the NIS (YP) maps.

NNF-03002: Unknown BIND error code: string: Cause: The return code in the BIND (DNS) query response did not conform to those values listed in RFC 1035.; Action: Verify that the error is generated by the BIND functions on this platform. Notify Worldwide Customer Support of the error.

NNF-03003: Format error parsing server response: Cause: The query response packet returned from the BIND (DNS) API did not conform to the format listed in RFC 1035.; Action: Verify that the error is generated by the BIND functions on this platform. Notify Worldwide Customer Support of the error.

NNF-03004: DNS Class mismatch (string): Cause: The query response packet returned a class different from the ones expected by the interface.; Action: Verify that the error is generated by the BIND functions on this platform. Notify Worldwide Customer Support of the error.

NNF-04000: File succesfully converted: Cause: The requested conversion is performed.; Action: Normal condition, no action necessary.

NNF-04001: Error converting input file: Cause: The input file contains lines that cannot be converted by the conversion program.; Action: Check that the syntax of the input file is correct.

NNF-04002: Outputfile already exists: Cause: An old output file already exists in the current directory; Action: Remove the existing file, and restart the conversion tool

NNF-04003: Entry in inputfile is too long: Cause: The makedbm program, limits entries in mapfiles to 1017 characters. Therefor, the conversion tool will not process TNS addresses which are longer than 1017 characters.; Action: Shorten the offending entry.

NNF-04004: Invalid string in inputfile: Cause: the input file contains invalid lines.; Action: Check that the syntax of the input file is correct.

NNF-04005: Cannot open inputfile: Cause: The specified input file could not be found.; Action: restart the conversion tool with the correct input file.

NNF-04006: Could not create outputfile: Cause: An output file could not be created in the current working directory; Action: Change the permissions of the current directory and restart the conversion tool.

NNF-04007: Error reading input file: Cause: A problem while reading the input file. This could be caused by an unexpected end of file in the input file.; Action: Check that the file is intact and that the syntax of the input file is correct.

NNF-04008: Error writing outputfile: Cause: An error occured while writing to the output file.; Action: Check available disk space. If the error persists, contact Worldwide Customer Support.

NNF-04009: Usage: tns2nis <filename>: Cause: The conversion tool was not invoked properly. The filename should either be tnsnames.ora or native.ora; Action: Restart the conversion tool with the proper parameter.