Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
ORA-12400 DBLOW is not a valid operating system label
Cause: The operating system label corresponding to DBLOW has become invalid due to a change in operating system label definitions.
Action: Use the operating system facilities to restore the definition of this label, or change the value of DBLOW to a valid label. To change the value of DBLOW, you must mount the database and switch to OSMAC mode.
ORA-12401 DBHIGH is not a valid operating system label
Cause: The operating system label corresponding to DBHIGH has become invalid due to a change in operating system label definitions.
Action: Use the operating system facilities to restore the definition of this label, or change the value of DBHIGH to a valid label. To change the value of DBHIGH, you must mount the database and switch to OSMAC mode.
ORA-12402 file: string
Cause: Reporting file name for detail of another message.
Action: Examine the message stack for additional detail.
ORA-12403 file label (string) must be equal to DBHIGH (string)
Cause: An Oracle file was found to have a label that does not match the operating system equivalent of DBHIGH. This may be caused if DBHIGH has been changed, or if the file has been relabeled.
Action: Either relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file.
ORA-12404 device low (string) must be dominated by DBLOW (string)
Cause: A Oracle file was found on a device with an authorized range insufficient to handle the lowest labeled data in the file. DBLOW must always dominate the minimum device label.
Action: Lower the authorized minimum device label or move the file to a different device.
ORA-12405 device high (string) must dominate DBHIGH (string)
Cause: An Oracle file was found on a device with an authorized range insufficient to handle the highest labeled data in the file. DBHIGH must always be dominated by the maximum device label.
Action: Raise the authorized maximum device label or move the file to a different device.
ORA-12406 must be at DBHIGH (string) in OS to add files to a tablespace
Cause: A file was added to a new or existing tablespace by a user whose operating system label was not equal to DBHIGH.
Action: Log in to the operating system at DBHIGH to add the file. If you are creating a new tablespace, set your session label to the label at which you want the tablespace to be created, then create the tablespace. If you are adding a file to an existing tablespace, set your session label to match the creation label of the tablespace, then alter the tablespace See the Trusted Oracle7 Administrator's Guide for more detailed information about creating and altering tablespaces.
ORA-12407 cannot insert or update the ROWLABEL column of a view
Cause: An attempt was made to insert into or update the ROWLABEL column of a view. Trusted Oracle does not allow you to modify the ROWLABEL column of a view.
Action: While you cannot modify the ROWLABEL column of a view, you can modify the ROWLABEL column in the base table(s) of the view. Use the INSERT or UPDATE commands to modify the base tables(s); consequently, this modifies the view.
ORA-12408 tablespace previously existed at another label (string)
Cause: A tablespace by this name was previously created and dropped at another label. Part of the dictionary entry for the old tablespace remains, and the new tablespace is attempting to reuse the old entry.
Action: Either re-create the tablespace at the original label or choose a new name for this tablespace.
ORA-12409 DBLOW cannot be null in DBMS MAC mode
Cause: The database was started in DBMS MAC mode before resetting DBLOW.
Action: Restart the database in OS MAC mode and supply valid values for both DBHIGH and DBLOW before starting up in DBMS MAC mode.
ORA-12410 DBHIGH cannot be null in DBMS MAC mode
Cause: The database was started in DBMS MAC mode before resetting DBHIGH.
Action: Restart the database in OS MAC mode and supply valid values for both DBHIGH and DBLOW before starting up in DBMS MAC mode.
ORA-12411 DBHIGH must dominate DBLOW
Cause: DBHIGH does not dominate DBLOW.
Action: Restart the database in OS MAC mode and supply valid values for DBHIGH and DBLOW before starting up in DBMS MAC mode.
ORA-12412 Cannot raise DBLOW above string
Cause: You tried raise DBLOW above its current value. DBLOW can only be lowered; it cannot be raised.
Action: Do not attempt to raise DBLOW.
ORA-12413 Cannot lower DBHIGH below string
Cause: An attempt was made to lower DBHIGH below its current value. DBHIGH can only be raised.
Action: Do not attempt to lower DBHIGH.
ORA-12414 must be DBHIGH (string) to startup database
Cause: An attempt was made to open a database while at an operating system label not equal to DBHIGH.
Action: Login at DBHIGH to start the database.
ORA-12415 session label must dominate the creation label of role string
Cause: An attempt was made to grant a privilege to a role while at a label that does not dominate the role's creation label. Your DBMS label must dominate the role's creation label in order to grant a privilege to the role.
Action: Check the creation label of the role and perform the grant while at a label that dominates the creation label of the role.
ORA-12416 label of audit must dominate user
Cause: An attempt was made to set statement audit options for a user while at a label that does not dominate the user's creation label. Your DBMS label must dominate the user's creation label in order to set statement audit options for the user.
Action: Check the creation label of the user and set the statement audit option while at a label that dominates the creation label of the user.
ORA-12418 label of index must equal table
Cause: An attempt was made to create an index on a table while at a label that does not match the table's creation label. Your DBMS label must match the table's creation label in order to create an index on the table. If the table was created at DBHIGH or DBLOW, your label must be set to DBHIGH or DBLOW.
Action: Check the creation label of the table and create the index while at a label that matches the creation label of the table.
ORA-12419 label of column must equal table
Cause: An attempt was made to add a column to a table while at a label that does not match the table's creation label. Your DBMS label must match the table's creation label in order to add a column to the table.
Action: Check the creation label of the table and add the column while at a label that matches the creation label of the table.
ORA-12420 label of stored object must dominate referenced object string
Cause: An attempt was made to create or you issued a statement that tried to create a stored object (view, procedure, function, trigger) which references some object while at a label that does not dominate the referenced object's creation label. Your DBMS label must dominate the creation labels of all referenced objects in order to create a stored object. While the referenced object may be visible due to enabled MAC privileges, MAC privileges cannot be used to create the stored object.
Action: Check the creation labels of the referenced objects and create the stored object while at a label that dominates the creation labels of all referenced objects.
ORA-12421 label of grant must dominate object
Cause: An attempt was made to grant privileges on an object while at a label that does not dominate the object's creation label. Your DBMS label must dominate the object's creation label in order to grant privileges on the object.
Action: Check the creation label of the object and perform the grant while at a label that dominates the creation label of the object.
ORA-12422 label of grant must dominate grantee string
Cause: An attempt was made to grant privileges to a user while at a label that does not dominate the user's creation label. Your DBMS label must dominate the user's creation label in order to grant privileges to the user.
Action: Check the creation label of the user and grant the privileges while at a label that dominates the creation label of the user.
ORA-12423 label of constraint must equal table
Cause: An attempt was made to add a constraint to a table while at a label that does not match the table's creation label. Your DBMS label must match the creation label of the table in order to add a constraint to the table.
Action: Check the creation label of the table and add the constraint while at a label that matches the creation label of the table.
ORA-12424 label of object must dominate tablespace
Cause: An attempt was made to create an object in a tablespace while at a label that does not dominate the tablespace's creation label. Your DBMS label must dominate the tablespace's creation label in order to create an object in the tablespace.
Action: Check the creation label of the tablespace and create the object while at a label that dominates the creation label of the tablespace.
ORA-12425 label of table must dominate cluster
Cause: An attempt was made to create a table in a cluster while at a label that does not dominate the cluster's creation label. Your DBMS label must dominate the cluster's creation label in order to create a table in the cluster.
Action: Check the creation label of the cluster and create the table while at a label that dominates the creation label of the cluster.
ORA-12426 label of user must dominate default or temporary tablespace
Cause: An attempt was made to assign a user a default or temporary tablespace when the user's creation label did not dominate the tablespace's creation label. The user's creation label must dominate the tablespace's creation label in order for the default or temporary tablespace to be assigned to the user. Your DBMS label must dominate both the user's and the tablespace's creation labels in order to assign the tablespace to the user.
Action: Check the creation label of the default or temporary tablespaces and create the user so that the user's creation label dominates the creation label of the tablespaces.
ORA-12427 label of object must dominate schema
Cause: An attempt was made to create an object in a schema while at a label that does not dominate the schema's creation label. Your DBMS label must dominate the schema's creation label in order to create an object in the schema.
Action: Check the creation label of the schema and create the object while at a label that dominates the creation label of the schema.
ORA-12428 insufficient MAC privileges
Cause: An attempt was made to write to an object when you did not have sufficient privileges. You may have sufficient privileges to read the object, but do not have MAC write access to the object.
Action: Either retry the operation at the label of the object or ask the database administrator for sufficient MAC privileges to write the object. See the Trusted Oracle7 Administrator's Guide for more information on MAC privileges.
ORA-12429 label of comment must equal table or view
Cause: An attempt was made to comment a table or view while at a label that does not match the table's or view's creation label. Your DBMS label must match the table's or view's creation label in order to comment the table or view.
Action: Check the creation label of the table or view and add the comment while at a label that matches the creation label of the table or view.
ORA-12430 label of trigger must equal table
Cause: An attempt was made to create or you issued a statement that tried to create a trigger on a table while at a label that does not match the table's creation label. Your DBMS label must match the table's creation label in order to create the trigger on the table. While the table may be visible due to enabled MAC privileges, MAC privileges cannot be used to create a trigger.
Action: Check the creation label of the table and create the trigger while at a label that matches the creation label of the table.
ORA-12431 label of user must dominate default profile
Cause: An attempt was made to assign a user a default profile when the user's creation label did not dominate the default profile's creation label. In order to assign a default profile to a user, the user's creation label must dominate the default profile's creation label. Your DBMS label must dominate both the user's and the default profile's creation labels in order to assign the user the default profile.
Action: Check the creation label of the default profile and create the user so that the user's creation label dominates the creation label of the default profile.
ORA-12432 label of grant must equal label of procedure
Cause: An attempt was made to assign MAC privileges to a procedure at a label other than the creation label of the procedure.
Action: Grant MAC privileges to the procedure at the procedure's creation label.
ORA-12433 label of default role string must dominate user
Cause: An attempt was made to assign a default role to a user when the default role's creation label did not dominate the user's creation label. The default role's creation label must dominate the user's creation label. Your DBMS label also must dominate both the role's and user's creation label in order to assign a user a role.
Action: Check the creation labels of the user and role and assign only those roles whose creation labels dominate the creation label of the user.
ORA-12434 label of child record must dominate parent
Cause: An attempt was made to insert a child record with a label that does not dominate the corresponding parent record's label or update a parent record such that the child records would not dominate the corresponding parent's label. The label of a child record must always dominate that of its parent record.
Action: Check the label of the parent record and insert the child record while at a label that dominates the label of the parent record or update the label of the child record before updating the parent record so that the child can still dominate the parent after the update.
ORA-12435 label of package body must equal package
Cause: An attempt was made to create a package body while at a label that does not match the corresponding package's creation label. Your DBMS label must match the package's creation label in order to create a package body.
Action: Check the creation label of the package and create the package body while at a label that matches the creation label of the package.
ORA-12436 package body must exist to grant MAC privileges
Cause: An attempt was made to grant MAC privileges to a package when the package body does not exist.
Action: Create the package body for the package and then re-attempt the grant.
ORA-12437 cannot write down to a database at a lower label
Cause: An attempt was made to perform a write operation in a secondary database. You can only perform write operations in your primary database.
Action: Connect directly to the secondary database to perform the operation.
ORA-12438 insufficient privileges to validate constraint on all rows
Cause: You must have access to all rows in a table in order to attempt to enable a constraint.
Action: Either enable MAC privileges so that you can read all rows in the table, or downgrade all rows in the table so you can read them. Then enable the constraint.
ORA-12439 cannot modify ROWLABEL column
Cause: An attempt was made to modify the definition of the ROWLABEL column with the ALTER command. For example, you may have tried to lengthen the ROWLABEL column.
Action: Although the value of the ROWLABEL column can be changed, the ROWLABEL column definition cannot be modified.
ORA-12440 database has not been mounted in read-compatible mode
Cause: The requested secondary database was not started in read-compatible mode. In order for a database to be mounted by a higher level read-secure instance, the database must be mounted by its primary instance in read-compatible mode.
Action: Set the DB_MOUNT_MODE parameter to READ_COMPATIBLE in the secondary database and start the secondary database.
ORA-12441 grant already exists at a different label
Cause: An attempt was made to grant a privilege that was previously granted at a different label.
Action: Check USER_SYS_GRANTS or USER_OBJ_GRANTS to identify the label of the privilege's previous grant. If you want to execute the grant at the new label, revoke the old grant and regrant the privilege while at the new label.
ORA-12442 must be at same label as user to modify default roles
Cause: An attempt was made to modify a user's default roles while at a label that does not match the user's creation label. Your DBMS label must match the user's creation label in order to alter a user.
Action: Check the ALL_USERS view to determine the creation label of the user and modify the user's default roles while at a label that matches the creation label of the user.
ORA-12443 audit option already exists at a different label
Cause: An attempt was made to audit an event that was previously audited at a different label.
Action: Check the DBA_STMT_AUDIT_OPTS or DBA_PRIV_AUDIT_OPTS dictionary views to identify the label of the previous audit statement. If you want to audit the event at the new label, stop the old audit (using the NOAUDIT statement) and re-audit the event while at the new label.
ORA-12444 file label is lower than instance label
Cause: An attempt was made to reuse a file with a label different than the database instance label.
Action: Examine the message stack for the file name. Remove the file or relabel it to match the database instance label.
ORA-12446 file label is higher than instance label
Cause: An attempt was made to reuse a file with a label different than the database instance label. You can only reuse files labeled at or below the instance label.
Action: Examine the message stack for the file name. Remove the file or relabel it to match the database instance label.
ORA-12447 non-secure protocol used; connection denied
Cause: An attempt was made to connect to Trusted Oracle7 with a networking protocol that was not secure. You must use a secure networking protocol to connect via a remote location.
Action: Either connect to the database with a secure networking protocol or log in directly to the database.
ORA-12448 greatest lower bound resulted in an invalid operating system label
Cause: An attempt was made to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system.
Action: Examine the message stack for a more specific messages. See your installation or user's guide for information on invalid label generation. See the Trusted Oracle7 Administrator's Guide for information on greatest lower bound (GLB) functions.
ORA-12449 least upper bound resulted in an invalid operating system label
Cause: An attempt was made to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system.
Action: Examine the message stack for a more specific messages. See your installation or user's guide for information on invalid label generation. See the Trusted Oracle7 Administrator's Guide for information on least upper bound (LUB) functions.
ORA-12450 internal buffer overflow during label translation
Cause: An internal buffer used to translate labels overflowed. A possible cause could be a format mask you specified is too large.
Action: Try using a smaller format mask.
ORA-12451 format mask for TO_LABEL or TO_CHAR function is invalid
Cause: The format mask that you specified did not contain valid format codes for label conversion.
Action: Check the Trusted Oracle7 Administrator's Guide for valid format codes. Correct the format mask and reattempt the operation.
ORA-12452 error initializing label context
Cause: An internal error occurred that prevented initialization of the label context. This may be caused by internal memory corruption or a software defect.
Action: Contact Oracle Customer Support.
ORA-12453 binary label could not be translated into a string
Cause: The binary label that you specified for conversion is not valid.
Action: Check the source of the binary label. Execute the conversion with a valid binary label.
ORA-12454 input string does not contain expected punctuation or literal
Cause: The punctuation you supplied in the label string is inconsistent with the format you specified.
Action: Change the punctuation in the label string or format, whichever is appropriate, and reissue the statement.
ORA-12455 invalid internal format code found
Cause: In performing the requested translation, a format code was invalid. This message may result from memory corruption.
Action: Contact Oracle Customer Support.
ORA-12456 duplicate format code specified in string to label conversion
Cause: You may not specify duplicate string input when converting to a binary label. For example, 'SEN SENLEV' is an invalid format mask.
Action: Change the format mask and input string to specify a format code only once.
ORA-12457 invalid length for MLSLABEL bind variable
Cause: A bind variable of type MLSLABEL is too long.
Action: Consult your documentation for proper datatype lengths.
ORA-12458 the input string could not be translated into a binary label
Cause: The input string you specified is not a valid binary label on your operating system.
Action: Check the input string, change any components so that they form a valid label, and retry the operation.
ORA-12459 maximum number of columns in a Trusted Oracle table is 253
Cause: A CREATE or ALTER TABLE statement tried to add more than 253 columns (not counting ROWLABEL) to a table.
Action: Specify no more than 253 columns in your CREATE or ALTER TABLE command.
ORA-12460 the value string for the MLS_LABEL_FORMAT parameter is not valid
Cause: The value for the MLS_LABEL_FORMAT parameter you specified does not contain a valid format mask. You must have a valid MLS_LABEL_FORMAT parameter for the database to start.
Action: Change this parameter setting in your INIT.ORA file to a correct value.
ORA-12461 invalid binary label
Cause: You provided a binary label in an OCI program's bind statement that was not a valid operating system label.
Action: Replace the invalid binary label with one that is valid.
ORA-12470 process label could not be found
Cause: An error was encountered in translating the your operating system process label into a label number.
Action: Examine the message stack for a more specific message.
ORA-12475 cannot log in below DBLOW (string)
Cause: An attempt was made to log in at a label dominated by DBLOW. You can only log in to Trusted Oracle between DBLOW and DBHIGH, inclusive.
Action: Either log in at a higher label, or lower DBLOW.
ORA-12476 cannot log in above DBHIGH (string)
Cause: An attempt was made to log in at a label dominating DBHIGH. You can only log in to Trusted Oracle between DBLOW and DBHIGH, inclusive.
Action: Either log in at a lower label, or raise DBHIGH.
ORA-12477 cannot insert label below DBLOW (string)
Cause: An attempt was made to explicitly insert a value below DBLOW into the ROWLABEL column, or tried to specify a value lower than DBLOW in a column of datatype MLSLABEL. Any label you insert into Trusted Oracle table must fall between DBLOW and DBHIGH, inclusive.
Action: Either lower the value of DBLOW, or specify a higher label on the INSERT or UPDATE statement.
ORA-12478 cannot insert label above DBHIGH (string)
Cause: An attempt was made to explicitly insert a value above DBHIGH into the ROWLABEL column, or tried to specify a value higher than DBHIGH in a column of datatype MLSLABEL. Any label you insert into a Trusted Oracle table must fall between DBLOW and DBHIGH, inclusive.
Action: Either raise the value of DBHIGH, or specify a lower label on the INSERT or UPDATE statement.
ORA-12480 secondary database changing between OS MAC and DBMS MAC modes
Cause: An attempt was made to access a secondary database while the secondary database was in the process of changing between OS MAC and DBMS MAC modes.
Action: Re-attempt the operation after the change is complete.
ORA-12485 cannot find file label for string
Cause: An error was encountered while reading the label of the specified file.
Action: Examine the message stack for an operating system message.
ORA-12487 insufficient privileges to set label to DBHIGH or DBLOW
Cause: You must connect to Trusted Oracle using the INTERNAL keyword in order to set your label to DBHIGH or DBLOW.
Action: Connect to Trusted Oracle using INTERNAL, then set your label to DBHIGH or DBLOW. If you do not have privileges to connect using INTERNAL, contact your database administrator.
ORA-12488 session label must be equal to string
Cause: An attempt was made to log in to an OS MAC database at other than the database label.
Action: Log in from an OS process at the specified label.
ORA-12489 insufficient MAC privileges to alter your session label
Cause: An attempt was made to alter your session label without the appropriate MAC privileges. You must have the appropriate MAC privileges in order to dynamically change your session label. Note that MAC privileges are not available in an OS MAC database, only in a DBMS MAC database.
Action: To change your session label, do one of the following:
ORA-12490 cannot alter DBMS label below username creation label (string)
Cause: An attempt was made to alter your DBMS label to a label lower than that at which your username was created. You can only alter your DBMS label between your username's creation label and DBHIGH, within the limits of your clearance.
Action: Either do not alter your DBMS label below the specified label, or contact the database administrator to re-create your username at lower level.
ORA-12491 cannot change MAC mode when mounted in READ_COMPATIBLE mode
Cause: An attempt was made to change between OS and DB MAC mode while the database was mounted in READ_COMPATIBLE mode.
Action: Set the DB_MOUNT_MODE parameter to NORMAL and restart the database.
ORA-12494 cannot mount secondary database labeled above DBLOW
Cause: The secondary database that you attempted to mount is labeled above DBLOW in the primary database. You can only mount a secondary database if that DBHIGH in that database (or, in OS MAC mode, the label of the database) is lower than DBLOW in your primary database.
Action: Determine if you really want to establish a read-secure link between the two databases. If so, relabel the secondary database so that DBHIGH in the secondary database is lower than DBLOW in the primary database.
ORA-12495 multi-threaded server cannot be used with Trusted Oracle
Cause: The MTS_DISPATCHERS parameter is set in the initialization file, which initiated the configuration of the multi-threaded server.
Action: Remove the MTS_DISPATCHERS parameter from the initialization file and restart the instance.
