Enum Class OMRSErrorCode

java.lang.Object
java.lang.Enum<OMRSErrorCode>
org.odpi.openmetadata.repositoryservices.ffdc.OMRSErrorCode
All Implemented Interfaces:
Serializable, Comparable<OMRSErrorCode>, Constable, ExceptionMessageSet

public enum OMRSErrorCode extends Enum<OMRSErrorCode> implements ExceptionMessageSet
The OMRSErrorCode is used to define first failure data capture (FFDC) for errors that occur within the OMRS It is used in conjunction with all OMRS Exceptions, both Checked and Runtime (unchecked). The 5 fields in the enum are:
  • HTTP Error Code for translating between REST and JAVA. Typically the numbers used are:
    • 500: internal error
    • 501: not implemented
    • 503: Service not available
    • 400: invalid parameters
    • 401: unauthorized
    • 404: not found
    • 405: method not allowed
    • 409: data conflict errors, for example an item is already defined
  • Error Message Id: to uniquely identify the message
  • Error Message Text: includes placeholder to allow additional values to be captured
  • SystemAction: describes the result of the error
  • UserAction: describes how a user should correct the error
  • Nested Class Summary

    Nested classes/interfaces inherited from class java.lang.Enum

    Enum.EnumDesc<E extends Enum<E>>
  • Enum Constant Summary

    Enum Constants
    Enum Constant
    Description
    OMRS-AUDIT-LOG-400-009 - The archive manager is not active in server {0}
    OMRS-OPEN-METADATA-ARCHIVE-500-001 - The archive builder failed to initialize
    OMRS-PROPERTIES-400-004 - {0} is unable to add a new element to location {1} of an array of size {2} value
    OMRS-REPOSITORY-400-004 - Unable to add the AttributeTypeDef {0} (guid = {1}) since it is already defined in the open metadata repository {2}
    OMRS-REPOSITORY-404-008 - The AttributeTypeDef {0} (guid {1}) passed on a {2} request to open metadata repository {3} is not known to this repository
    OMRS-REPOSITORY-400-002 - Unable to delete the AttributeTypeDef {0} (guid = {1}) since it is still in use in the open metadata repository {2}
    OMRS-REPOSITORY-404-010 - The TypeDef unique name {0} passed on a {1} request to open metadata repository {2} is not known to the repository
    OMRS-REPOSITORY-404-006 - The AttributeTypeDef {0} (guid = {1}) passed on the {2} call is not known to the open metadata repository {3}
    OMRS-AUDIT-LOG-400-008 - The Audit log destination {0} is not able to convert an audit log record to JSON format
    OMRS-AUDIT-LOG-400-007 - The Audit Log destination {0} is not available.
    OMRS-PROPERTIES-400-005 - AttributeDefs may only be of primitive, collection or enum type.
    OMRS-CONTENT-MANAGER-500-004 - Source {0} has requested type {1} with an incompatible category of {2} from repository content manager
    OMRS-PROPERTIES-400-007 - Data type {0} is not supported by method {1}
    OMRS-REPOSITORY-400-058 - An instance status of {0} has been passed as the {1} parameter on a {2} request to open metadata repository {3} however this status is not valid for an instance of type {4}
    OMRS-REPOSITORY-400-035 - An instance status of {0} has been passed as the {1} parameter on a {2} request to open metadata repository {3} but this status is not valid for an instance of type {4}
    OMRS-METADATA-COLLECTION-500-007 - Open metadata repository {0} has used an invalid paging parameter during the {1} operation
    OMRS-METADATA-COLLECTION-500-008 - Open metadata repository {0} has used an invalid sequencing parameter during the {1} operation
    OMRS-LOCAL-REPOSITORY-503-004 - The connection to the local open metadata repository server has not been configured correctly
    OMRS-REPOSITORY-400-040 - Unexpected exception {0} occurred when comparing properties against a search string of {1} during the {2} operation from {3}.
    OMRS-REPOSITORY-400-028 - A property called {0} has been proposed for a new metadata instance of category {1} and type {2}; it is not supported for this type in open metadata repository {3}
    OMRS-REPOSITORY-400-030 - A property called {0} of type {1} has been proposed for a new metadata instance of category {2} and type {3}; this property should be of type {4} in open metadata repository {5}
    OMRS-CONNECTOR-400-005 - The connector to the local repository failed with a {0} exception and the following error message: {1}
    OMRS-CONTENT-MANAGER-500-001 - The repository content manager method {0} has detected an unknown TypeDef {1} from {2} on behalf of method {3}
    OMRS-CONTENT-MANAGER-500-002 - The repository content manager has detected an invalid attribute name in a TypeDef from {0}
    OMRS-REPOSITORY-400-034 - A invalid TypeDef unique identifier (guid) has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-039 - Incompatible TypeDef unique identifiers (name={0}, guid{1}) have been passed on a {2} request for instance {3} to open metadata repository {4}
    OMRS-ARCHIVE-BUILDER-400-012 - Type name {0} is invalid because it contains a blank character
    OMRS-AUDIT-LOG-400-006 - The Audit Log destination {0} is not able to support queries
    OMRS-REST-API-503-006 - A client-side exception was received from API call {0} to repository {1}.
    OMRS-METADATA-HIGHWAY-404-002 - The local server is unable to disconnect from an open metadata repository cohort {0}
    OMRS-REPOSITORY-CONNECTOR-404-002 - The Open Metadata Repository Servers in the cohort are not available
    OMRS-METADATA-HIGHWAY-404-004 - The local server is unable to initiate a connection to the cohort {0} when starting up
    OMRS-ENTERPRISE-REPOSITORY-400-001 - Conflicting TypeDefs have been detected
    OMRS-LOCAL-REPOSITORY-503-006 - An OMRS repository connector {0} has passed an invalid parameter to the repository content manager {1} operation as part of the {2} request
    OMRS-ARCHIVE-BUILDER-400-011 - Duplicate attribute name {0} is defined in ClassificationDef {1}
    OMRS-METADATA-HIGHWAY-404-003 - There are more than one cohort configurations with the same name of {0}
    OMRS-ARCHIVE-BUILDER-400-007 - RelationshipEndDef1 type {0} and EndDef1 name {1} in RelationshipDef {2} are incorrect, because another entity or relationship endDef is already using this attribute name
    OMRS-ARCHIVE-BUILDER-400-008 - RelationshipEndDef2 type {0} and EndDef2 name {1} in RelationshipDef {2} are incorrect, because another entity or relationship endDef is already using this attribute name
    OMRS-ARCHIVE-BUILDER-400-010 - Duplicate attribute name {0} is defined in EntityDef {1}
    OMRS-ARCHIVE-BUILDER-400-004 - The guid {0} has been used twice to an open metadata archive.
    OMRS-ARCHIVE-BUILDER-400-002 - The {0} instance {1} has been added twice to an open metadata archive.
    OMRS-ARCHIVE-BUILDER-400-009 - Duplicate attribute name {0} is defined in RelationshipDef {1}
    OMRS-ARCHIVE-BUILDER-400-001 - The same type {0} of category {1} has been added twice to an open metadata archive.
    OMRS-ARCHIVE-BUILDER-400-003 - The same type name {0} has been added twice to an open metadata archive.
    OMRS-ENTERPRISE-REPOSITORY-503-002 - The enterprise repository services are disconnected from the open metadata repositories
    OMRS-ENTERPRISE-REPOSITORY-CONNECTOR-405-001 - The requested method {0} is not supported by the EnterpriseOMRSRepositoryConnector
    OMRS-REPOSITORY-400-081 - A {0} request has been made to repository {1} to add a classification {2} to entity {3} when this entity is already classified
    OMRS-LOCAL-REPOSITORY-503-009 - The local OMRS repository connector {0} has been asked to update entity {1} but it is not the owner.
    OMRS-REPOSITORY-400-048 - A {0} request has been made to repository {1} to remove a non-existent classification {2} from entity {3}
    OMRS-REPOSITORY-404-002 - The entity identified with guid {0} passed on the {1} call is not known to the open metadata repository {2}
    OMRS-LOCAL-REPOSITORY-503-007 - The local OMRS repository connector {0} hosts the home metadata collection for entity {1} but only has an entity proxy stored.
    OMRS-REPOSITORY-400-051 - A request for entity {0} has been passed to repository {1} as the {2} parameter of the {3} operation but only an entity proxy has been found
    OMRS-REPOSITORY-404-013 - The {0} entity identified with guid {1} passed on the {2} call is soft-deleted in the open metadata repository {3}
    OMRS-REPOSITORY-HELPER-503-001 - A caller {0} has passed an invalid parameter to the repository helper {1} operation as part of the {2} request
    OMRS-REPOSITORY-HELPER-503-002 - A caller {0} has passed an invalid parameter to the repository helper {1} operation as part of the {2} request resulting in an unexpected exception {3} with message {4}
    OMRS-REPOSITORY-400-063 - Method {0} is unable to request a refresh of instance {1} as it is a local member of metadata collection {2} in repository {3}
    OMRS-METADATA-COLLECTION-500-014 - During the {0} operation, open metadata repository {1} retrieved an instance (guid={2}) from its metadata store that has an inactive type called {3} (type guid = {4})
    OMRS-REPOSITORY-400-068 - Method {0} has detected that a TypeDef patch from {1} is for a future level from the active TypeDef.
    OMRS-REPOSITORY-400-070 - Method {0} has detected that a TypeDef patch from {1} attempts to change the type of property {2} from {3} to {4}.
    OMRS-REPOSITORY-400-045 - A {0} request has been made to repository {1} for an instance {2} that is already deleted
    OMRS-METADATA-COLLECTION-500-017 - The home metadata collection identifier {0} found by method {1} for instance with GUID {2} is the metadata collection identifier {3} for the local metadata repository {4}
    OMRS-METADATA-COLLECTION-500-016 - The home metadata collection identifier {0} found by method {1} for instance with GUID {2} is not the metadata collection identifier {3} for the local metadata repository {4}
    OMRS-REPOSITORY-400-046 - A {0} request has been made to repository {1} for an instance {2} that is not deleted
    OMRS-REPOSITORY-400-018 - An invalid AttributeTypeDef {0} (guid={1}) has been passed as the {2} parameter on a {3} request to open metadata repository {4}.
    OMRS-REPOSITORY-400-006 - Open metadata repository {0} is unable to assign a classification of type {1} to an entity of type {2} as the classification type is not valid for this type of entity
    OMRS-REPOSITORY-400-075 - An invalid list of classification-based search conditions was provided: name of the classification is mandatory
    OMRS-REPOSITORY-CONNECTOR-404-003 - The open metadata repository servers in the cohort are not configured correctly
    OMRS-REPOSITORY-400-052 - The entity {0} retrieved from repository {1} during the {2} operation has invalid contents: {3}
    OMRS-REPOSITORY-400-061 - An invalid instance has been detected by repository helper method {0}.
    OMRS-REPOSITORY-400-073 - An invalid instance was found in a batch of reference instances send by a remote member of the cohort.
    OMRS-REPOSITORY-400-077 - An invalid string was provided for the value of a LIKE operator
    OMRS-REPOSITORY-400-076 - An invalid list was provided for the value of an IN operator
    OMRS-COHORT-REGISTRY-400-002 - The Open Metadata Repository Cohort {0} is not available to server {1} because the local metadata collection id has been changed from {2} to {3} since this server registered with the cohort
    OMRS-REPOSITORY-400-078 - An invalid string was provided for the value of the {0} operator
    OMRS-CONNECTOR-400-004 - The connection {0} passed to the EnterpriseOMRSRepositoryConnector is invalid
    OMRS-REPOSITORY-400-067 - Method {0} has detected invalid version values in TypeDef patch from {1}.
    OMRS-METADATA-COLLECTION-500-003 - There is a problem in the definition of primitive type {0}
    OMRS-METADATA-COLLECTION-500-001 - The Java class {0} for PrimitiveDefCategory {1} is not known
    OMRS-METADATA-COLLECTION-500-015 - The value supplied for an attribute of PrimitiveDefCategory {0} is expected as Java class {1} but was supplied as Java class {2}
    OMRS-METADATA-COLLECTION-500-002 - The primitive value should be stored in Java class {0} rather than {1} since it is of PrimitiveDefCategory {2}
    OMRS-REPOSITORY-400-074 - An invalid list of property-based search conditions was provided: nestedConditions is mutually exclusive with property, operator, value.
    OMRS-REPOSITORY-400-047 - A {0} request has been made to repository {1} for a relationship that has one or more ends of the wrong or invalid type.
    OMRS-REPOSITORY-400-053 - The relationship {0} retrieved from repository {1} during the {2} operation has invalid contents: {3}
    OMRS-PROPERTIES-400-006 - A {0} exception was returned when matching {2} against {1} in method {4}.
    OMRS-REPOSITORY-400-083 - The OMRS repository connector operation {0} does not allow a time range from {1} to {2}
    OMRS-REPOSITORY-400-017 - An invalid TypeDef {0} (guid={1}) has been passed as the {2} parameter on a {3} request to open metadata repository {4}.
    OMRS-REPOSITORY-400-044 - An entity proxy has been passed to repository {0} as the {1} parameter of the {2} operation which has the local repository as its home
    OMRS-LOCAL-REPOSITORY-503-003 - The connection to the local open metadata repository server is not configured correctly
    OMRS-LOCAL-REPOSITORY-500-002 - The local repository for server {0} failed to initialize and returned a {1} exception with message {2}
    OMRS-REST-REPOSITORY-CONNECTOR-500-001 - A remote open metadata repository {0} returned a metadata collection identifier of {1} on its REST API after it registered with the cohort using a metadata collection identifier of {2}
    OMRS-METADATA-HIGHWAY-404-00 - The local server's metadata highway communication components are failing to initialize
    OMRS-METADATA-COLLECTION-501-001 - OMRSMetadataInstanceStore method {0} for OMRS Connector {1} to repository type {2} is not implemented
    OMRS-ARCHIVE-BUILDER-400-006 - A request for a type from category {0} passed a null name
    OMRS-ARCHIVE-BUILDER-400-005 - The type {0} of category {1} is not found in an open metadata archive
    OMRS-METADATA-COLLECTION-409-001 - Multiple instances of type {0} have been returned to {2} of service {1} when there should be one at most.
    OMRS-METADATA-COLLECTION-409-002 - Multiple instances of type {0} have been returned to {2} of service {1} when there should be a maximum of one.
    OMRS-REPOSITORY-400-050 - A negative pageSize of {0} has been passed on the {0} parameter of a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-016 - A null AttributeTypeDef has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-010 - A null AttributeTypeDef category has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-008 - A null AttributeTypeDef name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-071 - The Open Metadata Repository Services (OMRS) has been called to initialize with no audit log destinations defined for server {0}
    OMRS-AUDIT-LOG-400-001 - There are no Audit Log destinations configured for server {0}
    OMRS-REST-API-503-002 - There is no enterprise repository to support REST API call {0}
    OMRS-TOPIC-CONNECTOR-400-002 - The connector {0} has been configured without an embedded event bus connector
    OMRS-REPOSITORY-400-012 - Null values for all the parameters describing an external id for a standard has been passed on a {0} request to open metadata repository {1}
    OMRS-REPOSITORY-400-014 - A null unique identifier (guid) has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-082 - The OMRS repository connector operation {0} from the OMRS Enterprise Repository Services can not locate the home repository connector for classification {1} located in metadata collection {2}
    OMRS-REPOSITORY-400-056 - The OMRS repository connector operation {0} from the OMRS Enterprise Repository Services can not locate the home repository connector for instance {1} located in metadata collection {2}
    OMRS-REST-API-503-001 - There is no local repository to support REST API call {0}
    OMRS-REPOSITORY-400-011 - A null list of match criteria properties has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REST-API-503-003 - There is no metadata highway to support REST API call {0}
    OMRS-PROPERTIES-400-001 - No more elements in {0} iterator
    OMRS-REPOSITORY-400-037 - No properties have been passed on the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-029 - Properties have been proposed for a new metadata instance of category {0} and type {1}; properties not supported for this type in open metadata repository {2}
    OMRS-ENTERPRISE-REPOSITORY-503-001 - There are no open metadata repositories available for access service {0}
    OMRS-METADATA-COLLECTION-500-009 - Unable to complete operation {0} to open metadata repository {1} because the repository connector is null
    OMRS-METADATA-COLLECTION-500-011 - Unable to complete operation {0} to open metadata repository {1} as the repository connector is null
    OMRS-METADATA-COLLECTION-500-010 - Unable to complete operation {0} to open metadata repository {1} because the repository validator is null
    OMRS-REST-API-503-005 - Unable to create REST Client for repository {0}.
    OMRS-REPOSITORY-400-013 - A null search criteria has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-015 - A null TypeDef has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-009 - A null TypeDef category has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-007 - A null TypeDef name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-ENTERPRISE-REPOSITORY-400-002 - No TypeDefs have been defined in any of the connected repositories
    OMRS-LOCAL-REPOSITORY-400-002 - The local repository is not able to re-home the instance {0} of type {1} ({2}) because it is not managing the repository with the requested home metadata collection of {3}.
    OMRS-ARCHIVE-MANAGER-400-001 - An open metadata archive configured for server {0} is not accessible
    OMRS-REPOSITORY-400-057 - The OMRS repository connector operation {0} does not allow a null value for {1} from {2}
    OMRS-REPOSITORY-400-020 - A null AttributeTypeDef has been passed as the {0} parameter on a {1} request to the open metadata repository {2}
    OMRS-REPOSITORY-400-024 - A null unique identifier (guid) for a AttributeTypeDef object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-072 - The Open Metadata Repository Services (OMRS) has been called to initialize its subsystems for server {0} before the audit log is initialized
    OMRS-AUDIT-LOG-400-002 - An Audit Log destination for server {0} is not correctly configured
    OMRS-LOCAL-REPOSITORY-503-008 - An OMRS repository connector or access server {0} has passed a null classification to the repository helper {1} operation as part of the {2} request
    OMRS-REPOSITORY-400-026 - A null classification name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-PROPERTIES-400-002 - No name provided for entity classification
    OMRS-ENTERPRISE-REPOSITORY-503-003 - The enterprise repository services has detected a repository connector from cohort {0} for metadata collection identifier {1} that has a null metadata collection API object
    OMRS-COHORT-MANAGER-500-001 - OMRSCohortManager has been initialized with a null cohort name
    OMRS-OPERATIONAL-SERVICES-500-001 - No configuration has been passed to the Open Metadata Repository Services (OMRS) on initialization os server {0}
    OMRS-CONNECTOR-400-002 - The connection passed to OMASConnectedAssetProperties for connector {0} is null
    OMRS-TOPIC-CONNECTOR-500-006 - The requested connector for connection named {0} has not been created.
    OMRS-LOCAL-REPOSITORY-503-001 - A null repository content manager has been passed to one of the local repository's components on method {0}
    OMRS-ENTERPRISE-REPOSITORY-500-001 - The enterprise repository services has detected a repository connector with a null metadata collection
    OMRS-REPOSITORY-400-043 - A null entity proxy has been passed to repository {0} as the {1} parameter of the {2} operation
    OMRS-LOCAL-REPOSITORY-400-001 - The repository event mapper configured for the local repository for server {0} is not accessible
    OMRS-EVENT-MANAGEMENT-500-001 - A null exchange rule has been passed to one of the event management components on method {0}
    OMRS-METADATA-COLLECTION-500-004 - Null home metadata collection identifier found by method {1} in property {0} from open metadata repository {3}
    OMRS-LOCAL-REPOSITORY-503-011 - The local OMRS repository connector {0} requested an instance {1} from the real metadata collection but a null was returned.
    OMRS-REPOSITORY-400-054 - The element {0} retrieved from repository {1} during the {2} operation has a null metadata collection id in its header: {3}
    OMRS-REPOSITORY-400-036 - A null instance status has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-METADATA-COLLECTION-500-013 - During the {0} operation, open metadata repository {1} retrieved an instance from its metadata store that has a null type
    The local repository services have been initialized with a null real metadata collection.
    OMRS-AUDIT-LOG-400-003 - A null log record has been passed by the audit log to the audit log destination {0}
    OMRS-AUDIT-LOG-400-004 - A log record with a null originator has been passed by the audit log to the audit log destination {0}
    OMRS-AUDIT-LOG-400-005 - A log record with a null reporting component has been passed by the audit log to the audit log destination {0}
    OMRS-REPOSITORY-400-069 - Method {0} has detected that a TypeDef patch from {1} has the mandatory field {2} set to null which is invalid.
    OMRS-REPOSITORY-400-025 - Local metadata repository has not initialized correctly because it was unable to create its metadata collection
    OMRS-METADATA-COLLECTION-500-006 - The open metadata repository connector {0} has been initialized with a null metadata collection identifier
    OMRS-METADATA-COLLECTION-500-018 - The open metadata repository connector {0} has returned a null metadata collection identifier
    OMRS-CONNECTOR-400-003 - The connection passed to the EnterpriseOMRSRepositoryConnector is null
    OMRS-TOPIC-CONNECTOR-500-001 - A null topic listener has been specified to the open metadata topic connector {0}
    OMRS-METADATA-TOPIC-CONNECTOR-500-001 - A null topic listener has been passed to the {0} open metadata topic connector {1}
    OMRS-EVENT-MANAGEMENT-500-004 - A null event has been passed to one of the event management components
    OMRS-REPOSITORY-400-060 - The repository helper method {0} has been called with a null parameter
    OMRS-PROPERTIES-400-003 - Null property name passed to properties object
    OMRS-REPOSITORY-400-031 - A null property name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-033 - A null property type has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-032 - A null property value has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-041 - A null reference instance has been passed to repository {0} during the {1} in the {2} parameter
    OMRS-COHORT-REGISTRY-404-001 - The Open Metadata Repository Cohort Registry Store for cohort {0} is not available
    OMRS-REST-REPOSITORY-CONNECTOR-500-002 - A remote open metadata repository {0} returned a null metadata collection identifier on its REST API.
    OMRS-EVENT-MANAGEMENT-500-003 - A null repository helper has been passed to one of the event management components
    OMRS-EVENT-MANAGEMENT-500-002 - A null repository validator has been passed to one of the event management components
    OMRS-REST-API-503-004 - A null response was received from REST API call {0} to repository {1}
    OMRS-LOCAL-REPOSITORY-503-002 - A null repository content manager has been specified to one of the local repository's components on method {0}
    OMRS-TOPIC-CONNECTOR-400-001 - Unable to send or receive events for source {0} because the connector to the OMRS Topic failed to initialize
    OMRS-REPOSITORY-400-019 - A null TypeDef has been passed as the {0} parameter on a {1} request to the open metadata repository {2}
    OMRS-CONTENT-MANAGER-500-003 - The repository content manager has detected a null attribute in a TypeDef from {0}
    OMRS-REPOSITORY-400-021 - A null TypeDefGalleryResponse object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-022 - A null unique identifier (guid) for a TypeDef object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-023 - A null unique name for a TypeDef object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REPOSITORY-400-049 - A null TypeDef patch has been passed on the {0} operation of repository {1}
    OMRS-REPOSITORY-400-027 - A null username has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    OMRS-REST-API-400-001 - The OMRS REST API for server {0} has been called with a null username (userId)
    OMRS-TOPIC-CONNECTOR-500-002 - Connector {0} received an unexpected exception from sending event {1}.
    OMRS-TOPIC-CONNECTOR-500-003 - Connector {0} is unable to send a null event
    OMRS-TOPIC-CONNECTOR-501-001 - Connector {0} is not able to support event protocol {1}
    OMRS-LOCAL-REPOSITORY-503-010 - The local OMRS repository connector {0} has been asked to update relationship {1} but it is not the owner.
    OMRS-REPOSITORY-404-011 - The relationship identified with guid {0} passed on the {1} call is not found to the open metadata repository {2}
    OMRS-REPOSITORY-404-003 - The relationship identified with guid {0} passed on the {1} call is not known to the open metadata repository {2}
    OMRS-REPOSITORY-404-012 - The {0} relationship identified with guid {1} passed on the {2} call is soft-deleted in the open metadata repository {3}
    OMRS-REST-REPOSITORY-CONNECTOR-404-001 - A call to the {0} of the open metadata repository server {1} results in an exception {2} with message {3}
    OMRS-METADATA-COLLECTION-500-012 - Open metadata repository {0} has encountered an unexpected exception during the {1} operation.
    OMRS-REPOSITORY-404-001 - The open metadata repository connector for server {0} is not active and is unable to service the {1} request
    OMRS-REPOSITORY-400-038 - A future time of {0} has been passed on the {0} parameter of a {1} request to open metadata repository {2}
    OMRS-CONNECTOR-400-001 - The Open Metadata Repository Server URL {0} is not in a recognized format
    OMRS-REST-CONNECTOR-400-001 - The connection passed in the cohort registration event does not contain the root URL for calling the server's REST API
    OMRS-TOPIC-CONNECTOR-404-001 - The OMRS Topic Connector is not available
    OMRS-METADATA-COLLECTION-501-002 - Repository {0} is not able to support the {1} type
    OMRS-REPOSITORY-400-003 - Unable to add the TypeDef {0} (guid = {1}) since it is already defined in the open metadata repository {2}
    OMRS-REPOSITORY-404-007 - The TypeDef unique identifier {0} passed as parameter {1} on a {2} request to open metadata repository {3} is not known to this repository
    OMRS-REPOSITORY-400-001 - Unable to delete the TypeDef {0} (guid = {1}) since it is still in use in the open metadata repository {2}
    OMRS-REPOSITORY-404-009 - The TypeDef unique name {0} passed on a {1} request to open metadata repository {2} is not known to this repository
    OMRS-REPOSITORY-404-004 - The TypeDef {0} (guid = {1}) passed on the {2} parameter of the {3} operation is not known to the open metadata repository {4}
    OMRS-REPOSITORY-404-005 - The TypeDef {0} of category {1} passed by the {2} operation is not known to the open metadata repository {3}
    OMRS-REPOSITORY-400-079 - The provided subtype {0} is not a subtype of typedef {1}
    OMRS-REPOSITORY-400-062 - An unexpected {0} exception was caught by {1}; error message was {2}
    OMRS-REPOSITORY-400-055 - An unexpected {0} exception was received from a repository connector during the {1} operation which had message: {2}
    OMRS-REPOSITORY-400-005 - Classification {0} is not a recognized classification type by open metadata repository {1}
    OMRS-REPOSITORY-400-064 - Method {0} is unable to locate an instance with guid {1} in the archive
    OMRS-CONTENT-MANAGER-500-005 - The repository content manager has detected an unknown TypeDef {0} ({1}) from {2}.
    OMRS-ARCHIVE-BUILDER-400-013 - The archive builder has been passed an unknown type name {0}
    OMRS-REPOSITORY-400-080 - Classification {0} is not a supported classification type in open metadata repository {1}
    OMRS-REPOSITORY-400-066 - Method {0} is unable to accept the new {1} instance from {2} with guid {3} and type {4} because it has a header version of {5} which is greater than this repository can support ({6})
    OMRS-REPOSITORY-400-065 - Method {0} is unable to accept the new type definition {1} from {2} because it has a header version of {3} which is greater than this repository can support ({4})
    OMRS-LOCAL-REPOSITORY-503-005 - An OMRS repository connector or access service {0} has passed an invalid parameter to the repository validator {1} operation as part of the {2} request
    OMRS-REPOSITORY-400-059 - Type definition with guid {0} and name {1} conflicts with an existing type definition in open metadata repository {2}
    OMRS-TOPIC-CONNECTOR-500-007 - The connector generated from the connection named {0} return by the {1} service running in OMAG Server at {2} is not of the required type.
  • Method Summary

    Modifier and Type
    Method
    Description
    Retrieve a message definition object for an exception.
    Retrieve a message definition object for an exception.
    JSON-style toString
    Returns the enum constant of this class with the specified name.
    static OMRSErrorCode[]
    Returns an array containing the constants of this enum class, in the order they are declared.

    Methods inherited from class java.lang.Object

    getClass, notify, notifyAll, wait, wait, wait
  • Enum Constant Details

    • TYPEDEF_IN_USE

      public static final OMRSErrorCode TYPEDEF_IN_USE
      OMRS-REPOSITORY-400-001 - Unable to delete the TypeDef {0} (guid = {1}) since it is still in use in the open metadata repository {2}
    • ATTRIBUTE_TYPEDEF_IN_USE

      public static final OMRSErrorCode ATTRIBUTE_TYPEDEF_IN_USE
      OMRS-REPOSITORY-400-002 - Unable to delete the AttributeTypeDef {0} (guid = {1}) since it is still in use in the open metadata repository {2}
    • TYPEDEF_ALREADY_DEFINED

      public static final OMRSErrorCode TYPEDEF_ALREADY_DEFINED
      OMRS-REPOSITORY-400-003 - Unable to add the TypeDef {0} (guid = {1}) since it is already defined in the open metadata repository {2}
    • ATTRIBUTE_TYPEDEF_ALREADY_DEFINED

      public static final OMRSErrorCode ATTRIBUTE_TYPEDEF_ALREADY_DEFINED
      OMRS-REPOSITORY-400-004 - Unable to add the AttributeTypeDef {0} (guid = {1}) since it is already defined in the open metadata repository {2}
    • UNKNOWN_CLASSIFICATION

      public static final OMRSErrorCode UNKNOWN_CLASSIFICATION
      OMRS-REPOSITORY-400-005 - Classification {0} is not a recognized classification type by open metadata repository {1}
    • INVALID_CLASSIFICATION_FOR_ENTITY

      public static final OMRSErrorCode INVALID_CLASSIFICATION_FOR_ENTITY
      OMRS-REPOSITORY-400-006 - Open metadata repository {0} is unable to assign a classification of type {1} to an entity of type {2} as the classification type is not valid for this type of entity
    • NO_TYPEDEF_NAME

      public static final OMRSErrorCode NO_TYPEDEF_NAME
      OMRS-REPOSITORY-400-007 - A null TypeDef name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_ATTRIBUTE_TYPEDEF_NAME

      public static final OMRSErrorCode NO_ATTRIBUTE_TYPEDEF_NAME
      OMRS-REPOSITORY-400-008 - A null AttributeTypeDef name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_TYPEDEF_CATEGORY

      public static final OMRSErrorCode NO_TYPEDEF_CATEGORY
      OMRS-REPOSITORY-400-009 - A null TypeDef category has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_ATTRIBUTE_TYPEDEF_CATEGORY

      public static final OMRSErrorCode NO_ATTRIBUTE_TYPEDEF_CATEGORY
      OMRS-REPOSITORY-400-010 - A null AttributeTypeDef category has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_MATCH_CRITERIA

      public static final OMRSErrorCode NO_MATCH_CRITERIA
      OMRS-REPOSITORY-400-011 - A null list of match criteria properties has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_EXTERNAL_ID

      public static final OMRSErrorCode NO_EXTERNAL_ID
      OMRS-REPOSITORY-400-012 - Null values for all the parameters describing an external id for a standard has been passed on a {0} request to open metadata repository {1}
    • NO_SEARCH_CRITERIA

      public static final OMRSErrorCode NO_SEARCH_CRITERIA
      OMRS-REPOSITORY-400-013 - A null search criteria has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_GUID

      public static final OMRSErrorCode NO_GUID
      OMRS-REPOSITORY-400-014 - A null unique identifier (guid) has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_TYPEDEF

      public static final OMRSErrorCode NO_TYPEDEF
      OMRS-REPOSITORY-400-015 - A null TypeDef has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_ATTRIBUTE_TYPEDEF

      public static final OMRSErrorCode NO_ATTRIBUTE_TYPEDEF
      OMRS-REPOSITORY-400-016 - A null AttributeTypeDef has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • INVALID_TYPEDEF

      public static final OMRSErrorCode INVALID_TYPEDEF
      OMRS-REPOSITORY-400-017 - An invalid TypeDef {0} (guid={1}) has been passed as the {2} parameter on a {3} request to open metadata repository {4}. Full TypeDef is {5}
    • INVALID_ATTRIBUTE_TYPEDEF

      public static final OMRSErrorCode INVALID_ATTRIBUTE_TYPEDEF
      OMRS-REPOSITORY-400-018 - An invalid AttributeTypeDef {0} (guid={1}) has been passed as the {2} parameter on a {3} request to open metadata repository {4}. Full AttributeTypeDef is {5}
    • NULL_TYPEDEF

      public static final OMRSErrorCode NULL_TYPEDEF
      OMRS-REPOSITORY-400-019 - A null TypeDef has been passed as the {0} parameter on a {1} request to the open metadata repository {2}
    • NULL_ATTRIBUTE_TYPEDEF

      public static final OMRSErrorCode NULL_ATTRIBUTE_TYPEDEF
      OMRS-REPOSITORY-400-020 - A null AttributeTypeDef has been passed as the {0} parameter on a {1} request to the open metadata repository {2}
    • NULL_TYPEDEF_IDENTIFIER

      public static final OMRSErrorCode NULL_TYPEDEF_IDENTIFIER
      OMRS-REPOSITORY-400-022 - A null unique identifier (guid) for a TypeDef object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NULL_TYPEDEF_NAME

      public static final OMRSErrorCode NULL_TYPEDEF_NAME
      OMRS-REPOSITORY-400-023 - A null unique name for a TypeDef object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NULL_ATTRIBUTE_TYPEDEF_IDENTIFIER

      public static final OMRSErrorCode NULL_ATTRIBUTE_TYPEDEF_IDENTIFIER
      OMRS-REPOSITORY-400-024 - A null unique identifier (guid) for a AttributeTypeDef object has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NULL_METADATA_COLLECTION

      public static final OMRSErrorCode NULL_METADATA_COLLECTION
      OMRS-REPOSITORY-400-025 - Local metadata repository has not initialized correctly because it was unable to create its metadata collection
    • NULL_CLASSIFICATION_NAME

      public static final OMRSErrorCode NULL_CLASSIFICATION_NAME
      OMRS-REPOSITORY-400-026 - A null classification name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NULL_USER_ID

      public static final OMRSErrorCode NULL_USER_ID
      OMRS-REPOSITORY-400-027 - A null username has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • BAD_PROPERTY_FOR_TYPE

      public static final OMRSErrorCode BAD_PROPERTY_FOR_TYPE
      OMRS-REPOSITORY-400-028 - A property called {0} has been proposed for a new metadata instance of category {1} and type {2}; it is not supported for this type in open metadata repository {3}
    • NO_PROPERTIES_FOR_TYPE

      public static final OMRSErrorCode NO_PROPERTIES_FOR_TYPE
      OMRS-REPOSITORY-400-029 - Properties have been proposed for a new metadata instance of category {0} and type {1}; properties not supported for this type in open metadata repository {2}
    • BAD_PROPERTY_TYPE

      public static final OMRSErrorCode BAD_PROPERTY_TYPE
      OMRS-REPOSITORY-400-030 - A property called {0} of type {1} has been proposed for a new metadata instance of category {2} and type {3}; this property should be of type {4} in open metadata repository {5}
    • NULL_PROPERTY_NAME_FOR_INSTANCE

      public static final OMRSErrorCode NULL_PROPERTY_NAME_FOR_INSTANCE
      OMRS-REPOSITORY-400-031 - A null property name has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NULL_PROPERTY_VALUE_FOR_INSTANCE

      public static final OMRSErrorCode NULL_PROPERTY_VALUE_FOR_INSTANCE
      OMRS-REPOSITORY-400-032 - A null property value has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NULL_PROPERTY_TYPE_FOR_INSTANCE

      public static final OMRSErrorCode NULL_PROPERTY_TYPE_FOR_INSTANCE
      OMRS-REPOSITORY-400-033 - A null property type has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • BAD_TYPEDEF_ID_FOR_INSTANCE

      public static final OMRSErrorCode BAD_TYPEDEF_ID_FOR_INSTANCE
      OMRS-REPOSITORY-400-034 - A invalid TypeDef unique identifier (guid) has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • BAD_INSTANCE_STATUS

      public static final OMRSErrorCode BAD_INSTANCE_STATUS
      OMRS-REPOSITORY-400-035 - An instance status of {0} has been passed as the {1} parameter on a {2} request to open metadata repository {3} but this status is not valid for an instance of type {4}
    • NULL_INSTANCE_STATUS

      public static final OMRSErrorCode NULL_INSTANCE_STATUS
      OMRS-REPOSITORY-400-036 - A null instance status has been passed as the {0} parameter on a {1} request to open metadata repository {2}
    • NO_NEW_PROPERTIES

      public static final OMRSErrorCode NO_NEW_PROPERTIES
      OMRS-REPOSITORY-400-037 - No properties have been passed on the {0} parameter on a {1} request to open metadata repository {2}
    • REPOSITORY_NOT_CRYSTAL_BALL

      public static final OMRSErrorCode REPOSITORY_NOT_CRYSTAL_BALL
      OMRS-REPOSITORY-400-038 - A future time of {0} has been passed on the {0} parameter of a {1} request to open metadata repository {2}
    • BAD_TYPEDEF_IDS_FOR_DELETE

      public static final OMRSErrorCode BAD_TYPEDEF_IDS_FOR_DELETE
      OMRS-REPOSITORY-400-039 - Incompatible TypeDef unique identifiers (name={0}, guid{1}) have been passed on a {2} request for instance {3} to open metadata repository {4}
    • BAD_PROPERTY_FOR_INSTANCE

      public static final OMRSErrorCode BAD_PROPERTY_FOR_INSTANCE
      OMRS-REPOSITORY-400-040 - Unexpected exception {0} occurred when comparing properties against a search string of {1} during the {2} operation from {3}. Error message was {4}
    • NULL_REFERENCE_INSTANCE

      public static final OMRSErrorCode NULL_REFERENCE_INSTANCE
      OMRS-REPOSITORY-400-041 - A null reference instance has been passed to repository {0} during the {1} in the {2} parameter
    • NULL_ENTITY_PROXY

      public static final OMRSErrorCode NULL_ENTITY_PROXY
      OMRS-REPOSITORY-400-043 - A null entity proxy has been passed to repository {0} as the {1} parameter of the {2} operation
    • LOCAL_ENTITY_PROXY

      public static final OMRSErrorCode LOCAL_ENTITY_PROXY
      OMRS-REPOSITORY-400-044 - An entity proxy has been passed to repository {0} as the {1} parameter of the {2} operation which has the local repository as its home
    • INSTANCE_ALREADY_DELETED

      public static final OMRSErrorCode INSTANCE_ALREADY_DELETED
      OMRS-REPOSITORY-400-045 - A {0} request has been made to repository {1} for an instance {2} that is already deleted
    • INSTANCE_NOT_DELETED

      public static final OMRSErrorCode INSTANCE_NOT_DELETED
      OMRS-REPOSITORY-400-046 - A {0} request has been made to repository {1} for an instance {2} that is not deleted
    • INVALID_RELATIONSHIP_ENDS

      public static final OMRSErrorCode INVALID_RELATIONSHIP_ENDS
      OMRS-REPOSITORY-400-047 - A {0} request has been made to repository {1} for a relationship that has one or more ends of the wrong or invalid type. Relationship type is {2}; entity proxy {3} for end 1 is of type {4} rather than {5} and entity proxy {6} for end 2 is of type {7} rather than {8}
    • ENTITY_NOT_CLASSIFIED

      public static final OMRSErrorCode ENTITY_NOT_CLASSIFIED
      OMRS-REPOSITORY-400-048 - A {0} request has been made to repository {1} to remove a non-existent classification {2} from entity {3}
    • NULL_TYPEDEF_PATCH

      public static final OMRSErrorCode NULL_TYPEDEF_PATCH
      OMRS-REPOSITORY-400-049 - A null TypeDef patch has been passed on the {0} operation of repository {1}
    • NEGATIVE_PAGE_SIZE

      public static final OMRSErrorCode NEGATIVE_PAGE_SIZE
      OMRS-REPOSITORY-400-050 - A negative pageSize of {0} has been passed on the {0} parameter of a {1} request to open metadata repository {2}
    • ENTITY_PROXY_ONLY

      public static final OMRSErrorCode ENTITY_PROXY_ONLY
      OMRS-REPOSITORY-400-051 - A request for entity {0} has been passed to repository {1} as the {2} parameter of the {3} operation but only an entity proxy has been found
    • INVALID_ENTITY_FROM_STORE

      public static final OMRSErrorCode INVALID_ENTITY_FROM_STORE
      OMRS-REPOSITORY-400-052 - The entity {0} retrieved from repository {1} during the {2} operation has invalid contents: {3}
    • INVALID_RELATIONSHIP_FROM_STORE

      public static final OMRSErrorCode INVALID_RELATIONSHIP_FROM_STORE
      OMRS-REPOSITORY-400-053 - The relationship {0} retrieved from repository {1} during the {2} operation has invalid contents: {3}
    • NULL_INSTANCE_METADATA_COLLECTION_ID

      public static final OMRSErrorCode NULL_INSTANCE_METADATA_COLLECTION_ID
      OMRS-REPOSITORY-400-054 - The element {0} retrieved from repository {1} during the {2} operation has a null metadata collection id in its header: {3}
    • UNEXPECTED_EXCEPTION_FROM_COHORT

      public static final OMRSErrorCode UNEXPECTED_EXCEPTION_FROM_COHORT
      OMRS-REPOSITORY-400-055 - An unexpected {0} exception was received from a repository connector during the {1} operation which had message: {2}
    • NO_HOME_FOR_INSTANCE

      public static final OMRSErrorCode NO_HOME_FOR_INSTANCE
      OMRS-REPOSITORY-400-056 - The OMRS repository connector operation {0} from the OMRS Enterprise Repository Services can not locate the home repository connector for instance {1} located in metadata collection {2}
    • NULL_AS_OF_TIME

      public static final OMRSErrorCode NULL_AS_OF_TIME
      OMRS-REPOSITORY-400-057 - The OMRS repository connector operation {0} does not allow a null value for {1} from {2}
    • BAD_DELETE_INSTANCE_STATUS

      public static final OMRSErrorCode BAD_DELETE_INSTANCE_STATUS
      OMRS-REPOSITORY-400-058 - An instance status of {0} has been passed as the {1} parameter on a {2} request to open metadata repository {3} however this status is not valid for an instance of type {4}
    • VERIFY_CONFLICT_DETECTED

      public static final OMRSErrorCode VERIFY_CONFLICT_DETECTED
      OMRS-REPOSITORY-400-059 - Type definition with guid {0} and name {1} conflicts with an existing type definition in open metadata repository {2}
    • NULL_PARAMETER

      public static final OMRSErrorCode NULL_PARAMETER
      OMRS-REPOSITORY-400-060 - The repository helper method {0} has been called with a null parameter
    • INVALID_INSTANCE

      public static final OMRSErrorCode INVALID_INSTANCE
      OMRS-REPOSITORY-400-061 - An invalid instance has been detected by repository helper method {0}. The instance is {1}
    • UNEXPECTED_EXCEPTION

      public static final OMRSErrorCode UNEXPECTED_EXCEPTION
      OMRS-REPOSITORY-400-062 - An unexpected {0} exception was caught by {1}; error message was {2}
    • HOME_REFRESH

      public static final OMRSErrorCode HOME_REFRESH
      OMRS-REPOSITORY-400-063 - Method {0} is unable to request a refresh of instance {1} as it is a local member of metadata collection {2} in repository {3}
    • UNKNOWN_GUID

      public static final OMRSErrorCode UNKNOWN_GUID
      OMRS-REPOSITORY-400-064 - Method {0} is unable to locate an instance with guid {1} in the archive
    • UNSUPPORTED_TYPE_HEADER_VERSION

      public static final OMRSErrorCode UNSUPPORTED_TYPE_HEADER_VERSION
      OMRS-REPOSITORY-400-065 - Method {0} is unable to accept the new type definition {1} from {2} because it has a header version of {3} which is greater than this repository can support ({4})
    • UNSUPPORTED_INSTANCE_HEADER_VERSION

      public static final OMRSErrorCode UNSUPPORTED_INSTANCE_HEADER_VERSION
      OMRS-REPOSITORY-400-066 - Method {0} is unable to accept the new {1} instance from {2} with guid {3} and type {4} because it has a header version of {5} which is greater than this repository can support ({6})
    • INVALID_PATCH_VERSION

      public static final OMRSErrorCode INVALID_PATCH_VERSION
      OMRS-REPOSITORY-400-067 - Method {0} has detected invalid version values in TypeDef patch from {1}. The updateToVersion {2} is less than the applyToVersion {3}. This is the contents of the patch {4}
    • INCOMPATIBLE_PATCH_VERSION

      public static final OMRSErrorCode INCOMPATIBLE_PATCH_VERSION
      OMRS-REPOSITORY-400-068 - Method {0} has detected that a TypeDef patch from {1} is for a future level from the active TypeDef. The applyToVersion is {2} and the active TypeDef's version is {3}. This is the contents of the patch {4}
    • NULL_MANDATORY_PATCH_FIELD

      public static final OMRSErrorCode NULL_MANDATORY_PATCH_FIELD
      OMRS-REPOSITORY-400-069 - Method {0} has detected that a TypeDef patch from {1} has the mandatory field {2} set to null which is invalid. This is the contents of the patch {3}
    • INCOMPATIBLE_PROPERTY_PATCH

      public static final OMRSErrorCode INCOMPATIBLE_PROPERTY_PATCH
      OMRS-REPOSITORY-400-070 - Method {0} has detected that a TypeDef patch from {1} attempts to change the type of property {2} from {3} to {4}. This is the contents of the patch {5}
    • NO_AUDIT_LOG_DESTINATIONS

      public static final OMRSErrorCode NO_AUDIT_LOG_DESTINATIONS
      OMRS-REPOSITORY-400-071 - The Open Metadata Repository Services (OMRS) has been called to initialize with no audit log destinations defined for server {0}
    • NULL_AUDIT_LOG

      public static final OMRSErrorCode NULL_AUDIT_LOG
      OMRS-REPOSITORY-400-072 - The Open Metadata Repository Services (OMRS) has been called to initialize its subsystems for server {0} before the audit log is initialized
    • INVALID_INSTANCES

      public static final OMRSErrorCode INVALID_INSTANCES
      OMRS-REPOSITORY-400-073 - An invalid instance was found in a batch of reference instances send by a remote member of the cohort. The exception was {0} with message {1}
    • INVALID_LIST_CONDITION

      public static final OMRSErrorCode INVALID_LIST_CONDITION
      OMRS-REPOSITORY-400-076 - An invalid list was provided for the value of an IN operator
    • INVALID_LIKE_CONDITION

      public static final OMRSErrorCode INVALID_LIKE_CONDITION
      OMRS-REPOSITORY-400-077 - An invalid string was provided for the value of a LIKE operator
    • INVALID_NUMERIC_CONDITION

      public static final OMRSErrorCode INVALID_NUMERIC_CONDITION
      OMRS-REPOSITORY-400-078 - An invalid string was provided for the value of the {0} operator
    • TYPEDEF_NOT_SUBTYPE

      public static final OMRSErrorCode TYPEDEF_NOT_SUBTYPE
      OMRS-REPOSITORY-400-079 - The provided subtype {0} is not a subtype of typedef {1}
    • UNSUPPORTED_CLASSIFICATION

      public static final OMRSErrorCode UNSUPPORTED_CLASSIFICATION
      OMRS-REPOSITORY-400-080 - Classification {0} is not a supported classification type in open metadata repository {1}
    • ENTITY_ALREADY_CLASSIFIED

      public static final OMRSErrorCode ENTITY_ALREADY_CLASSIFIED
      OMRS-REPOSITORY-400-081 - A {0} request has been made to repository {1} to add a classification {2} to entity {3} when this entity is already classified
    • NO_HOME_FOR_CLASSIFICATION

      public static final OMRSErrorCode NO_HOME_FOR_CLASSIFICATION
      OMRS-REPOSITORY-400-082 - The OMRS repository connector operation {0} from the OMRS Enterprise Repository Services can not locate the home repository connector for classification {1} located in metadata collection {2}
    • INVALID_TIME_RANGE

      public static final OMRSErrorCode INVALID_TIME_RANGE
      OMRS-REPOSITORY-400-083 - The OMRS repository connector operation {0} does not allow a time range from {1} to {2}
    • NULL_USER_NAME

      public static final OMRSErrorCode NULL_USER_NAME
      OMRS-REST-API-400-001 - The OMRS REST API for server {0} has been called with a null username (userId)
    • NO_MORE_ELEMENTS

      public static final OMRSErrorCode NO_MORE_ELEMENTS
      OMRS-PROPERTIES-400-001 - No more elements in {0} iterator
    • NULL_CLASSIFICATION_PROPERTY_NAME

      public static final OMRSErrorCode NULL_CLASSIFICATION_PROPERTY_NAME
      OMRS-PROPERTIES-400-002 - No name provided for entity classification
    • NULL_PROPERTY_NAME

      public static final OMRSErrorCode NULL_PROPERTY_NAME
      OMRS-PROPERTIES-400-003 - Null property name passed to properties object
    • ARRAY_OUT_OF_BOUNDS

      public static final OMRSErrorCode ARRAY_OUT_OF_BOUNDS
      OMRS-PROPERTIES-400-004 - {0} is unable to add a new element to location {1} of an array of size {2} value
    • BAD_ATTRIBUTE_TYPE

      public static final OMRSErrorCode BAD_ATTRIBUTE_TYPE
      OMRS-PROPERTIES-400-005 - AttributeDefs may only be of primitive, collection or enum type. {0} of category {1} is not allowed
    • INVALID_SEARCH_CRITERIA

      public static final OMRSErrorCode INVALID_SEARCH_CRITERIA
      OMRS-PROPERTIES-400-006 - A {0} exception was returned when matching {2} against {1} in method {4}. The exception message was: {3}
    • BAD_DATA_TYPE

      public static final OMRSErrorCode BAD_DATA_TYPE
      OMRS-PROPERTIES-400-007 - Data type {0} is not supported by method {1}
    • REPOSITORY_URL_NULL

      public static final OMRSErrorCode REPOSITORY_URL_NULL
      OMRS-REST-CONNECTOR-400-001 - The connection passed in the cohort registration event does not contain the root URL for calling the server's REST API
    • REPOSITORY_URL_MALFORMED

      public static final OMRSErrorCode REPOSITORY_URL_MALFORMED
      OMRS-CONNECTOR-400-001 - The Open Metadata Repository Server URL {0} is not in a recognized format
    • NULL_CONNECTION

      public static final OMRSErrorCode NULL_CONNECTION
      OMRS-CONNECTOR-400-002 - The connection passed to OMASConnectedAssetProperties for connector {0} is null
    • NULL_OMRS_CONNECTION

      public static final OMRSErrorCode NULL_OMRS_CONNECTION
      OMRS-CONNECTOR-400-003 - The connection passed to the EnterpriseOMRSRepositoryConnector is null
    • INVALID_OMRS_CONNECTION

      public static final OMRSErrorCode INVALID_OMRS_CONNECTION
      OMRS-CONNECTOR-400-004 - The connection {0} passed to the EnterpriseOMRSRepositoryConnector is invalid
    • BAD_REAL_LOCAL_REPOSITORY_CONNECTOR

      public static final OMRSErrorCode BAD_REAL_LOCAL_REPOSITORY_CONNECTOR
      OMRS-CONNECTOR-400-005 - The connector to the local repository failed with a {0} exception and the following error message: {1}
    • NULL_TOPIC_CONNECTOR

      public static final OMRSErrorCode NULL_TOPIC_CONNECTOR
      OMRS-TOPIC-CONNECTOR-400-001 - Unable to send or receive events for source {0} because the connector to the OMRS Topic failed to initialize
    • NO_EVENT_BUS_CONNECTORS

      public static final OMRSErrorCode NO_EVENT_BUS_CONNECTORS
      OMRS-TOPIC-CONNECTOR-400-002 - The connector {0} has been configured without an embedded event bus connector
    • NULL_REGISTRY_STORE

      public static final OMRSErrorCode NULL_REGISTRY_STORE
      OMRS-COHORT-REGISTRY-404-001 - The Open Metadata Repository Cohort Registry Store for cohort {0} is not available
    • INVALID_LOCAL_METADATA_COLLECTION_ID

      public static final OMRSErrorCode INVALID_LOCAL_METADATA_COLLECTION_ID
      OMRS-COHORT-REGISTRY-400-002 - The Open Metadata Repository Cohort {0} is not available to server {1} because the local metadata collection id has been changed from {2} to {3} since this server registered with the cohort
    • NULL_ARCHIVE_STORE

      public static final OMRSErrorCode NULL_ARCHIVE_STORE
      OMRS-ARCHIVE-MANAGER-400-001 - An open metadata archive configured for server {0} is not accessible
    • NULL_EVENT_MAPPER

      public static final OMRSErrorCode NULL_EVENT_MAPPER
      OMRS-LOCAL-REPOSITORY-400-001 - The repository event mapper configured for the local repository for server {0} is not accessible
    • NOT_FOR_LOCAL_COLLECTION

      public static final OMRSErrorCode NOT_FOR_LOCAL_COLLECTION
      OMRS-LOCAL-REPOSITORY-400-002 - The local repository is not able to re-home the instance {0} of type {1} ({2}) because it is not managing the repository with the requested home metadata collection of {3}. This local repository is managing the {4} metadata collection
    • CONFLICTING_ENTERPRISE_TYPEDEFS

      public static final OMRSErrorCode CONFLICTING_ENTERPRISE_TYPEDEFS
      OMRS-ENTERPRISE-REPOSITORY-400-001 - Conflicting TypeDefs have been detected
    • NO_TYPEDEFS_DEFINED

      public static final OMRSErrorCode NO_TYPEDEFS_DEFINED
      OMRS-ENTERPRISE-REPOSITORY-400-002 - No TypeDefs have been defined in any of the connected repositories
    • DUPLICATE_TYPE_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_TYPE_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-001 - The same type {0} of category {1} has been added twice to an open metadata archive. First version was {2} and the second was {3}
    • DUPLICATE_INSTANCE_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_INSTANCE_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-002 - The {0} instance {1} has been added twice to an open metadata archive. First version was {2} and the second was {3}
    • DUPLICATE_TYPENAME_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_TYPENAME_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-003 - The same type name {0} has been added twice to an open metadata archive. First version was {1} and the second was {2}
    • DUPLICATE_GUID_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_GUID_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-004 - The guid {0} has been used twice to an open metadata archive. First version was {1} and the second was {2}
    • MISSING_TYPE_IN_ARCHIVE

      public static final OMRSErrorCode MISSING_TYPE_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-005 - The type {0} of category {1} is not found in an open metadata archive
    • MISSING_NAME_FOR_ARCHIVE

      public static final OMRSErrorCode MISSING_NAME_FOR_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-006 - A request for a type from category {0} passed a null name
    • DUPLICATE_ENDDEF1_NAME_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_ENDDEF1_NAME_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-007 - RelationshipEndDef1 type {0} and EndDef1 name {1} in RelationshipDef {2} are incorrect, because another entity or relationship endDef is already using this attribute name
    • DUPLICATE_ENDDEF2_NAME_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_ENDDEF2_NAME_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-008 - RelationshipEndDef2 type {0} and EndDef2 name {1} in RelationshipDef {2} are incorrect, because another entity or relationship endDef is already using this attribute name
    • DUPLICATE_RELATIONSHIP_ATTR_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_RELATIONSHIP_ATTR_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-009 - Duplicate attribute name {0} is defined in RelationshipDef {1}
    • DUPLICATE_ENTITY_ATTR_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_ENTITY_ATTR_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-010 - Duplicate attribute name {0} is defined in EntityDef {1}
    • DUPLICATE_CLASSIFICATION_ATTR_IN_ARCHIVE

      public static final OMRSErrorCode DUPLICATE_CLASSIFICATION_ATTR_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-011 - Duplicate attribute name {0} is defined in ClassificationDef {1}
    • BLANK_TYPENAME_IN_ARCHIVE

      public static final OMRSErrorCode BLANK_TYPENAME_IN_ARCHIVE
      OMRS-ARCHIVE-BUILDER-400-012 - Type name {0} is invalid because it contains a blank character
    • UNKNOWN_TYPENAME

      public static final OMRSErrorCode UNKNOWN_TYPENAME
      OMRS-ARCHIVE-BUILDER-400-013 - The archive builder has been passed an unknown type name {0}
    • NO_AUDIT_LOG_STORE

      public static final OMRSErrorCode NO_AUDIT_LOG_STORE
      OMRS-AUDIT-LOG-400-001 - There are no Audit Log destinations configured for server {0}
    • NULL_AUDIT_LOG_STORE

      public static final OMRSErrorCode NULL_AUDIT_LOG_STORE
      OMRS-AUDIT-LOG-400-002 - An Audit Log destination for server {0} is not correctly configured
    • NULL_LOG_RECORD

      public static final OMRSErrorCode NULL_LOG_RECORD
      OMRS-AUDIT-LOG-400-003 - A null log record has been passed by the audit log to the audit log destination {0}
    • NULL_LOG_RECORD_ORIGINATOR

      public static final OMRSErrorCode NULL_LOG_RECORD_ORIGINATOR
      OMRS-AUDIT-LOG-400-004 - A log record with a null originator has been passed by the audit log to the audit log destination {0}
    • NULL_LOG_RECORD_REPORTING_COMPONENT

      public static final OMRSErrorCode NULL_LOG_RECORD_REPORTING_COMPONENT
      OMRS-AUDIT-LOG-400-005 - A log record with a null reporting component has been passed by the audit log to the audit log destination {0}
    • CAN_NOT_QUERY_AUDIT_LOG_STORE

      public static final OMRSErrorCode CAN_NOT_QUERY_AUDIT_LOG_STORE
      OMRS-AUDIT-LOG-400-006 - The Audit Log destination {0} is not able to support queries
    • AUDIT_LOG_STORE_NOT_AVAILABLE

      public static final OMRSErrorCode AUDIT_LOG_STORE_NOT_AVAILABLE
      OMRS-AUDIT-LOG-400-007 - The Audit Log destination {0} is not available. The error returned was {1}
    • AUDIT_LOG_RECORD_NOT_JSON_ENABLED

      public static final OMRSErrorCode AUDIT_LOG_RECORD_NOT_JSON_ENABLED
      OMRS-AUDIT-LOG-400-008 - The Audit log destination {0} is not able to convert an audit log record to JSON format
    • ARCHIVE_MANAGER_NOT_ACTIVE

      public static final OMRSErrorCode ARCHIVE_MANAGER_NOT_ACTIVE
      OMRS-AUDIT-LOG-400-009 - The archive manager is not active in server {0}
    • REPOSITORY_NOT_AVAILABLE

      public static final OMRSErrorCode REPOSITORY_NOT_AVAILABLE
      OMRS-REPOSITORY-404-001 - The open metadata repository connector for server {0} is not active and is unable to service the {1} request
    • ENTITY_NOT_KNOWN

      public static final OMRSErrorCode ENTITY_NOT_KNOWN
      OMRS-REPOSITORY-404-002 - The entity identified with guid {0} passed on the {1} call is not known to the open metadata repository {2}
    • RELATIONSHIP_NOT_KNOWN

      public static final OMRSErrorCode RELATIONSHIP_NOT_KNOWN
      OMRS-REPOSITORY-404-003 - The relationship identified with guid {0} passed on the {1} call is not known to the open metadata repository {2}
    • TYPEDEF_NOT_KNOWN

      public static final OMRSErrorCode TYPEDEF_NOT_KNOWN
      OMRS-REPOSITORY-404-004 - The TypeDef {0} (guid = {1}) passed on the {2} parameter of the {3} operation is not known to the open metadata repository {4}
    • TYPEDEF_NOT_KNOWN_FOR_INSTANCE

      public static final OMRSErrorCode TYPEDEF_NOT_KNOWN_FOR_INSTANCE
      OMRS-REPOSITORY-404-005 - The TypeDef {0} of category {1} passed by the {2} operation is not known to the open metadata repository {3}
    • ATTRIBUTE_TYPEDEF_NOT_KNOWN

      public static final OMRSErrorCode ATTRIBUTE_TYPEDEF_NOT_KNOWN
      OMRS-REPOSITORY-404-006 - The AttributeTypeDef {0} (guid = {1}) passed on the {2} call is not known to the open metadata repository {3}
    • TYPEDEF_ID_NOT_KNOWN

      public static final OMRSErrorCode TYPEDEF_ID_NOT_KNOWN
      OMRS-REPOSITORY-404-007 - The TypeDef unique identifier {0} passed as parameter {1} on a {2} request to open metadata repository {3} is not known to this repository
    • ATTRIBUTE_TYPEDEF_ID_NOT_KNOWN

      public static final OMRSErrorCode ATTRIBUTE_TYPEDEF_ID_NOT_KNOWN
      OMRS-REPOSITORY-404-008 - The AttributeTypeDef {0} (guid {1}) passed on a {2} request to open metadata repository {3} is not known to this repository
    • TYPEDEF_NAME_NOT_KNOWN

      public static final OMRSErrorCode TYPEDEF_NAME_NOT_KNOWN
      OMRS-REPOSITORY-404-009 - The TypeDef unique name {0} passed on a {1} request to open metadata repository {2} is not known to this repository
    • ATTRIBUTE_TYPEDEF_NAME_NOT_KNOWN

      public static final OMRSErrorCode ATTRIBUTE_TYPEDEF_NAME_NOT_KNOWN
      OMRS-REPOSITORY-404-010 - The TypeDef unique name {0} passed on a {1} request to open metadata repository {2} is not known to the repository
    • RELATIONSHIP_NOT_FOUND

      public static final OMRSErrorCode RELATIONSHIP_NOT_FOUND
      OMRS-REPOSITORY-404-011 - The relationship identified with guid {0} passed on the {1} call is not found to the open metadata repository {2}
    • RELATIONSHIP_SOFT_DELETED

      public static final OMRSErrorCode RELATIONSHIP_SOFT_DELETED
      OMRS-REPOSITORY-404-012 - The {0} relationship identified with guid {1} passed on the {2} call is soft-deleted in the open metadata repository {3}
    • ENTITY_SOFT_DELETED

      public static final OMRSErrorCode ENTITY_SOFT_DELETED
      OMRS-REPOSITORY-404-013 - The {0} entity identified with guid {1} passed on the {2} call is soft-deleted in the open metadata repository {3}
    • COHORT_NOT_CONNECTED

      public static final OMRSErrorCode COHORT_NOT_CONNECTED
      OMRS-REPOSITORY-CONNECTOR-404-002 - The Open Metadata Repository Servers in the cohort are not available
    • INVALID_COHORT_CONFIG

      public static final OMRSErrorCode INVALID_COHORT_CONFIG
      OMRS-REPOSITORY-CONNECTOR-404-003 - The open metadata repository servers in the cohort are not configured correctly
    • METADATA_HIGHWAY_NOT_AVAILABLE

      public static final OMRSErrorCode METADATA_HIGHWAY_NOT_AVAILABLE
      OMRS-METADATA-HIGHWAY-404-00 - The local server's metadata highway communication components are failing to initialize
    • COHORT_DISCONNECT_FAILED

      public static final OMRSErrorCode COHORT_DISCONNECT_FAILED
      OMRS-METADATA-HIGHWAY-404-002 - The local server is unable to disconnect from an open metadata repository cohort {0}
    • DUPLICATE_COHORT_NAME

      public static final OMRSErrorCode DUPLICATE_COHORT_NAME
      OMRS-METADATA-HIGHWAY-404-003 - There are more than one cohort configurations with the same name of {0}
    • TOPIC_CONNECTOR_NOT_AVAILABLE

      public static final OMRSErrorCode TOPIC_CONNECTOR_NOT_AVAILABLE
      OMRS-TOPIC-CONNECTOR-404-001 - The OMRS Topic Connector is not available
    • REMOTE_REPOSITORY_ERROR

      public static final OMRSErrorCode REMOTE_REPOSITORY_ERROR
      OMRS-REST-REPOSITORY-CONNECTOR-404-001 - A call to the {0} of the open metadata repository server {1} results in an exception {2} with message {3}
    • COHORT_STARTUP_ERROR

      public static final OMRSErrorCode COHORT_STARTUP_ERROR
      OMRS-METADATA-HIGHWAY-404-004 - The local server is unable to initiate a connection to the cohort {0} when starting up
    • ENTERPRISE_NOT_SUPPORTED

      public static final OMRSErrorCode ENTERPRISE_NOT_SUPPORTED
      OMRS-ENTERPRISE-REPOSITORY-CONNECTOR-405-001 - The requested method {0} is not supported by the EnterpriseOMRSRepositoryConnector
    • MULTIPLE_ENTITIES_FOUND

      public static final OMRSErrorCode MULTIPLE_ENTITIES_FOUND
      OMRS-METADATA-COLLECTION-409-001 - Multiple instances of type {0} have been returned to {2} of service {1} when there should be one at most. These are examples of the entities returned: {3}
    • MULTIPLE_RELATIONSHIPS_FOUND

      public static final OMRSErrorCode MULTIPLE_RELATIONSHIPS_FOUND
      OMRS-METADATA-COLLECTION-409-002 - Multiple instances of type {0} have been returned to {2} of service {1} when there should be a maximum of one. These are examples of the entities returned: {3}
    • INVALID_PRIMITIVE_CLASS_NAME

      public static final OMRSErrorCode INVALID_PRIMITIVE_CLASS_NAME
      OMRS-METADATA-COLLECTION-500-001 - The Java class {0} for PrimitiveDefCategory {1} is not known
    • INVALID_PRIMITIVE_VALUE

      public static final OMRSErrorCode INVALID_PRIMITIVE_VALUE
      OMRS-METADATA-COLLECTION-500-002 - The primitive value should be stored in Java class {0} rather than {1} since it is of PrimitiveDefCategory {2}
    • INVALID_PRIMITIVE_CATEGORY

      public static final OMRSErrorCode INVALID_PRIMITIVE_CATEGORY
      OMRS-METADATA-COLLECTION-500-003 - There is a problem in the definition of primitive type {0}
    • NULL_HOME_METADATA_COLLECTION_ID

      public static final OMRSErrorCode NULL_HOME_METADATA_COLLECTION_ID
      OMRS-METADATA-COLLECTION-500-004 - Null home metadata collection identifier found by method {1} in property {0} from open metadata repository {3}
    • NULL_METADATA_COLLECTION_ID

      public static final OMRSErrorCode NULL_METADATA_COLLECTION_ID
      OMRS-METADATA-COLLECTION-500-006 - The open metadata repository connector {0} has been initialized with a null metadata collection identifier
    • BAD_INTERNAL_PAGING

      public static final OMRSErrorCode BAD_INTERNAL_PAGING
      OMRS-METADATA-COLLECTION-500-007 - Open metadata repository {0} has used an invalid paging parameter during the {1} operation
    • BAD_INTERNAL_SEQUENCING

      public static final OMRSErrorCode BAD_INTERNAL_SEQUENCING
      OMRS-METADATA-COLLECTION-500-008 - Open metadata repository {0} has used an invalid sequencing parameter during the {1} operation
    • NO_REPOSITORY_CONNECTOR_FOR_COLLECTION

      public static final OMRSErrorCode NO_REPOSITORY_CONNECTOR_FOR_COLLECTION
      OMRS-METADATA-COLLECTION-500-009 - Unable to complete operation {0} to open metadata repository {1} because the repository connector is null
    • NO_REPOSITORY_VALIDATOR_FOR_COLLECTION

      public static final OMRSErrorCode NO_REPOSITORY_VALIDATOR_FOR_COLLECTION
      OMRS-METADATA-COLLECTION-500-010 - Unable to complete operation {0} to open metadata repository {1} because the repository validator is null
    • NO_REPOSITORY_HELPER_FOR_COLLECTION

      public static final OMRSErrorCode NO_REPOSITORY_HELPER_FOR_COLLECTION
      OMRS-METADATA-COLLECTION-500-011 - Unable to complete operation {0} to open metadata repository {1} as the repository connector is null
    • REPOSITORY_LOGIC_ERROR

      public static final OMRSErrorCode REPOSITORY_LOGIC_ERROR
      OMRS-METADATA-COLLECTION-500-012 - Open metadata repository {0} has encountered an unexpected exception during the {1} operation. The full message was {2}
    • NULL_INSTANCE_TYPE

      public static final OMRSErrorCode NULL_INSTANCE_TYPE
      OMRS-METADATA-COLLECTION-500-013 - During the {0} operation, open metadata repository {1} retrieved an instance from its metadata store that has a null type
    • INACTIVE_INSTANCE_TYPE

      public static final OMRSErrorCode INACTIVE_INSTANCE_TYPE
      OMRS-METADATA-COLLECTION-500-014 - During the {0} operation, open metadata repository {1} retrieved an instance (guid={2}) from its metadata store that has an inactive type called {3} (type guid = {4})
    • INVALID_PRIMITIVE_TYPE

      public static final OMRSErrorCode INVALID_PRIMITIVE_TYPE
      OMRS-METADATA-COLLECTION-500-015 - The value supplied for an attribute of PrimitiveDefCategory {0} is expected as Java class {1} but was supplied as Java class {2}
    • INSTANCE_HOME_NOT_LOCAL

      public static final OMRSErrorCode INSTANCE_HOME_NOT_LOCAL
      OMRS-METADATA-COLLECTION-500-016 - The home metadata collection identifier {0} found by method {1} for instance with GUID {2} is not the metadata collection identifier {3} for the local metadata repository {4}
    • INSTANCE_HOME_IS_LOCAL

      public static final OMRSErrorCode INSTANCE_HOME_IS_LOCAL
      OMRS-METADATA-COLLECTION-500-017 - The home metadata collection identifier {0} found by method {1} for instance with GUID {2} is the metadata collection identifier {3} for the local metadata repository {4}
    • NULL_METADATA_COLLECTION_ID_FROM_REMOTE

      public static final OMRSErrorCode NULL_METADATA_COLLECTION_ID_FROM_REMOTE
      OMRS-METADATA-COLLECTION-500-018 - The open metadata repository connector {0} has returned a null metadata collection identifier
    • NULL_COHORT_NAME

      public static final OMRSErrorCode NULL_COHORT_NAME
      OMRS-COHORT-MANAGER-500-001 - OMRSCohortManager has been initialized with a null cohort name
    • NULL_CONFIG

      public static final OMRSErrorCode NULL_CONFIG
      OMRS-OPERATIONAL-SERVICES-500-001 - No configuration has been passed to the Open Metadata Repository Services (OMRS) on initialization os server {0}
    • NULL_LOCAL_METADATA_COLLECTION

      public static final OMRSErrorCode NULL_LOCAL_METADATA_COLLECTION
      The local repository services have been initialized with a null real metadata collection.
    • LOCAL_REPOSITORY_FAILED_TO_START

      public static final OMRSErrorCode LOCAL_REPOSITORY_FAILED_TO_START
      OMRS-LOCAL-REPOSITORY-500-002 - The local repository for server {0} failed to initialize and returned a {1} exception with message {2}
    • NULL_ENTERPRISE_METADATA_COLLECTION

      public static final OMRSErrorCode NULL_ENTERPRISE_METADATA_COLLECTION
      OMRS-ENTERPRISE-REPOSITORY-500-001 - The enterprise repository services has detected a repository connector with a null metadata collection
    • BAD_TYPEDEF

      public static final OMRSErrorCode BAD_TYPEDEF
      OMRS-CONTENT-MANAGER-500-001 - The repository content manager method {0} has detected an unknown TypeDef {1} from {2} on behalf of method {3}
    • BAD_TYPEDEF_ATTRIBUTE_NAME

      public static final OMRSErrorCode BAD_TYPEDEF_ATTRIBUTE_NAME
      OMRS-CONTENT-MANAGER-500-002 - The repository content manager has detected an invalid attribute name in a TypeDef from {0}
    • NULL_TYPEDEF_ATTRIBUTE

      public static final OMRSErrorCode NULL_TYPEDEF_ATTRIBUTE
      OMRS-CONTENT-MANAGER-500-003 - The repository content manager has detected a null attribute in a TypeDef from {0}
    • BAD_CATEGORY_FOR_TYPEDEF_ATTRIBUTE

      public static final OMRSErrorCode BAD_CATEGORY_FOR_TYPEDEF_ATTRIBUTE
      OMRS-CONTENT-MANAGER-500-004 - Source {0} has requested type {1} with an incompatible category of {2} from repository content manager
    • UNKNOWN_TYPEDEF

      public static final OMRSErrorCode UNKNOWN_TYPEDEF
      OMRS-CONTENT-MANAGER-500-005 - The repository content manager has detected an unknown TypeDef {0} ({1}) from {2}. It was passed to method {3} via parameters {4} and {5}
    • ARCHIVE_UNAVAILABLE

      public static final OMRSErrorCode ARCHIVE_UNAVAILABLE
      OMRS-OPEN-METADATA-ARCHIVE-500-001 - The archive builder failed to initialize
    • NULL_EXCHANGE_RULE

      public static final OMRSErrorCode NULL_EXCHANGE_RULE
      OMRS-EVENT-MANAGEMENT-500-001 - A null exchange rule has been passed to one of the event management components on method {0}
    • NULL_REPOSITORY_VALIDATOR

      public static final OMRSErrorCode NULL_REPOSITORY_VALIDATOR
      OMRS-EVENT-MANAGEMENT-500-002 - A null repository validator has been passed to one of the event management components
    • NULL_REPOSITORY_HELPER

      public static final OMRSErrorCode NULL_REPOSITORY_HELPER
      OMRS-EVENT-MANAGEMENT-500-003 - A null repository helper has been passed to one of the event management components
    • NULL_OUTBOUND_EVENT

      public static final OMRSErrorCode NULL_OUTBOUND_EVENT
      OMRS-EVENT-MANAGEMENT-500-004 - A null event has been passed to one of the event management components
    • METADATA_COLLECTION_ID_MISMATCH

      public static final OMRSErrorCode METADATA_COLLECTION_ID_MISMATCH
      OMRS-REST-REPOSITORY-CONNECTOR-500-001 - A remote open metadata repository {0} returned a metadata collection identifier of {1} on its REST API after it registered with the cohort using a metadata collection identifier of {2}
    • NULL_REMOTE_METADATA_COLLECTION_ID

      public static final OMRSErrorCode NULL_REMOTE_METADATA_COLLECTION_ID
      OMRS-REST-REPOSITORY-CONNECTOR-500-002 - A remote open metadata repository {0} returned a null metadata collection identifier on its REST API. It registered with the cohort using a metadata collection identifier of {1}
    • NULL_OPEN_METADATA_TOPIC_LISTENER

      public static final OMRSErrorCode NULL_OPEN_METADATA_TOPIC_LISTENER
      OMRS-METADATA-TOPIC-CONNECTOR-500-001 - A null topic listener has been passed to the {0} open metadata topic connector {1}
    • NULL_OMRS_TOPIC_LISTENER

      public static final OMRSErrorCode NULL_OMRS_TOPIC_LISTENER
      OMRS-TOPIC-CONNECTOR-500-001 - A null topic listener has been specified to the open metadata topic connector {0}
    • OMRS_TOPIC_SEND_EVENT_FAILED

      public static final OMRSErrorCode OMRS_TOPIC_SEND_EVENT_FAILED
      OMRS-TOPIC-CONNECTOR-500-002 - Connector {0} received an unexpected exception from sending event {1}. The exception message was: {2}
    • OMRS_TOPIC_SEND_NULL_EVENT

      public static final OMRSErrorCode OMRS_TOPIC_SEND_NULL_EVENT
      OMRS-TOPIC-CONNECTOR-500-003 - Connector {0} is unable to send a null event
    • NULL_CONNECTOR_RETURNED

      public static final OMRSErrorCode NULL_CONNECTOR_RETURNED
      OMRS-TOPIC-CONNECTOR-500-006 - The requested connector for connection named {0} has not been created. The connection was provided by the {1} service running in OMAG Server at {2}
    • WRONG_TYPE_OF_CONNECTOR

      public static final OMRSErrorCode WRONG_TYPE_OF_CONNECTOR
      OMRS-TOPIC-CONNECTOR-500-007 - The connector generated from the connection named {0} return by the {1} service running in OMAG Server at {2} is not of the required type. It should be an instance of {3}
    • METHOD_NOT_IMPLEMENTED

      public static final OMRSErrorCode METHOD_NOT_IMPLEMENTED
      OMRS-METADATA-COLLECTION-501-001 - OMRSMetadataInstanceStore method {0} for OMRS Connector {1} to repository type {2} is not implemented
    • TYPE_NOT_IMPLEMENTED

      public static final OMRSErrorCode TYPE_NOT_IMPLEMENTED
      OMRS-METADATA-COLLECTION-501-002 - Repository {0} is not able to support the {1} type
    • OMRS_UNSUPPORTED_EVENT_PROTOCOL

      public static final OMRSErrorCode OMRS_UNSUPPORTED_EVENT_PROTOCOL
      OMRS-TOPIC-CONNECTOR-501-001 - Connector {0} is not able to support event protocol {1}
    • NO_REPOSITORIES

      public static final OMRSErrorCode NO_REPOSITORIES
      OMRS-ENTERPRISE-REPOSITORY-503-001 - There are no open metadata repositories available for access service {0}
    • ENTERPRISE_DISCONNECTED

      public static final OMRSErrorCode ENTERPRISE_DISCONNECTED
      OMRS-ENTERPRISE-REPOSITORY-503-002 - The enterprise repository services are disconnected from the open metadata repositories
    • NULL_COHORT_METADATA_COLLECTION

      public static final OMRSErrorCode NULL_COHORT_METADATA_COLLECTION
      OMRS-ENTERPRISE-REPOSITORY-503-003 - The enterprise repository services has detected a repository connector from cohort {0} for metadata collection identifier {1} that has a null metadata collection API object
    • NULL_CONTENT_MANAGER

      public static final OMRSErrorCode NULL_CONTENT_MANAGER
      OMRS-LOCAL-REPOSITORY-503-001 - A null repository content manager has been passed to one of the local repository's components on method {0}
    • NULL_SOURCE_NAME

      public static final OMRSErrorCode NULL_SOURCE_NAME
      OMRS-LOCAL-REPOSITORY-503-002 - A null repository content manager has been specified to one of the local repository's components on method {0}
    • LOCAL_REPOSITORY_CONFIGURATION_ERROR

      public static final OMRSErrorCode LOCAL_REPOSITORY_CONFIGURATION_ERROR
      OMRS-LOCAL-REPOSITORY-503-003 - The connection to the local open metadata repository server is not configured correctly
    • BAD_LOCAL_REPOSITORY_CONNECTION

      public static final OMRSErrorCode BAD_LOCAL_REPOSITORY_CONNECTION
      OMRS-LOCAL-REPOSITORY-503-004 - The connection to the local open metadata repository server has not been configured correctly
    • VALIDATION_LOGIC_ERROR

      public static final OMRSErrorCode VALIDATION_LOGIC_ERROR
      OMRS-LOCAL-REPOSITORY-503-005 - An OMRS repository connector or access service {0} has passed an invalid parameter to the repository validator {1} operation as part of the {2} request
    • CONTENT_MANAGER_LOGIC_ERROR

      public static final OMRSErrorCode CONTENT_MANAGER_LOGIC_ERROR
      OMRS-LOCAL-REPOSITORY-503-006 - An OMRS repository connector {0} has passed an invalid parameter to the repository content manager {1} operation as part of the {2} request
    • ENTITY_PROXY_IN_HOME

      public static final OMRSErrorCode ENTITY_PROXY_IN_HOME
      OMRS-LOCAL-REPOSITORY-503-007 - The local OMRS repository connector {0} hosts the home metadata collection for entity {1} but only has an entity proxy stored. It is not able to complete the {2} request
    • NULL_CLASSIFICATION_CREATED

      public static final OMRSErrorCode NULL_CLASSIFICATION_CREATED
      OMRS-LOCAL-REPOSITORY-503-008 - An OMRS repository connector or access server {0} has passed a null classification to the repository helper {1} operation as part of the {2} request
    • ENTITY_CAN_NOT_BE_UPDATED

      public static final OMRSErrorCode ENTITY_CAN_NOT_BE_UPDATED
      OMRS-LOCAL-REPOSITORY-503-009 - The local OMRS repository connector {0} has been asked to update entity {1} but it is not the owner. It is not able to complete the {2} request
    • RELATIONSHIP_CAN_NOT_BE_UPDATED

      public static final OMRSErrorCode RELATIONSHIP_CAN_NOT_BE_UPDATED
      OMRS-LOCAL-REPOSITORY-503-010 - The local OMRS repository connector {0} has been asked to update relationship {1} but it is not the owner. It is not able to complete the {2} request
    • NULL_INSTANCE

      public static final OMRSErrorCode NULL_INSTANCE
      OMRS-LOCAL-REPOSITORY-503-011 - The local OMRS repository connector {0} requested an instance {1} from the real metadata collection but a null was returned. It is not able to complete the {2} request
    • HELPER_LOGIC_ERROR

      public static final OMRSErrorCode HELPER_LOGIC_ERROR
      OMRS-REPOSITORY-HELPER-503-001 - A caller {0} has passed an invalid parameter to the repository helper {1} operation as part of the {2} request
    • HELPER_LOGIC_EXCEPTION

      public static final OMRSErrorCode HELPER_LOGIC_EXCEPTION
      OMRS-REPOSITORY-HELPER-503-002 - A caller {0} has passed an invalid parameter to the repository helper {1} operation as part of the {2} request resulting in an unexpected exception {3} with message {4}
    • NO_LOCAL_REPOSITORY

      public static final OMRSErrorCode NO_LOCAL_REPOSITORY
      OMRS-REST-API-503-001 - There is no local repository to support REST API call {0}
    • NO_ENTERPRISE_REPOSITORY

      public static final OMRSErrorCode NO_ENTERPRISE_REPOSITORY
      OMRS-REST-API-503-002 - There is no enterprise repository to support REST API call {0}
    • NO_METADATA_HIGHWAY

      public static final OMRSErrorCode NO_METADATA_HIGHWAY
      OMRS-REST-API-503-003 - There is no metadata highway to support REST API call {0}
    • NULL_RESPONSE_FROM_API

      public static final OMRSErrorCode NULL_RESPONSE_FROM_API
      OMRS-REST-API-503-004 - A null response was received from REST API call {0} to repository {1}
    • NO_REST_CLIENT

      public static final OMRSErrorCode NO_REST_CLIENT
      OMRS-REST-API-503-005 - Unable to create REST Client for repository {0}. The error message was {1}
    • CLIENT_SIDE_REST_API_ERROR

      public static final OMRSErrorCode CLIENT_SIDE_REST_API_ERROR
      OMRS-REST-API-503-006 - A client-side exception was received from API call {0} to repository {1}. The error message was {2}
  • Method Details

    • values

      public static OMRSErrorCode[] values()
      Returns an array containing the constants of this enum class, in the order they are declared.
      Returns:
      an array containing the constants of this enum class, in the order they are declared
    • valueOf

      public static OMRSErrorCode valueOf(String name)
      Returns the enum constant of this class with the specified name. The string must match exactly an identifier used to declare an enum constant in this class. (Extraneous whitespace characters are not permitted.)
      Parameters:
      name - the name of the enum constant to be returned.
      Returns:
      the enum constant with the specified name
      Throws:
      IllegalArgumentException - if this enum class has no constant with the specified name
      NullPointerException - if the argument is null
    • getMessageDefinition

      public ExceptionMessageDefinition getMessageDefinition()
      Retrieve a message definition object for an exception. This method is used when there are no message inserts.
      Specified by:
      getMessageDefinition in interface ExceptionMessageSet
      Returns:
      message definition object.
    • getMessageDefinition

      public ExceptionMessageDefinition getMessageDefinition(String... params)
      Retrieve a message definition object for an exception. This method is used when there are values to be inserted into the message.
      Specified by:
      getMessageDefinition in interface ExceptionMessageSet
      Parameters:
      params - array of parameters (all strings). They are inserted into the message according to the numbering in the message text.
      Returns:
      message definition object.
    • toString

      public String toString()
      JSON-style toString
      Overrides:
      toString in class Enum<OMRSErrorCode>
      Returns:
      string of property names and values for this enum