Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility.
Action: Specify a valid facility error handling parameter value.
Cause: The policy could not convert the label string to a valid internal label.
Action: Correct the syntax of the label string.
Cause: The format string is not supported by the policy.
Action: Correct the syntax of the format string.
Cause: An internal label could not be converted to a valid label for the policy.
Action: Analyze any additional messages on the error stack and consult the policy documentation.
Cause: The policy could not interpret the privilege string.
Action: Specify a privilege string that is supported by the policy.
Cause: The policy determined that the label list was invalid for its intended use.
Action: Check the policy constraints on the specific list of labels.
Cause: The policy did not authorize the database session to perform the requested SQL statement.
Action: Grant the user or program unit the necessary policy privilege or additional authorizations.
Cause: The policy did not authorize the database session to perform the requested operation.
Action: Grant the user or program unit the necessary policy privilege or additional authorizations.
Cause: The specified policy does not support the requested operation.
Action: Consult the policy documentation to determine the supported access mediation operations.
Cause: The policy encountered an error during startup processing; access to the data protected by the policy is prohibited.
Action: Check the alert log for additional information, correct the policy error, and restart the instance.
Cause: The policy enforcement encountered an internal error.
Action: Consult the policy documentation for details.
Cause: The specified label value does not exist.
Action: Check the data dictionary views for the policy to identify valid labels.
Cause: The policy package does not exist in the database.
Action: Check that the policy package name is correct or install the required policy package.
Cause: The labels being compared belong to different policies.
Action: Only compare labels that belong to the same policy.
Cause: An internal label policy framework error occurred.
Action: Contact Oracle Support Services.
Cause: The datatype of the column present in the table is different from the datatype set for the policy column.
Action: Drop the column on the table or change the datatype for the policy column.
Cause: The specified policy does not exist in the database.
Action: Enter the correct policy name or create the policy.
Cause: The specified object was not in the database.
Action: Enter the correct name for the database object.
Cause: The specified user does not exist in the database.
Action: Correct the user name or create the user.
Cause: A null value was provided for a binary label operation.
Action: Provide a valid binary label for the operation.
Cause: The policy package did not contain all of the procedures and functions necessary to enforce the policy.
Action: Consult the label framework documentation for a list of required procedures and functions for a policy package.
Cause: The label sizes for the binary label operation were not equal.
Action: Provide binary labels with the same lengths for the operation.
Cause: You tried to create a new policy, but the maximum number of policies for the instance had already been created.
Action: Increase the size of the MAX_LABEL_POLICIES initialization parameter and restart the server.
Cause: The position specified for a binary label operation was invalid.
Action: Provide a position that is within the label size limits.
Cause: The length specified for a binary label operation exceeded the size of the binary label.
Action: Provide a bit or byte length that is within the label size limits.
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.
Action: Apply policies and set authorizations only for non-system users.
Cause: The option specified was not a valid audit option for the specified policy.
Action: Enter a correct audit option.
Cause: An input parameter was specified incorrectly.
Action: Correct the parameter value.
Cause: The specified index value was not between 1 and 6.
Action: Correct the index value for the label list operation.
Cause: The specified privilege number was not between 1 and 32.
Action: Correct the privilege number.
Cause: The specified audit action was not a valid audit action.
Action: Correct the audit action number.
Cause: LBAC enforcement resulted in an error.
Action: Correct the problem identified in the error message.
Cause: The policy could not be applied due to errors during the creation of a DML trigger.
Action: Correct the SQL syntax of the label function specification.
Cause: The audit type must be BY ACCESS or BY SESSION.
Action: Correct the audit type value.
Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.
Action: Correct the audit success value.
Cause: A NULL option string was specified, but no default schema or policy option string was found.
Action: Enter a valid option string, or alter the schema or policy to have a valid default option string.
Cause: A value that was not a valid policy option was entered.
Action: Correct the policy option value.
Cause: A policy option was entered more than once in the option string.
Action: Remove the duplicate policy option value.
Cause: A set of contradictory policy options was entered.
Action: Provide a set of compatible policy options.
Cause: The use of the SYSDBA package requires the LBAC_DBA role.
Action: Grant the LBAC_DBA role to the database user.
Cause: You tried to create a policy with the same name as an existing one.
Action: Use a different name or drop the existing policy.
Cause: You tried to create a policy with the same policy column name as an existing policy.
Action: Use a different name for the policy column or drop the existing policy.
Cause: You applied a policy to a schema, and some of the tables in the schema already had the policy applied.
Action: No action necessary; the policy was applied to the remaining tables.
Cause: You tried to apply a policy to a table that was already protected by the policy.
Action: To change the policy options, predicate, or label function, remove the policy from the table and re-apply it.
Cause: You tried to specify a different HIDE option for a table with an existing policy column.
Action: Drop the column from the table and re-apply the policy with the new HIDE option.
Cause: You tried to perform an administrative function for a policy, but you have not been granted the policy_DBA role.
Action: Grant the user the policy_DBA role for the specified policy.
Cause: The role named policy_DBA already exists.
Action: Correct the policy name or delete the existing policy.
Cause: You tried to alter a schema policy that was not applied.
Action: Correct the policy name or schema name.
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.
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.
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.
Cause: The label tag value you entered is already in use for another label.
Action: Enter a different value for the label tag.
Cause: The label value you entered already exists.
Action: No action necessary; alter the label to change its tag or type.
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.
Cause: The specified level is not defined for the policy.
Action: Correct the level identifier value.
Cause: The specified compartment is not defined for the policy.
Action: Correct the compartment identifier value.
Cause: The specified group is not defined for the policy.
Action: Correct the group identifier value.
Cause: Label components can contain only alphanumeric characters, blanks, and underscores.
Action: Correct syntax of the label component.
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.
Cause: The default level cannot be greater than the user's maximum.
Action: Enter an authorized level.
Cause: You included compartments or groups in the minimum label.
Action: Enter only an authorized minimum level as the label.
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.
Cause: No levels have been specified for the user.
Action: Enter the maximum and minimum labels for the user.
Cause: The label entered is NULL or not within the user's authorizations.
Action: Enter the authorized labels for the 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.
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.
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.
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.
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.
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.
Cause: An internal MLS policy error occurred.
Action: Contact Oracle Support Services.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW.
Action: Enter a value for DBHIGH that dominates 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.
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.
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.
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.
Cause: You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may exist in some database label, so it 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.
Cause: You attempted to change the number assigned to level, category or releasability category.
Action: Change the character string representations, not the numbers.
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.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
