B
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 which 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 short transactions on the table to be version-disabled.

Action: The user with the open short 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/update a record in a parent table of a referential integrity constraint with restrict option and there was a matching record in the child table of the integrity constraint. Restrict is a default property of a referential integrity constraint, the other being "on delete cascade", where the dependent rows in the child tables are deleted if corresponding rows in the parent table are deleted. The "cascade" option applies only to a delete from the parent table. An update of the parent table always follows the restrict option.

Action: Delete all matching records from the child table first.

WM_ERROR_6 integrity constraint ('string'.'string') violated - parent key not found

Cause: An attempt was made to insert/update a record in a child table of a referential integrity constraint and there was no matching record in the parent table of the integrity constraint.

Action: Insert a matching record in the parent table first.

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 operation 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 operation 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 operation 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 operation 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 merge 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_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 short transactions existed.

Action: The user with the open short 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 short transactions existed.

Action: The user with the open short 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 short transactions existed.

Action: The user with the open short 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 short transactions existed.

Action: The user with the open short transaction should issue a standard data

WM_ERROR_50 commit/rollback open short transactions before calling GotoWorkspace

Cause: GotoWorkspace failed because open short transactions existed.

Action: The user with the open short 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 short transactions existed.

Action: The user with the open short 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

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/to the same user.

Action: Do not attempt to grant or revoke privileges from/to the same user. Privileges can only be granted or revoked between different users.

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 a GrantWorkspacePriv or GrantSystemPriv operation with an invalid input parameter.

Action: Ensure that the valid parameters are passed to the GrantWorkspacePriv or GrantSystemPriv operation. The grant_option parameter may only be YES or NO.

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 a LockRows operation on a versioned table without the required privileges on the table.

Action: Ensure that the invoking user has the required privileges before invoking the operation. A lockRows operation requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table.

WM_ERROR_71 insufficient privileges on 'string' to unlock rows

Cause: An attempt was made to invoke an UnlockRows operation on a versioned table without the required privileges on the table.

Action: Ensure that the invoking user has the required privileges before invoking the operation. An UnlockRows operation requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table.

WM_ERROR_72 insufficient privileges on 'string'.'string'

Cause: An attempt was made to invoke a ResolveConflicts operation on a versioned table without the required privileges on the table.

Action: Ensure that the invoking user has the required privileges before invoking the operation. A ResolveConflicts operation requires the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on the versioned table being conflict resolved.

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 a CreateWorkspace operation from a workspace without the required privileges on the workspace.

Action: Ensure that the invoking user has the required privileges before invoking the operation. The invoking user must have CREATE privileges on a workspace to be allowed to create a workspace off of it. Privileges can be granted using the grantWorkspacePriv or the grantSystemPriv procedures. Use the function GetPrivs to see which privileges you have on a workspace.

WM_ERROR_76 insufficient privileges to grant 'string'

Cause: An attempt was made to invoke the GrantWorkspacePriv or GrantSystemPriv operation without the required privileges to do so.

Action: Ensure that the invoking user has the required privileges to grant the privilege. A user needs to have been granted a privilege with the grant option to be able to grant it to others.

WM_ERROR_77 insufficient privileges on the versioned table 'string'

Cause: An attempt was made to invoke a Workspace Manager operation without the required privileges on the versioned table.

Action: Ensure that the invoking user has the required privileges before invoking the operation. All Workspace Manager workspace wide operations require the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on all versioned tables that were modified in the input workspace.

WM_ERROR_78 insufficient privileges on the versioned table: 'string'.'string'

Cause: An attempt was made to invoke a Workspace Manager operation without the required privileges on the versioned table.

Action: Ensure that the invoking user has the required privileges before invoking the operation. All Workspace Manager workspace wide operations require the invoking user to have SELECT, INSERT, UPDATE and DELETE privileges on all versioned tables that were modified in the input workspace.

WM_ERROR_79 WM internal error ['string']

Cause: An Workspace Manager operation resulted in an internal error.

Action: Contact Oracle support 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 operation with an invalid where-clause parameter as input.

Action: Ensure that the input where-clause contains only valid column names and has proper syntax.

WM_ERROR_82 invalid privilege type: 'string' was specified as input

Cause: An attempt was made to invoke a Grant/Revoke Privilege operation with an invalid priv_type parameter.

Action: Ensure that the valid parameters are passed to the Grant/Revoke Privilege operation. The valid privilege types are: ACCESS_WORKSPACE, MERGE_WORKSPACE, ROLLBACK_WORKSPACE, REVOKE_WORKSPACE, and CREATE_WORKSPACE.

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, 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, 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/exclusive lock on a row in a versioned table failed because the row was already versioned in some other workspace.

Action: To update/delete/insert a row that was already versioned in some other workspace, the current session must turn locking off. Consult the table's _LOCK view to see which rows in this table are locked.

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 on Workspace Manager operation with a null savepoint name parameter.

Action: User must pass in a non-null savepoint parameter for this operation to succeed

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: A user must 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 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 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. Workspace Manager does not support (except for self referential integrity constraints) such transitive referential integrity constraints.

Action: Those referential integrity constraints (except for self referential integrity constraints) for which the table to be version-enabled is the child table should be dropped before version-enabling it.

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 T, all tables that are child tables of referential integrity constraints (excluding self referential integrity constraints) that have T as the parent table, must be version-enabled.

WM_ERROR_102 cannot version enable this table

