Release 2 (9.2)
Part Number A96628-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Application Developer's Guide - Workspace Manager Release 2 (9.2) Part Number A96628-01 |
|
This appendix lists the Workspace Manager error messages, including the cause and recommended user action for each.
Cause: An attempt was made to version-enable a table that had a column with a name that has more than 28 characters.
Action: Ensure that all column names for the table are 28 characters or less.
Cause: An operation was executed on a workspace that was frozen.
Action: Unfreeze the workspace before retrying the operation.
Cause: A DML operation that modifies one or more values in columns in the primary key constraint was performed on a version-enabled table.
Action: Do not perform DML operations on columns in the primary key constraints of version-enabled tables.
Cause: DisableVersioning failed because there were open database transactions on the table to be version-disabled.
Action: The user with the open database transaction should issue a standard database commit or rollback.
Cause: An attempt was made to delete/update a record in a parent table of a referential integrity constraint with restrict option and there was a matching record in the child table of the integrity constraint. Restrict is a default property of a referential integrity constraint, the other being "on delete cascade", where the dependent rows in the child tables are deleted if corresponding rows in the parent table are deleted. The "cascade" option applies only to a delete from the parent table. An update of the parent table always follows the restrict option.
Action: Delete all matching records from the child table first.
Cause: An attempt was made to insert/update a record in a child table of a referential integrity constraint and there was no matching record in the parent table of the integrity constraint.
Action: Insert a matching record in the parent table first.
Cause: Import of a version-enabled database failed because the import platform did not have Workspace Manager installed.
Action: Install Workspace Manager on the import platform and retry.
Cause: Import of a version-enabled database failed because the import platform already had one or more version-enabled tables.
Action: The import platform may not have any version-enabled tables. A clean install of Workspace Manager is needed on the import platform.
Cause: Import of a version-enabled database failed because the import platform had either non-LIVE workspaces in the workspace hierarchy, or explicit savepoints in the LIVE workspace.
Action: The import platform may have only the LIVE workspace and there may be no explicit savepoints. A clean install of Workspace Manager is needed on the import platform.
Cause: An insert operation failed because it violated the table's primary key constraint.
Action: Ensure that the primary key is not violated by the insert operation in the current workspace.
Cause: A delete operation failed because the delete was being made in a non-latest version of a workspace.
Action: Ensure that the current session is on the latest version in the workspace by using the GotoWorkspace or GotoSavepoint procedures.
Cause: An insert operation failed because the insert was being made in a non-latest version of a workspace.
Action: Ensure that the current session is on the latest version in the workspace by using the GotoWorkspace or GotoSavepoint procedures.
Cause: An update operation failed because the update was made in a non-latest version of a workspace.
Action: Ensure that the current session is on the latest version in the workspace by using the GotoWorkspace or GotoSavepoint procedures.
Cause: This operation failed because it can only be invoked on a version-enabled table.
Action: Verify that the table is version-enabled.
Cause: CreateWorkspace failed because the workspace name contained a "/".
Action: Choose another workspace name that does not contain a "/".
Cause: DisableVersioning failed because only a user with WM_ADMIN_ROLE role can version-disable a table in another schema.
Action: Ensure that the invoking user has the required privileges before attempting to version-disable this table. Otherwise, have the owner of the table version-disable it.
Cause: EnableVersioning failed because only a user with WM_ADMIN_ROLE can version-enable a table in another schema.
Action: Ensure that the invoking user has the required privileges before attempting to version-enable this table. Otherwise, have the owner of the table version-enable it.
Cause: AlterWorkspace failed because only a user with WM_ADMIN_ROLE or the owner of the workspace can alter workspace attributes.
Action: Ensure that the invoking user has the required privileges before attempting to alter the workspace attributes. Otherwise, have the owner of the workspace alter the workspace attributes.
Cause: FreezeWorkspace failed because only a user with WM_ADMIN_ROLE or the owner of the workspace can freeze a workspace.
Action: Ensure that the invoking user has the required privileges before attempting to freeze the workspace. Otherwise, have the owner of the workspace freeze it.
Cause: SetWorkspaceLockModeOn failed because only a user with WM_ADMIN_ROLE role or the owner of the workspace can set the workspace lock mode.
Action: Ensure that the invoking user has the required privileges before attempting to set the workspace lock mode. Otherwise, have the owner of the workspace set the workspace lock mode.
Cause: AlterSavepoint failed because only a user with WM_ADMIN_ROLE role or the owner of the workspace or savepoint can alter the savepoint attributes.
Action: Ensure that the invoking user has the required privileges before attempting to alter the savepoint attributes. Otherwise, have the workspace owner or the savepoint owner alter the savepoint attributes.
Cause: DeleteSavepoint failed because only a user with WM_ADMIN_ROLE role or the owner of the workspace or savepoint can delete the savepoint.
Action: Ensure that the invoking user has the required privileges before attempting to delete the savepoint. Otherwise, have the workspace owner or the savepoint owner delete the savepoint.
Cause: CreateWorkspace failed because a workspace with the same name already existed in the system. Workspace Manager requires that workspace names be unique across the database.
Action: Choose another workspace name and retry.
Cause: A RollbackWorkspace operation was invoked on a non-leaf workspace across an implicit savepoint.
Action: Do not rollback over an implicit savepoint. To remove the implicit savepoint, merge or remove the descendant workspace.
Cause: MergeTable was invoked with the input workspace specified as the LIVE workspace. The LIVE workspace is the root workspace in the workspace hierarchy tree.
Action: Do not invoke MergeTable with the workspace parameter LIVE.
Cause: RefreshTable was invoked with the input workspace specified as the LIVE workspace. The LIVE workspace is the root workspace in the workspace hierarchy tree.
Action: Do not invoke RefreshTable with the workspace parameter LIVE.
Cause: A RollbackTable operation was invoked on a non-leaf workspace across an implicit savepoint.
Action: Do not rollback over an implicit savepoint. To remove the implicit savepoint, merge or remove the descendant workspace.
Cause: RollbackTable failed because the table to be rolled back is part of a referential integrity constraint.
Action: Use RollbackWorkspace or RollbackToSP instead.
Cause: MergeTable failed because the table to be merged is part of a referential integrity constraint.
Action: Use MergeWorkspace instead.
Cause: An attempt was made to drop a database user who owns one or more version-enabled tables.
Action: Ensure that all the version-enabled tables owned by the user have been explicitly disabled before attempting to drop the database user.
Cause: Workspace Manager does not support index-organized tables.
Action: Ensure the table to be version-enabled is not index-organized.
Cause: A DML operation failed because the row was previously locked.
Action: Wait for the lock on the row to be released or have the lock owner use the UnlockRows operation to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
Cause: A DML operation failed because the row was previously locked.
Action: Wait for the lock on the row to be released or have the lock owner use the UnlockRows operation to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
Cause: The operation failed because a lock could not be obtained on the row, since it was already locked.
Action: Wait for the lock on the row to be released or have the lock owner use the UnlockRows operation to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
Cause: The operation failed because a lock could not be obtained on the row, since it was already locked.
Action: Wait for the lock on the row to be released or have the lock owner use the UnlockRows operation to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
Cause: An attempt to drop or re-create a database procedure failed because that procedure was created by Workspace Manager.
Action: Do not drop or re-create this procedure.
Cause: DisableVersioning failed because the table had been modified in non-LIVE workspaces.
Action: Remove or merge all workspaces that have modified this table. Otherwise, use the FORCE option of DisableVersioning.
Cause: An attempt to drop a database table failed because it was involved in a foreign key relationship with a version-enabled table.
Action: Consult the WM_RIC_INFO view and version-disable the table that is involved in the foreign key relationship before attempting to drop the table.
Cause: An attempt was made to revoke a privilege that was not granted by the current user.
Action: Do not attempt to revoke this privilege.
Cause: SetWorkspaceLockModeOn failed because the workspace contained modifications from one or more version-enabled tables.
Action: Use SetLockingOn to set the session's lock mode. Use SetWorkspaceLockModeOn only for those workspaces that have not yet modified any version-enabled tables.
Cause: EnableVersioning failed because Workspace Manager can only version-enable tables owned by users other than SYS.
Action: Do not invoke EnableVersioning on tables owned by SYS.
Cause: CreateWorkspace failed because the workspace to be created was to be a child of a continually refreshed workspace. Continually refreshed workspaces carry with them the restriction that they must be leaf workspaces.
Action: Do not create a workspace off of a continually refreshed workspace.
Cause: The operation invoked failed because it required both ACCESS and MERGE privileges on the workspace on which it was invoked.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges on the workspace.
Cause: The operation invoked failed because it required ACCESS privileges on the parent workspace of the workspace it was invoked on.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges on the parent workspace.
Cause: CommitResolve failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
Cause: CompressWorkspace failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
Cause: CompressWorkspaceTree failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
Cause: DeleteSavepoint failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard data
Cause: GotoWorkspace failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
Cause: RollbackResolve failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
Cause: CommitResolve failed because BeginResolve was not previously invoked.
Action: To resolve conflicts, first issue a BeginResolve, then issue ResolveConflicts, and finally issue CommitResolve.
Cause: The operation invoked failed because it required both ACCESS and MERGE privileges on the workspace on which it was invoked.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges on the workspace.
Cause: The operation invoked failed because it required ACCESS privileges on the workspace on which it was invoked.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges on the workspace.
Cause: An operation failed because there were conflicts detected for the table.
Action: To resolve conflicts, first issue a BeginResolve, then issue ResolveConflicts, and finally issue CommitResolve. Otherwise, refrain from calling this operation.
Cause: An operation failed because there were conflicts detected for the table.
Action: To resolve conflicts, first issue a BeginResolve, then issue ResolveConflicts, and finally issue CommitResolve. Otherwise, refrain from calling this operation.
Cause: The operation invoked failed because it required ACCESS privileges on the workspace on which it was invoked.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges on the workspace.
Cause: The operation invoked failed because it required both ACCESS and REMOVE privileges on the workspace on which it was invoked.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges on the workspace.
Cause: EnableVersioning of the spatial table failed because the spatial metadata table already contained an entry for the table.
Action: Contact Oracle Support
Cause: RollbackResolve can be successful only if the user invoking it also invoked BeginResolve, or if the user invoking it had the WM_ADMIN_ROLE role.
Action: Ensure that the invoking user has the required privileges before attempting to invoke RollbackResolve. Otherwise, have the user that issued the BeginResolve operation invoke RollbackResolve.
Cause: An attempt to drop a database table or view failed because it was associated with a version-enabled table.
Action: version-disable the table first. In the case of a view, version-disable the table associated with the view.
Cause: The operation failed because the table passed in as input did not exist or was not version-enabled.
Action: Pass in an existing, version-enabled table as input.
Cause: CreateWorkspace failed because the session was in a non-latest version of the workspace.
Action: Ensure that the current session is on the latest version in the workspace by using the GotoWorkspace or GotoSavepoint procedures.
Cause: CreateSavepoint failed because the session was in a non-latest version of the workspace.
Action: Ensure that the current session is on the latest version in the workspace by using the GotoWorkspace or GotoSavepoint procedures.
Cause: An attempt was made to grant or revoke a privilege from/to the same user.
Action: Do not attempt to grant or revoke privileges from/to the same user. Privileges can only be granted or revoked between different users.
Cause: An attempt was made to version-enable a table with VIEW_WO_OVERWRITE or VIEW_W_OVERWRITE option and the cumulative length of the names of the primary key columns was greater than 600.
Action: Rename the primary key columns.
Cause: A grant operation was attempted with an invalid grantee parameter.
Action: The grantee may only be an existing user, role, or PUBLIC. Verify correct spelling of the grantee parameter.
Cause: An attempt was made to invoke a GrantWorkspacePriv or GrantSystemPriv operation with an invalid input parameter.
Action: Ensure that the valid parameters are passed to the GrantWorkspacePriv or GrantSystemPriv operation. The grant_option parameter may only be YES or NO.
Cause: GotoDate was invoked with an in_date time less than the create time of the current workspace.
Action: The in_date parameter for GotoDate must be greater than or equal to the create time for the current workspace.
Cause: An attempt was made to invoke a LockRows operation on a versioned table without the required privileges on the table.
Action: Ensure that the invoking user has the required privileges before invoking the operation. A lockRows operation requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table.
Cause: An attempt was made to invoke an UnlockRows operation on a versioned table without the required privileges on the table.
Action: Ensure that the invoking user has the required privileges before invoking the operation. An UnlockRows operation requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table.
Cause: An attempt was made to invoke a ResolveConflicts operation on a versioned table without the required privileges on the table.
Action: Ensure that the invoking user has the required privileges before invoking the operation. A ResolveConflicts operation requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table being conflict resolved.
Cause: An attempt was made to invoke an operation that required the specified privileges on the input workspace.
Action: Ensure that the invoking user has the required privileges before invoking the operation. Privileges can be granted using the GrantWorkspacePriv or the GrantSystemPriv procedures. Use the function GetPrivs to see which privileges you have on a workspace.
Cause: An attempt was made to invoke an operation that required the specified privileges on the parent workspace of the input workspace.
Action: Ensure that the invoking user has the required privileges before invoking the operation. Privileges can be granted using the grantWorkspacePriv or the grantSystemPriv procedures. Use the function GetPrivs to see which privileges you have on a workspace.
Cause: An attempt was made to invoke a CreateWorkspace operation from a workspace without the required privileges on the workspace.
Action: Ensure that the invoking user has the required privileges before invoking the operation. The invoking user must have CREATE privileges on a workspace to be allowed to create a workspace off of it. Privileges can be granted using the grantWorkspacePriv or the grantSystemPriv procedures. Use the function GetPrivs to see which privileges you have on a workspace.
Cause: An attempt was made to invoke the GrantWorkspacePriv or GrantSystemPriv operation without the required privileges to do so.
Action: Ensure that the invoking user has the required privileges to grant the privilege. A user needs to have been granted a privilege with the grant option to be able to grant it to others.
Cause: An attempt was made to invoke a Workspace Manager operation without the required privileges on the versioned table.
Action: Ensure that the invoking user has the required privileges before invoking the operation. All Workspace Manager workspace wide operations require the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on all versioned tables that were modified in the input workspace.
Cause: An attempt was made to invoke a Workspace Manager operation without the required privileges on the versioned table.
Action: Ensure that the invoking user has the required privileges before invoking the operation. All Workspace Manager workspace wide operations require the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on all versioned tables that were modified in the input workspace.
Cause: An Workspace Manager operation resulted in an internal error.
Action: Contact Oracle support to resolve the issue.
Cause: An invalid value was specified for the hist parameter of procedure EnableVersioning.
Action: Valid values for the hist parameter are NONE, VIEW_W_OVERWRITE, and VIEW_WO_OVERWRITE.
Cause: An attempt was made to invoke a Workspace Manager operation with an invalid where-clause parameter as input.
Action: Ensure that the input where-clause contains only valid column names and has proper syntax.
Cause: An attempt was made to invoke a Grant/Revoke Privilege operation with an invalid priv_type parameter.
Action: Ensure that the valid parameters are passed to the Grant/Revoke Privilege operation. The valid privilege types are: ACCESS_WORKSPACE, MERGE_WORKSPACE, ROLLBACK_WORKSPACE, REVOKE_WORKSPACE, and CREATE_WORKSPACE.
Cause: The FreezeWorkspace procedure was called with an invalid freezewriter parameter.
Action: Ensure that the freezewriter parameter passed in as input to the FreezeWorkspace procedure is an existing database user.
Cause: An invalid value was specified for the lock_mode parameter of procedure LockRows.
Action: Specify a valid value for lock_mode. The valid values for lock_mode are E and S (default is E).
Cause: An invalid value has been specified for the lock_mode parameter (fifth parameter) of procedure UnlockRows.
Action: Specify a valid value for lock_mode. The valid values for lock_mode are E, S, and ES (default is ES).
Cause: An invalid value has been specified for the all_or_user parameter (fourth parameter) of procedure UnlockRows.
Action: Specify a valid value for all_or_user. The valid values for all_or_user are ALL and USER (default is USER).
Cause: A user attempted to invoke IsWorkspaceOccupied on the LIVE workspace.
Action: Workspace Manager allows IsWorkspaceOccupied to be invoked only on workspaces other than LIVE. The LIVE workspace is the default workspace for any session that is connected and Workspace Manager does not monitor users in the LIVE workspace. Do not invoke this method on the LIVE workspace.
Cause: IsWorkspaceOccupied was invoked for a workspace on which the user did not have ACCESS privilege.
Action: IsWorkspaceOccupied can only be invoked for a workspace on which the user has ACCESS privilege.
Cause: An attempt was made to Freeze the LIVE workspace in NO_ACCESS mode. Workspace Manager does not support this mode for the LIVE workspace.
Action: Use one of (READ_ONLY, 1WRITER, 1WRITER_SESSION, WM_ONLY) modes to freeze the LIVE workspace.
Cause: LockRows was invoked for a workspace whose parent workspace was not accessible to the user.
Action: The user requires ACCESS privilege on the parent workspace of the workspace for which lockRows in invoked.
Cause: LockRows was invoked for a workspace on which the user did not have ACCESS privilege.
Action: The user requires ACCESS privilege on the workspace for which LockRows in invoked.
Cause: An attempt to place a shared/exclusive lock on a row in a versioned table failed because the row was already versioned in some other workspace.
Action: To update/delete/insert a row that was already versioned in some other workspace, the current session must turn locking off. Consult the table's _LOCK view to see which rows in this table are locked.
Cause: SetMultiWorkspaces was invoked with the name of a workspace on which the user did not have ACCESS privilege.
Action: Names of only those workspaces for which the user has ACCESS privilege can be passed to SetMultiWorkspaces.
Cause: This operation was invoked on a non-version-enabled table.
Action: This operation can only be invoked on a version-enabled table. Verify that the table is version-enabled. The xxx_VERSIONED_TABLES views show all the versioned tables in the database.
Cause: An attempt was made to invoke on Workspace Manager operation with a null savepoint name parameter.
Action: User must pass in a non-null savepoint parameter for this operation to succeed
Cause: A null value was passed in as input to a Workspace Manager operation
Action: A user must pass in a non-null workspace parameter for this operation to succeed
Cause: MergeTable was invoked with a null table name.
Action: Specify name of the version-enabled table to be merged.
Cause: SetMultiWorkspaces was invoked with more than 8 workspace names.
Action: Invoke SetMultiWorkspaces with 8 or fewer workspace names.
Cause: One of the Workspace Manager generated database triggers was not created properly.
Action: Contact Oracle support to resolve the issue.
Cause: An attempt was made to version-enable a table that was both parent and child tables of referential integrity constraints.
Action: Version-enable both tables (specifying a comma-delimited list of table names) in the same call to the EnableVersioning procedure.
Cause: An attempt was made to version-enable the parent table of a referential integrity constraint whose child table was not version-enabled.
Action: Before version-enabling a table T, all tables that are child tables of referential integrity constraints (excluding self referential integrity constraints) that have T as the parent table, must be version-enabled.
Cause: An attempt was made to version-enable a table that was the child table of a non-self referential integrity constraint with cascade option and that had a self referential integrity constraint defined on it.
Action: If application semantics permit, change the cascade option to the restrict option.
Cause: Force option was specified while version-disabling a table that was the parent table of a referential integrity constraint.
Action: Force option cannot be specified while version-disabling a table that is the parent table of a referential integrity constraint. Commit/rollback all changes done on this table in non-LIVE workspaces and then version-disable the table without the force option.
Cause: An attempt has been made to version-disable the child table of a referential integrity constraint whose parent table was still version-enabled.
Action: User must first disable the parent table before successfully version-disabling this table.
Cause: An attempt was made to version-enable a table that was the child table of a referential integrity constraint with another table and the owner of the table to be version-enabled did not have select privilege on the parent table.
Action: Workspace Manager requires that before version-enabling the child table of a integrity constraint, the child table owner must have select privilege on the parent table. Grant the required privilege before version-enabling.
Cause: An attempt was made to version-enable a table that was the parent table of a referential integrity constraint with another table and the owner of the table to be version-enabled did not have select/delete privilege on the child table.
Action: Workspace Manager requires that before version-enabling the parent table of a referential integrity constraint, the parent table owner must have select and delete privileges on the child table. Grant select and delete privileges on the child table to the owner of the table being version-enabled.
Cause: An attempt was made to version-enable a table that was the parent table of a referential integrity constraint with another table and the owner of the table to be version-enabled did not have select privilege on the child table.
Action: Workspace Manager requires that before version-enabling the parent table of a referential integrity constraint, the parent table owner must have select and delete privileges on the child table. Grant select and delete privileges on the child table to the owner of the table being version-enabled.
Cause: A triggering event of the form "insert OR update OR delete" was specified.
Action: Drop the trigger and re-create separate triggers (with identical bodies) for insert, update and delete.
Cause: An attempt was made to version-enable a table that had unique constraints defined on it.
Action: Drop the unique constraint on this table before version-enabling it. If the table needs to have a index for performance reasons, create a non-unique index on the relevant set of columns. Oracle will use the created index to optimize queries on the version-enabled table whenever appropriate.
Cause: An attempt was made to invoke RefreshTable or RefreshWorkspace and the user did not have ACCESS/MERGE privilege on the (child) workspace.
Action: Ensure that the invoking user has ACCESS and MERGE privileges on the (child) workspace before invoking RefreshTable or RefreshWorkspace. Privileges can be granted using the GrantWorkspacePriv or the GrantSystemPriv procedures. Use the function GetPrivs to see which privileges the current user has on a workspace.
Cause: An attempt was made to invoke RefreshTable or RefreshWorkspace and the user did not have ACCESS privilege on the parent workspace.
Action: Ensure that the invoking user has ACCESS privilege on the parent workspace before invoking RefreshTable or RefreshWorkspace. Privileges can be granted using the GrantWorkspacePriv or the GrantSystemPriv procedures. Use the function GetPrivs to see which privileges the current user has on a workspace.
Cause: An attempt was made to create a continually refreshed workspace off a non-LIVE workspace.
Action: Workspace Manager only supports creation of continually refreshed workspaces off the LIVE workspace. The user needs to be in the LIVE workspace before invoking CreateWorkspace for creating a continually refreshed workspace.
Cause: The ResolveConflicts procedure was invoked without calling the BeginResolve procedure first.
Action: Ensure that BeginResolve is invoked by the current user on a workspace before invoking ResolveConflicts for a version-enabled table in that workspace. (See the Resolving Conflicts section of the User Guide for details on the process of resolving conflicts for version-enabled tables.)
Cause: An attempt was made to invoke RollbackTable or RollbackWorkspace and the user did not have ACCESS/ROLLBACK privilege on the workspace.
Action: Ensure that the invoking user has ACCESS and ROLLBACK privileges on the workspace before invoking RollbackTable or RollbackWorkspace. Privileges can be granted using the GrantWorkspacePriv or the GrantSystemPriv procedures. Use the function GetPrivs to see which privileges the current user has on a workspace.
Cause: RollbackResolve procedure was invoked without calling the BeginResolve procedure first.
Action: Ensure that BeginResolve is invoked first before invoking RollbackResolve. (See the Resolving Conflicts section of the User Guide for details on the process of resolving conflicts for version-enabled tables.)
Cause: An attempt was made to create a savepoint whose name had more than 30 characters.
Action: Please choose a shorter savepoint name.
Cause: An attempt was made to create a savepoint whose name began with the string "ICP-".
Action: Choose a savepoint name that does not begin with the string "ICP-". Workspace Manager reserves names starting with "ICP-" for naming implicit savepoints.
Cause: An attempt was made to create a savepoint with the same name as an existing savepoint. Workspace Manager savepoint names must be unique within a workspace.
Action: Choose another savepoint name.
Cause: An attempt was made to invoke a Workspace Manager operation on a savepoint that did not exist in the specified workspace.
Action: Verify that the savepoint name is spelled correctly and that it exists in the specified workspace. Workspace names and savepoint names are case sensitive.
Cause: An attempt was made to invoke a Workspace Manager operation on a workspace that did not exist.
Action: Pass in an existing workspace name as input. Workspace names and savepoint names are case sensitive.
Cause: The user invoked a Workspace Manager operation that cannot proceed because the specified workspace has been frozen in the specified mode.
Action: Wait for the database session that holds the lock to release the lock. Refer to the User Guide for a description of the Workspace Manager operations allowed for different workspace freeze modes. Consult the xxx_WM_WORKSPACES view to see which workspaces are currently frozen.
Cause: A user attempted to CreateWorkspace with the name BASE.
Action: Workspace Manager considers "BASE" to be a reserved keyword. Therefore, Workspace Manager does not allow the workspace to be named BASE. Choose another workspace name.
Cause: A user attempted to CreateWorkspace with the name LIVE.
Action: Workspace Manager considers "LIVE" to be a reserved keyword. Therefore, Workspace Manager does not allow new workspaces to be named LIVE. Choose another workspace name.
Cause: A user attempted to create a workspace with the workspace name length greater than 30 characters.
Action: Workspace Manager limits workspace names to 30 characters. Choose a shorter workspace name.
Cause: A user attempted to invoke BeginResolve on a workspace that was already being conflict resolved by some other user.
Action: Workspace Manager allows only one user to resolve conflicts for a workspace at the same time. Wait until the user is finished resolving conflicts in the workspace and verify that the conflicts you are attempting to resolve still exist. Use the xxx_WORKSPACES views to check on the current resolve status of the workspace.
Cause: A user attempted to invoke a Workspace Manager operation on a workspace that was frozen internally for another Workspace Manager operation.
Action: Workspace Manager acquires internal freezes on workspaces for the duration of various Workspace Manager operations. Wait until Workspace Manager releases the internal freeze on the workspace. Refer to the User Guide for details on the freezes that Workspace Manager acquires for various workspace-wide operations. Use the xxx_WORKSPACES views to check on the current freeze status of the workspace.
Cause: An attempt was made to invoke a Workspace Manager operation on a table that did not exist.
Action: Verify that the table exists.
Cause: An attempt was made to execute a Workspace Manager operation that required that there be no open database transactions on the table.
Action: Ensure that all open database transactions on the specified table have completed before invoking the Workspace Manager operation.
Cause: The specified table is already version-enabled.
Action: To version-disable it, execute the DisableVersioning procedure. The xxx_VERSIONED_TABLES views show all the versioned tables in the database.
Cause: This operation can only be invoked on a version-enabled table.
Action: Verify that the specified table is version-enabled. The xxx_VERSIONED_TABLES views show all the versioned tables in the database.
Cause: An attempt was made to version-enable a table that did not have any primary key defined on it. Workspace Manager requires that a primary key exist on a version-enabled table.
Action: Add a primary key constraint on this table before version-enabling it.
Cause: An attempt was made to version-disable a table which another transaction was in the process of version-disabling.
Action: Wait until the other transaction finishes version-disabling the specified table. The xxx_VERSIONED_TABLES views show all the versioned tables in the database.
Cause: An attempt was made to version-enable a table which another transaction was in the process of version-enabling.
Action: Wait until the other transaction finishes version-enabling the specified table. The xxx_VERSIONED_TABLES views show all the versioned tables in the database.
Cause: An attempt was made to version-enable a table whose name was longer than 25 characters.
Action: Rename the table to a shorter table name.
Cause: An attempt to disable version a table has failed due to the existence of database transaction locks on the table.
Action: To successfully disable version this table, verify that there are no database transaction locks on the table.
Cause: An attempt was made to invoke the FreezeWorkspace procedure with an invalid freezemode parameter.
Action: The freezemode parameter for the FreezeWorkspace procedure must be one of (NO_ACCESS, READ_ONLY, 1WRITER, 1WRITER_SESSION, WM_ONLY). Ensure that FreezeWorkspace is invoked with the correct parameters.
Cause: An attempt was made to invoke the FreezeWorkspace procedure with an invalid freezewriter parameter.
Action: The freezewriter parameter for the FreezeWorkspace procedure can be non-null only when the freezemode parameter is 1WRITER. Ensure that FreezeWorkspace is invoked with the correct parameters.
Cause: The ResolveConflicts procedure was called with an invalid keep parameter.
Action: Ensure that the keep parameter to the ResolveConflicts procedure is one of (CHILD,PARENT,BASE). This parameter is not case sensitive. Refer to the Resolving Conflicts section of the User Guide for details on the process of conflict resolution.
Cause: An attempt was made to rollback the entire LIVE workspace. Workspace Manager only supports the RollbackToSP operation for the LIVE workspace.
Action: Use RollbackToSP to achieve the desired result.
Cause: A user attempted to invoke MergeWorkspace on the LIVE workspace.
Action: Workspace Manager disallows commit of the LIVE workspace. Do not invoke MergeWorkspace on the LIVE workspace.
Cause: A user attempted to invoke RemoveWorkspace on the LIVE workspace.
Action: To rollback changes in the LIVE workspace, use the RollbackToSP operation. To remove descendants to the LIVE workspace, use the RemoveWorkspace operation on the child workspaces.
Cause: A user attempted to invoke RefreshWorkspace on the LIVE workspace.
Action: Workspace Manager disallows the Refresh operation on the LIVE workspace. Do not invoke RefreshWorkspace on the LIVE workspace.
Cause: The user invoked a SetLockingOFF operation without having called SetLockingON earlier in the current session.
Action: A user can only execute SetLockingOff if the user had called SetLockingOn in the session. To see what the current lock mode is, use the GetLockMode function.
Cause: The user invoked a SetLockingON operation with an invalid lockMode parameter.
Action: Use a lockmode that Workspace Manager currently supports: E, or exclusive, and S, or shared. For a discussion of the differences and similarities between these two modes, refer to the Workspace Manager Guide.
Cause: An attempt was made to invoke the SetWorkspaceLockModeON operation for a workspace whose lock mode has already been set.
Action: To change the lock mode for a workspace, use the SetWorkspaceLockModeOFF procedure to first unset the lock mode.
Cause: An attempt was made to invoke a Workspace Manager operation that required the specified parent workspace to be unfrozen.
Action: Wait for the workspace to be unfrozen before invoking the Workspace Manager operation. The workspace can be unfrozen by the owner of the workspace or by a user with the WM_ADMIN_ROLE using the UnfreezeWorkspace procedure.
Cause: A workspace wide operation was invoked on an intermediate workspace. Workspace Manager supports this operation only on leaf workspaces. A leaf workspace is one that does not have any descendants.
Action: Invoke the operation only on leaf workspaces.
Cause: A CompressWorkspace or CompressWorkspaceTree operation resulted in this internal error.
Action: Contact Oracle support to resolve the issue.
Cause: An attempt was made to invoke the SetLockingON or the SetLockingOFF procedure while the current session was in a workspace whose lock mode was set without override.
Action: The lock mode can be changed by the current session only if the session is in a workspace whose lock mode has not been set or if the session is in a workspace whose lock mode has been set with the override option. Privileged users can change the lock mode for a workspace using the SetWorkspaceLockModeON and the SetWorkspaceLockModeOFF procedures.
Cause: An attempt was made to invoke a Workspace Manager operation with an invalid where_clause parameter as input.
Action: Ensure that the input where_clause contains only valid column names and has proper syntax. The where_clause for this Workspace Manager operation can contain only columns that are part of the primary key.
Cause: An attempt was made to invoke a Workspace Manager operation that required that there be no sessions in the specified workspace.
Action: To successfully invoke the Workspace Manager operation on the specified workspace, ensure that there are no sessions in the workspace. Privileged users can view all the sessions in a workspace using the DBA_WORKSPACE_USERS view.
Cause: An attempt was made to invoke CompressWorkspace with some sessions in the workspace being on non-LATEST savepoints in the workspace. CompressWorkspace requires that all sessions in the specified workspace be on the latest version of the workspace.
Action: All sessions in the specified workspace must either go to another workspace using GotoWorkspace or must go to the LATEST savepoint using GotoSavepoint. Privileged users can view all the sessions in a workspace using the DBA_WORKSPACE_USERS view.
Cause: An attempt was made to invoke a Workspace Manager procedure on the LIVE workspace.
Action: Invoke this Workspace Manager procedure only on non-LIVE workspaces.
Cause: An attempt to disable version a table failed due to the existence of database transaction locks on the table.
Action: To successfully disable version this table, verify that there are no database transaction locks on the table.
Cause: An attempt to disable version a table failed due to an internal error in granting/revoking appropriate privileges on the table being version-enabled.
Action: Contact Oracle support to resolve the issue.
Cause: An attempt was made to invoke a Workspace Manager operation that failed because Workspace Manager was unable to acquire an exclusive lock on the specified resource.
Action: The specified resource may have been locked by some other database session performing a Workspace Manager operation. Wait for the lock on the resource to be released before proceeding with the Workspace Manager operation.
Cause: The user attempted to invoke the UnlockRows operation on a workspace without ACCESS privileges on the workspace.
Action: The UnlockRows operation requires ACCESS privileges on the workspace. Invoke the UnlockRows operation only on workspaces that you have ACCESS privileges for.
Cause: A user attempted to invoke UnfreezeWorkspace on a workspace being conflict resolved. This workspace was frozen due to a user having issued a BeginResolve operation on it.
Action: To unfreeze it, issue a CommitResolve or a RollbackResolve. Only a user with WM_ADMIN_ROLE or the user who initiated the BeginResolve on the workspace can issue a Commit/Rollback Resolve for that workspace.
Cause: A user attempted to invoke RemoveWorkspace on an intermediate workspace. To prevent the occurrence of orphaned workspaces, RemoveWorkspace can only be invoked on leaf workspaces.
Action: Execute the RemoveWorkspaceTree procedure to remove the workspace and all its descendants.
Cause: An attempt was made to invoke the FreezeWorkspace procedure for a workspace that was already frozen.
Action: To freeze workspaces that are already frozen, use the FreezeWorkspace procedure with the force parameter.
Cause: A user attempted to invoke CommitResolve without having initiated the BeginResolve operation earlier and without having the WM_ADMIN_ROLE.
Action: CommitResolve can be invoked only by the user who initiated the BeginResolve operation or by a user who has the WM_ADMIN_ROLE.
Cause: A user called a procedure that requires that the lockMode parameter have a non-null value.
Action: The user must pass in a non-null lockMode parameter for this operation to succeed
Cause: An attempt was made to set the workspace lock mode off for a continually refreshed workspace.
Action: Do not attempt to turn off locking for continually refreshed workspaces.
Cause: UnfreezeWorkspace failed because only a user with WM_ADMIN_ROLE or the owner of the workspace can unfreeze a frozen workspace.
Action: Ensure that the invoking user has the required privileges before attempting to unfreeze the workspace. Otherwise, have the owner of the workspace unfreeze it.
Cause: LockRows failed because the row specified to be locked was already versioned.
Action: Do not attempt to lock rows that have already been versioned. Use the where_clause parameter of LockRows to specify those rows that have not already been versioned.
Cause: A Workspace Manager error occurred.
Action: Refer to the Workspace Manager Guide.
Cause: An attempt was made to uninstall Workspace Manager with existing version-enabled tables.
Action: Version-disable all version-enabled tables before attempting to uninstall Workspace Manager. Version-enabled tables can be disabled using the DisableVersioning procedure.
Cause: An attempt was made to create a workspace that is more than 30 levels in depth from the LIVE workspace.
Action: Do not create workspaces that are more than 30 levels in depth from the LIVE workspace.
Cause: An attempt was made to version-enable a table with one or more columns with an unsupported data type.
Action: Ensure that all the columns in the table being version-enabled are of supported data types. The currently unsupported data types for version-enabled tables are: LONG and LONG RAW.
Cause: An attempt was made to invoke the DeleteSavepoint procedure on an implicit savepoint with dependent child workspaces.
Action: Ensure that the savepoint being deleted is not implicit or it does not have any child workspaces created off of it. The xxx_WORKSPACES views show the parent savepoints for all the workspaces in the system. Ensure that the savepoint being deleted is not a parent savepoint for some workspace.
Cause: An attempt was made to version-enable a table that has a user defined trigger with compilation errors defined on it.
Action: Ensure that all user defined triggers on the table to be version-enabled have no compilation errors.
Cause: An attempt was made to version-enable a table where the sum of the column name lengths exceeded 8250 characters.
Action: Rename some of the table's columns to reduce the sum of the column name lengths.
Cause: An attempt was made to version-enable a table that has a user defined trigger with a trigger body length of more than 28000 characters defined on it.
Action: Ensure that all user defined triggers on the table to be version-enabled have trigger body lengths that are less than 28000 characters.
Cause: An attempt was made to version-enable a table where the length of all of the column names combined with the length of the largest trigger body defined on the table was too large.
Action: Reduce the length of the largest trigger body defined on this table and/or rename some of the table's columns to reduce the sum of the column name lengths.
Cause: An attempt was made to version-enable a table that has more than 31 primary key columns.
Action: Decrease the number of primary key columns on the table to 31, at most.
Cause: An attempt to drop or re-create a database trigger failed because that trigger was created by Workspace Manager.
Action: Do not drop or re-create this trigger.
Cause: An attempt to re-create a database view failed because it was associated with a version-enabled table.
Action: Do not re-create this view. The view will automatically be dropped when the table associated with it is version-disabled.
Cause: An attempt to version-enable the table failed because it had a column with the name as one of the following: VERSION, NEXTVER, DELSTATUS, LTLOCK, CREATETIME, or RETIRETIME.
Action: Rename the column to a different name.
Cause: An attempt to version-enable the table failed because it had an index on it with the index name being the name of the table (to version-enabled) with the prefix _PKI$ or _TI$.
Action: Re-create the index using a different name.
Cause: An attempt was made to execute an operation on a Workspace undergoing conflict resolution. A Workspace is under conflict resolution if BeginResolve method has been called on the workspace but CommitResolve or RollbackResolve has not been called yet.
Action: Wait for conflict resolution to either commit or rollback before trying the operation on the workspace.
Cause: An attempt was made to invoke the FreezeWorkspace procedure with an invalid freezewriter parameter.
Action: The freezewriter parameter of the FreezeWorkspace procedure must be null whenever the session_duration parameter is "TRUE". The freezewriter is implicitly assumed to be the currently connected session. Ensure that FreezeWorkspace is invoked with the correct parameters.
Cause: An attempt was made to invoke the FreezeWorkspace procedure with an invalid session_duration parameter.
Action: The session_duration parameter of the FreezeWorkspace must be TRUE when attempting to freeze a workspace in 1WRITER_SESSION mode. Ensure that FreezeWorkspace is invoked with the correct parameters.
Cause: If lightweight Disable-Versioning fails for some reason during the upgrade or downgrade.
Action: Contact Oracle Support with the upgrade or downgrade log.
Cause: The instance you are importing Workspace Manager into has some savepoints, workspaces, or version-enabled tables.
Action: Clean up savepoints, workspaces and version-enabled tables, or reinstall Workspace Manager before importing other Workspace Manager data.
Cause: When a structural operation like DisableVersioning is in progress on a table, another structural operation like BeginDDL was invoked.
Action: Complete the ongoing operation before calling a new one.
Cause: Internal error during the upgrade or downgrade.
Action: Contact Oracle Support with the upgrade or downgrade output log.
Cause: Internal error during downgrade.
Action: Contact Oracle Support with downgrade output log.
Cause: Lightweight enable-versioning failed for some reason during the upgrade or downgrade.
Action: Internal error: contact Oracle Support with the upgrade or downgrade output log.
Cause: Primary-key constraint could not be re-created during the upgrade or downgrade.
Action: Internal error: contact Oracle Support with the upgrade or downgrade log.
Cause: Insufficient privilege for freezing or unfreezing a workspace.
Action: Grant FREEZE_WORKSPACE privilege on the workspace, or FREEZE_ANY_WORKSPACE or WM_ADMIN_ROLE system privilege, to the user trying the operation.
Cause: A DDL operation is in the process of being committed on the table.
Action: Wait until the DDL operation is complete and then retry the current operation.
Cause: An attempt was made to rename the primary key constraint of the skeleton table associated with a version-enabled table.
Action: Rename the primary key constraint of the skeleton table to its original name and call the CommitDDL procedure again.
Cause: An attempt was made to add, drop, modify, or reorder the primary key columns of the skeleton table associated with a version-enabled table.
Action: Restore the primary key columns to their original state and call the CommitDDL procedure again.
Cause: A check/unique constraint was detected on the skeleton table associated with a version-enabled table.
Action: Check/unique constraints cannot be defined on a version-enabled table. Remove the constraint from the skeleton table and call the CommitDDL procedure again.
Cause: A partitioned/join index was detected on the skeleton table associated with a version-enabled table.
Action: Drop all partitioned/join indexes on the skeleton table and call the CommitDDL procedure again.
Cause: An index name with more than 26 characters was detected on the skeleton table associated with a version-enabled table.
Action: Rename the index and call the CommitDDL procedure again.
Cause: Enable/disable versioning or BeginDDL or CommitDDL is getting executed on this table.
Action: Wait until enable/disable versioning or BeginDDL or CommitDDL is complete and then retry the current operation. The operation getting executed on the table can be found by querying the ALL_WM_VERSIONED_TABLES view.
Cause: BeginDDL needs to executed on the table before the current operation can be performed.
Action: Call BeginDDL on the table and then perform the current operation again.
Cause: A column of the skeleton table associated with a version-enabled table was modified and versioned table contains non-null data in this column.
Action: Restore the column to its original state and call the CommitDDL procedure again.
Cause: Columns of the skeleton table associated with a version-enabled table were reordered.
Action: Restore the columns to their original state and call the CommitDDL procedure again. Reordering of columns can be achieved by first dropping columns in a DDL session and then adding columns in a subsequent DDL session.
Cause: A referential integrity constraint exists with a table not contained in the list of tables passed to enable/disable versioning.
Action: Add the table to the list passed to enable/disable versioning. If you do not want to version-enable this table not contained in the list, you need to version-enable the tables one at a time.
Cause: A cycle exists in the referential integrity constraints between tables passed to enable/disable versioning or a new referential constraint added between two skeleton tables caused a cycle in the referential constraints.
Action: Drop one of the referential constraints in the cycle and implement it using user-defined triggers.
Cause: DisableVersioning failed because the table had been modified in non-LIVE workspaces.
Action: Remove or merge all workspaces that have modified this table. Otherwise, use the FORCE option of DisableVersioning.
Cause: DisableVersioning failed because the table has a cascade referential constraint with a version-enabled child table that in turn is the parent table of another referential constraint.
Action: Version-disable the child and parent tables together.
Cause: A DDL session has already been started on the table.
Action: Wait until the previous DDL session has been committed or rolled back.
Cause: Deferrable option is not supported for referential integrity constraints defined on version-enabled tables.
Action: Re-create referential constraints that have the deferrable option to remove the deferrable option.
Cause: The skeleton table associated with a version-enabled table has a referential constraint with a table that is not a skeleton table.
Action: Drop this referential constraint. You can only define referential constraints between two skeleton tables.
Cause: A new referential integrity constraint was added between the skeleton tables of two version-enabled tables, but the parent table already had a cascade referential constraint with a non-version-enabled table.
Action: Drop the new referential integrity constraint between the skeleton tables and perform the current operation again.
Cause: A workspace operation or DML/DDL on a versioned table was attempted at a nonwriter replication site.
Action: Workspace Manager supports workspace operations and operations on versioned tables only on the writer site in a replication environment. Perform the operation on the writer site.
Cause: An attempt was made to generate replication support between sites running different versions of Workspace Manager.
Action: Replication can be set up only between sites running the same version of Workspace Manager. The version of Workspace Manager installed can be verified using the WM_INSTALLATION view.
Cause: An attempt was made to generate replication support with one of the nonwriter sites containing workspaces, savepoints or versioned tables.
Action: All the nonwriter sites in a replication environment are restricted from having any workspaces, savepoints or versioned tables when replication support is generated. Ensure that all the nonwriter sites do not contain any of the above mentioned objects. Versioned tables can be disabled using the DisableVersioning procedure. Workspaces can be dropped using the RemoveWorkspace procedure. Savepoints can be removed using the CompressWorkspaceTree procedure.
Cause: A Workspace Manager operation was issued in the presence of a replication environment.
Action: Look up the error specified and take the necessary action recommended for that error.
Cause: An error occurred when Workspace Manager was being migrated from one version to another.
Action: Examine the spool file to find the Oracle error that caused this error to occur. Correct the error and enter the following SQL statement while connected AS SYSDBA:
SQL> EXECUTE SYS.OWM_MIG_PKG.AllFixSentinelVersion;
Cause: An error occurred when Workspace Manager was being migrated from one version to another.
Action: The view ALL_WM_VT_ERRORS can be queried for more detailed information about the error. The RecoverMigratingTable or RecoverAllMigratingTables procedures can be used to recover one or more tables that were left in an inconsistent state. For more information, see Appendix B, "Migrating to Another Workspace Manager Release".
Cause: An error occurred when Workspace Manager was being migrated from one version to another.
Action: The view ALL_WM_VT_ERRORS can be queried for more detailed information about the error. The RecoverMigratingTable or RecoverAllMigratingTables procedures can be used to recover one or more tables that were left in an inconsistent state. For more information, see Appendix B, "Migrating to Another Workspace Manager Release".
Cause: A Workspace Manager operation was invoked without the requisite privileges.
Action: The WM_ADMIN_ROLE is required to invoke this specific operation. Ensure that the current user has the required privileges to invoke this operation.
Cause: A Workspace Manager operation was invoked in the presence of a replication environment.
Action: Look up the error specified and take the necessary action recommended for that error.
Cause: A Workspace Manager operation was invoked on the specified table in the presence of a replication environment.
Action: Look up the error specified for the table specified and take the necessary action recommended for that error.
Cause: An attempt was made to generate replication support between sites running incompatible versions of the database.
Action: Replication can be set up only between sites running the compatible versions of the Oracle database. All the different sites must run either a database version < `9.0.0.0.0' OR all the sites must have a database installed with version >= `9.0.0.0.0'. A configuration with some sites running a database with version < `9.0.0.0.0' and some sites running a database with version >= `9.0.0.0.0' is not supported.
Cause: An attempt was made to invoke a workspace operation on a table with a version state that is invalid.
Action: The table on which the operation was invoked has a version state that disallows the operation from being performed. Query the ALL_WM_VERSIONED_TABLES view to look up the version state for the specified table, and see the documentation for the ALL_WM_VERSIONED_TABLES view (in Section 3.6) for a definition of the possible version state values.
Cause: Enable Versioning of the table failed due to some error. This may occur due to insufficient resources or some unexpected Oracle error.
Action: Retry the operation after fixing the cause of the error.
Cause: If EnableVersioning fails for some reason, an attempt is made to bring back the table to original state. This error occurs when this undo attempt fails on the partially versioned tables.
Action: Check the ALL_WM_VT_ERRORS view to see the statement that failed and the error that occurred. After fixing the cause of the error, you can version-enable the table using EnableVersioning or disable versioning on the table using DisableVersioning. (Be careful if you specify 'ignore_last_error => TRUE' with DisableVersioning.)
Cause: DisableVersioning of the table failed due to some error. This may occur due to insufficient resources or some unexpected Oracle error.
Action: See the Usage Notes for the DisableVersioning procedure for information about handling the error.
|
 Copyright © 2000, 2002 Oracle Corporation. All Rights Reserved. |
|
