ORA-12519: TNS:no appropriate service handler found

ORA-12519: TNS:no appropriate service handler found

Cause: The listener could not find any available service handlers that are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) have registered with the listener, and are accepting connections.

ORA-12518: TNS:listener could not hand off client connection

ORA-12518: TNS:listener could not hand off client connection

Cause: The process of handing off a client connection to another process failed.

Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support.

ORA-12516: TNS:listener could not find available handler with matching protocol stack

ORA-12516: TNS:listener could not find available handler with matching protocol stack

Cause: None of the known and available service handlers for the given SERVICE_ NAME support the client s protocol stack: transport, session, and presentation protocols.

Action: Check to make sure that the service handlers (e.g. dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols.

ORA-12515: TNS:listener could not find a handler for this presentation

ORA-12515: TNS:listener could not find a handler for this presentation

Cause: None of the listener s known service handlers are registered as supporting the presentation protocol required by the connecting client.

Action: Check that the destination service is configured to accept the presentation protocol.

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action: services lamp;lt;lamp;nbsp;listener namelamp;gt; service name used specifies a service known by the listener. name specified is a service known by the listener.

ORA-12513: TNS:service handler found but it has registered for a different protocol

ORA-12513: TNS:service handler found but it has registered for a different protocol

Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client.

Action: Contact the DBA to register a dispatcher on your protocol.

ORA-12511: TNS:service handler found but it is not accepting connections

ORA-12511: TNS:service handler found but it is not accepting connections

Cause: The dispatchers notified the listener that they temporarily do not accept new connections.

Action: Attempt the connection again. If error persists, contact the DBA to check the state of the dispatchers and or or ask him to increase the number of dispatchers.

ORA-12510: TNS:database temporarily lacks resources to handle the request

ORA-12510: TNS:database temporarily lacks resources to handle the request

Cause: The dispatchers appear to be busy handling other requests.

Action: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers and or or dispatchers limit on number of connections or sessions that they can accept.

ORA-12509: TNS:listener failed to redirect client to service handler

ORA-12509: TNS:listener failed to redirect client to service handler

Cause: The dispatcher terminated unexpectedly

Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect.

ORA-12508: TNS:listener could not resolve the COMMAND given

ORA-12508: TNS:listener could not resolve the COMMAND given

Cause: d by incompatible Oracle Net or Net8 versions. Do not include in error manual.

Action: This is not seen in normal use of Oracle Net.

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action: services lamp;lt;lamp;nbsp;listener namelamp;gt; known by the listener.

ORA-12504: TNS:listener was not given the SID in CONNECT_DATA

ORA-12504: TNS:listener was not given the SID in CONNECT_DATA

Cause: The SID was missing from the CONNECT_DATA.

Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA.

ORA-12502: TNS:listener received no CONNECT_DATA from client

ORA-12502: TNS:listener received no CONNECT_DATA from client

Cause: No CONNECT_DATA was passed to the listener.

Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor.

ORA-12500: TNS:listener failed to start a dedicated server process

ORA-12500: TNS:listener failed to start a dedicated server process

Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly.

Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support.

ORA-12497: maximum combined categories exceeds string

ORA-12497: maximum combined categories exceeds string

Cause: The maximum number of descriptive categories plus release categories supported by the MLS policy was exceeded.

Action: Enter numbers that do not add up to more than the maximum.

ORA-12496: cannot change existing level, category, or release numbers

ORA-12496: cannot change existing level, category, or release numbers

Cause: You attempted to change the number assigned to level, category or releasability category.

Action: Change the character string representations, not the numbers.

ORA-12495: cannot disable an enabled level, category, or release category

ORA-12495: cannot disable an enabled level, category, or release category

Cause: You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may be exist in some database label, so cannot be disabled.

Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used.

ORA-12494: cannot insert or delete a level, category, or release category

ORA-12494: cannot insert or delete a level, category, or release category

Cause: You attempted to insert or delete a level, category, or release category definition.

Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used.

ORA-12493: invalid MLS binary label

ORA-12493: invalid MLS binary label

Cause: The MLS binary label contained an invalid value, was not the correct size, or contained a level, category, or release category that was not enabled.

Action: Check the DBA_MLS_LABELS view for the valid MLS labels.

ORA-12492: DBLOW cannot be changed

ORA-12492: DBLOW cannot be changed

Cause: You attempted to change the value of DBLOW after it had been set to any initial value. DBLOW can only be set once after initial database creation.

Action: To change DBLOW, you have to create a new database, set DBLOW to the new value, and import your data into the new database.

ORA-12491: DBHIGH value does not dominate DBLOW

ORA-12491: DBHIGH value does not dominate DBLOW

Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW.

Action: Enter a value for DBHIGH that dominates DBLOW.

ORA-12490: DBHIGH cannot be lowered

ORA-12490: DBHIGH cannot be lowered

Cause: You attempted to enter a value for DBHIGH that did not dominate the existing value of DBHIGH.

Action: Enter a value for DBHIGH that dominates the old value.

ORA-12489: default label not within clearance range

ORA-12489: default label not within clearance range

Cause: You attempted to enter a value for a default label that did not dominate the minimum clearance or was not dominated by the maximum clearance.

Action: Enter a default label value within the clearance range.

ORA-12488: maximum label does not dominate minimum label

ORA-12488: maximum label does not dominate minimum label

Cause: You attempted to enter a value for a clearance label that did not preserve the dominance relationship between the minimum and maximum labels.

Action: Enter label values that preserves the dominance relationship between the minimum and maximum.

ORA-12487: clearance labels not between DBHIGH and DBLOW

ORA-12487: clearance labels not between DBHIGH and DBLOW

Cause: You attempted to enter a value for a clearance label that was not dominated by DBHIGH or did not dominate DBLOW.

Action: Enter clearance label values between DBHIGH and DBLOW.

ORA-12486: effective max labels and min labels cannot be changed

ORA-12486: effective max labels and min labels cannot be changed

Cause: You attempted to enter a value for an effective min label or effective max label, but these labels cannot be changed.

Action: Enter NULL values for the effective minimum and maximum labels.

ORA-12485: new effective label not within effective clearance

ORA-12485: new effective label not within effective clearance

Cause: You attempted to enter a value for an effective label that did not dominate the effective min label or was not dominated by the effective max label.

Action: Enter a value between the min and the max labels.

ORA-12484: invalid OS label

ORA-12484: invalid OS label

Cause: The specified label does not exist in the OS host s label definition file.

Action: Use the OS label management tools to define the label.

ORA-12483: label not in OS system accreditation range

ORA-12483: label not in OS system accreditation range

Cause: The specified label is above the OS maximum label or below the OS minimum label.

Action: Use a label that is within the accreditation range for the host OS.

ORA-12482: internal MLS error: string Error: string

ORA-12482: internal MLS error: string Error: string

Cause: An internal MLS policy error occurred.

Action: Contact Oracle Customer Support.

ORA-12481: effective label not within program unit clearance range

ORA-12481: effective label not within program unit clearance range

Cause: The effective label when the program unit was invoked was not within the range authorized for the program unit.

Action: Modify the program unit clearance range or invoke the program unit from a session with an authorized effective clearance.

ORA-12480: specified clearance labels not within the effective clearance

ORA-12480: specified clearance labels not within the effective clearance

Cause: You specified a clearance range that was not within your authorized clearance; you can only specify clearance ranges that are within your clearance.

Action: Specify clearance labels that are within your own clearance range.

ORA-12479: file label string must equal DBHIGH string

ORA-12479: file label string must equal DBHIGH string

Cause: A database file had an OS label that did not match DBHIGH. Either DBHIGH was altered or the OS file was relabeled.

Action: Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file.

ORA-12477: greatest lower bound resulted in an invalid OS label

ORA-12477: greatest lower bound resulted in an invalid OS label

Cause: You tried to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system.

Action: Consult your OS label management documentation for information on invalid label generation.

ORA-12476: least upper bound resulted in an invalid OS label

ORA-12476: least upper bound resulted in an invalid OS label

Cause: You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system.

Action: Consult your OS label management documentation for information on invalid label generation.

ORA-12473: The procedure is disabled when Label Security is used with OID.

ORA-12473: The procedure is disabled when Label Security is used with OID.

Cause: Using Label Security with OID disabled this procedure.

Action: Do not use OID with Label Security if this procedure is required to function.

ORA-12472: policy string is being used

ORA-12472: policy string is being used

Cause: The policy which was being dropped due to event propagation from OID was applied to some table or schema.

Action: Drop a policy in OID only if it is not used in any of the databases using the policy.

ORA-12471: Specified compartment or group is not authorized for user

ORA-12471: Specified compartment or group is not authorized for user

Cause: The specified compartment or group is not in user s authorizations or the user does not have read on compartment or group specified for write.

Action: Enter an authorized compartment or group.

ORA-12470: NULL or invalid user label: string

ORA-12470: NULL or invalid user label: string

Cause: The label entered is NULL or not within the user s authorizations.

Action: Enter the authorized labels for the user.

ORA-12469: no user levels found for user string and policy string

ORA-12469: no user levels found for user string and policy string

Cause: No levels have been specified for the user.

Action: Enter the maximum and minimum labels for the user.

ORA-12468: max write level does not equal max read level

ORA-12468: max write level does not equal max read level

Cause: The level in the max write label must equal the level in the max read label.

Action: Enter max read and max write labels with the same level component.

ORA-12467: minimum label can contain a level only

ORA-12467: minimum label can contain a level only

Cause: You included compartments or groups in the minimum label.

Action: Enter only an authorized minimum level as the label.

ORA-12466: default level is greater than the user s maximum

ORA-12466: default level is greater than the user s maximum

Cause: The default level cannot be greater than the user s maximum.

Action: Enter an authorized level.

ORA-12465: Not authorized for read or write on specified groups or compartments

ORA-12465: Not authorized for read or write on specified groups or compartments

Cause: You included groups or compartments that are not in the user s list of groups and compartments authorized for read or write access.

Action: Include read access when authorizing groups or compartments for write access.

ORA-12464: invalid characters in label component string

ORA-12464: invalid characters in label component string

Cause: Label components can contain only alphanumeric characters, blanks, and underscores.

Action: Correct syntax of the label component.

ORA-12463: undefined group string for policy string

ORA-12463: undefined group string for policy string

Cause: The specified group is not defined for the policy.

Action: Correct the group identifier value.

ORA-12462: undefined compartment string for policy string

ORA-12462: undefined compartment string for policy string

Cause: The specified compartment is not defined for the policy.

Action: Correct the compartment identifier value.

ORA-12461: undefined level string for policy string

ORA-12461: undefined level string for policy string

Cause: The specified level is not defined for the policy.

Action: Correct the level identifier value.

ORA-12457: security label exceeded maximum allowable length

ORA-12457: security label exceeded maximum allowable length

Cause: An operation attempted to materialize a security label greater than 4000 bytes in length.

Action: Consult the Oracle Label Security documentation for information on how the length of a security label is calculated. Re-submit the operation once the problem has been corrected.

ORA-12456: label security startup in progress

ORA-12456: label security startup in progress

Cause: You attempted to connect to the database before the Oracle Label Security component was fully initialized.

Action: Wait until the database is fully open before attempting to connect.

ORA-12455: internal error in Label Security MMON cleanup task

ORA-12455: internal error in Label Security MMON cleanup task

Cause: An internal error occurred in the Label Security MMON cleanup task.

Action: Contact Oracle Customer Support.

ORA-12454: label string does not exist for policy string

ORA-12454: label string does not exist for policy string

Cause: The label tag or value you entered did not identify a label for the policy.

Action: Enter a label value or tag that is in use by the policy.

ORA-12453: label string already exists

ORA-12453: label string already exists

Cause: The label value you entered already exists.

Action: No action necessary; alter the label to change its tag or type.

ORA-12452: label tag string already exists

ORA-12452: label tag string already exists

Cause: The label tag value you entered is already in use for another label.

Action: Enter a different value for the label tag.

ORA-12451: label not designated as USER or DATA

ORA-12451: label not designated as USER or DATA

Cause: A label is either a DATA label, a USER label, or both DATA and USER.

Action: Enter TRUE for at least DATA or USER.

ORA-12450: LOB datatype disabled in LBAC initialization file

ORA-12450: LOB datatype disabled in LBAC initialization file

Cause: You tried to specify a LOB datatype for a column or attribute, but the use of the LOB datatype has been disabled.

Action: Change the LBAC initialization file to allow the creation of LOB columns and attributes.

ORA-12449: Labels specified for user must be of type USER

ORA-12449: Labels specified for user must be of type USER

Cause: You tried to set labels for a user, but the labels in the list were not all designated as USER labels.

Action: Alter the labels to be USER labels.

ORA-12448: policy string not applied to schema string

ORA-12448: policy string not applied to schema string

Cause: You tried to alter a schema policy that was not applied.

Action: Correct the policy name or schema name.

ORA-12447: policy role already exists for policy string

ORA-12447: policy role already exists for policy string

Cause: The role named lamp;lt;lamp;nbsp;policylamp;gt;_DBA already exists.

Action: Correct the policy name or delete the existing policy.

ORA-12446: Insufficient authorization for administration of policy string

ORA-12446: Insufficient authorization for administration of policy string

Cause: You tried to perform an administrative function for a policy, but you have not been granted the lamp;lt;lamp;nbsp;policylamp;gt;_DBA role.

Action: Grant the user the lamp;lt;lamp;nbsp;policylamp;gt;_DBA role for the specified policy.