Skip Headers

Oracle® Database Application Developer's Guide - Workspace Manager
10g Release 1 (10.1)
Part Number B10824-01
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Feedback
Go to previous page
Previous		 Go to next page
Next
 View PDF

D Workspace Manager Error Messages

This appendix lists the Workspace Manager error messages, including the cause and recommended user action for each.

WM_ERROR_1 name of column 'string' has more than 28 characters
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.
WM_ERROR_2 'string' is not allowed for workspace: 'string' frozen in 'string' mode
Cause: An operation was executed on a workspace that was frozen.
Action: Unfreeze the workspace before retrying the operation.
WM_ERROR_3 cannot modify primary key values for version-enabled table
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.
WM_ERROR_4 There are open short transactions on this table.
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.
WM_ERROR_5 integrity constraint ('string'.'string') violated - child record found
Cause: An attempt was made to delete or update a record in a parent table of a referential integrity constraint with the 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 deletion 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.
WM_ERROR_6 integrity constraint ('string'.'string') violated - parent key not found
Cause: An attempt was made to insert or 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.
WM_ERROR_7 WM not found on the import platform
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.
WM_ERROR_8 the import platform cannot have any versioned tables
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.
WM_ERROR_9 the import platform has non-"LIVE" workspaces or explicit savepoints
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.
WM_ERROR_10 unique key violation
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.
WM_ERROR_11 need to be on the latest version to delete
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.
WM_ERROR_12 need to be on the latest version to insert
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.
WM_ERROR_13 need to be on the latest version to update
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.
WM_ERROR_14 'string'.'string' has not been version enabled
Cause: This operation failed because it can only be invoked on a version-enabled table.
Action: Verify that the table is version-enabled.
WM_ERROR_15 "/" is not allowed in a workspace name
Cause: CreateWorkspace failed because the workspace name contained a "/".
Action: Choose another workspace name that does not contain a "/".
WM_ERROR_16 "WM_ADMIN_ROLE" is required to version disable a table in another schema
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.
WM_ERROR_17 "WM_ADMIN_ROLE" is required to version enable a table in another schema
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.
WM_ERROR_18 "WM_ADMIN_ROLE" or ownership is required to alter workspace attributes
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.
WM_ERROR_19 "WM_ADMIN_ROLE" or ownership is required to freeze a workspace
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.
WM_ERROR_20 "WM_ADMIN_ROLE" or ownership is required to set workspace lock mode
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.
WM_ERROR_21 insufficient privileges to change savepoint attributes
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.
WM_ERROR_22 insufficient privileges to delete savepoint
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.
WM_ERROR_23 a workspace already exists with the name: 'string'
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.
WM_ERROR_24 a workspace cannot be rolled back over an implicit savepoint
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.
WM_ERROR_25 a table cannot be merged from the "LIVE" 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.
WM_ERROR_27 a table cannot be refreshed to the "LIVE" workspace
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.
WM_ERROR_28 a table cannot be rolled back over an implicit savepoint
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.
WM_ERROR_29 cannot rollback this table using RollbackTable
Cause: RollbackTable failed because the table to be rolled back is part of a referential integrity constraint.
Action: Use RollbackWorkspace or RollbackToSP instead.
WM_ERROR_30 cannot merge this table using MergeTable
Cause: MergeTable failed because the table to be merged is part of a referential integrity constraint.
Action: Use MergeWorkspace instead.
WM_ERROR_31 All version enabled tables owned by 'string' must be disabled first.
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.
WM_ERROR_32 An index-organized table cannot be version enabled.
Cause: Workspace Manager does not support index-organized tables.
Action: Ensure the table to be version-enabled is not index-organized.
WM_ERROR_33 attempt to 'string' a row locked by: 'string' in workspace 'string'
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 procedure to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
WM_ERROR_34 attempt to 'string' a row locked by 'string' in workspace: 'string'
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 procedure to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
WM_ERROR_35 attempt to lock a row locked in workspace: 'string'
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 procedure to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
WM_ERROR_36 attempt to lock a row locked by 'string'
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 procedure to unlock the row. Consult the table's _LOCK view to see which rows in this table are locked.
WM_ERROR_37 attempt to modify a WM generated procedure
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.
WM_ERROR_38 cannot disable version a table modified in non-LIVE workspaces
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.
WM_ERROR_39 cannot drop tables involved in foreign key relationships
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.
WM_ERROR_40 only grantor of a privilege may revoke it
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.
WM_ERROR_41 unable to set workspace lock mode
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.
WM_ERROR_42 cannot version enable tables owned by SYS
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.
WM_ERROR_43 A continually refreshed workspace must be a leaf workspace.
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.
WM_ERROR_44 insufficient privileges to merge data
Cause: The merge operation failed because the user does not have both ACCESS and MERGE privileges on the workspace on which it was invoked; or, in a multiparent workspace environment, the user does not have both ACCESS and MERGE privileges on the non-root workspaces and ACCESS privilege on the root workspace of the multiparent workspace graph.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges.
WM_ERROR_45 merge operation requires ACCESS privileges on the parent 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.
WM_ERROR_46 commit/rollback open short transactions before calling CommitResolve
Cause: CommitResolve failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
WM_ERROR_47 commit/rollback open short transactions before calling CompressWorkspace
Cause: CompressWorkspace failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
WM_ERROR_48 commit/rollback open short transactions before calling CompressWorkspaceTree
Cause: CompressWorkspaceTree failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
WM_ERROR_49 commit/rollback open short transactions before calling DeleteSavepoint
Cause: DeleteSavepoint failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard data
WM_ERROR_50 commit/rollback open short transactions before calling GotoWorkspace
Cause: GotoWorkspace failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
WM_ERROR_51 commit/rollback open short transactions before calling RollbackResolve
Cause: RollbackResolve failed because open database transactions existed.
Action: The user with the open database transaction should issue a standard database commit or rollback.
WM_ERROR_52 CommitResolve can be called only after BeginResolve has been invoked
Cause: CommitResolve failed because BeginResolve was not previously invoked.
Action: To resolve conflicts, first issue a BeginResolve, then issue ResolveConflicts, and finally issue CommitResolve.
WM_ERROR_53 CompressWorkspace operation requires ACCESS and MERGE privileges on the 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.
WM_ERROR_54 CompressWorkspace operation requires ACCESS privilege 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.
WM_ERROR_55 conflicts detected for workspace: 'string' in table: 'string'
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.
WM_ERROR_56 conflicts detected for workspace: 'string' in table: 'string'.'string'
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.
WM_ERROR_57 CreateSavepoint operation requires ACCESS 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.
WM_ERROR_58 RemoveWorkspace operation requires ACCESS and REMOVE 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.
WM_ERROR_59 entry already exists in spatial metadata table for 'string'_WM
Cause: EnableVersioning of the spatial table failed because the spatial metadata table already contained an entry for the table.
Action: Contact Oracle Support Services.
WM_ERROR_60 user must call BeginResolve or have WM_ADMIN_ROLE to invoke RollbackResolve
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.
WM_ERROR_61 versioned objects have to be version disabled before being dropped
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.
WM_ERROR_62 versioned table: 'string' does not exist
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.
WM_ERROR_63 need to be on the latest version to create a continually refreshed workspace.
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.
WM_ERROR_64 need to be on the latest version to create a savepoint
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.
WM_ERROR_65 grantor and grantee may not be the same user
Cause: An attempt was made to grant or revoke a privilege from or to the same user.
Action: Do not attempt to grant or revoke privileges from or to the same user. Privileges can only be granted or revoked between different users.
WM_ERROR_66 unable to version enable this table with history option
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.
WM_ERROR_67 grantee must be an existing user, an existing role or PUBLIC
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.
WM_ERROR_68 input parameter grant_option must be "YES" or "NO"
Cause: An attempt was made to invoke the GrantWorkspacePriv or GrantSystemPriv procedure with an invalid input parameter.
Action: Ensure that the valid parameters are passed to the GrantWorkspacePriv or GrantSystemPriv procedure. The grant_option parameter may only be YES or NO.
WM_ERROR_69 invalid in_date time for GotoDate
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.
WM_ERROR_70 insufficient privileges on 'string' to lock rows
Cause: An attempt was made to invoke the LockRows procedure 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. The lockRows procedure requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table.
WM_ERROR_71 insufficient privileges on 'string' to unlock rows
Cause: An attempt was made to invoke the UnlockRows procedure 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. The UnlockRows procedure requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table.
WM_ERROR_72 insufficient privileges on 'string'.'string'
Cause: An attempt was made to invoke the ResolveConflicts procedure 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. The ResolveConflicts procedure requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table being conflict resolved.
WM_ERROR_73 insufficient privileges to ACCESS the workspace: 'string'
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.
WM_ERROR_74 insufficient privileges to ACCESS the parent workspace: 'string'
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.
WM_ERROR_75 insufficient privileges to create a child workspace of: 'string'
Cause: An attempt was made to invoke the CreateWorkspace procedure 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.
WM_ERROR_76 insufficient privileges to grant 'string'
Cause: An attempt was made to invoke the GrantWorkspacePriv or GrantSystemPriv procedure 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.
WM_ERROR_77 insufficient privileges on the versioned table 'string'
Cause: An attempt was made to invoke a Workspace Manager procedure 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.
WM_ERROR_78 insufficient privileges on the versioned table: 'string'.'string'
Cause: An attempt was made to invoke a Workspace Manager procedure 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.
WM_ERROR_79 WM internal error ['string']
Cause: A Workspace Manager operation resulted in an internal error.
Action: Contact Oracle Support Services to resolve the issue.
WM_ERROR_80 invalid "hist" parameter for EnableVersioning
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.
WM_ERROR_81 invalid column name specified in the where-clause
Cause: An attempt was made to invoke a Workspace Manager procedure with an invalid where_clause parameter as input.
Action: Ensure that the input where_clause parameter contains only valid column names and has proper syntax.
WM_ERROR_82 invalid privilege type: 'string' was specified as input
Cause: An attempt was made to invoke a Grant or Revoke Privilege procedure with an invalid priv_type parameter.
Action: Ensure that the valid parameters are passed to the Grant or Revoke Privilege operation. The valid privilege types are: ACCESS_WORKSPACE, MERGE_WORKSPACE, ROLLBACK_WORKSPACE, REVOKE_WORKSPACE, and CREATE_WORKSPACE.
WM_ERROR_83 invalid user specified for the freezewriter parameter
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.
WM_ERROR_84 invalid value for lock_mode - "E" or "S" expected
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).
WM_ERROR_85 invalid value for the lock_mode argument - "E", "S" or "ES" expected
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).
WM_ERROR_86 invalid value for the all_or_user argument - "ALL" or "USER" expected
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).
WM_ERROR_87 IsWorkspaceOccupied cannot be used for "LIVE" workspace
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.
WM_ERROR_88 IsWorkspaceOccupied requires ACCESS privilege on the 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.
WM_ERROR_89 "LIVE" workspace can be frozen only in (READ_ONLY, 1WRITER, 1WRITER_SESSION, WM_ONLY) modes
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.
WM_ERROR_90 lock operation requires ACCESS privilege on the parent 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.
WM_ERROR_91 lock operation requires ACCESS privilege on the workspace
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.
WM_ERROR_92 cannot 'string' because locking is on and row is already versioned
Cause: An attempt to place a shared or exclusive lock on a row in a versioned table failed because the row was already versioned in some other workspace.
Action: To update, delete, or 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.
WM_ERROR_93 The multi-workspace view requires ACCESS privilege on the workspace : 'string'
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.
WM_ERROR_94 non-existent versioned table: 'string'.'string'
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.
WM_ERROR_95 null savepoint name passed in as input
Cause: An attempt was made to invoke a Workspace Manager procedure with a null savepoint name parameter.
Action: Pass in a non-null savepoint parameter for this procedure to succeed
WM_ERROR_96 null workspace name passed in as input
Cause: A null value was passed in as input to a Workspace Manager operation
Action: Pass in a non-null workspace parameter for this operation to succeed
WM_ERROR_97 null table name parameter passed in
Cause: MergeTable was invoked with a null table name.
Action: Specify the name of the version-enabled table to be merged.
WM_ERROR_98 Number of workspaces in the multi-workspace view cannot be greater than 8.
Cause: SetMultiWorkspaces was invoked with more than 8 workspace names.
Action: Invoke SetMultiWorkspaces with 8 or fewer workspace names.
WM_ERROR_99 WM failed to install - system triggers not properly created
Cause: One of the Workspace Manager generated database triggers was not created properly.
Action: Contact Oracle Support Services to resolve the issue.
WM_ERROR_100 'string' is both parent and child tables of referential integrity constraints
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.
WM_ERROR_101 child table must be version enabled
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, all tables that are child tables of referential integrity constraints (excluding self referential integrity constraints) that have this table as the parent table must be version-enabled.
WM_ERROR_102 cannot version enable this table
Cause: An attempt was made to version-enable a table that was the child table of a non-self referential integrity constraint with the 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.
WM_ERROR_103 cannot version disable this table with force option
Cause: The FORCE option was specified while version-disabling a table that was the parent table of a referential integrity constraint.
Action: The FORCE option cannot be specified while version-disabling a table that is the parent table of a referential integrity constraint. Commit or roll back all changes done on this table in non-LIVE workspaces and then version-disable the table without the FORCE option.
WM_ERROR_104 cannot version disable this table
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: Version-disable the parent table before version-disabling this table.
WM_ERROR_105 owner of constraint ('string'.'string') must have select privilege on the parent
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.
WM_ERROR_106 select and delete privileges needed on the child of constraint ('string'.'string')
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 or 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.
WM_ERROR_107 select privilege needed on the child of constraint ('string'.'string')
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.
WM_ERROR_108 triggering event 'string' not allowed
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.
WM_ERROR_109 a table with unique constraints cannot be version enabled
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.
WM_ERROR_112 insufficient privileges to refresh data
Cause: The refresh operation failed because the user does not have both ACCESS and MERGE privileges on the child workspace on which it was invoked; or, in a multiparent workspace environment, the user does not have both ACCESS and MERGE privileges on the non-root workspaces and ACCESS privilege on the root workspace of the multiparent workspace graph.
Action: Use the GetPrivs function to ensure that the user invoking this operation has the required privileges.
WM_ERROR_113 refresh operation requires ACCESS privileges on the parent 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 GetPrivs function to see which privileges the current user has on a workspace.
WM_ERROR_114 Continually refreshed workspaces can be created only off of the "LIVE" 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.
WM_ERROR_115 ResolveConflicts can be called only after BeginResolve is invoked
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.)
WM_ERROR_116 rollback operation requires ACCESS and ROLLBACK privileges on the workspace
Cause: An attempt was made to invoke RollbackTable or RollbackWorkspace and the user did not have ACCESS or 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.
WM_ERROR_117 RollbackResolve can be called only after BeginResolve has been invoked
Cause: RollbackResolve procedure was invoked without calling the BeginResolve procedure first.
Action: Ensure that BeginResolve is invoked before you invoke RollbackResolve. (See the Resolving Conflicts section of the User Guide for details on the process of resolving conflicts for version-enabled tables.)
WM_ERROR_118 savepoint names may not be longer than 30 characters
Cause: An attempt was made to create a savepoint whose name had more than 30 characters.
Action: Choose a shorter savepoint name.
WM_ERROR_119 savepoint names may not begin with \"ICP-\"
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.
WM_ERROR_120 savepoint: 'string' already exists in workspace: 'string'
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.
WM_ERROR_121 savepoint: 'string' does not exist in workspace: 'string'
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.
WM_ERROR_122 workspace 'string' does not exist
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.
WM_ERROR_123 workspace 'string' is currently frozen in 'string' mode
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. See the Workspace Manager documentation 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.
WM_ERROR_124 workspace name may not be "BASE"
Cause: A user attempted to create a workspace 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.
WM_ERROR_125 workspace name may not be "LIVE"
Cause: A user attempted to create a workspace 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.
WM_ERROR_126 workspace name may not exceed 30 characters
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.
WM_ERROR_127 workspace: 'string' is already being conflict resolved by user: 'string'
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.
WM_ERROR_128 workspace: 'string' is temporarily frozen in an internal mode for a 'string' operation
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. See 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.
WM_ERROR_129 table 'string' does not exist
Cause: An attempt was made to invoke a Workspace Manager operation on a table that did not exist.
Action: Verify that the table exists.
WM_ERROR_130 table 'string' has been modified in an open transaction
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.
WM_ERROR_131 table 'string' is already version enabled
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.
WM_ERROR_132 table 'string' is not version enabled
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.
WM_ERROR_133 table 'string' needs to have a primary key
Cause: An attempt was made to version-enable a table that did not have a 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.
WM_ERROR_134 table 'string' is already being version disabled
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.
WM_ERROR_135 table 'string' is being version enabled
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.
WM_ERROR_136 table names are limited to 25 characters
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.
WM_ERROR_138 table: 'string' is in use in other sessions
Cause: An attempt to version-disable a table has failed due to the existence of database transaction locks on the table.
Action: To successfully version-disable this table, verify that there are no database transaction locks on the table.
WM_ERROR_140 invalid value for FreezeMode parameter
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.
WM_ERROR_141 the parameter freezewriter can be non-null only for the 1WRITER mode
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.
WM_ERROR_142 the keep parameter must be one of ("PARENT","CHILD","BASE")
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. See the Resolving Conflicts section of the Workspace Manager documentation for details on the process of conflict resolution.
WM_ERROR_143 the "LIVE" workspace can only be rolled back to a savepoint
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.
WM_ERROR_144 the "LIVE" workspace cannot be merged
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.
WM_ERROR_145 the "LIVE" workspace cannot be removed
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.
WM_ERROR_147 the "LIVE" workspace cannot be refreshed
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.
WM_ERROR_148 the lock mode is currently not set for this session
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.
WM_ERROR_149 the lock mode must be one of ("C","E","S")
Cause: The user invoked a SetLockingON operation with an invalid lockmode parameter.
Action: Use a lock mode that Workspace Manager currently supports: E (exclusive) or S (shared). For a discussion of the differences and similarities between these two modes, see the Workspace Manager documentation.
WM_ERROR_150 the lock mode is already set for workspace: 'string'
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.
WM_ERROR_151 the parent workspace 'string' is currently frozen in 'string'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.
WM_ERROR_152 the workspace 'string' is not a leaf workspace
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.
WM_ERROR_153 the workspace: 'string' has savepoints in the branch specified
Cause: A CompressWorkspace or CompressWorkspaceTree operation resulted in this internal error.
Action: Contact Oracle Support Services to resolve the issue.
WM_ERROR_154 the workspaceLockMode for 'string' has been set to 'string' without override
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.
WM_ERROR_155 the where-clause can involve only primary key columns
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 parameter contains only valid column names and has proper syntax. The where_clause parameter for this Workspace Manager operation can contain only columns that are part of the primary key.
WM_ERROR_156 there are active sessions in the workspace: 'string'
Cause: An attempt was made to invoke a Workspace Manager operation that required that there be no sessions in the specified workspace (or, in a multiparent workspace environment, in any non-root workspaces in the multiparent workspace graph).
Action: To successfully invoke the Workspace Manager operation on the specified workspace, ensure that there are no sessions in the workspace or workspaces involved. Privileged users can view all the sessions in a workspace using the DBA_WORKSPACE_USERS view.
WM_ERROR_157 there are sessions on non-latest versions in the workspace: 'string'
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.
WM_ERROR_158 this procedure cannot be invoked on the "LIVE" workspace
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.
WM_ERROR_159 unable to exclusively lock table: 'string'.'string'
Cause: An attempt to version-disable a table failed due to the existence of database transaction locks on the table.
Action: To successfully version-disable this table, verify that there are no database transaction locks on the table.
WM_ERROR_160 unable to grant/revoke appropriate privileges
Cause: An attempt to version-disable a table failed due to an internal error in granting or revoking appropriate privileges on the table being version-enabled.
Action: Contact Oracle Support Services to resolve the issue.
WM_ERROR_161 unable to lock 'string': 'string' in 'string' mode
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.
WM_ERROR_162 unlock operation requires ACCESS privilege on the workspace
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.
WM_ERROR_163 use Commit/Rollback Resolve to unfreeze workspaces being conflict resolved
Cause: A user attempted to invoke UnfreezeWorkspace on a workspace undergoing conflict resolution. This workspace was frozen due to a user having issued a BeginResolve operation on it.
Action: To unfreeze the workspace, call the CommitResolve or a RollbackResolve procedure. Only a user with WM_ADMIN_ROLE or the user who initiated the BeginResolve operation on the workspace can issue a CommitResolve or RollbackResolve call for that workspace.
WM_ERROR_164 use the RemoveWorkspaceTree procedure to drop non-leaf workspaces
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.
WM_ERROR_165 use the force parameter to freeze a currently frozen workspace
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.
WM_ERROR_166 only a BeginResolve invoker or a WM_ADMIN_ROLE user can call CommitResolve
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.
WM_ERROR_167 null lockMode parameter passed in
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.
WM_ERROR_168 Cannot disable workspace lockmode for continually refreshed workspaces
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.
WM_ERROR_169 "WM_ADMIN_ROLE" or ownership is required to UnFreeze a workspace
Cause: UnfreezeWorkspace failed because only a user with the WM_ADMIN_ROLE 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.
WM_ERROR_170 The row to be locked has already been versioned
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.
WM_ERROR_171 WM error: 'string'
Cause: A Workspace Manager error occurred.
Action: See the Workspace Manager documentation.
WM_ERROR_172 all version enabled tables have to be disabled before uninstalling
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.
WM_ERROR_173 cannot create workspaces that are more than 30 levels deep
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.
WM_ERROR_174 table: 'string' contains columns with unsupported data types
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.
WM_ERROR_175 cannot delete implicit savepoints with dependent child workspaces
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.
WM_ERROR_176 A user trigger defined on 'string'.'string' has compilation errors.
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.
WM_ERROR_177 sum of length of all column names of 'string'.'string' exceeds 8250 characters
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.
WM_ERROR_178 user-defined trigger body defined on 'string'.'string' exceeds 28000 characters
Cause: An attempt was made to version-enable a table that has a user-defined trigger with a trigger body length of more than 28,000 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 28,000 characters.
WM_ERROR_179 combination of column name sizes and user-defined trigger lengths too large
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, rename some of the table's columns to reduce the sum of the column name lengths, or do both.
WM_ERROR_180 table 'string'.'string' has too many primary key columns
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.
WM_ERROR_181 attempt to modify a WM generated trigger
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.
WM_ERROR_182 attempt to modify a WM generated view
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.
WM_ERROR_183 reserved column name found
Cause: An attempt to version-enable the table failed because it had a column whose name started with WM$ or WM_ or had the same name as one of the following: VERSION, NEXTVER, DELSTATUS, LTLOCK, CREATETIME, or RETIRETIME.
Action: Rename the column to a different name.
WM_ERROR_184 reserved index name found
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.
WM_ERROR_185 operation disallowed on workspace 'string' involved in a conflict resolution session
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.
WM_ERROR_186 the parameter freezewriter must be null when session_duration is true',
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.
WM_ERROR_187 the parameter session_duration must be true for the 1WRITER_SESSION mod
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.
WM_ERROR_188 At least one table failed during lwDisableVersioning. Please query all_wm_vt_errors view to get the errors 'string'
Cause: If lightweight disable-versioning fails for some reason during the upgrade or downgrade.
Action: Contact Oracle Support Services with the upgrade or downgrade log.
WM_ERROR_189 workspaces, savepoints, or versioned tables cannot be present on the IMPORT platform
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.
WM_ERROR_190 table 'string' is in mutating state, no structural operations can be performed
Cause: When a structural operation (for example, DisableVersioning) is in progress on a table, another structural operation (for example, BeginDDL) was invoked.
Action: Complete the ongoing operation before calling a new one.
WM_ERROR_191 LWDisableVersioning not called on the table 'string'
Cause: Internal error during the upgrade or downgrade.
Action: Contact Oracle Support Services with the upgrade or downgrade output log.
WM_ERROR_192 At least one table failed during temporary disable-versioning 'string'
Cause: Internal error during downgrade.
Action: Contact Oracle Support Services with downgrade output log.
WM_ERROR_194 At least one table failed during lwEnableVersioning. Please query all_wm_vt_errors view to get the errors 'string'
Cause: Lightweight enable-versioning failed for some reason during the upgrade or downgrade.
Action: Internal error: contact Oracle Support Services with the upgrade or downgrade output log.
WM_ERROR_195 Following tables with VIEW_WO_OVERWRITE failed during recreation of PRIMARY KEY constraint 'string'
Cause: The primary key constraint could not be re-created during the upgrade or downgrade.
Action: Internal error: contact Oracle Support Services with the upgrade or downgrade log.
WM_ERROR_196 'string' operation requires ''FREEZE_WORKSPACE'' privilege on the workspace or ''FREEZE_ANY_WORKSPACE'' or ''WM_ADMIN_ROLE'' system privilege
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.
WM_ERROR_197 a ddl operation is being committed on 'string'
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.
WM_ERROR_198 primary key constraint of a version enabled table cannot be renamed
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.
WM_ERROR_199 primary key columns cannot be added/dropped/modified/reordered for version enabled tables
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.
WM_ERROR_200 unsupported constraint 'string' detected
Cause: A check or unique constraint was detected on the skeleton table associated with a version-enabled table.
Action: Check or unique constraints cannot be defined on a version-enabled table. Remove the constraint from the skeleton table and call the CommitDDL procedure again.
WM_ERROR_201 creation of partitioned/join indexes on version enabled tables is not supported
Cause: A partitioned or join index was detected on the skeleton table associated with a version-enabled table.
Action: Drop all partitioned or join indexes on the skeleton table and call the CommitDDL procedure again.
WM_ERROR_202 index name 'string' is longer than 26 characters
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.
WM_ERROR_203 enable/disable versioning or begin/commitDDL is being executed on 'string'
Cause: Versioning is being enabled or disabled, or BeginDDL or CommitDDL is being executed, on this table.
Action: Wait until the version-enabling, version-disabling, or BeginDDL or CommitDDL operation 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.
WM_ERROR_204 beginDDL not called on 'string'
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.
WM_ERROR_205 'string' contains data - cannot be modified
Cause: A column of the skeleton table associated with a version-enabled table was modified, and the versioned table contains non-null data in this column.
Action: Restore the column to its original state and call the CommitDDL procedure again.
WM_ERROR_206 column reordering is not supported
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.
WM_ERROR_207 referential integrity constraint exists with a table not contained in the list of specified tables
Cause: A referential integrity constraint exists with a table not contained in the list of tables passed to the EnableVersioning or DisableVersioning procedure.
Action: Add the table to the list passed to enable or 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.
WM_ERROR_208 cycle detected in referential integrity constraints on specified tables
Cause: A cycle exists in the referential integrity constraints between tables passed to enable or 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.
WM_ERROR_209 table 'string' has been modified in non-LIVE workspaces
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.
WM_ERROR_210 multi-level referential integrity constraint with cascade option detected
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.
WM_ERROR_211 DDL is being done on 'string'
Cause: A DDL session has already been started on the table.
Action: Wait until the previous DDL session has been committed or rolled back.
WM_ERROR_212 deferrable option not supported for integrity constraints
Cause: Deferrable option is not supported for referential integrity constraints defined on version-enabled tables.
Action: Re-create any referential constraints that have the deferrable option so that they do not have the deferrable option.
WM_ERROR_213 unsupported referential constraint with 'string' detected
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.
WM_ERROR_214 'string' has a cascade referential constraint with a non-version enabled table
Cause: A new referential integrity constraint was added between the skeleton tables of two version-enabled tables, but the parent table already had a cascading referential constraint with a table that is not version-enabled.
Action: Drop the new referential integrity constraint between the skeleton tables and perform the current operation again.
WM_ERROR_215 A savepoint cannot be created with the name "LATEST"
Cause: A savepoint cannot be named "LATEST".
Action: Choose another name for the savepoint.
WM_ERROR_216 workspace operations are disallowed for nonwriter replication sites
Cause: A workspace operation or DML or 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.
WM_ERROR_217 all replicated sites must have the same version of OWM installed
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.
WM_ERROR_218 workspaces, savepoints or versioned tables cannot be present on nonwriter replication sites
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 previously 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.
WM_ERROR_219 replication error at site ‘string': [‘string']
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.
WM_ERROR_220 Following tables failed during sentinel row adjustment ‘string'
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;
WM_ERROR_221 ‘string' could not be recovered from Migration Error: [‘string']
Cause: An error occurred when Workspace Manager was being migrated from one version to another.
Action: The ALL_WM_VT_ERRORS view 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".
WM_ERROR_222 Following tables could not be recovered from Migration Error: ‘string'
Cause: An error occurred when Workspace Manager was being migrated from one version to another.
Action: The ALL_WM_VT_ERRORS view 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" in the Workspace Manager documentation.
WM_ERROR_223 WM_ADMIN_ROLE is required to invoke this procedure
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.
WM_ERROR_224 replication error: [‘string']
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.
WM_ERROR_225 replication error for table ‘string': [‘string']
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.
WM_ERROR_227 replicated sites database versions must all be < '9.0.0.0.0' or >= '9.0.0.0.0'
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.
WM_ERROR_228 this operation is not allowed for table ‘string' with version state ‘string'
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 5.12) for a definition of the possible version state values.
WM_ERROR_229 statement 'string' failed during EnableVersioning. Error: string'
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.
WM_ERROR_230 table 'string' failed during UndoEnableVersioning/DisableVersioning. Error: string'
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.)
WM_ERROR_231 table 'string' failed during DisableVersioning. Error: string'
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.
WM_ERROR_232 unique constraint 'string'.'string' violated'
Cause: The DML operation or workspace operation violated the unique constraint 'string'.'string' on a version-enabled table.
Action: Find the row that violates the constraint, and attempt the operation without the row.
WM_ERROR_233 deadlock detected when trying to acquire lock for 'string': 'string', session may have open database transactions'
Cause: The workspace operation with an auto_commit value of TRUE is invalid if the current session has an open database transaction on that workspace.
Action: Commit or roll back the current database transaction before invoking the procedure, or invoke the procedure with an auto_commit value of FALSE.
WM_ERROR_234 continually-refreshed workspaces may have only continually-refreshed workspaces as children
Cause: An attempt was made to create a workspace that is not continually refreshed as a child of a continually refreshed workspace
Action: Continually refreshed workspaces can have only continually refreshed workspaces as child workspaces.
WM_ERROR_235 invalid system parameter name or value
Cause: An invalid string was passed as a name or value for a parameter for GetSystemParameter or SetSystemParameter.
Action: Check the documentation for valid names and values of Workspace Manager system parameters.
WM_ERROR_236 system setting does not allow invocation of this procedure'
Cause: UnlockRows cannot be called if the Workspace Manager system parameter NONCR_WORKSPACE_MODE is set to PESSIMISTIC_LOCKING.
Action: If no data exists in workspaces that are not continually refreshed, you can set NONCR_WORKSPACE_MODE is set to OPTIMISTIC_LOCKING. To see the current Workspace Manager system parameter settings, use the WM_INSTALLATION metadata view.
WM_ERROR_237 integrity constraint ('string'.'string') violated in workspace 'string' or one of its descendants - child record found
Cause: An attempt was made to delete or update a record in a parent table of a referential integrity constraint with the RESTRICT option, and there was a matching record in the child table of the integrity constraint in the identified workspace or one of its continually refreshed descendant workspaces.
Action: Delete or roll back matching child table records first.
WM_ERROR_238 integrity constraint ('string'.'string') violated in workspace 'string' or one of its descendants - parent key not found
Cause: An attempt was made to insert or 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 in the identified workspace or one its continually refreshed descendant workspaces.
Action: Insert a matching record in the parent table or roll back deleted matching parent table records first.
WM_ERROR_239 integrity constraint ('string'.'string') violated in a descendant workspace - parent key not found
Cause: An attempt was made to insert or 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 in a continually refreshed descendant workspace of the current workspace.
Action: Insert a matching record in the parent table or roll back deleted matching parent table records first.
WM_ERROR_240 reserved character found in workspace name
Cause: The name of a workspace contains one or more of these characters: "/", "*", ",", "$", "#"
Action: Remove these characters or replace them with valid characters.
WM_ERROR_241 system parameter 'string' should be set to 'string' for multiparent functionality'
Cause: The Workspace Manager system parameter is not set correctly to allow multiparent workspaces.
Action: Check the documentation about Workspace Manager system parameters, and be sure that any values required for multiparent workspace support are set correctly.
WM_ERROR_242 'string' already in ancestor hierarchy of 'string'
Cause: The workspace that is being added as a parent workspace is already an ancestor of the (child) workspace.
Action: Ensure that a workspace is not already an ancestor of a workspace to which it is to be added as a parent workspace.
WM_ERROR_243 all workspaces under the root of multiparent graph must be same type'
Cause: In a multiparent workspace graph, all workspaces must be either continually refreshed or not continually refreshed.
Action: Ensure that the workspaces under the root of a multiparent graph are either all continually refreshed or all not continually refreshed. You can use the ChangeWorkspaceType procedure to change the workspace type between continually refreshed and not continually refreshed.
WM_ERROR_244 AddAsParentWorkspace operation requires ACCESS privilege on all nodes except root in the graph and CREATE privilege on the new parent workspace'
Cause: The user in the multiparent workspace environment does not have the specified privileges.
Action: Use the function GetPrivs to ensure that the user invoking this operation has the required privileges.
WM_ERROR_245 'string' is not multi-parent of 'string'
Cause: For a RemoveWorkspaceAsParent operation, the workspace to be removed was not previously added as a parent workspace.
Action: Ensure that you have specified the correct workspace.
WM_ERROR_246 'string' cannot be removed because data has been versioned from the workspace branch being removed
Cause: In a multiparent workspace environment, if data has been versioned in the multiparent leaf workspace from any of the workspaces that will be removed as ancestors by this operation, the operation is not allowed.
Action: Roll back the leaf workspace to remove the versioned data from the branch being removed.
WM_ERROR_247 the multi-parent graph formed by 'string' is not a leaf graph
Cause: In a multiparent workspace environment, there is a workspace that is a child of some non-root workspace of the multi-parent graph on which this operation was invoked.
Action: Remove all the workspaces that are children of non-root workspaces of the graph before performing this operation.
WM_ERROR_248 intermediate workspaces of a multiparent graph cannot be refreshed
Cause: In a multiparent workspace environment, only the leaf workspace of a multiparent graph can be refreshed.
Action: Ensure that you are refreshing the correct workspace.
WM_ERROR_249 primary key constraint violated for 'string.string'
Cause: In a multiparent workspace environment, the primary key constraint for the table is violated, as viewed from the leaf workspace of the multiparent graph.
Action: Delete or roll back one of the rows that is shown as a duplicate.
WM_ERROR_250 workspace name may not be "NULL"
Cause: An attempt was made to name a workspace "NULL".
Action: Choose another name for the workspace.
WM_ERROR_251 attempt to 'string' a row locked by 'string' in workspace 'string' in mode '"WE"
Cause: Only the user that locked the row in WE mode can further edit the row in the same workspace.
Action: The row cannot be edited by the current user until the locking user removes the lock on the row.
WM_ERROR_252 attempt to 'string' a row locked by 'string' in mode "VE"
Cause: Only the user who locked the row in VE mode can further edit the row.
Action: The row cannot be edited by the current user until the locking user removes the lock on the row.
WM_ERROR_253 lock_mode of only ''VE'' is allowed when workspace is "NONE"
Cause: A value of NONE for the workspace parameter is permitted only with VE as the value for lock_mode.
Action: Specify the name of an existing workspace when specifying a lock_mode value other than VE.
WM_ERROR_254 cannot 'string' because PESSIMISTIC_LOCKING is on and row is already versioned'
Cause: The DML operation cannot be executed because system parameter CR_WORKSPACE_MODE or NONCR_WORKSPACE_MODE is set to PESSIMISTIC_LOCKING and the DML operation violates the system setting.
Action: If data has not been versioned in non-LIVE workspaces, you can change the PESSIMISTIC_LOCKING setting to OPTIMISTIC_LOCKING. To see the current Workspace Manager system parameter settings, use the WM_INSTALLATION metadata view.
WM_ERROR_255 insufficient privileges ['string']
Cause: An attempt was made to invoke an import or export operation without the required privileges.
Action: Ensure that the user has the required privileges before invoking the operation. To import from or export to a staging table, the user must have privileges to select from and perform DML operations on the staging table.
WM_ERROR_256 'string' cannot be invoked with a null 'string' parameter
Cause: The specified parameter cannot be null.
Action: Reissue the operation using a non-null value for the specified parameter.
WM_ERROR_257 savepoint 'string' does not exist in 'string''s hierarchy
Cause: The ancestor savepoint for an import operation does not exist in the hierarchy of the workspace.
Action: Specify a savepoint that is contained in the workspace's hierarchy.
WM_ERROR_258 specified system where clause is invalid ['string'']
Cause: An import or export operation was invoked with an invalid system WHERE clause.
Action: Ensure the compatibility of the system WHERE clause in conjunction with the parameters for the operation.
WM_ERROR_259 table 'string' is invalid ['string']
Cause: The staging table has been modified from its original state required for an import or export operation.
Action: Restore the staging table to its original state.
WM_ERROR_260 Export error ['string']
Cause: Unable to perform the export operation due to the specified error.
Action: Fix the error and retry the appropriate operation.
WM_ERROR_261 Import error ['string']
Cause: Unable to perform the import operation due to the specified error.
Action: Fix the error and retry the appropriate operation.
WM_ERROR_262 this parameter cannot be set to 'PESSIMISTIC_LOCKING' if data has been versioned in Non-LIVE workspaces'
Cause: This setting is not permitted if data exists in non-LIVE workspaces.
Action: If you want to use the PESSIMISTIC_LOCKING setting, ensure that there is no data versioned in non-LIVE workspaces for the workspace type (continually refreshed or not continually refreshed) for which the parameter is being set.
WM_ERROR_ 263 minimum version of workspace manager with replication support is 9.0.1.0.0
Cause: An attempt was made to set up replication support on a database with a release number less than 9.0.1.0.0.
Action: Upgrade to release 9.0.1.0.0 or higher of the database.
WM_ERROR_264 replication group 'string' already exists on this site
Cause: An attempt was made to set up replication support with a group name that already exists on the local site.
Action: Choose a different group name.
WM_ERROR_265 replication is already set up for this site with group 'string'
Cause: An attempt was made to set up replication support on a site where replication support already exists.
Action: Drop existing replication support before setting it up again.
WM_ERROR_266 replication support does not exist on this site
Cause: An operation related to replication was invoked without replication support existing on the local site.
Action: Set up support for replication using the DBMS_WM.GenerateReplicationSupport procedure before invoking this operation.
WM_ERROR_267 this operation has to be executed from the writer site 'string'
Cause: An operation related to replication was invoked on a site which is not the master definition (same as writer) site.
Action: Invoke this operation from the specified writer site.
WM_ERROR_268 the new master definition site must be a master site for the group
Cause: An operation related to replication was invoked with a site name passed in as a parameter that is not a master site for the replication group set up for Workspace Manager.
Action: Invoke the operation by passing a master site as the site name for the new master definition site parameter.
WM_ERROR_269 'string' is already the master definition site for the group 'string'
Cause: An attempt was made to change the master definition site to a site which is already the master definition site for the replication group set up for Workspace Manager.
Action: Invoke the operation by passing a different master site as the site name for the new master definition site parameter.
WM_ERROR_270 this operation has to be executed from the old writer site 'string'
Cause: An attempt was made to invoke a replication related operation, such as DBMS_WM.SynchronizeSite, from a site which is not the old writer site.
Action: Invoke the operation from the old writer site.
WM_ERROR_271 all version-enabled tables at the local site must exist at all remote sites as non-versioned tables
Cause: An attempt was made to set up replication with a mismatch in the set of version-enabled tables between the master definition site and other master sites. Workspace Manager requires that all version-enabled tables at the local master definition site exist as non-versioned tables at all remote sites specified as master sites.
Action: Invoke the operation after ensuring that all version-enabled tables at the local master definition site exist as non-versioned tables at all remote sites specified as master sites.
WM_ERROR_272 invalid event name: 'string'
Cause: An invalid Workspace Manager event name was passed as an argument to the function.
Action: Pass a valid event name. See the WM_EVENTS_INFO view for a list of all valid events.
WM_ERROR_273 set system parameter 'ALLOW_CAPTURE_EVENTS' to 'ON' for capturing events
Cause: An attempt was made to capture an event even though the Workspace Manager system parameter ALLOW_CAPTURE_EVENTS was set to OFF.
Action: Call SetSystemParameter to set ALLOW_CAPTURE_EVENTS to ON, and retry the operation.
WM_ERROR_274 this parameter cannot be set to 'OFF' when some events are set to be captured
Cause: An attempt was made to disallow the capture of Workspace Manager events while one or more types of events were set to be captured.
Action: Turn off event capture by calling SetCaptureEvents('ALL_EVENTS','OFF'), and retry the operation.
WM_ERROR_275 invalid value for capture - 'ON' or 'OFF' expected
Cause: The SetCaptureEvent procedure was called with an invalid value for the capture parameter.
Action: Specify either ON or OFF for the capture parameter.
WM_ERROR_276 this parameter cannot be set to 'OFF' when some multiparent workspaces exist
Cause: An attempt was made to set ALLOW_MULTI_PARENT_WORKSPACES to OFF when one or more multiparent workspaces existed in the system.
Action: Remove all multiparent workspaces by using any combination of the RemoveAsParentWorkspace, MergeWorkspace, and RemoveWorkspace procedures.
WM_ERROR_277 system parameter 'ALLOW_NESTED_TABLE_COLUMNS' cannot be set to 'OFF' when a version enabled table exists containing a nested table column
Cause: An attempt was made to set ALLOW_NESTED_TABLE_COLUMNS to OFF when one or more version-enabled tables contained a nested table column.
Action: Disable versioning on all tables that contain a nested table column.
WM_ERROR_278 'string' cannot be version enabled because system parameter 'ALLOW_NESTED_TABLE_COLUMNS' has been set to 'OFF'
Cause: An attempt was made to version-enable a table containing a nested table column and the Workspace Manager system parameter ALLOW_NESTED_TABLE_COLUMNS was set to OFF.
Action: Call DBMS_WM.SetSystemParameter to set ALLOW_NESTED_TABLE_COLUMNS to ON, and retry the operation.
WM_ERROR_279 histogram stats not found for table 'string.string' on column 'string'
Cause: Required histogram statistics have not been collected on the specified column.
Action: Use ANALYZE TABLE ... ESTIMATE STATISTICS FOR COLUMNS ... to collect the histogram statistics; then try the operation again.
WM_ERROR_280 datatype of column 'string' in table 'string.string' not supported for batch updates
Cause: The specified data type cannot be used for batches of PRIMARY_KEY_RANGE.
Action: Specify the batch size as TABLE.
WM_ERROR_281 batch_size parameter must be 'TABLE' or 'PRIMARY_KEY_RANGE'
Cause: The batch_size parameter value was invalid.
Action: Specify the batch_size parameter value as TABLE or PRIMARY_KEY_RANGE.
WM_ERROR_282 number of batches must be between 1 and 1000
Cause: The value specified for the Workspace Manager system parameter NUMBER_OF_COMPRESS_BATCHES was invalid.
Action: Specify a number from 1 to 1000 (inclusive).
Go to previous page
Previous		 Go to next page
Next
 Oracle
Copyright © 2000, 2003 Oracle Corporation
All Rights Reserved.
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Master Index
Master Index		 Go to Feedback page
Feedback