Cause: An attempt was made to version-enable a table which was the child table of a non-self referential integrity constraint with cascade option and which 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: Force option was specified while version-disabling a table which was the parent table of a referential integrity constraint.

Action: Force option cannot be specified while version-disabling a table which is the parent table of a referential integrity constraint. Commit/rollback all changes done on this table in non-LIVE workspaces and then version-disable the table without the force option.

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: User must first disable the parent table before successfully 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 which 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 which was the parent table of a referential integrity constraint with another table and the owner of the table to be version-enabled did not have select/delete privilege on the child table.

Action: Workspace Manager requires that before version-enabling the parent table of a referential integrity constraint, the parent table owner must have select and delete privileges on the child table. Grant select and delete privileges on the child table to the owner of the table being version-enabled.

WM_ERROR_107 select privilege needed on the child of constraint ('string'.'string')

Cause: An attempt was made to version-enable a table which 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 which 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 refresh operation requires ACCESS and MERGE privileges on the workspace

Cause: An attempt was made to invoke RefreshTable or RefreshWorkspace and the user did not have ACCESS/MERGE privilege on the (child) workspace.

Action: Ensure that the invoking user has ACCESS and MERGE privileges on the (child) workspace before invoking RefreshTable or RefreshWorkspace. Privileges can be granted using the GrantWorkspacePriv or the GrantSystemPriv procedures. Use the function GetPrivs to see which privileges the current user has on a workspace.

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 function GetPrivs 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/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 first before invoking RollbackResolve. (See the Resolving Conflicts section of the User Guide for details on the process of resolving conflicts for version-enabled tables.)

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: Please 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 which cannot proceed as the specified workspace has been frozen in the specified mode.

Action: Wait for the database session that holds the lock to release the lock. Refer to the User Guide for a description of the Workspace Manager operations allowed for different workspace freeze modes. Consult the xxx_WM_WORKSPACES view to see which workspaces are currently frozen.

WM_ERROR_124 workspace name may not be "BASE"

Cause: A user attempted to CreateWorkspace with the name BASE.

Action: Workspace Manager considers "BASE" to be a reserved keyword. Therefore, Workspace Manager does not allow the workspace to be named BASE. Choose another workspace name.

WM_ERROR_125 workspace name may not be "LIVE"

Cause: A user attempted to CreateWorkspace with the name LIVE.

Action: Workspace Manager considers "LIVE" to be a reserved keyword. Therefore, Workspace Manager does not allow new workspaces to be named LIVE. Choose another workspace name.

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 which 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. Refer to the User Guide for details on the freezes that Workspace Manager acquires for various workspace-wide operations. Use the xxx_WORKSPACES views to check on the current freeze status of the workspace.

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 short transactions on the table.

Action: Ensure that all open short 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 any primary key defined on it. Workspace Manager requires that a primary key exist on a version-enabled table.

Action: Add a primary key constraint on this table before version-enabling it.

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 disable version a table has failed due to the existence of short transaction locks on the table.

Action: To successfully disable version this table, verify that there are no short 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, 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. Refer to the Resolving Conflicts section of the User Guide 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 lockmode that Workspace Manager currently supports: E, or exclusive, and S, or shared. For a discussion of the differences and similarities between these two modes, refer to the Workspace Manager Guide.

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

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 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 contains only valid column names and has proper syntax. The where_clause for this Workspace Manager operation can contain only columns which 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.

Action: To successfully invoke the Workspace Manager operation on the specified workspace, ensure that there are no sessions in the workspace. Privileged users can view all the sessions in a workspace using the DBA_WORKSPACE_USERS view.

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 disable version a table failed due to the existence of short transaction locks on the table.

Action: To successfully disable version this table, verify that there are no short transaction locks on the table.

WM_ERROR_160 unable to grant/revoke appropriate privileges

Cause: An attempt to disable version a table failed due to an internal error in granting/revoking appropriate privileges on the table being version-enabled.

Action: Contact Oracle support to resolve the issue.

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 being conflict resolved. This workspace was frozen due to a user having issued a BeginResolve operation on it.

Action: To unfreeze it, issue a CommitResolve or a RollbackResolve. Only a user with WM_ADMIN_ROLE or the user who initiated the BeginResolve on the workspace can issue a Commit/Rollback Resolve for that workspace.

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 workspaces.

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 WM_ADMIN_ROLE or the owner of the workspace can unfreeze a frozen workspace.

Action: Ensure that the invoking user has the required privileges before attempting to unfreeze the workspace. Otherwise, have the owner of the workspace unfreeze it.

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 which have not already been versioned.

WM_ERROR_171 WM error: 'string'

Cause: A Workspace Manager error occurred.

Action: Refer to the Workspace Manager Guide.

WM_ERROR_172 all version enabled tables have to be disabled before uninstalling

Cause: An attempt was made to uninstall the Workspace Manager product with existing version-enabled tables.

Action: Version-disable all version-enabled tables before attempting to uninstall the workspace manager product. 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: \"%s\" 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 \"%s.%s\" 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 \"%s.%s\" 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 \"%s.%s\" 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 28000 characters defined on it.

Action: Ensure that all user defined triggers on the table to be version-enabled have trigger body lengths that are less than 28000 characters.

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 and/or rename some of the table's columns to reduce the sum of the column name lengths.

WM_ERROR_180 table \"%s.%s\" 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 with the 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.