Cause: An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility.

Cause: The policy could not convert the label string to a valid internal label.

Cause: The format string is not supported by the policy.

Cause: An internal label could not be converted to a valid label for the policy.

Cause: The policy could not interpret the privilege string.

Cause: The policy determined that the label list was invalid for its intended use.

Cause: The policy did not authorize the database session to perform the requested SQL statement.

Cause: The policy did not authorize the database session to perform the requested operation.

Cause: The specified policy does not support the requested operation.

Cause: The policy encountered an error during startup processing; access to the data protected by the policy is prohibited.

Cause: The policy enforcement encountered an internal error.

Cause: The specified label value does not exist.

Cause: The policy package does not exist in the database.

Cause: The labels being compared belong to different policies.

Cause: An internal label policy framework error occurred.

Cause: The datatype of the column present in the table is different from the datatype set for the policy column.

Cause: The specified policy does not exist in the database.

Cause: The specified object was not in the database.

Cause: The specified user does not exist in the database.

Cause: A null value was provided for a binary label operation.

Cause: The policy package did not contain all of the procedures and functions necessary to enforce the policy.

Cause: The label sizes for the binary label operation were not equal.

Cause: You tried to create a new policy, but the maximum number of policies for the instance had already been created.

Cause: The position specified for a binary label operation was invalid.

Cause: The length specified for a binary label operation exceeded the the size of the binary label.

Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS schema or to set user labels/privileges for the SYS, SYSTEM, or LBACSYS user.

Cause: The option specified was not a valid audit option for the specified policy.

Cause: An input parameter was specified incorrectly.

Cause: The specified index value was not between 1 and 6.

Cause: The specified privilege number was not between 1 and 32.

Cause: The specified audit action was not a valid audit action.

Cause: LBAC enforcement resulted in an error.

Cause: The policy could not be applied due to errors during the creation of a DML trigger.

Cause: The audit type must be BY ACCESS or BY SESSION.

Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.

Cause: A NULL option string was specified, but no default schema or policy option string was found.

Cause: A value that was not a valid policy option was entered.

Cause: A policy option was entered more than once in the option string.

Cause: A set of contradictory policy options was entered.

Cause: The use of the SYSDBA package requires the LBAC_DBA role.

Cause: You tried to create a policy with the same name as an existing one.

Cause: You tried to create a policy with the same policy column name as an existing policy.

Cause: You applied a policy to a schema, and some of the tables in the schema already had the policy applied.

Cause: You tried to apply a policy to a table that was already protected by the policy.

Cause: You tried to specify a different HIDE option for a table with an existing policy column.

Cause: You tried to perform an administrative function for a policy, but you have not been granted the policy_DBA role.

Cause: The role named policy_DBA already exists.

Cause: An attempt was made to alter, enable or disable a schema or table policy that was not applied.

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

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

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

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

Cause: The label value you entered already exists.

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

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

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

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

Cause: A Label Security operation was attempted without enabling Oracle Label Security.

Cause: An administrative operation was attempted without configuring Oracle Label Security.

Cause: An attempt was made to disable Oracle Label Security when Database Vault was enabled.

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

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

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

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

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

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

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

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

Cause: No levels have been specified for the user.

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

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.

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

Cause: Using Label Security with OID disabled this procedure.

Cause: An attempt was made to change a column name for a policy that was applied on user schemas or tables.

Cause: An attempt was made to configure Oracle Label Security with OID in a pluggable database when Oracle Label Security without OID is configured in another pluggable database or vice-versa.

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.

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.

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

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

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

Cause: An internal MLS policy error occurred.

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

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

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.

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

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

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

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.

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

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

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.

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.

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

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.

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

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